The reconciliation chapter: every line meets its job file.

First, what the numbers are and aren’t

An honest note before the story: the quantified, published results from this deployment are quoting-side — the win rate that moved from 35% to 73%, documented at aiquotedesk.com and freigh.ai. We are not going to invent a matching statistic for the payable side, and this page deliberately contains none. The reconciliation chapter is an operational story: what changed on the desk when the vendor invoices behind all those won jobs started meeting their job files automatically instead of waiting for month-end.

The desk before

A growing forwarder’s classic payable-side picture: carrier, co-loader and trucking invoices arriving in every format PDF permits, each needing a hunt for its job before anyone could say whether the numbers were right; one job generating financial events for weeks — freight, THC, a detention line, an amendment fee — under charge codes that never quite matched; overseas agents settling by statement rather than invoice, in more than one currency; and the real check happening at month-end, when the jobs in question were already cold. Nothing broken; everything arriving faster than line-level scrutiny could keep up with.

What the reconciliation desk changed

Variances with names on them

The texture change the floor notices first is that an exception arrives pre-explained. The desk doesn’t hand a human an invoice and a suspicion; it hands over a named reason and the evidence behind it — this line against that buy rate, this THC against its twin on the co-loader’s statement, this detention clock against the tracking desk’s own event history. The conversation with the vendor starts from the second sentence, because the first one is already written.

The agent statement, netted

Agent settlement is where forwarder reconciliation stops resembling ordinary accounts payable: statements instead of invoices, netting instead of payment, currencies plural. On this deployment the desk matches each SOA line to its job and accrual, computes the net position, and flags the lines that don’t belong before the settlement wire goes out— which is the only moment a flag on an agent statement is worth anything. A discrepancy found after settlement isn’t a variance anymore; it’s a favour you have to ask for.

The cost that used to arrive too late

The quiet star of the chapter is the flag that connects payables to billing. When a vendor cost lands afterthe customer has already been invoiced — an amendment fee, a late accessorial, a D&D pass-through — the desk flags it and routes it for re-billing instead of letting it dissolve into the write-off line. On forwarder margins, that flag is the difference between a job that made what the quote promised and one that quietly didn’t. It works because reconciliation and billing live on one platform: the desk knows the customer invoice went out on Tuesday, so Thursday’s cost gets caught, not absorbed.

The other chapters

Six agents run at Infinity — quotation, booking, tracking, partner discovery, reconciliation, collections. The full platform story is at freigh.ai; the quoting chapter with its measured 35%→73% arc is at aiquotedesk.com; the collections chapter — the receivable-side mirror of this one — is at receivables-ai.com. This chapter is where the jobs those agents create and win get their costs checked before the money leaves.