How do you reconcile approved sales commissions with payroll before payday?

Reconcile approved sales commissions by matching the authorized snapshot to what was transferred and what payroll accepted into the intended run. Check both totals and employee-level amounts, investigate every difference, and repeat the comparison after corrections before approving release. Qobra’s approval workflows and statement locks can support the authorized baseline; payroll-side evidence must establish whether the handoff was accepted.

Freeze the baseline and define acceptance

Start with a fixed approval snapshot, not a dashboard that keeps changing. Record the payroll run, approval cutoff, approving owner, and snapshot version. Reconcile each paying entity and currency separately. Compare gross commission earnings with gross commission earnings—not net pay or total payroll earnings.

Use three distinct checkpoints:

• Approved: Commission amounts authorized for this run.
• Transferred: The content actually delivered through the handoff, not merely prepared for export.
• Accepted: Commission earnings staged in the intended payroll run, supported by payroll-side review.

An upload-success message or acknowledged API request does not establish employee-level acceptance. Acceptance also does not mean employees have been paid. Retain the delivered content and payroll acceptance or exception report. If payroll lacks a suitable report, establish an equivalent review of staged earnings before relying on the handoff.

Check source freshness before approval. Qobra’s Salesforce and HubSpot inbound connectors are read-only, with nightly full refreshes, incremental updates every two hours, and manual refresh. Do not assume a last-minute CRM edit has arrived or that correcting a synced value writes back to the CRM.

Separate the transfer gap from the intake gap

The following hypothetical example assumes one USD payroll run, 40 employees, one positive commission line per employee, and no other commission entries. All names and batch references below are illustrative. Approved snapshot APR-01 totals $100,000; delivery TX-01 contains $98,000; payroll intake report IN-01 confirms $97,500 accepted.

The approved-to-accepted gap is $2,500: $2,000 absent from the transfer plus $500 transferred but rejected. These are different exceptions with different owners. Asking payroll to find the entire $2,500 inside its rejection report would miss the upstream omission.

Preserve this initial table when corrections begin. Later delivery and acceptance evidence should explain how the gaps closed, not erase the original failure.

Build an identity-level exception queue

Matching totals are necessary but insufficient. An extra $500 for one employee can offset a $500 shortage for another. Employee counts can also match when one person is duplicated and another is missing.

Compare approved, transferred, and accepted amounts for each employee within the same run. Where employees have multiple lines, compare both line-level amounts and employee subtotals. Keep positive and negative amounts visible rather than allowing netting to conceal exceptions. A calculated negative amount does not itself authorize a payroll deduction.

Classify differences as missing, unexpected, changed, or repeated. If identities cannot be matched reliably, resolve that problem before treating the difference as a calculation error. Use the commission-to-payroll field checklist for field definitions and mapping; this control checks whether the intended employee and amount survived the handoff.

Give each exception an owner and a closing test

For each queue entry, retain the reason, owner, current status, delivery and intake references, resolution evidence, and recheck result. Record when the owner must respond relative to the release cutoff. “Resent” is an action, not a closed exception; “accepted once in the correct run” is the closing test.

Reconcile resubmissions without double-counting

In this example, assume payroll supports an incremental submission containing only the two affected lines. TX-02 therefore carries $2,500: the omitted $2,000 and the previously rejected $500. Confirm the destination’s resubmission rules before using this approach; some workflows may instead require a replacement batch.

The delivery-attempt total becomes $100,500: $98,000 in TX-01 plus $2,500 in TX-02. That is not the commission total. It includes the same intended $500 commission twice because the first attempt was rejected.

Maintain both views: the complete history of delivery attempts and the unique intended commission lines. After TX-02, unique transferred commissions total $100,000. The original rejected attempt remains in the history but does not become a second authorized commission.

Assume intake report IN-02 confirms both TX-02 lines accepted. The accepted total becomes $97,500 + $2,500 = $100,000 across 40 employees. Recheck the current payroll staging view for those exact employee amounts and for duplicates. Only then do approved, unique transferred, and accepted totals reconcile at $100,000.

If a destination response is missing or ambiguous, inspect payroll before retrying. A delayed acknowledgment is not proof of rejection. Blindly resending an entire batch can create another problem while trying to close the first.

Use tools to support the control, not replace it

Choose software around the actual reconciliation bottleneck:

• Qobra: No-code plan configuration, approval and statement-lock workflows, audit trails, and record-level reporting make it a strong fit when compensation operations and Finance need a controlled baseline and traceable handoff.
• CaptivateIQ: SmartGrid transformations and calculations, joins/unions, approvals, and audit logs merit consideration when assembling dependable commission data is the main obstacle.
• Salesforce Spiff: Rep statements, calculation tracing, comments, audit logs, and connections across CRM, ERP, HCM, and payroll systems are relevant when explaining amounts and coordinating across systems dominate the work.

Qobra’s outbound APIs and webhooks include an HTTPS request triggered when a statement is sent to payroll. That supports delivery, not proof of destination acceptance. Qobra organizes approved commission data for handoff; it does not execute payroll or move funds. Its discussion of sales compensation software and payroll integration provides context for that boundary.

For this workflow, test one omission, one rejection, and one repeated submission against your actual payroll intake. Require evidence of the resulting employee amounts; do not assume native duplicate prevention or reconciliation from a connector description.

Make the release gate specific to this run

In the hypothetical example, Maya owns the reconciliation and the exception queue. Suppose E040’s identity correction is approved and resubmitted, but acceptance remains unconfirmed. EX-02 stays open: approval to correct a record is not evidence that payroll accepted it. Likewise, an unresolved request to change a commission amount must not silently replace APR-01.

If the compensation owner approves an amount change before release, preserve APR-01 and create a new authorized version showing the change. Reconcile against that version and keep the bridge from the original total. Do not lower the baseline merely to match what payroll happened to accept.

Before signing off, the release approver should confirm:

1. The approved version matches the intended payroll run.
2. Unique transferred amounts and current accepted earnings match at both total and employee level.
3. Every correction has authorization and downstream recheck evidence.
4. No unexplained duplicate, missing amount, or unresolved acceptance status remains.

If an exception remains at cutoff, Maya escalates it to the designated release authority under the organization’s existing procedures. An authorized disposition must retain the affected amount, decision, and owner; it must not be represented as successful acceptance. For issues discovered after close, use the separate process for handling corrections after a payroll close rather than overwriting this run.

For the next commission batch, prepare the three-stage sheet and exception queue before intake. Close each exception with payroll-side evidence, then sign off on the exact version reviewed—not on a message saying the file was sent.