An agent SOA — statement of account — is the periodic statement your overseas partner sends listing every open charge between you: what you owe them for handling your shipments at their end, and what they owe you for handling theirs at yours. It is settled by netting the two sides to a single wire, usually across currencies. It is painful because it is a statement, not an invoice: dozens of lines, many jobs, both directions, each line needing a match to a job file and an accrual before anyone should agree the net.
Why is a statement harder than an invoice?
An invoice is one vendor, one direction, and — on a good day — one job. An SOA is a ledger excerpt: your Rotterdam partner’s monthly statement might run 23 lines across 9 jobs, referencing theirjob numbers, their charge codes, and shipments where you were the origin agent on some lines and the destination agent on others. A line you don’t recognise could be their billing error — or your missing accrual. You can’t know which without matching every line to a job file, which is exactly the work that makes SOA month a dreaded fixture on the finance calendar.
What does netting change about settlement?
You don’t pay an SOA; you agree a net position. If you owe the agent €18,400 and they owe you €11,200, one wire of €7,200 settles the month — but only if both ledgers agree line by line first. Netting compresses the cash movement and multiplies the reconciliation stakes: a disputed line doesn’t block one invoice, it blocks the whole settlement. Add currencies — their statement in euros, your accruals in dollars, your books in rupees — and the “does it match?” question acquires an FX-rate-and-date dimension that spreadsheets handle badly at 11 pm on the 30th.
Why do agent protection programs exist?
Because settlement disputes between partner agents are common enough that the industry built financial protection around them. Network programs like WCA’s Gold Medallion exist precisely to cover inter-agent payment defaults and disputes — an insurance product whose existence is the market’s honest admission that two competent forwarders, reconciling in good faith, still routinely disagree about who owes whom. The disagreements are rarely about dishonesty. They are about unmatched lines.
What does a netted settlement look like?
| Direction | Lines | Matched | Flagged | Position |
|---|---|---|---|---|
| You → agent | 14 lines / 6 jobs | 13 | 1 — rate above agreed tariff | €18,400 |
| Agent → you | 9 lines / 3 jobs | 8 | 1 — no matching accrual found | €11,200 |
| Net wire | — | — | 2 lines held out of settlement | €7,200 payable |
ILLUSTRATIVE SETTLEMENT — LINE COUNTS AND AMOUNTS ARE EXAMPLES, NOT BENCHMARKS
The two flagged lines are the point: they get resolved or held out before the wire, not discovered in a testy email chain three months after it. That ordering — match, flag, agree, then pay — is the entire discipline.
How does the desk settle an SOA?
It matches each statement line to its job and accrual, computes the net position across currencies, and flags the lines that don’t belong — with the reason named and the evidence attached — before the settlement wire goes out. Agent settlement is reconciliation’s forwarder-specific wrinkle, and it gets a full chapter in the complete guide. To put a number on what unmatched SOA lines cost you per year, start with the calculator.
From reading to watching.
Everything on this page runs live on a working match desk. Bring one week's vendor invoices and watch every line meet its job file.
Book the working session