Pull fifty invoices from your billing platform. Export the same fifty from your accounting software. Compare totals. Odds are high you'll find money missing. Not fraud—just drift. A rounding error here, a manual write-off there, a tax recalculation nobody logged back. By month six, most teams discover invoices totalling ₹2–3L have silently diverged from their GL, and nobody can explain why without digging through six different system logs. The gap isn't a bug. It's the architecture. Billing platforms and accounting systems aren't designed to be twins—they're designed to move fast and stay flexible. They sync on opposite schedules, calculate tax differently, handle refunds in separate loops, and neither one is the source of truth until someone decides to make it so. That someone is you. The nine sync breaks that create divergence Invoice totals split at predictable points. Once you know them, you can audit for them, and once you audit, you can build a rule to catch them next month. 1. Tax calculation timing Your billing platform calculates tax at invoice creation. Your accounting software recalculates it at GL posting. GST rates change. A 5% invoice becomes 8% in transit. Some platforms round per-line, others round at the total. Difference: 0–2% of invoice value, usually under ₹500 per invoice, but compound it across 500 invoices and you've lost ₹2.5L. 2. Currency conversion slippage Multi-currency invoices are reconciliation nightmares. Billing platform locks the exchange rate at invoice date. Accounting software re-rates at GL posting. Between the two, spot rates drift 0.5–2%. On a ₹50L invoice in USD, that's ₹15K–₹30K unaccounted for. Most teams don't catch this until the bank deposit clears. 3. Manual write-offs and adjustments A customer disputes a line item. Finance adjusts it in the GL but never updates the source invoice in billing. Or vice versa: billing shows adjustment but GL doesn't reflect it yet because it's in a pending reversal journal. Typical drift: 1–3% of total invoice value. 4. Refund reversals not synced back A refund posts to accounting. The original invoice in billing still shows as fully paid. Reconciliation looks balanced in each system—until you try to match them. The billing total includes the refund; the GL doesn't. Drift: full refund amount, usually ₹5K–₹50K per incident. 5. Batch posting delays Billing creates invoice daily. Accounting posts to GL in batches, usually weekly or on month-end. For 5–25 days, the systems are out of sync by design. Most teams work around this by freezing their invoice exports on the GL posting date—but if a billing invoice is created after that freeze and before GL posting, it orphans. 6. Line-item tax breakdowns Billing platform shows invoice total with GST embedded. Accounting software separates GST into a tax liability account. The line items are identical, but the invoice total in billing doesn't match the sum of taxable amount + tax in accounting. Drift: typically 0–1% but conceptually confusing, which is where manual errors creep in. 7. Partial payment and credit tracking A customer pays half an invoice now, half next week. Billing marks it as partial. Accounting hasn't received the second payment yet, so GL shows it unpaid. Or a credit from a prior month is applied: billing shows net ₹50L; GL shows ₹70L invoice with ₹20L credit applied separately. Total is identical, but the line items don't match. 8. Invoice reversals and cancellations You cancel an invoice in billing. A reversal entry should post to GL. Sometimes it doesn't post immediately, or it posts to a different GL account, or it posts with a different date, making it hard to match the pair. Billing total: ₹0 (cancelled). GL total: ₹0 (invoice + reversal), but the two ₹0s are made from different components. 9. Dormant and archived invoice states Some invoices sit in 'draft' status in billing and never reach accounting. Others are marked 'sent to client' in billing but never post to GL because they don't meet accounting's criteria (e.g., no PO number in mandatory field). These invoices are real in billing but invisible in accounting, creating silent gaps in both directions. Running your spot audit: 50-invoice framework Pick the last fifty invoices created in your billing platform. Use a consistent date range—ideally 30–60 days ago, so enough time has passed for all GL posting to complete. Create a simple spreadsheet: Invoice ID from billing system Total in billing Total in accounting GL Difference (amount and %) Root cause (which of the nine sync points above) Owner (who fixes it) Fix status (pending / resolved) Pull the billing invoice totals first—this is your baseline. Then match each one to the GL entry by invoice number. If you can't find a match, note it as 'missing in GL' or 'missing in billing' and investigate whether it's a timing delay or a process break. Most teams find: 0–5% of invoices have no discrepancy 5–10% have minor drift (<₹1,000) 3–8% have moderate drift (₹1K–₹1