Automating Multi-Channel Commission Payouts for a Driver-Sourcing Network
A leading pan-India fleet management company sourcing driver-partners through a mixed acquisition network.
Where things stood
To grow its driver-partner base, the company sources new drivers through several parallel channels — third-party sourcing vendors, in-house field sales staff, franchise partners running physical onboarding centers, and rural-market-focused vendors — each earning commission at rates that vary by city, performance tier, vehicle model, and product type.
Calculating this by hand each week across multiple channels and a multi-dimensional rate structure was slow and error-prone: the manual process took three to four days each cycle, and any change to the underlying rate card risked breaking whatever manual process was in place.
What we built
MySQL/PostgreSQL source data (referrals, allocations, vendor master records) feeds a PostgreSQL analytics warehouse, through a daily rules-engine computation into weekly payout tables plus a summary view for the finance team.
How it works
TopN Analytics built an automated commission-payout engine that classifies each vendor into a performance tier — based on conversion volume, with a separate override for franchise partners — then looks up the correct payout rate through channel-specific logic: a bucketed rate table for standard leasing/EV conversions, a flat per-city rate for a drive-to-own product line, a model-and-year-based rate for another product, and an entirely distinct table for franchise partners.
On top of the per-conversion rate, a weekly milestone bonus rewards vendors who clear a volume threshold, with documented city-specific carve-outs. When the rate card was redesigned partway through the year, the engine was built with an explicit date-based cutover so historical calculations using the old structure remain correct alongside new ones using the redesigned rates.
What we delivered and learned
The payout logic supports at least five distinct commission structures under one engine rather than treating each acquisition channel as a separate one-off calculation.
The date-based rate-card cutover is a concrete example of the pipeline absorbing a real mid-project business change without manual patching.
What it's built on
Want the full picture?
We're happy to walk through the details, numbers, and trade-offs directly.