What should invoice processing automation actually deliver?
A useful invoice workflow ends with an employee able to make a decision without searching the inbox, accounting system and purchase-order folder. Extracting a total is only one step. The system also needs to identify the supplier, look for an existing bill, compare the relevant order and explain what remains unresolved.
The process below prepares supplier invoices for accounts-payable review. It does not collect payments from customers or authorize supplier payments. The sample records are fictional, and the checks are a proposed operating design rather than results from a customer deployment. Product documentation was checked on October 10, 2026.
1. Keep the original and give each arrival a reference
Choose an approved invoice inbox or upload channel. Save the original attachment in access-controlled storage and record its arrival time, sender, file reference and processing status. Keep a link to the original throughout the workflow so a reviewer can check a number against the document that supplied it.
Give the arrival its own reference before extracting fields. If the same email event arrives twice, resume that record instead of starting another review. An identical file arriving through another channel should become a possible duplicate to investigate. A revised invoice is a new version to compare, not a reason to silently replace the evidence behind an earlier decision.
2. Extract fields without turning guesses into facts
Microsoft's Document Intelligence invoice model documents extraction of invoice fields and line items into structured output. Its confidence guidance also explains that not every field has a confidence score. Extraction can prepare data for checking; it does not establish that an invoice is genuine or payable.
Map the fields your process requires: supplier, invoice number, invoice date, due date, currency, purchase-order reference, line descriptions, quantities, prices, subtotal, tax and total. Preserve missing values as missing. Show uncertain readings beside the source rather than completing an invoice number from context.
Choose review rules using representative documents from your business. An unreadable invoice number should stop matching even if the total looks clear. Do not translate a model's confidence score into a promised business accuracy rate. Your pilot needs its own observed corrections and failure cases.
3. Separate duplicate checks from order checks
Match the supplier to an existing approved supplier record. A display name alone may be ambiguous. Then compare the supplier reference and invoice number with existing records, retaining the original text when you normalize spaces or capitalization. Use date, currency and amount as additional evidence when an invoice number is absent or inconsistent.
A match is a reason to inspect the existing bill, not automatically delete the new arrival. It could be a resend, a corrected invoice or an unrelated document with a reused number. Likewise, finding no match in an unavailable accounting system is not proof that the invoice is new.
For the order check, compare the invoiced lines with the relevant purchase order and available receiving evidence. Include prior partial invoices when checking quantities. An approved order does not prove that everything arrived. Intuit documents linking full or partial purchase orders to bills or expenses in QuickBooks Online; the documented purchase-order feature requires Plus or Advanced. Verify the account plan and supported integration actions before promising that connection.
4. Hand over a complete review packet
Here is one illustrative packet for a fictional equipment invoice. These are designed example values, not output from a tested extraction service. The reviewer can see both the reason for the hold and the action needed to resolve it.
- Record: SAMPLE-AP-014. Original file: invoice-SAMPLE-884.pdf in the approved invoice folder; page 1 contains the line and total. Received: October 10, 2026, 09:14 Eastern. Owner: accounts-payable coordinator.
- Supplier and invoice: Sample Equipment Supplier, approved supplier reference SUP-SAMPLE-07. Invoice SAMPLE-884, dated October 9; due November 8. Currency: USD. Purchase order: PO-SAMPLE-204.
- Extracted amounts: 12 units at $100 each; subtotal $1,200; tax shown as $96; total $1,296. Arithmetic check: $1,200 plus $96 equals $1,296. This check does not establish that the tax treatment is correct.
- Order comparison: PO-SAMPLE-204 authorizes 10 units at $100. Invoice quantity exceeds that order by 2 units, or $200 before tax. No receiving confirmation is attached. Check amendments and earlier partial bills before deciding what is payable.
- Duplicate result: an existing review record has the same supplier and invoice number. Its source and status must be inspected. This is a possible duplicate, not a confirmed duplicate payment.
- Required decision: hold for employee review. Confirm whether the new file corrects the existing invoice, resolve the quantity difference and obtain receiving evidence. Accounting write: not attempted. Payment approval: not requested. Payment: not initiated.
5. Record a decision before moving the bill forward
Assign an approver according to the business's existing authority rules. Show the source, comparison and open questions in the request. Record the reviewer, decision time, comments and the exact document version reviewed. A corrected amount or replacement file should return to review under the agreed policy.
Microsoft distinguishes creating an approval request from waiting for its outcome: Create an approval does not block the flow, while Start and wait for an approval waits for the approval criteria or a timeout. Sending a notification is therefore separate from receiving a decision. Licensing, permissions and environment setup still need checking for a particular implementation.
Define the allowed step after each outcome. Approval might permit an authorized employee to post the bill; rejection sends it back with a reason. An expired request stays unresolved and is reassigned. Silence never becomes payment approval. Keep payment release in the business's separate authorized process, including its existing banking and supplier-change checks.
6. Make failed connections visible and safe to resume
Use clear states such as received, needs a better document, waiting for an accounting check, awaiting employee review and posted. Show the last confirmed step and the next owner. If the accounting connection is down, keep duplicate status unknown and queue the check; do not mark it clear just to finish the automation.
After an ambiguous write timeout, check the accounting destination for the intended record before trying again. Save the returned accounting reference only after confirmation. Replaying the same arrival must not create a second bill or a fresh approval for an already reviewed version.
Limit access to invoice files and credentials, set retention with the business and record who can change supplier information. A request to change payment details should go through the existing independent verification process. The invoice-reading workflow should not update bank details simply because they appear in an attachment.
7. Test the handoff, not just the extraction
Before connecting production records, use an agreed sample set with the accounts-payable owner. Include clean invoices, poor scans, partial deliveries and corrected documents. Inspect the resulting packet and receiving system. The following cases describe acceptance checks to run, not tests Monchera has performed for your business.
- Resend the same email and file: the existing arrival is recognized, with no second bill or approval request.
- Use the same invoice number for two different suppliers: supplier identity keeps the records separate; an ambiguous supplier match remains held.
- Submit a corrected version and a partial-delivery invoice: the reviewer sees the earlier record, changed fields and relevant order quantities.
- Remove the order reference or make the total unreadable: the packet names the missing evidence and assigns the next action without inventing a value.
- Simulate an accounting outage or uncertain write result: the item remains unresolved until the destination is checked, with no blind duplicate write.
- Reject or let an approval expire: no bill-posting or payment step treats the missing approval as permission.
What to bring to an invoice automation scoping call
Bring anonymized examples of a normal invoice, a duplicate, an order mismatch and a corrected invoice. Identify the accounting system, available purchase orders and receiving records, monthly volume, current approvers and the person who handles exceptions. Confirm which actions the integration may perform and which must stay with employees.
Measure the current waiting time, manual touches, corrections and unresolved items before a pilot. Afterward, compare those measures alongside reviewer workload and operating cost. A faster extraction step is not enough if employees still reconstruct the packet or chase missing approvals.
Monchera can scope the intake, checks, employee handoff and ongoing monitoring around your existing tools. Start with one supplier-invoice process and a clearly defined review packet, then decide which connections and maintenance responsibilities the implementation needs.
