Incoming invoices · Accounts payable workflows
A readable PDF is only the beginning. Someone still has to identify the vendor, check the purchase, find the right approver and confirm that accounting received the bill. ALCA designs invoice processing around those handoffs, with a visible queue for anything that needs a person’s judgment.
Follow the example workflowWhere work stalls
An attachment gets forwarded to three people, but nobody can tell whether it is new, already under review or already recorded. Assign an intake identity, retain the original file and record who owns the next step. A forwarded copy must not become another payable.
A clear total does not prove that the vendor is correct, the goods were received or the job is open. Check extracted fields against authorized vendor, purchase, receipt and project records. Make unresolved matches visible instead of choosing the nearest name.
An email saying “looks good” may refer to an older attachment or an amount before a correction. Tie authorization to the invoice version, matched evidence and permitted action, so a material revision sends the request back through the right decision.
A timeout can occur after the accounting system accepted a write. A second create request can duplicate the bill. Keep the destination identifier, check uncertain outcomes and reconcile the accepted fields before the item leaves the queue.
Input → decision → confirmed result
Capture an authorized inbox attachment or upload. Store the original, source reference, received time and file fingerprint; separate invoices from statements, credit notes and unrelated documents.
Read vendor details, invoice number/date, currency, totals, tax and line items. Keep field-level confidence and the supporting document region so a reviewer can inspect the source.
Match the legal vendor, PO, receipts and job or project. Check arithmetic, allowed tolerances, coding and possible duplicates before selecting an approval route.
Send uncertainty to a named reviewer with the original and failed checks side by side. Record corrections and their reason; run validation again after a change.
Apply the company’s authorization policy to the validated invoice. Record the approver, evidence and rule version. Material changes invalidate affected approvals.
Create the allowed Bill or ERP payable, retain its destination ID and read back the agreed fields. Archive evidence and reconciliation status. Payment authorization remains a separate control.
At the decision gate
Low extraction confidence, ambiguous vendor, missing receipt or a totals mismatch pauses progression. A person resolves the specific issue; a high confidence score never overrides a failed business rule.
High-confidence fields may continue automatically through validation. Passing checks makes a record eligible for the configured approval policy; it does not silently approve a payment or guarantee the document is genuine.
Hold the record with a reason and owner. Keep suspected duplicates available for comparison. An authorized reviewer can distinguish a re-send from a legitimate recurring bill, with evidence for the decision.
Records & business rules
Consider an illustrative contractor buying materials for a job. The vendor invoice, PO and receipt are separate records with separate owners. A $12,480 invoice against a $12,000 PO needs a policy decision about the difference; extraction confidence says nothing about whether the extra charge is authorized. No example amount or threshold here comes from an ALCA client.
| Record / evidence | Check | Decision owner | Allowed next step |
|---|---|---|---|
| Vendor + invoice identity | Match company, vendor ID, normalized invoice number and currency; compare dates, totals and file fingerprints for likely duplicates. | AP reviewer resolves uncertain identity and duplicate candidates. | Continue with one stable internal invoice ID; never merge solely by a similar name. |
| PO, receipt + line items | Compare quantities, prices, tax and any agreed tolerances. Distinguish partial receipt from a missing receipt. | Buyer or receiving owner confirms exceptions; AP records the result. | Route the supported amount/version for approval or hold for missing evidence. |
| Job / project + coding | Check job identity, status, allowed cost code and the legal entity that incurred the expense. | Project and accounting owners agree mappings. | Prepare account-specific Bill lines; a text job name is not a verified accounting reference. |
| Approved invoice → payable | Confirm current version, authorized approver, destination company and one permitted write. | Accounting owns posting policy and reconciliation. | Store destination ID, read back fields and mark COMPLETE only after confirmation. |
On smaller screens, swipe the table or focus it and use the arrow keys.
An incoming vendor invoice normally becomes a QuickBooks Online Bill: an accounts-payable transaction. A QuickBooks Invoice is a customer receivable. Confirm the legal entity, vendor, account/item references and permitted tax treatment with the accounting owner; do not send supplier documents into the wrong object because both are called invoices.
Rent, service fees and other non-PO bills cannot pass a PO test that does not apply. Define required evidence, coding and approvers for that route. Credit notes, deposits, currency differences and amended invoices also need explicit handling instead of being forced through a purchase-order match.
The workflow records who approved which version and for which action. A successful Bill creation confirms a payable record, not a released payment. Payment files, bank-detail changes and money movement require separately scoped permissions and controls.
Show the original next to extracted fields, matching evidence and the precise failed rule. Capture before/after values, reason, reviewer and time. The audit record links intake, document revision, validation, approval and destination confirmation without copying sensitive payloads into every log.
When the normal path breaks
Hold the invoice and ask the designated vendor-data owner to verify the supplier. Do not automatically create a vendor or replace bank details from the PDF. Resume only after the approved vendor record and mapping are available.
Route the item to purchasing or receiving with a due date and visible owner. If the invoice is legitimately non-PO, move it through that approved route. Missing evidence is a reason to pause, not to bypass the control.
A file hash catches identical files; vendor and invoice references help catch re-scans and forwarded copies. Compare legitimate recurring bills carefully. Store the reviewer’s resolution so the same suspect document is not endlessly reopened.
Keep the source visible and ask a reviewer to correct the uncertain field or challenge the supplier. Recalculate dependent totals and rerun matching. A corrected amount may require a different approval level and must not retain a stale authorization.
Queue temporary failures with retry limits and respect the vendor’s rate guidance. If a create request timed out, first determine whether the Bill already exists using supported identifiers and read-back. Do not blindly create it again.
Compare the destination company, vendor, totals and agreed line mappings against the intended record. Route differences to accounting with the destination ID. An authorized correction follows a documented process; the integration should not silently edit a closed period.
Access & accountability
Use supported authorization with server-side credentials and separate test access. Give extraction, review, approval and posting only the permissions they require. Restrict originals and attachments by company and role; agree storage, retention and any model-provider data handling before processing real invoices.
Log decision metadata and record references, redact credentials and restrict exports. Apply upload type/size checks and malware scanning appropriate to the document store. Limit replay and correction tools to authorized operators, with audit history, so a support action cannot become an untracked financial write.
Buy, configure or build
Evaluate an existing AP platform with representative invoice layouts, partial receipts, approval rules and your accounting account. Many products already support matching, confidence review, complex approvals and audit trails. If those controls and integrations fit, buying and configuring the product may be the better scope.
A supported connector or workflow tool may connect an established AP product to a project database or document store. Test field coverage, task costs, permissions, duplicate handling and failure visibility. A small integration can preserve a working AP product without rebuilding it.
Custom work may fit proprietary job allocation, unusual records or cross-system decisions that remain unsupported after a product assessment. Varying PDFs alone are not sufficient evidence. Scope the smallest missing layer and include monitoring, vendor changes and ongoing ownership in the cost decision.
Scope & acceptance
Review redacted examples representing clean invoices, poor scans, credits, duplicates, partial receipts and non-PO costs. Map who owns each decision. Document what may continue automatically and which exceptions must be held before estimating the work.
Verify account access, allowed objects, field references, attachment options and the destination company with its administrator. Agree posting timing, open-period rules and reconciliation checks. Document the fallback queue and who operates it if integration access is interrupted.
Use an authorized sandbox or isolated test process. Repeat the same intake, change an approved total, remove permissions and simulate a timeout after a successful write. Acceptance means each expected record is accounted for, duplicates are contained and exceptions remain visible.
Start with an agreed vendor or document group, compare outcomes against the existing process and review false matches and queue age. Separate historical backfill from new intake. Hand over mappings, operating instructions and ownership before extending the scope.
Relevant ALCA work
ALCA Coffee connects sales, recipe inventory, expenses and staff roles in an operating platform. It demonstrates connected records and operational controls. It is not presented as an invoice-extraction, AP posting or QuickBooks automation case study; the supplier-invoice pipeline on this page is illustrative.
Before you decide
Not for every step. Digital fields, arithmetic checks, record matching, authorization and retry logic can be deterministic. OCR or an extraction model can help with varied documents, but uncertain fields still need review and all financial rules need explicit validation.
Only records that meet an agreed policy should be eligible for automatic progression. The policy may still require approval before posting. Unknown vendors, missing evidence, suspected duplicates and consequential changes belong in review. We would not promise universal unattended posting.
Potentially, subject to your account’s supported API, product, permissions and record model. Discovery verifies the actual Bill or payable fields and recovery behavior. A connector listing by itself does not prove that your job codes, taxes or attachments are supported.
The document mix, matching sources, approval policy, legal entities, API access and recovery requirements matter more than the number of screens. We scope those decisions first and include support responsibilities; an implementation date or savings figure without that evidence would be premature.
Connected systems
For authorization rules that apply beyond supplier invoices.
For repeated re-keying across other operational records.
For extraction and classification that need a bounded AI-assisted step.
For the broader engineering scope of a connection.
Where supplier costs need a confirmed job and purchase reference.
Where property/entity coding and approved maintenance expenses affect the handoff. These are potential use cases, not client-history claims.
Prepare a process map and identify the first bounded workflow.
Technical references
Reviewed September 10, 2026. These references describe platform capabilities; access, plans and the final design must be verified for your account. They do not imply a vendor partnership.
The supplier-payable Bill object is distinct from a customer sales Invoice. Field support and account access require verification.
Configurable products can support approval gates; an existing tool should be assessed before custom logic is proposed.
Start with one workflow
Describe how supplier invoices arrive, where they are recorded and which exceptions make someone leave the normal process. Approximate volume and the systems involved help us assess an existing AP product, a configured workflow or a custom integration.
Map your invoice handoffsUse our existing project brief. No credentials or customer records needed.