Published Updated

A supplier invoices 100 units, but the purchasing system shows only 90 received. The accounts payable team needs the invoice, delivery evidence, and the right person's decision before the discrepancy can be resolved. Which system should hold the evidence, and which should update the financial transaction?
Connect the invoice file to the payment process, with a named owner for each decision. Document management keeps the invoice and supporting records controlled and traceable. Accounts payable (AP) automation handles the configured invoice-processing steps. The enterprise resource planning (ERP) system maintains the accounting records and payment status in the architecture described here.
These responsibilities can overlap. For example, Dynamics 365 Finance documents invoice matching, workflow submission, and posting automation in the finance platform itself. Decide what your existing system already handles and where a connected document workflow adds value, especially for evidence and reviews spanning several systems.
The PDF, the processing task, and the accounting entry describe the same business event. They serve different purposes, and a status change in one should have an explicit meaning in the others.
The received document, attachments, later corrections, delivery evidence, and review history. This explains what arrived and why someone accepted or challenged it.
Extraction, supplier checks, matching, approval routing, and exception handling in the configured AP and document workflows. This explains what needs attention next.
The accepted financial entry, posting reference, and payment or reversal status in the designated finance system. This explains what was recorded and paid.
Assign ownership explicitly for your deployment. A field extracted from a supplier's invoice is a proposal until the appropriate checks accept it; an approved document is not itself proof that the invoice has been posted or paid.
| Information | Primary authority |
|---|---|
| Received invoice bytes and attachments | Document repository, with checksum, source, received time, and accepted version. |
| Extracted invoice fields | Proposed processing result until validated against source and business rules. |
| Supplier, PO, receipt, tax, account | ERP or procurement source of truth. |
| Exception and approval evidence | Governed workflow linked to the ERP exception and invoice version. |
| Posting and payment | ERP, with transaction and status references returned to the document file. |
Record source, checksum, attachments, received time, supplier claim, and extraction run.
Match vendor, PO, receipt, currency, totals, tax, and duplicate indicators with ERP data.
Track the integration request and destination response, then link the accepted transaction or unresolved exception to the invoice file.
Use the receiving legal entity, supplier identity, invoice reference, and your duplicate-detection rules to identify an invoice; the printed invoice number alone may repeat across suppliers. Give each integration operation a stable reference. Use destination-supported duplicate protection where available, and reconcile an uncertain outcome before resubmitting a request.
A three-way match compares the invoice with the purchase order (PO) and goods receipt under the configured tolerances. Microsoft's invoice-matching guidance describes those comparisons. The following fictional case uses an invoice for 100 units, a PO for 100, and a recorded receipt for 90.
The document workflow retains invoice INV-00088, its attachments, and the extracted proposal. The AP system finds the receipt discrepancy. The exception links to the exact invoice version, supplier, PO, and receipt reference.
The warehouse confirms that all 100 units arrived and provides the delivery note. The authorised receiving team checks that evidence and records the missing 10 units in the purchasing system. Uploading the note or approving its document review does not itself change the receipt.
The AP system reruns matching and the required approval rules against the updated receipt. Once those checks pass, the designated finance system posts the invoice. The invoice file receives the accepted transaction reference and keeps the delivery note and review decision.
A later payment update adds its reference and status to the connected view. If a posting response is lost, the integration queries or reconciles the original operation before trying again. A corrected invoice or reversal keeps its relationship to the earlier record.
If the missing units have not arrived, the exception remains open for the appropriate resolution. The workflow should preserve that distinction instead of changing a receipt merely to make the invoice match.
When a corrected scan replaces an invoice, the OCR reprocessing guide follows the new source through extraction, field validation, search and AI updates, including late results and partial failures.
The invoice file explains what arrived and how an exception was resolved. The AP process applies the agreed processing and approval rules, and the finance system records postings and payments. Connect these views with stable references and explicit statuses so a reviewer can explain both the evidence and the financial outcome.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.