How tiered lead pay actually works in a BPO payroll run

Most BPO payroll disputes are not about the rate — they are about trust. An agent who watched a live lead counter all month expects the payslip to match it. When a spreadsheet recalculates pay with a different rule than the dashboard, that trust evaporates and finance spends days reconciling.

Zivo solves this by computing tiered lead pay from a single precedence chain that both the live preview and the official payroll run share. There is exactly one source of truth.

The precedence chain

When Zivo resolves the rate for a single lead, it walks a fixed order and stops at the first match:

• Employee-level override for the campaign and lead type
• Campaign + lead-type band (the tiered slab table)
• Campaign default rate
• Organization default rate

Why preview equals payout

The dashboard preview does not estimate. It calls the same resolver the payroll engine calls, with the same inputs. The only difference between a mid-month preview and the final run is that more days of lead counts have accrued.

That single design choice removes the most common reason BPO agents distrust their pay, and it removes the reconciliation pass that finance teams dread.