E-commerce purchase review
Matching supplier invoices to order evidence, with human review before accounting actions.
Private client project · active build
- Who it is for
- An e-commerce business reviewing supplier purchases across separate systems.
- The system
- Supplier PDFs · Commerce order exports · n8n · Purchase review drafts
The problem
A supplier invoice and a commerce order describe different parts of the same transaction. Grouped documents, missing identifiers and inconsistent PDF layouts make a simple copy into accounting unreliable.
The approach
Build a rules engine that extracts invoice lines, checks them against independently exported order evidence and prepares a review record. Documents that cannot be matched stay unresolved for a person to inspect.
What the work covers
Document extraction
Reconstruct invoice lines from PDF text and page geometry, including wrapped rows and grouped references.
Cross-source matching
Compare identifiers, products and quantities against order evidence. Treat supplier cost and sales revenue as different amounts.
Review before action
Surface duplicate, uncertain and mismatched cases. A private worker runs the same rules through a supervised workflow and returns a review decision.
Client anonymized. No client data, internal screens, financial figures or identifiable documents are displayed.
Where it stands
A supervised read-only workflow has been exercised. Accounting-write validation and wider operational integrations remain separate work; this is not unattended accounting automation.
What this demonstrates
Turning a messy document workflow into explicit checks, traceable decisions and a controlled integration boundary.
What isn’t working in your business?
Tell me about the workflow, the tools or the idea. We’ll work out a sensible next step.