How an MLM Commission Engine Calculates Payouts (With Examples)

What are the stages of a commission calculation?

1. Event intake: a paid order or activation is received and validated.
2. Volume assignment: business volume (BV) or point value (PV) is attached to the event.
3. Volume propagation: volume is credited up the sponsor or placement tree.
4. Qualification checks: each potential earner's status, KYC, personal volume and rank are verified.
5. Rule application: percentages, pairing ratios, level limits and pool shares are applied.
6. Limits: caps, carry-forward and flush-out rules adjust the result.
7. Deductions: TDS, admin charges and other deductions are calculated.
8. Posting: net amounts are posted to e-wallets and every step is logged.

Event-driven vs batch calculation: what is the difference?

Most production systems combine both. MLM.ERP's engine credits event-driven income in real time and runs period-based income, such as pairing closings, pools and rank evaluation, on configurable schedules.

How do qualification rules work?

Qualification decides whether a member is eligible to receive a particular income in a period. Common conditions include:

• Active status: the member has made a qualifying purchase within the period.
• Personal volume: for example, at least 100 PV of own or retail orders this month.
• Direct sponsors: for example, at least one active member on each binary leg.
• Rank: deeper levels or certain bonuses unlock only at higher ranks.
• KYC approval: commissions may accrue but payouts are held until KYC is verified.

The engine must also decide what happens to income a member does not qualify for: whether it is lost, passed up to the next qualified member (often called compression or roll-up), or held for a grace period. This should be written into the plan and visible to members.

What are capping, flush-out and carry-forward?

• Capping limits earnings per period, per income type or per rank. It protects the company's payout ratio.
• Carry-forward keeps unmatched or unused volume for future periods, for example the stronger leg's surplus in a binary plan.
• Flush-out removes volume that exceeds a cap or that has been carried for too long, so it no longer counts.

Example 1: binary pairing with cap and carry-forward

Plan rules: 10% on matched BV, 1:1 ratio, daily cap of 1,000 matched BV, unmatched volume carried forward, volume above the cap flushed.

On day 2, 1,300 BV was matched but only 1,000 counted because of the cap. The 300 BV of matched volume above the cap was flushed from both legs, and the right leg's 500 unmatched BV carried forward.

How does rank evaluation work?

Ranks are usually evaluated at the end of a period against criteria such as personal volume, group volume, the number of qualified legs and maximum volume counted from any single leg. A common safeguard is a leg cap: no more than, say, 50% of required group volume may come from one leg, which encourages balanced teams. The engine should store each evaluation so that a member can see exactly why they did or did not reach a rank, and whether ranks are lifetime or must be re-qualified.

Example 2: unilevel with qualification and compression

Plan rules: level 1 pays 10%, level 2 pays 5%, level 3 pays 3%. Members need 100 PV personal volume to be paid. Compression is on, so inactive members are skipped.

Dev places a 200 BV order. His upline, in order, is Meena (active), Kiran (inactive this month) and Sara (active), followed by Tom (active).

• Meena is level 1 and qualified: 10% of 200 = 20 points.
• Kiran is inactive, so with compression he is skipped.
• Sara moves up to effective level 2: 5% of 200 = 10 points.
• Tom moves up to effective level 3: 3% of 200 = 6 points.

Without compression, Kiran's 10 points would be lost and Tom would receive nothing from this order. Both approaches are valid; the plan must state which applies.

How are TDS and admin charges deducted?

After gross commission is calculated, the engine applies deductions. Typical ones are tax deducted at source, an admin or processing charge, and in some plans a repurchase or product wallet allocation. The order and base of each deduction must be defined clearly, because it affects the net amount.

Example 3: deductions on a payout

Assume a member's gross commission for the period is 10,000 units, an admin charge of 5% and an illustrative TDS rate of 2% calculated on the gross commission, for a member with a valid PAN who has crossed the annual threshold.

• Gross commission: 10,000
• TDS at 2% of gross: 200
• Admin charge at 5% of gross: 500
• Net credited to wallet: 10,000 - 200 - 500 = 9,300

In India, commission has generally attracted TDS under Section 194H of the Income-tax Act, 1961, with a 2% rate from 1 October 2024, a threshold of ₹20,000 a year from 1 April 2025, and a higher rate where PAN is missing. The Income-tax Act, 2025 replaces the 1961 Act from 1 April 2026 and renumbers these provisions. As of 2026, verify the current rate, threshold and the correct deduction base with your CA. The software should let admins change these settings without code. See our compliance checklist for more on TDS and GST.

Why do idempotency and reconciliation matter?

Payment gateways send duplicate callbacks, users double-click and servers retry after timeouts. If the engine processes the same order twice, it pays twice. Idempotency means each event has a unique key and processing it again has no further effect. Combined with database transactions that post all ledger entries together or not at all, it prevents duplicate and partial payouts.

Reconciliation regularly checks that the numbers agree:

1. Total volume credited equals the volume of paid orders in the period.
2. Total commissions equal the sum of wallet credits.
3. Wallet balances equal credits minus withdrawals, transfers and deductions.
4. TDS deducted matches the tax report and the amounts deposited.
5. Refunded orders have matching commission reversals.

What should a commission audit trail record?

For every payout, the audit trail should show the source event, the rule and plan version applied, the input volumes, qualification results, caps and carry-forward applied, deductions, the resulting wallet entry, and who or what triggered it. When a member asks "why did I get this amount?", support should be able to answer from the record in minutes. MLM.ERP keeps this trail for every income type across its 20 supported plan types; see the features page and our plans library.

How do you test a commission engine?

• Build a small test tree with known positions and calculate expected results by hand.
• Cover edge cases: caps reached, inactive uplines, refunds, rank changes mid-period.
• Replay the same events twice to confirm idempotency.
• Run a full period and reconcile every total.
• Re-test after any plan setting change.

Choosing software? Our buyer's checklist includes the questions to ask about commission accuracy.

See these calculations happen live. Book a free demo of MLM.ERP, share your plan, and we will run your own examples through the commission engine with a full audit trail.