Sixlinked

Demos / Payables

Sixlinked demoDocuments

Invoices in as PDFs. Checked, or held for a person.

An accounts desk tool that reads supplier invoice PDFs and checks them against purchase orders and arithmetic. It shows where on the page each value came from. Anything doubtful is held for a person to approve.

Made-up business
Harbour Lane Provisions
Staff in the film
Ruth Okafor, Accounts
Recorded
21 November 2026
The 40 second film, 0:40

What we measured.

60 of 60invoices had every field read right
20 of 20planted problems were caught and held for a person
0 of 40clean invoices were wrongly held
0 of 60invoices were posted without a person, counted from the ledger table
0 of 4planted instructions in invoice notes changed an outcome

Where it missed.

No misses in this run. That is one small test on made-up data, so read what it does not show.

What it does not show

  • All invoices are invented, text PDFs generated for this test in seven layouts. Scans, photos, handwriting and real supplier paperwork are not tested.
  • The generator and the checks were written by the same builder, so the test set is likely easier than real paperwork. A clean score here does not predict a clean score on yours.
  • One machine, one run, one model. Purchase orders and the ledger are small invented tables.
  • Query supplier writes a draft to a local outbox and sends nothing.

What staff see.

Screens from the recording. Scroll sideways, or use the arrow keys.

  1. The invoice page with every value the reader found outlined in amber, beside the list of checks, all ticked.
    1Each value is outlined where it was read
  2. A confirmation that Ruth Okafor approved the invoice and it was posted to the ledger.
    2A person approves, then it posts
  3. An invoice held because a line price of 17.76 dollars differs from 14.80 dollars on the purchase order, with the price marked on the page.
    3A price that differs from the purchase order is held
  4. The Query supplier button and a note that a draft was written and nothing was sent.
    4Query supplier writes a draft only
  5. An invoice held as a duplicate because the same supplier already has that invoice number.
    5A repeated invoice number is held

How it was built and tested.

  1. About 70 invented invoice PDFs were made by a seeded generator in seven layouts, kept apart from the reader, with the true answer for each saved in files the reader never sees.
  2. The reader pulls the text and word positions from each PDF with code, makes one model launch per invoice to turn the text into fields, then finds each value on the page and runs the checks in code.
  3. Anything that fails a check is held for a person with the reason and the marked region. Only a click on Approve writes to the ledger table; the model has no path to it.
  4. A suite of 60 invoices not used in development was frozen and committed before scoring. 20 carried one planted problem and 4 carried a planted instruction in the notes.
  5. The session was recorded by a script driving the running app in a real browser. Median read time was 6.1 seconds per invoice.

About this recording

Waits were shortened by a fixed rule and the camera zooms into the page; clicks were scripted and every read, check and ledger row is what the software did.

Recorded
21 November 2026
Model
Claude Sonnet 5
Model runs behind it
71 in total, across building and testing
Real time of the session
43 seconds over 4 steps

Talk about a job like thisAbout this job

Let's talk

Want a Documents job like this?

Tell us what the work is today, who does it, and who should decide when something is doubtful.

You will get a reply by email from Matthew, the engineer who would do the work.

Your enquiry goes straight to our inbox. We use your details only to reply to you. Privacy

Send an enquiry

Sending an enquiry needs JavaScript. You can also email hello@sixlinked.com.