Flagship workflow

The most painful AP workflow, automated end-to-end.

Three-way matching is the moment your AP team manually compares a purchase order, a goods receipt, and an invoice — line by line, exception by exception, day after day. RoboExpress reads all three, matches them, flags only the genuine discrepancies, and posts the rest to your General Ledger. No human in the middle.

Three-way matching is one of the most universally painful processes in finance. Every company that buys physical goods has to do it. The pain comes not from the matching itself — the logic is simple — but from the volume, the document variation, the human attention it demands, and the cost of getting it wrong.

Get it wrong by being too lenient and you overpay suppliers, you pay for goods you never received, you create reconciliation problems your auditors will catch six months later. Get it wrong by being too strict and your AP team becomes the bottleneck for every supplier payment in the company — you damage supplier relationships, you miss early-payment discounts, you slow your own operations. Most companies tolerate the cost of doing it manually because the alternative — building a matching engine — has historically required either expensive professional services or in-house engineering time nobody has.

RoboExpress changes that calculation. It is a pure-play SaaS product. You sign up, you connect your inboxes and your ERP, and within days the engine is matching at production volume. The accuracy comes from the engine, not from a consulting engagement.

The cost of doing it manually

What manual three-way matching actually costs a finance team.

Numbers from finance leaders who switched to RoboExpress, comparing the manual process they ran before to the automated process they run now.

The cost is not just the AP team's time. It is the missed discounts, the duplicate payments, the audit findings, the supplier relationships strained by slow approvals, and the strategic work the finance team cannot do because they are matching invoices.

Manual processing time
14 minutes per match
Average time an AP analyst spends manually verifying a single PO-GRN-invoice triplet, including exception lookup. With RoboExpress: 2.4 seconds for clean matches.
Duplicate payment risk
0.4% of invoices
Industry baseline for duplicate payments slipping through manual matching. On a ₹100 cr annual spend, that is ₹40 lakh paid twice. RoboExpress catches every duplicate before posting.
Early-payment discounts lost
2-3% per invoice
Typical discount missed when AP cannot match and pay within the discount window. RoboExpress posts within hours, not days — the discount becomes capturable again.
The matching flow, in detail

Three documents in. One ledger entry out.

The platform reads each of the three input documents, extracts the data points needed to match, applies your tolerance rules, and produces a single deterministic output: a journal entry posted to your GL, or a flagged exception sent to a human.

Input 01 · Purchase Order

From your ERP

  • PO number
  • Vendor identity
  • Line items + quantities
  • Unit prices + taxes
  • Delivery terms
  • Approved by
Input 02 · Goods Receipt

From the warehouse

  • GRN number
  • Linked PO reference
  • Quantities received
  • Quality status
  • Receipt date
  • Received by
Input 03 · Invoice

From the supplier

  • Invoice number
  • Vendor identity
  • Line items + quantities
  • Unit prices + taxes
  • Payment terms
  • Total amount due
✓ Output 01 · Clean match

Posted to GL automatically

All three documents agree within tolerance. Journal entry created, posted to your ERP via API, audit trail attached, and the invoice moves into the payment queue. No human touch.

⚠ Output 02 · Discrepancy

Routed to a human

Mismatch outside tolerance — price variance, quantity variance, missing GRN, vendor mismatch, or duplicate. Routed to AP with the specific reason flagged. The exception is the only thing your team touches.

Configurable tolerance rules

You define what counts as a match.

Different organisations tolerate different variances. RoboExpress does not impose a one-size answer — the matching engine runs against your rules, your thresholds, your exception types.

Tolerance type

Price variance

Allow invoice unit price to differ from PO unit price by N percent or N rupees. Configurable per vendor, per category, per contract.

Tolerance type

Quantity variance

Allow received quantity to differ from invoiced quantity by N percent or N units. Useful for bulk goods where partial deliveries are normal.

Tolerance type

Tax variance

Allow tax computation to differ from PO tax by rounding tolerance. Catches tax engine differences without flagging every decimal.

Tolerance type

Date variance

Allow goods receipt and invoice dates to differ by N days. Useful when goods receipt is delayed but the supplier invoiced on dispatch.

Tolerance type

Vendor identity match

Match by vendor master record, not by free-text name. Fuzzy matching available for vendor name variations across documents.

Tolerance type

Duplicate detection

Detect re-submitted invoices by invoice number, by amount + vendor + date, or by document fingerprint. No duplicate ever clears the engine.

Discrepancy handling

The exception is the only thing your team touches.

When a match fails, RoboExpress does not just dump the documents back to your AP team. It tells them exactly what is wrong, why, and what the resolution options are. Their work is to decide, not to investigate.

ID
Vendor
Discrepancy
Amount
Status
INV-AC-9847
Acme Components
Price variance: invoice ₹485/unit vs. PO ₹460/unit (+5.4%)
₹ 4,82,500
Review
INV-MT-1124
Metro Logistics
No matching GRN found. Goods receipt may not be recorded yet.
₹ 1,28,900
Hold
INV-RP-7782
Raghav Pharma
Duplicate invoice number detected. Original posted on 2026-04-14.
₹ 67,200
Block
INV-SK-4451
SKY Textiles
Quantity variance: invoice 500 units vs. GRN 480 units (-4%)
₹ 2,40,000
Review
INV-ZC-9008
ZenCorp Industries
All checks passed. Posted to GL.
₹ 8,75,400
Cleared
Universal ERP connectivity

Posts to every ERP you might run.

RoboExpress is ERP-agnostic by design. Matched journal entries flow to whichever system you use as your system of record — via native API where available, via direct file integration where not.

Don't see yours? If it has an API, RoboExpress connects to it.

See your actual three-way match
processed in 30 minutes.

Send us a sample of your real PO, GRN, and invoice documents. We will run them through RoboExpress live on a call and show you the matched output in your ERP format.