Three days ofinvoice matching, gone

Client
Calder Foods
Sector
Food manufacturing
Delivered
Span 06 — Calder Foods

In one paragraph

Supplier invoices, delivery notes and purchase orders matched automatically, with a small exception queue that a single person can clear before lunch.

Measured afterwards

94%
Straight-through matching
3d → 40min
Matching cycle
9,200
Invoices per month
4 days
Close brought forward

The problem

Four people spent three days a week matching invoices to delivery notes and purchase orders across two ERP instances and a shared mailbox. Month-end close slipped regularly, and early-payment discounts were being missed because approvals arrived too late.

What we did

We shadowed the process for a week and documented every step, including the ones that only existed in one person's head. Intake parses email and PDF into structured records, matching runs on a tolerance model agreed with finance rather than exact equality, and anything outside tolerance is routed to a named owner with the three documents side by side. Every run is observable end to end, and the whole pipeline is idempotent so a replay after an ERP outage is safe. Finance owns the tolerance rules through an editor, so a threshold change does not need us.

What changed

Straight-through matching runs at 94% and the cycle dropped from three days to forty minutes. Month-end close moved four working days earlier, and the missed early-payment discounts stopped.

Built with

Node.jsTemporalPostgresRabbitMQZodGrafanaOpenTelemetry