Reconcile calls.
Explain the differences.

When your call platform, partner report and invoice disagree, a total tells you where to look. A call-level reconciliation helps explain why. Use this six-step process to connect records, separate confirmed matches from exceptions, and give each unresolved item an owner.

What you need: call-level exports from each source, the applicable commercial terms, and a spreadsheet. Start with one partner and one reporting period.

01 / Set the boundaries

Choose the partner, date range, time zone, currency and reporting cutoff. Decide which date governs the comparison: call time, approval date or invoice date. Record the choice. A call can legitimately land in different periods across systems.

02 / Preserve the sources

Save untouched exports. Note each source, export time, filters and row count. Work from separate copies. Retain original IDs, statuses, timestamps and amounts so every adjustment remains traceable.

03 / Build the call map

Match exact shared call IDs. Where IDs differ, keep a documented, verified crosswalk. Secondary fields can suggest a match; they cannot confirm an ambiguous one. Separate duplicates, transfers and adjustments before combining rows. Unknown identities remain exceptions.

04 / Calculate the expectation

Apply the terms effective for the call. Check eligibility, rate, duration rules, caps and adjustments. Keep revenue and payout separate. Record the source of each rule. Unknown or disputed terms stay unresolved rather than becoming guessed amounts.

05 / Compare and classify

Compare amounts on the same basis. Use difference = reported amount minus expected amount. Flag missing records, eligibility disagreements, rate differences, timing differences and possible duplicates. A flag is a question, not proof of an error or money owed.

06 / Assign, resolve, repeat

Give every exception an owner, next action and review date. Attach evidence and record the resolution without overwriting the original finding. Recheck corrected reports. Close with agreed items, open items and timing differences shown separately.

Your exception register

Use these columns: Exception ID · Call ID · Source · Category · Expected amount · Reported amount · Difference · Evidence · Owner · Next action · Review date · Status · Resolution.

ILLUSTRATIVE EXAMPLE ONLY

EX-001 / CALL-1042
Rate difference: expected $15, reported $12, difference −$3.
Evidence: applicable rate sheet and partner export.
Owner: operations lead. Next action: confirm which rate was applied.
Status: open. No payment conclusion has been reached.

A process someone else can run.

The output is a traceable comparison, an exception register and a clear next step for each unresolved item. Operational findings do not authorize payments or settle disputed terms.

Discuss your reconciliation workflow →

FOLLOW A FORMULA
Useful methods. Thoughtful work. Always improving.

Reconcile calls. Explain the differences.