Invoice AI: match orders and receipts before payment review
After AI reads an invoice, match orders and receipts and hold lines without receipt evidence for a person’s review.
Key points
- Separate reading from receipt checks
- Match the receipts for this invoice
- Hold for a person’s evidence check
Overview diagram in preparation
Contents
Separate reading checks from receipt checks
A&A perspective
Invoice matching means comparing an invoice with purchase orders and goods receipt records to investigate differences. Even if AI reads an invoice correctly, a line without evidence of receipt stays on hold until a person checks it. This is a proposed process for purchases that proceed to payment review after the goods arrive.
Hypothetical example
Imagine a small wholesaler using AI to transcribe invoices. An invoice says 100 parts, and AI correctly reads 100. Only 60 parts have arrived. In this hypothetical example, the reading is accurate but receipt of the remaining 40 parts has not been confirmed.
From the sources
Microsoft’s business management product Dynamics 365 Finance includes an Invoice capture feature.
From the sources
Its documentation describes configurable warnings and errors based on recognition confidence, along with conditions for human review.
From the sources
The page warns that some or all of the described functionality is at a trial availability stage and may change. It describes invoice capture and transfer settings.
A&A perspective
High recognition confidence is not evidence that goods arrived.
A&A perspective
In the approach proposed here by Automate & Augment (A&A), reading checks and receipt checks are separate stages. Adopting Microsoft’s product is not a prerequisite.
Hypothetical example
A small company could place purchase order and receipt references next to the fields used to check the original invoice and extracted values.
Hypothetical example
A receipt record documents when goods arrived, which items were received and their quantities. AI could gather the values and references and identify missing evidence.
A&A perspective
Tightening confidence settings does not create receipt records.
A&A perspective
Separating improvements to reading accuracy from access to the receiving team’s records makes it clearer which problem needs attention. This documentation alone does not establish a recommended confidence threshold or expected savings.
Match the receipts linked to this invoice
A&A perspective
For a partial delivery, compare the invoiced quantity with the receipt records corresponding to this invoice.
A&A perspective
The total ordered quantity does not show how much arrived. Even for the same item, exclude receipts for other orders and do not count quantities already matched to earlier invoices again. The unused remainder of the same receipt can be used if its link to the current invoice is traceable in the records.
From the sources
Microsoft’s accounts payable documentation describes comparing invoice prices with purchase order prices. A further method adds a quantity comparison between the invoice and its corresponding product receipts. The latter is three-way matching.
Hypothetical example
In the hypothetical example, an order for 100, an invoice for 100 and corresponding receipts for 60 leave a difference of 40.
Hypothetical example
Even if the price matches the order, all 100 are not treated as received. The receiving team needs to establish whether the remainder arrived, rather than whether AI read 100 correctly.
Hypothetical example
For the same order of 100, an invoice for 60 with corresponding receipts for 60 matches on quantity for this invoice. Receipt of the remaining 40 is tracked separately. This quantity comparison does not establish that the price or other conditions have also been checked.
A&A perspective
If no receipt record can be found, leave the received quantity unconfirmed rather than entering zero.
A&A perspective
Goods that have not arrived and goods that arrived without a record require different follow-up. Do not rewrite the invoice quantity to match the received quantity; preserve the original value and show the difference.
Hypothetical example
A matching sheet could identify the item and purchase order line, then show the invoiced, ordered and corresponding received quantities.
Hypothetical example
Different units, such as individual items and boxes, do not match merely because their numbers are equal. If a receipt cannot be linked to a line, the proposed process holds it for review instead of letting AI guess the link.
From the sources
Microsoft also describes saving an invoice with a quantity difference and matching it to another receipt later. Tolerated differences and review responsibilities depend on product configuration and company procedures.
| Order, invoice and linked receipts | What remains unresolved | Reviewer and evidence |
|---|---|---|
| Ordered 100; invoiced 100; received 60 | Receipt of the difference of 40 is unconfirmed | Receiving staff check receiving records; the invoice handler contacts the supplier if goods have not arrived |
| Ordered 100; invoiced 60; received 60 | This invoice matches on quantity; track the remaining 40 separately | Accounting checks price and other conditions; quantity matching alone does not authorize payment |
| Ordered 100; invoiced 100; no receipt record | Received quantity is unconfirmed, not zero | Receiving staff check goods and receiving evidence; document the basis for any record correction |
A person releases holds after checking evidence
A&A perspective
Decide who can release a hold and which records that person must check. AI reads values and shows differences; a person investigates missing evidence. A generic “needs review” label does not say whether accounting or the receiving team should act.
Hypothetical example
The proposed sheet also names the person investigating the difference and records the evidence used to release the hold.
Hypothetical example
One possible division of work gives the receiving team responsibility for physical goods and receiving records, and the invoice handler responsibility for supplier inquiries. Record who returned the line to payment review, and do not let AI release the hold itself.
Hypothetical example
Suppose the remaining 40 items did arrive, but their receipt was entered late.
Hypothetical example
A person checks the receiving evidence, corrects the receipt record and runs matching again. Preserve both the original absence of a record and the basis for the correction. Repeating invoice extraction alone will not fill this gap.
Hypothetical example
If the goods really have not arrived, the accounting handler can contact the supplier and await the necessary response, such as an invoice correction or delivery schedule. The company’s transaction terms determine which response allows processing to resume. An AI prediction that the goods will probably arrive is not receipt evidence.
A&A perspective
For holds approaching a payment deadline, put the review deadline and contact on the same row so a person can make a timely decision. A processing hold does not change payment obligations or contractual deadlines. Purchases with agreed advance payment need a separate process from the after-receipt review described here.
Hypothetical example
To test this proposal, use normally received lines, partial deliveries and lines without receipt records, and compare the results with a person’s checks.
Hypothetical example
Record both lines that passed without confirmed receipt and lines unnecessarily held. Include review time and the effort of correcting records when deciding whether the process is workable.
A&A perspective
The two references are product documentation from the same provider, not measured results for this matching sheet.
A&A perspective
Checking completion of services, tax treatment and bank payment authorization are outside this article’s scope. Matching received quantities does not, by itself, authorize a transfer.
Separate reading, matching and hold release
A&A perspective
Confirming that an invoice was read correctly still leaves receipt of the goods to be established separately.
A&A perspective
For partial deliveries, select the receipts corresponding to the invoice and compare quantities. If the record is missing, leave receipt unconfirmed.
A&A perspective
A person releases the hold after checking the evidence. Keep quantity matching separate from final bank payment authorization.
Confirming that an invoice was read correctly still leaves receipt of the goods to be established separately. For partial deliveries, select the receipts corresponding to the invoice and compare quantities. If the record is missing, leave receipt unconfirmed. A person releases the hold after checking the evidence. Keep quantity matching separate from final bank payment authorization.
FAQ
Does a person have to reread every invoice even when the AI values are correct?
Decide reading checks separately from order and receipt matching. This proposal does not require every line to be reread. It calls for evidence of receipt from separate records even when AI’s extracted values are accurate.
Can we delay payment until goods arrive if a receipt record is missing?
This article cannot decide that. A missing record does not establish non-delivery, and advance payment may have been agreed. A person must check actual receipt and transaction terms and decide separately how to handle the payment deadline.
Do we need dedicated business management software for this?
The approach can be used in a spreadsheet if invoices, orders and receipts can be linked at line level and the original records and reviewer remain traceable. Include the effort of keeping those records current when deciding whether to adopt it.
Sources & editorial note
Primary pages read for this article. Publication dates below belong to the sources; access dates record our research.
- Invoice capture solution advanced settings
Microsoft Learn · Updated 2026-10-05
Accessed 2026-11-01 - Accounts payable invoice matching overview
Microsoft Learn · Updated 2025-05-15
Accessed 2026-11-01