Supplier invoices often arrive in different layouts even when the finance team needs the same information from each one. Norml builds a workflow that reads agreed invoice fields, preserves the source and prepares a record for review. Your team checks the vendor, coding and exceptions before any approved accounting handoff. The scope begins with incoming supplier invoices and ends at the explicitly agreed review or bill-creation step.
We agree where automation stops before building the workflow. Extracting an invoice does not authorize a purchase, establish a supplier’s legitimacy or approve payment.
We map the supplier name, invoice reference, dates, currency, amounts and required line items to your review record. The source file stays accessible for comparison. Missing or unreadable fields are flagged; normalization rules remain visible so a reviewer can check any changed date or number format.
The workflow checks required values, agreed arithmetic rules and potential duplicates. Duplicate detection considers supplier identity and invoice reference alongside the source file, since the same invoice may arrive as another attachment. Conflicting totals, unmatched suppliers and unusual document types remain in review.
If included, a reviewer approves the mapped vendor, accounts, tax treatment and other required fields before the workflow creates a bill. Bill creation changes accounting records; it is not treated as a harmless draft. We record the resulting ID and reconcile uncertain responses before retrying a write.
Provide anonymized invoices from representative suppliers, including scans and line-item layouts. Identify credit notes, partial invoices and other documents that require separate handling.
Your finance owner supplies the vendor matching, account and tax mappings, currency rules and required approvals. The workflow applies those decisions; it does not determine accounting policy.
Confirm the permitted invoice intake, Airtable review access and any QuickBooks Online permissions. Choose whether delivery ends with reviewed data or includes the approved bill-creation action.
We compare extracted fields and line items with values checked by your team. The evaluation identifies unsupported layouts, missing evidence and cases that should remain manual.
We connect intake, extraction and validation to a review state that records the approved values and reviewer. Rejected or corrected records do not advance merely because an automation runs again.
Where bill creation is included, we test vendor matching, repeated deliveries and interrupted responses. Your team checks the resulting records and receives instructions for reconciling failures before any retry.