Routing Extracted Invoices for Review and Accounting Handoff
Build an invoice workflow that routes extraction exceptions to AP and sends only verified, approved records to accounting.

After an invoice has been captured, the next step is not to post its extracted values. Define what accounting needs, check the invoice against that contract, and route anything missing, uncertain or mismatched to an AP reviewer. Only a verified and approved record should enter the accounting handoff; a failed handoff needs its own visible status so a retry cannot quietly create a second record.
Start with the handoff contract
Before building conditions in Power Automate, agree on the destination’s required fields and the person or role allowed to approve posting. For one illustrative workflow, the contract is invoice ID, supplier, invoice date, total amount, currency and, for a PO invoice, PO reference. Keep a reference to the original PDF alongside those values. The destination may require other fields; map them before deciding an invoice is complete.
Specify what verified means for each field. For example, AP might require the invoice ID, supplier, date, total and currency to agree with the source invoice; the PO reference must also identify the intended order. Record who checked any correction and who approved the invoice. Approval is a separate decision from extraction: a plausible total is not authorization to post it.
Capture once, then apply invoice-specific gates
Suppose invoices arrive as PDFs through a designated intake channel. Retain the original under a stable source reference, then pass the file to AI Builder invoice processing in a Power Automate flow. Microsoft says the prebuilt model recognizes common elements including invoice ID, date and amount due. Its documented inputs are JPEG, PNG or PDF, with a 20 MB maximum; Microsoft recommends one clear photo or scan per invoice for best results. Those constraints belong at intake, before a file reaches the review queue. Microsoft’s invoice-processing documentation describes the model and input guidance, not an approval or accounting-posting guarantee.
Run the extracted values through four gates in order:
- Completeness: Is every field required by the handoff contract present? An empty currency or PO reference on an invoice that requires one goes to AP, not accounting.
- Suspected duplicate: Compare the invoice’s supplier and invoice ID with the team’s existing intake and destination records. Treat a match as a review reason, not an automatic deletion: AP must determine whether it is a repeat submission, a correction or a genuinely different invoice.
- Extraction uncertainty: If a consequential value such as the total has low confidence, show AP the source and extracted value. Microsoft gives an example in which an invoice-total confidence score below 0.65 triggers a custom document-processing model. That is an example branch, not a universal acceptance threshold. Set a review rule appropriate to this workflow rather than treating 0.65 as proof of correctness.
- PO match: For a PO invoice, compare it with the purchase order. If the business requires a receiving check, compare invoice line items with the receiving report too. These are commonly called two-way and three-way matching, respectively. Route differences beyond the company’s defined tolerances to AP for resolution. The AP matching explanation distinguishes the two checks and describes tolerance-based exceptions.
These gates answer different questions. A complete invoice can still be a duplicate; a high-confidence total can still disagree with the PO. Do not collapse them into one “AI passed” flag.
Make review and approval explicit
Give the AP reviewer one exception item containing the original invoice reference, extracted and mapped values, the failed gate, and the relevant comparison value—for example, “invoice total differs from PO total.” The reviewer should be able to record a corrected value, a reason for the decision and whether the item is approved or remains unresolved. If a value changes, run the affected checks again before asking for approval. A corrected value is not yet an approved value.
This is an illustrative flow design, not a list of verified Power Automate action names or a claim that a particular accounting integration exists:
PDF intake → retain original and assign source reference
→ AI Builder invoice processing
→ required fields present?
→ suspected duplicate?
→ total confidence needs review?
→ if PO invoice: PO match and, if required, receiving match?
Any failed gate → AP exception with source, values and reason
→ correction → recheck affected gates → approval decision
All gates pass → approval decision
Approved only → verified accounting handoff → record destination ID or error
The approval gate applies to both the clean path and the resolved-exception path. An unresolved item stays in review. An item rejected by an approver stays out of the handoff, even if every extracted field was correct.
Transfer, then reconcile the handoff
Choose and verify an integration with the accounting destination before implementing the final step. Map the approved fields to a draft record rather than assuming the extraction flow itself is authorized to post a payable. The table below is a design example; its generic destination fields are not documented names for any accounting product.
| Verified workflow value | Generic destination field or handoff record | Required handoff result |
|---|---|---|
| Invoice ID, supplier | Invoice number, supplier reference | Preserve both identifiers |
| Invoice date, total, currency | Invoice date, total, currency | Send approved values |
| PO reference, when applicable | Purchase-order reference | Send the verified match |
| Original PDF reference | Source-document reference, or retained handoff record | Keep a route back to the source |
| Approval decision and handoff attempt | Handoff record | Store approval, status and any error |
| Successful draft creation | Destination record ID in handoff record | Mark transferred only when the ID is known |
Treat an uncertain handoff response as an unresolved state, not permission to create another draft. Before retrying, reconcile using the stable source reference and invoice identifiers against the destination if the verified integration supports that check. If it does not, require a person to resolve whether a record was created. Retain the error and attempt history until the destination ID or a confirmed failure is recorded.
For a hypothetical PO invoice from North Star Supplies, imagine the PDF states invoice NS-104, USD 1,200, and PO PO-27. If the required fields are verified, no existing invoice is suspected, the total-confidence check does not require review, and the invoice agrees with the PO and any required receiving report within the company’s tolerances, it reaches approval with its PDF reference and mapped values intact. An approver’s acceptance then permits a draft handoff; the recorded destination ID closes the transfer.
Now suppose the same PDF says USD 1,250 while the relevant PO comparison is USD 1,200, beyond this company’s tolerance. AP receives the PDF, both amounts and the mismatch reason. It remains out of accounting while AP resolves the discrepancy; any replacement or correction must pass the checks and approval again. That separation is the point of the workflow: extraction starts the process, but verified facts, a named approval decision and a reconciled handoff finish it.
