Closing the Month on Broker Commissions: A Step-by-Step Reconciliation Process

Most articles about commission reconciliation tell you that it's painful and that software fixes it. This one is the actual sequence—what you do, in what order, when the statements land.

What this covers, and what it doesn't

This is the operational side of month-end: gathering manufacturer statements, matching them against the orders you booked, finding the gaps, and deciding what to do about each one.

It is not an accounting close. Accruals, journal entries, and how commission revenue gets recognized on your books are a separate process with its own rules, and they depend on your contracts and your basis of accounting. That work belongs to your bookkeeper or CPA. What follows is the operational cycle that feeds them clean numbers.

One framing that makes the whole thing easier: reconciliation is a comparison, not a reconstruction. If you only start figuring out what you're owed when the statement arrives, you're not reconciling—you're rebuilding the month from scratch against a document written in someone else's numbering system. The steps below assume you have your own expected-commission figure to compare against. Building that figure is the highest-leverage change you can make to this process, and it happens before month-end, not during it.

Before you start: what you need on the desk

Gather these first. Chasing any one of them mid-reconciliation is what turns a morning into a week.

• The rate agreement for every principal—not your memory of it. Specifically: the percentage, and the basis it applies to (gross invoice or net after deductions). The basis is the part people can't recall under pressure, and it's the part that matters most.
• Your confirmed orders for the period, with SKU, ship-to, ship date, and invoice amount.
• The statements themselves, which arrive on no shared schedule and in no shared format.
• Last period's unresolved variances. Anything you flagged and didn't close is part of this month's work, and it's the most commonly dropped item in the entire cycle.
• Your rep split agreements, if you're paying commissions out as well as collecting them.

The six-step sequence

1. Assemble and inventory the statements

Before opening any of them, list which principals you expect statements from and check them off as they arrive. The failure mode here is silent: a statement that never showed up doesn't announce itself, and a principal you simply forgot to chase looks identical to a principal who paid you correctly. An explicit expected-list is the only thing that catches it.

2. Normalize the identifiers

This is the tedious step, and it's unavoidable. Manufacturers report against their own order numbers, which have no relationship to your PO numbers. So you match on what both sides share: product SKU, ship-to location, and ship date—usually approximate, since their date and yours may differ by the transit window.

Where a distributor services the account, the statement often won't tell you which lines are yours at all, particularly when several brokers work out of the same warehouse. You're matching on territory and ship-to rather than anything the document states outright.

3. Compare against your expected commission

For every matched line, calculate what you expected: invoice amount × your contracted rate, applied to the contracted basis. Then set it beside what they paid.

If you've built this record as orders were confirmed, this step is a column comparison. If you haven't, this is where the hours go.

4. Isolate the variances

Anything where expected and paid don't agree. Also flag two things that aren't strictly variances but behave like them: lines on their statement that you have no order for, and orders you booked that appear nowhere on their statement.

5. Classify each variance

This is the step that gets skipped, and skipping it is why the same problems recur every month. A variance you fix without diagnosing is a variance you'll fix again in thirty days. The four types are below.

6. Decide the action on each

Pursue, batch, or accept—covered further down.

The four variance types

Run one example through all of them. Your contracted rate is 4.0% on the gross invoice amount. A line ships at a gross invoice of $42,500, so you expected $1,700.

Rate error

The statement pays $1,275. Divide it back out: $1,275 ÷ $42,500 = 3.00%. You're contracted at 4.0% and they're paying 3.0%. Variance on this line: $425.

This is the easy one to catch, because the implied rate comes out as a suspiciously round wrong number. It's usually a configuration error in their system dating to whenever your rate was last renegotiated—which means it is almost certainly on every other line for that principal too, and has been since the change.

Rate-basis switch

The statement pays $1,380. Check the rate and it looks fine—$1,380 ÷ $34,500 is exactly 4.00%. Contract honored, apparently.

Except $34,500 isn't the gross invoice. It's the gross minus $8,000 in promotional deductions. They've applied your correct percentage to the net amount, and your contract specifies gross. Variance: $320.

This one is genuinely dangerous, and the reason is arithmetic. Checked against the figure they used, the rate reads as a clean, correct 4.00%. Checked against gross—the basis you actually contracted for—it's 3.25%. Whether you catch this depends entirely on which denominator you check against, which is why "what's the basis" belongs on your desk before you start.

Missing line

You booked and shipped the order. It isn't on the statement at all. Common causes: the reorder came through a secondary distributor channel under a different customer code, the ship-to was never mapped to your territory, or the line was credited to another broker.

These rarely surface from reading the statement, because nothing on a statement draws attention to what isn't there. They surface from working the other direction—from your order list to their document.

Timing difference

The order is missing this month and appears in full next month. Nothing is wrong; the ship date fell near the period boundary and landed in their next cycle.

Classify these correctly and be disciplined about it. Timing differences are the largest category of variance at most brokerages, they resolve themselves, and every hour spent disputing one is an hour not spent on the three types above. The tell is a variance that closes cleanly next period without anyone doing anything—which you'll only notice if you carried it forward in step 5 instead of re-discovering it.

What to pursue and what to let go

The instinct is to set a dollar threshold—chase anything over $500, let the rest go. That's the wrong axis.

Sort by whether it's systematic, not by size. A $180 variance that shows up once may not justify a chain of phone calls. The same $180 variance every month is $2,160 a year, and more importantly it's a signal: something is misconfigured at the source. Fixing that once is worth more than recovering any single line, because it stops the leak instead of bailing it.

So, practically:

• Anything that repeats gets pursued regardless of size, and gets pursued as a configuration problem rather than a line-item dispute. The conversation is "your system has our rate wrong," not "you underpaid us $180 in June."
• One-off small variances get batched. Log them, don't chase each one, and raise the accumulated list at your next scheduled conversation with that principal.
• Timing differences get carried forward, not disputed.

On deadlines: your window to raise a discrepancy is defined by your brokerage agreement with that principal, and it varies. There's no industry-standard number, and treating a remembered one as fact is how claims expire. Find the clause, and put the date in your process rather than in your head.

Handing off to your bookkeeper

Whatever they need to do on the ledger side is theirs to determine—confirm the treatment with them or your CPA, because it depends on your contracts and how your books are kept. What you owe them is a clean, unambiguous handoff.

A variance report that doesn't generate follow-up questions has, per line: the principal, your PO or order reference, their statement reference, the period, the gross invoice amount, the contracted rate and basis, the expected commission, the amount actually paid, the variance, its classification, and its current status. Plus the aggregate paid-versus-expected figure per principal for the period.

The reason to be exact about this is that ambiguity here comes back as questions weeks later, when reconstructing what you meant costs far more than writing it down did.

Where TradePath HQ fits

The step that consumes the month is step 3—and it only consumes the month if you're building the expected figure from scratch when the statement arrives.

TradePath calculates expected commissions from confirmed purchase orders as they're processed, applying your stored rate card—percentage and basis, per principal—along with rep splits. When the statement lands, the number you're comparing against already exists, so month-end starts at step 3 instead of ending there. Variances surface as differences against a record you already trusted, every line traces back to its originating PO, and commission invoices push to QuickBooks without re-keying.

That's the practical difference between reconciliation as a comparison and reconciliation as a reconstruction.

---

For more on where commission margin quietly leaks and what to look for in software built for this, see Food Broker Commission Reconciliation. If your brokerage runs on QuickBooks plus spreadsheets today, Food Broker Software That Works With QuickBooks covers where that combination breaks. And because clean reconciliation depends on clean orders upstream, Order Management for Food Brokers covers the other half of the loop.