Match invoices without checking every record by hand.
Build a NodeFox workflow to read invoices, compare purchase orders and receipts, and prepare discrepancies for AP review. Reduce repeated checking while keeping accounting records and payment decisions under your existing controls. Built on NodeFox’s executable workflow platform.
One workflow, 3 different cases.
Pick a case to see which steps run, what a reviewer is shown and what gets written.
Synthetic example · An invoice enters the AP queue
Invoice to checked posting record
Arrives
INV-4091
- Invoice / PO price
- $20 / $20
- Invoiced / received
- 100 / 100 units
- Duplicate check
- No existing invoice match
Runs
PDF or structured invoice arrives through a configured source.
AI structures invoice number, supplier, amounts, quantities and PO reference.
Permitted accounting and purchasing APIs return authoritative records.
Exact rules compare invoice / PO / receipt and check the invoice identity before posting.
Supplier, reference, quantities and amounts satisfy the configured rules.
Review source lines, receipts and tolerances; approve a correction or hold.
Use an authorized API with duplicate protection. Posting is separate from payment release.
Keep checks, reviewer decision and destination response with the run.
AI reads the document; exact rules check the transaction. AP retains judgment over exceptions and existing payment controls remain in place.
Result
Written
Checked posting recorded
- Accounting response retained
- Payment release follows the existing approval process
Work coordinated: input gathering, system lookups, repeated checks and approved updates. Select a step to inspect its role.
Human-owned: process rules, exception judgment and authorization. Synthetic records and transitions; no model calls or live system writes.
Interpret the invoice. Match exact records. Authorize the result.
The same work, with the checking done first.
- Today
AP retrieves the PO and delivery evidence for each invoice.
With NodeFoxConfigured lookups assemble the same records before review.
We measurePreparation minutes per invoice
- Today
Differences trigger messages without the underlying line details.
With NodeFoxA mismatch reaches its owner with amounts, receipts and the failed rule.
We measureTouches and days to resolve unmatched items
- Today
Approved corrections are rekeyed into accounting.
With NodeFoxAn authorized write carries the checked result with duplicate protection.
We measureRework and duplicate-posting incidents
Raw input → usable output
Make the match repeatable and the approval visible.
AP gets a matched record with all three source references. The team can focus on unresolved invoices instead of repeating the same evidence search.
- Input 1
- INV-6092 · Cedar Components
- Input 2
- PO-6008 · 96 units at $25
- Input 3
- Invoice amount: $2,400
- Input 4
- Receipt reference: GR-902
AP-6092 · payment-ready record
Matched amount
$2,400
- Evidence: invoice + PO + receipt
- No payment instruction executed
Decision attached
Approve payment-ready preparation
Source references and configured checks accompany the result.
Inspect the structured record
{
"invoice_id": "INV-6092",
"matched_amount": 2400,
"currency": "USD",
"three_way_match": true,
"payment_executed": false
}Synthetic sample files with inputs, checks and decisions. System updates require configured access and authorization. Documents and reports depend on the chosen Writer format and template.
Make the match repeatable and the approval visible.

Transcript and demonstration details
Illustrative execution, not a customer deployment. Narration is AI-generated. Actions and outputs depend on workflow configuration.
- 0–8s · Three records should tell the same story
Cedar Components submits an invoice for ninety-six units. The purchase order and goods receipt must agree.
INV-6092 · Cedar Components · PO-6008 · 96 units at $25 · Invoice amount: $2,400 · Receipt reference: GR-902
- 8–18s · A three-way match
Supplier, currency, quantity and price all match. Ninety-six times twenty-five dollars gives a supported total of twenty-four hundred dollars.
Supplier and currency match · 96 × $25 = $2,400 · Three-way match: passed
- 18–27s · Interpretation and arithmetic have different jobs
AI extracts the fields. Code performs the match. The workflow carries the evidence to the accounts payable owner.
Invoice files · ERP purchasing · Receipt ledger
- 27–35s · Prepare the payable record
The owner approves payment-ready preparation. This decision does not release funds or send a payment instruction.
AP owner reviews match package · Approve payment-ready preparation · Treasury retains payment release
- 35–43s · Ready for the next authorized step
The AP record includes the matched amount and all three source references. Treasury retains payment release.
AP-6092 · payment-ready record · Matched amount: $2,400 · Evidence: invoice + PO + receipt · No payment instruction executed
Value the matching work, not the invoice balance.
Editable hypothetical example · USD
What could less coordination be worth?
Change four assumptions to estimate annual capacity. These are example inputs, not customer results. Calculations stay in your browser.
- Annual capacity potentially released
- 1,560 hours
- Annual labor-capacity equivalent
- $70,200
- Reduction in hands-on time
- 60%
10,400 cases / year × 9 minutes removed per case ÷ 60. Includes eligibility, exception effort and rework when entered.
Capacity is not automatically cash savings. Value depends on how the released time is used and what the workflow costs to operate.
Your systems stay the system of record.
- Invoice sourcereadApproved file export or intake API.
- Purchasing and receivingreadPO, receipt and supplier identifiers through configured APIs or exports.
- Accountingread + writeRead existing invoices; scope writes to agreed posting operations, not payment release.
People keep the decisions that matter.
AP owner
Purchasing / receiving
Systems owner
Start with one supplier group and invoice format
Use a representative sample of matched, mismatched and missing-receipt cases. Start with reviewable posting proposals; enable writes only after the acceptance and authorization rules are agreed.
Reference sample with known correct outcomes
PO / receipt mapping and approved access
Duplicate, partial-receipt and tolerance rules
Named AP and systems owners
Measured effort, quality and ongoing operating cost
- Hands-on time
- Preparation, matching and review minutes, split by matched and unmatched invoices.
- Match rate
- Invoices satisfying all configured checks without manual preparation.
- Resolution age
- Median and 90th-percentile age of unmatched invoices, by cause.
- Posting quality
- Amount, supplier and duplicate accuracy against an audited reference sample.
Questions operations leaders ask
Does NodeFox replace our accounting system?
Does the workflow initiate payments?
What if a write times out?
For the technical review.
How much of AP’s time goes into gathering the evidence?
Discuss one invoice flow, the access available and the effort behind matched and unmatched cases. Establish whether a scoped paid evaluation or direct deployment makes sense.