Roofing sales commission tracking: keep the calculation explainable

Commission disputes often begin with two people looking at different numbers. One person sees the signed contract, another sees collected revenue, and a third sees a job margin that changed after a supplier credit.

A useful commission record makes those differences visible. It shows the applicable policy, the inputs, the calculation, and the approval history for each job.

This guide explains the tracking workflow. It does not prescribe a commission rate or change the compensation agreements your business uses. Have the responsible people approve the policy before turning it into an automated calculation.

Start with the approved policy

Write down the policy’s effective date, the jobs it applies to, and the person responsible for resolving questions. Keep older versions when terms change. Applying today’s formula to a job governed by an earlier agreement can create a misleading result.

The record should answer four questions:

• What event makes an amount eligible for calculation?
• What amount is the calculation based on?
• Which rate or split applies to this person and job?
• What approval is required before payment is recorded?

Separate the calculation from the decision that a payment is due. An estimated amount, an approved amount, and a paid amount are distinct states in the workflow. Use the definitions your team has agreed to rather than letting a software label redefine them.

Define the calculation base precisely

Common business models use contract revenue, collected revenue, or a form of job profit as the base. The important tracking requirement is to identify the chosen base and its inputs, not to assume one model works for every company.

If the policy uses profit, state which costs are included. Material costs, crew costs, and other job expenses may arrive at different times. Mark estimates as estimates and show when the inputs were last updated.

Consider this hypothetical example:

Input	Illustrative amount
Collected job revenue	$20,000
Materials included in the calculation	$6,000
Crew costs included in the calculation	$4,000
Other included job costs	$2,000
Defined calculation base	$8,000

If an illustrative policy applies 30% to that $8,000 base, the calculated amount is $2,400. The percentage is only for demonstrating the arithmetic; it is not a recommended rate or an industry benchmark.

The example is explainable because the base, costs, and rate are explicit. “Commission: $2,400” without the inputs gives the reviewer very little to verify.

Attach the calculation to the job and person

Use stable job and salesperson identifiers. Names alone can create ambiguity when two people share a name or a job is renamed.

For each calculation, retain the policy version, relevant dates, source records, formula inputs, and result. If more than one person shares a commission, record the approved allocation and the amount assigned to each person.

Check that the allocations match the policy. A split of an existing commission pool and two independently calculated commissions are different arrangements. The tracking system should not silently treat them as the same thing.

When a job changes ownership or a representative leaves a team, route the policy question to the responsible reviewer. Preserve the record rather than overwriting the original assignment without explanation.

Make adjustments visible

Job costs can change as deliveries, returns, credits, and corrections are recorded. Show which input changed and how that change affected the calculation.

Continuing the hypothetical example, suppose an approved $200 material credit changes included material cost from $6,000 to $5,800. Under the same illustrative formula, the base becomes $8,200 and the calculated amount becomes $2,460. The difference is $60.

That arithmetic alone does not authorize an additional payment. The workflow still needs the review and treatment defined by the applicable policy. Keep the prior result, new result, reason, source document, and approval together.

An unexplained replacement value creates confusion. A visible adjustment gives the salesperson and the reviewer the same record to discuss. For the document checks behind material adjustments, use the supplier invoice verification checklist.

Track calculation, approval, and payment separately

Use a small set of explicit statuses that match your operation. For example: awaiting inputs, calculated, under review, approved, and payment recorded.

Each transition should have an owner and a timestamp. A reviewer needs to know whether an amount is waiting on a final invoice or waiting on approval. A salesperson needs to know which question is unresolved and who can answer it.

When payment is recorded, link the payment reference and amount to the approved calculation. Reconcile partial payments or later adjustments with the record instead of marking the entire amount paid after the first transfer.

Access matters too. Let people see the information needed for their role, and restrict who can change policy settings or approve amounts. A shared spreadsheet with unrestricted editing makes it difficult to distinguish a correction from an accidental change.

Check the handoffs between systems

AccuLynx describes commission configuration within job files in its commission workflow guide. If it is your job system, begin by reviewing the configuration you already have.

Hibe’s sales commission workflow and AccuLynx integration should be evaluated against that setup. Confirm where the authoritative policy lives, which job inputs are read, where a calculation appears, and who approves the next action.

Do the same for accounting records. A calculation appearing in one tool does not prove that payment has been recorded in another. Verify the link with a real job before expanding the workflow.

Review a few jobs from start to finish

Pick a completed job, an unfinished job with estimated costs, and a job with a correction. For each, ask a reviewer to reconstruct the calculation from the saved inputs and policy version.

Check whether the salesperson can understand the amount without a separate explanation. Then confirm that approval and payment evidence are visible and that the same job has not been calculated twice.

Track unresolved questions, adjustments awaiting review, and the time between a complete calculation and approval. Avoid treating a lower question count as success if people cannot inspect the records.

An explainable process gives everyone the same starting point. Talk with Hibe about your current policy, job records, and approval steps to see how the workflow could fit your team.