Invoice Matching
Checks every invoice against the order it came from and the goods that actually arrived.
Accounts payable opens invoices one at a time and compares each against a purchase order and a receipt. That is an afternoon somebody loses every week, and it is the kind of attention that fades by the fortieth document. The concept does the comparison on every invoice, queues the ones that agree, and holds back the ones that do not with the disagreement written out in full. It would never pay anything and never approve anything. None of it is built yet.
Availability
In Development. Specified, and not built. The run below is the shape the job would take, not a recording of one. Nothing of it runs today, so it cannot be subscribed to and carries no price.
Intended user
An accounts payable clerk or a bookkeeper opening every invoice by hand against an order and a receipt.
Monthly price
Not purchasable. No price, and no subscribe button until it runs.
Nothing here runs yet, so there is no Subscribe and no Run on this page. Asking for it is what decides which of the five gets built first, and a close variation of it can be quoted as a custom build today.
What this is not.
The corrections worth making before anything else on this page is read, because each one is a thing a reader could reasonably assume and would be wrong about.
- This is purchase-order reconciliation. It is not the Bill Difference Checker, which compares two versions of the same supplier bill — a different job, a different buyer, and a different answer. Neither one substitutes for the other.
- It never pays, never approves and never posts. Holding an invoice back is the end of what it would do on its own.
- No accounting system is named here and none is integrated, because nothing has been built to integrate with one.
How the job would go.
Four steps, in order, ending where it stops. No timing is published for any of them: nothing has run, so there is nothing to measure, and a written duration shown as a measurement would be an invention.
Invoice Matching, start to finish
Illustrative- Opens the invoices in the batch
- Matches each to a purchase order and a receipt
- Holds back the ones that do not line up
- Queues the rest for your approval
Illustrative. The steps are written for this page to show the shape of the job, and none of it is a recording.
What would land when it finishes.
A queue of matched invoices, and an exceptions list naming what disagreed on each one it held.
| Invoice | Supplier | What disagreed |
|---|---|---|
| INV-4471 | Fenwick Supply | Billed 120 units, receipt shows 96 |
| INV-4488 | Arden Freight | No purchase order found |
| INV-4502 | Northgate Print | Unit price 14.50, order says 12.75 |
The other 39 would be queued for approval, unchanged. The suppliers, the numbers and the batch are written for this page.
Illustrative. These rows are written for this page and are never a customer’s data.
Supported inputs
Kinds of source, from accounts you would connect in your own Tools workspace. Which account, and the credential behind it, are yours and never appear anywhere on this site. No named integration is listed, because none has been built.
- Invoice documents
- Purchase order export
- Goods receipt records
Output
A queue of matched invoices, and an exceptions list naming what disagreed on each one it held.
IllustrativeApproval boundary
Approve the 39 and hold the 3?
Reading, checking and comparing change nothing outside your workspace and would happen on their own. Anything that cannot be taken back waits for you, and what it is asking about is shown in full rather than summarised.
Invoice Matching is in development.
It is specified and not built. Billing does not exist yet and the usage allowance has not been measured, so there is nothing to subscribe to and no price to show. Asking for it is what decides what gets built next; a close variation of it can be quoted as a custom build today, against acceptance cases you write.
The rest of the catalogue.
- Month-End CloseFinanceClears the accounts that reconcile at month end and writes the first draft of the close narrative.
- Incident TriageEngineeringTurns a night of alerts into a short list of grouped incidents, each with somewhere to look first.
- Review Before MergeEngineeringReads a change the way a careful colleague would, before anybody is asked to approve it.
- Idle Cloud SpendEngineeringFlags cloud resources with no recorded activity, works out who owns each one, and estimates what stopping it would save.