What's different from our ERP's built-in 3-way match?

Most ERPs match at the header level only — invoice total vs PO total. Flowie matches line-level with configurable fuzzy logic per supplier and category. Result: legitimate invoices stop failing on cosmetic variance (unit of measure, rounding, partial delivery), while real discrepancies surface immediately.

How do tolerance bands work across multiple entities?

Bands are inherited from a global template, then overridden per entity, supplier, or category as needed. Change the global threshold once and every entity picks it up unless explicitly overridden. No more 5-system change requests for a single policy update.

What's the network effect?

When a supplier is already on the Flowie network, their invoice arrives structured to Flowie's schema — line items, PO references, UOM all clean. Match time drops to under 2 seconds. 600M+ verified entities and growing — the network compounds every onboarding.

3-Way Match Workflow

PO + Receipt + Invoice. Auto

Invoice arrives → AI matches against PO + receipt → policy validation → auto-post if clean, exception queue if not. The universal AP verification step, fully automated, with fuzzy-match logic for line-level discrepancies.

Use This Template Preview Template

By the numbers

3-Way Match Workflow by the numbers.

95%

Touchless match

Line-level

Not header-only

Per-supplier

Tolerance bands

<2s

Network match

The use case

Three-way match that actually works. Line-level. Network-native.

Three-way match in the ERP fails 40% of the time on legitimate invoices. Tolerance bands are hardcoded across 5 entities — every change is a project. Receipts get entered 3 days late, so first-pass matching always fails. AP overrides exceptions manually and nobody looks at the pattern. Auditors flag the override rate every year, and procurement has no visibility into supplier-level discrepancy trends.

Pre-built workflow template: invoice arrives → Astral resolves PO + receipt + supplier from the knowledge graph → line-level fuzzy match with per-supplier tolerance bands → auto-post if clean → exception queue with full context if not. Network effect kicks in when supplier is on Flowie — invoice arrives pre-structured, matched in under 2 seconds. Receipt-first resilience handles late receivers gracefully. 95% touchless, line-level, audit-ready end-to-end.

For who

AP Operations

“Three-way match in our ERP fails 40% of the time on legitimate invoices.”

Controller

“Tolerance bands hardcoded across 5 entities. Every change is a project.”

Procurement Ops

“Receipts are entered 3 days late, so match always fails first time.”

Audit

“Match exceptions get manually overridden. No one looks at the pattern.”

Capabilities

What 3-Way Match Workflow actually does.

01Capability

Line-Level Fuzzy Matching

Not just header totals — every line item reconciled against PO and receipt with configurable fuzzy logic. Catches partial deliveries, unit-of-measure mismatches, and price drift the ERP misses.

02Capability

Configurable Tolerance Bands

Set tolerance thresholds per supplier, category, or entity. Quantity, price, total — each band tunable in minutes, not change requests. One template, every entity.

03Capability

Network-Accelerated Match

Supplier already on the Flowie network? Invoice arrives pre-structured, matched in under 2 seconds. 600M+ verified entities, growing every onboarding.

04Capability

Smart Exception Queue

Failed matches routed to the right resolver with full context — PO line, receipt timestamp, supplier history, similar past exceptions. AP teams resolve in one screen, not five tabs.

Continue exploring

More on Templates.

ISO 27001:2022 · GDPR · EU-hosted · Full audit trails · Trust Center →

See 3-Way Match Workflow on your stack.

Start free. See your first workflow run before the next quarter close.

Use This Template Preview Template

ISO 27001

GDPR

CyberVadis

PA Certified

Peppol