Stop Losing Commission Questions in Your Inbox

Commission reconciliation is revenue operations

A supplier statement arrives. Someone downloads it, checks the total, and saves it in a folder. Two weeks later an advisor asks why a client payment changed. Now the team is searching old statements, email threads, deal notes, and partner portals to rebuild what should have happened.

That is not a small accounting annoyance. For a recurring-revenue advisory firm, it is a broken revenue process.

The job is not finished when you import a statement or record a payment. You need to compare what arrived with what the firm expected, explain the difference, assign the next action, and preserve the answer beside the client, supplier, service, and contract.

Do this every month and commission questions become manageable exceptions. Skip it and every question becomes a fresh investigation.

Keep three records separate

Small firms often collapse three different records into one number.

The first is the commercial expectation. This comes from the signed order, supplier schedule, partner agreement, approved split, and any later amendment. It describes the payment the firm believes it should earn if the underlying conditions are met.

The second is the supplier statement. It shows what the supplier or distributor reported for a period. The statement may contain account names, service identifiers, revenue, rates, adjustments, and payment amounts. Treat it as reported data, not as the final truth.

The third is the firm's reconciliation record. This connects the expectation to the statement and records the result. It should show whether the item matched, why it did not match, who owns the review, and what evidence closes it.

If you overwrite the expectation with the latest payment, you lose the ability to see a variance. If you keep only the statement, you can confirm what was paid but not whether it was right.

Match the payment to the underlying business

A commission row needs more than a client name. Names change. Subsidiaries pay invoices. Suppliers abbreviate accounts. One client may have several locations, contracts, and services with different commission terms.

Match each payment to the strongest identifiers available. That may include the supplier, client, service, billing account, circuit or order number, contract, deal, and expected commission type. Keep the statement period and import source too.

Advisor OS can import carrier and vendor commission statements, map the data to client accounts, and keep commission import history available after later imports. That gives the team a better starting point. It does not remove the need to review uncertain matches or confirm the commercial terms behind a variance.

Do not force a questionable row into the nearest account so the report looks complete. Put it in an unmatched queue with an owner. Clean uncertainty is more useful than false certainty.

Use variance types your team can act on

"Commission issue" is too vague. The label tells nobody where to look or what to ask for.

Use a short list of variance types that fit your business. Common examples include:

• Missing payment: An expected service or account does not appear on the statement.
• Rate difference: The reported rate does not match the documented commercial expectation.
• Revenue basis difference: The supplier calculated commission on a different eligible amount than the firm expected.
• Timing difference: The item may be valid but belongs in another payment period because of installation, billing, acceptance, or supplier processing timing.
• Client or service mismatch: The payment cannot be confidently connected to the right account, order, or service.
• Adjustment or chargeback: A prior payment changed and the reason or supporting calculation needs review.
• Split difference: The advisor, house, subagent, or referral allocation does not match the approved split.

The category should point to a next step. A missing payment may require proof of installation and the supplier's eligibility date. A split difference may require the approved compensation record. A timing difference may need monitoring rather than an escalation.

Require evidence before opening a dispute

Forwarding a spreadsheet row with "Please check" creates work for everybody and gives the recipient very little to resolve.

Build a compact evidence packet for each disputed item. Include the client and service, supplier statement period, reported payment, expected payment, calculated variance, relevant identifier, commission terms, and the event that made the payment eligible. Add the exact question you need answered.

If the expected amount depends on a contract term, rate card, partner agreement, or supplier rule, link the source. Do not rely on a CRM field without checking where that field came from. If the term is unclear, mark it unconfirmed instead of treating a guess as receivable revenue.

A good dispute asks for a correction or explanation tied to evidence. It does not ask the supplier to investigate your entire book of business because your records are incomplete.

Give every variance a state, owner, and date

Commission work disappears when the process has only two states: paid and not paid.

Use states that show what happens next. An item might be unmatched, matched and pending review, confirmed correct, disputed with supplier, waiting on internal evidence, corrected in a later statement, or closed with an accepted explanation.

Every open variance needs one internal owner and one next review date. If the supplier has accepted a dispute, record the supplier owner, case number, response commitment, and latest confirmed update. Connect that follow-up to your revenue follow-up queue instead of creating another private reminder list.

The owner does not need to be the founder. The person does need enough context and authority to request evidence, contact the supplier, accept a valid explanation, or move the issue to the person who can decide.

Reconcile on a fixed monthly cadence

Waiting for an advisor to notice a short payment is not a control.

Set a monthly close for every supplier statement. Import or record the statement, resolve confident matches, classify variances, assign owners, and report the open exception total. Then review aging. An old unresolved variance deserves a decision: continue the dispute, accept the explanation, correct the expectation, or escalate.

Bring only material or stuck exceptions into the weekly advisor operating review. The whole team does not need a tour of every statement row. It needs visibility into issues that affect cash, advisor compensation, client records, supplier relationships, or the reliability of the forecast.

Keep reconciliation separate from forecasting. A disputed payment is not collected revenue. A commercial expectation is not earned revenue simply because the deal closed. Your next forecast should distinguish those states instead of turning them into one optimistic number.

Use the history to manage suppliers and accounts

One resolved difference may be routine. A pattern is operating data.

Track recurring mismatch types by supplier, service, and account. If one supplier repeatedly changes identifiers, delays explanations, or produces adjustments your team cannot trace, that belongs in the supplier record. It should inform the next supplier selection and partner review.

The account history matters too. A service disconnect, move, renewal, contract change, or billing correction may explain a commission change and may also signal client work that needs attention. Commission reconciliation can surface account changes that never reached the advisor's normal workflow.

Do not turn every difference into a supplier accusation. Sometimes the statement is right and your expectation is stale. The point is to preserve the answer so the team does not investigate the same question again next month.

Audit one statement before you build a giant process

Take the latest statement from one meaningful supplier. Pick ten rows across different clients and payment types. See whether your team can connect each row to the client, service, deal, contract, commission expectation, and payment history without opening five systems.

Then find every unmatched or changed item. Can you see the variance type, evidence, owner, next action, and review date? Can another person understand why the item was closed?

If the answer is no, fix that one statement first. You will learn more from a real reconciliation than from designing a perfect policy nobody has tested.

If your current system cannot connect deals, suppliers, clients, contracts, commission statements, and follow-up, run the free Advisor OS agency scorecard. Revenue operations should not depend on whoever remembers the spreadsheet.