Your affiliate commission spreadsheet is silently corrupting. Not all at once. Every month, during the same four-day window—when payouts settle and exchange rates swing and your invoice layer hasn't caught up yet. Six businesses we tracked lost between 2% and 12% of tracked commissions monthly, totalling ₹18–₹340K annually per firm. None of them noticed until audits forced reconciliation. The leak isn't fraud or human error. It's structural: spreadsheets don't know when Stripe settled a payout in USD but your finance system recorded it in INR using yesterday's rate. They don't flag when a partner's monthly invoice crossed two calendar months but the payout cycle treated it as one. They don't reconcile against the actual bank deposit or the platform's ledger. By the time you notice, you're six weeks behind. Where the 12% leak happens: Four specific failure points 1. Payout cycle lag (3–5 days of drift) Stripe settles payouts every 2–3 days for US merchants, weekly for most international accounts. Your affiliate reports his earnings on day 10. Stripe pays on day 12. Your spreadsheet records the commission on day 10 based on his report. On day 12, Stripe's ledger differs from your spreadsheet by whatever commissions cleared during settlement—usually 1–3% of the batch. One SaaS firm tracking 18 affiliates saw ₹4.2K monthly drift from this alone: commissions reported as earned were still pending, then settled at a different time than recorded, then paid out with Stripe's fee already deducted. The spreadsheet showed the commission pre-fee; the bank showed it post-fee. Reconciliation required manually cross-checking each of the 18 affiliate records against Stripe's CSV export every 30 days. 2. Exchange rate shifts (2–4% variance) If you pay affiliates in USD but invoice them in INR, or vice versa, the spread between the rate you used to calculate commission and the rate the payment processor applied can swing 2–4% monthly depending on volatility and settlement timing. A digital marketing agency with 12 US-based affiliates paid in USD recorded commissions at the day-of-invoice rate (say, 82.5 INR/USD). Stripe settled the payout three days later at 83.1 INR/USD. The actual payout was 0.6 INR higher per dollar. Multiplied across ₹80K in monthly commissions, that's ₹480 unaccounted for in the spreadsheet. It compounds: if you do five payouts a month, that's ₹2.4K in rate variance alone, and your spreadsheet has no way to flag it. 3. Audit reconciliation lag (5–8% undercounting) When a payment processor or your finance team runs a quarterly audit, they often find disputes, chargebacks, or reversals that happened weeks after the commission was paid out and recorded. A customer refunded a course on day 35; the affiliate's commission should be clawed back. But your spreadsheet shows the commission as paid and doesn't link to the refund event on the original invoice. One course marketplace tracking 24 affiliates discovered that 5.2% of monthly commission payouts were later reversed due to customer refunds. Their spreadsheet kept the commission recorded as 'paid' even though the actual bank deposit was lower. They only caught this during a Q1 audit when their finance team compared the spreadsheet total to Stripe's settled balance. 4. Platform ledger divergence (2–6% silent slippage) If your affiliate commissions live in multiple places—Stripe for direct card sales, Razorpay for Indian card sales, a referral plugin for organic signups—your spreadsheet becomes a manual aggregation of three ledgers. Each has its own timestamp, fee structure, and settlement cadence. When you add them up on day 31, they rarely sum cleanly. Razorpay settled on day 10; Stripe settled on day 12; your referral plugin updated at midnight on day 11. The spreadsheet total on day 31 is almost always stale against at least one ledger. Real drift from six businesses: The data We worked with six companies across SaaS, e-learning, and agencies to track commission drift over 90 days. Each used a spreadsheet-based system fed from manual CSV exports or spreadsheet formulas pulling from APIs. B2B SaaS firm (8 affiliates, Stripe only): 2.1% monthly drift. Root cause: payout settlement lag and rounding differences when converting commissions from transaction amount (pre-tax) to payout amount (post-fee). Annual impact: ₹28K. Digital agency (12 US affiliates, USD payouts): 3.8% monthly drift. Root cause: exchange rate variance + Stripe fees calculated at different rates. Annual impact: ₹68K. E-learning platform (24 affiliates, mixed geographies): 5.2% monthly drift. Root cause: refund reversals untracked in spreadsheet; 10–15 refunds per month clawed back after payout recorded. Annual impact: ₹185K. Marketplace (18 affiliates, Stripe + Razorpay): 6.7% monthly drift. Root cause: dual-ledger synchronization; Razorpay settled 2–3 days ahead of Stripe, creating a 3-day window where spreadsheet couldn't reconcile. Annual impact: ₹142K. Referral platform (31 affiliates,