Every supplier invoice, matched to its accrual.
An Andor and Shypple collaboration: accrual invoice matching and investigation for Shypple’s finance team.
Each invoice is read, coded to the general ledger and matched to the accrual on its job. Where invoice and accrual disagree, Jev and large language models investigate and close the gap, or hand a person the one decision left.
PDF in, outcome out, with the reason written down.
-
Read
A language model reads the PDF: supplier, invoice number, job references, every charge line, totals and VAT.
-
Code
Each line is coded to Shypple’s general ledger, with Jev choosing among the codes that supplier is known to use.
-
Match
Supplier and job references (SF, AF, RF, bill of lading, booking, container) pull the open accruals; lines pair to them on charge and amount.
-
Investigate
Jev answers typed questions about each pairing. Rules turn the answers and the amounts into an outcome with a written reason.
Three outcomes
Approved
Matched, and the total sits within tolerance of what was accrued.
Needs review
Matched, with one thing a person must settle: a variance, VAT, a duplicate, an overdrawn accrual.
No accrual to match against
The supplier or the job has no open accrual on the book yet.
The gaps between an invoice and its accrual.
Most invoices match. The ones that do not fall into a short list of reasons, and each reason has a place to land.
- Wrong supplier
The charge was accrued under another supplier, or under none. The invoice is held next to the accrual it should have drawn on.
Needs review
- Missing job reference
No SF, AF, RF, bill of lading, booking or container number the accrual book knows. There is nothing to match until the job is found.
No accrual to match against
- Amount over accrual
The total or a line lands outside the euro tolerance of what was accrued, or two invoices together draw more than one accrual holds.
Needs review
- VAT on the invoice
Shypple books net. An invoice carrying VAT is held for correction, whatever the match says.
Needs review
- Duplicate
Same supplier and invoice number as a document already received. Held so it is never paid twice.
Needs review
- No accrual
Supplier and job are known, but no open accrual for that supplier sits on the job.
No accrual to match against
Language models read the paper. Jev makes the calls.
Reading
A large language model reads each PDF the way a clerk would: letterhead, references, charge lines, totals, VAT. It extracts. It does not decide anything about money.
Deciding
Jev answers narrow, typed questions with a probability: is this the supplier on the accrual, does this charge belong to this job, which GL code fits. Code combines those answers with the amounts. A doubtful answer can move an invoice to review, never to approved.
Every outcome carries its reason in plain words, the accruals it drew on and the Jev answers behind it, so a review starts from the evidence.