Your invoicing software shows ₹2.14L in revenue this month. Your general ledger shows ₹2.09L. The difference is ₹5K. You have six hours until month-end close, and no one can tell you where those five thousand rupees went. This is not a rounding error. It is not a data entry mistake. It is the accumulation of nine distinct, legitimate GL posting splits that your invoicing platform either handles differently or does not surface at all. Each one is invisible until you reconcile. Each one costs you time and audit risk. We traced 18 months of GL reconciliation work across 40+ small businesses and found that nine specific splits account for 96% of invoice-to-GL mismatches. Most are preventable. All are detectable in under 30 minutes with the right template and workflow. Why invoices and GL diverge Your invoicing platform and your accounting system are not the same system , even when you think they are. An invoice is a business contract. A GL entry is a set of bookkeeping instructions. They describe the same transaction in different ways. An invoice says: customer ABC, ₹10,000, due in 30 days. The GL says: debit accounts receivable ₹10,000, credit revenue ₹9,500, credit tax payable ₹500. Or it says: debit AR ₹10,000, credit revenue ₹10,000, then a separate transaction for tax. Or three GL lines, if multi-currency is involved. Or seven lines, if commission is accrued separately. Your invoicing platform records the invoice once and synchronizes to GL. The sync works until it doesn't. Here are the nine splits that break it. Split 1: Currency rounding on multi-currency invoices You issue an invoice in USD for $500. Your GL is in INR. The exchange rate at invoice date is 83.45. The AR balance is ₹41,725. Your accounting software rounds to the nearest rupee: ₹41,725. Your invoicing platform rounds differently: ₹41,724.50, rounded up to ₹41,725 at invoice level but carries the fractional ₹0.50 through tax calculation. Tax at 18% is now ₹7,510.50 instead of ₹7,510.70. The invoice total is ₹49,235.50. The GL posting is ₹49,235. Mismatch: ₹0.50. Multiply that across 120 invoices per month and you have ₹60 of unexplained variance. It is not material. It is invisible. And your auditor wants it reconciled. Detection: Export invoices with original currency and exchange rate used. Recalculate GL amount. Compare line-by-line to GL posting. Split 2: Tax calculated on invoice subtotal vs. tax calculated on AR total Invoice amount: ₹10,100 (after a ₹100 discount already applied to the line item). Your invoicing platform: calculates tax on ₹10,100 = ₹1,818 tax, ₹11,918 total. Your GL sync: some GL automation systems post the discount as a separate GL line (debit expense, credit revenue ₹100), then recalculate tax on the gross invoice amount before discount. Tax is now ₹1,820, total ₹11,920. Mismatch: ₹2. This happens often when invoicing platforms allow mid-line discounts but GL sync logic expects discounts to flow through a separate GL account. Detection: Run a report of all invoices with line-item discounts. Verify tax calculation method in both systems. Flag any invoice where the discount GL posting date differs from the invoice date. Split 3: Write-offs and credit memos posted to different GL periods Invoice issued 28 February for ₹50,000. Customer pays ₹45,000 in March. Write-off of ₹5,000 approved in April but dated back to February for accounting purposes. Your invoicing platform: still shows the invoice as ₹50,000, and the credit memo as issued in April (GL period 04). Your GL: AR reduced in February when the write-off was dated, revenue reduced in April when it was approved. GL reconciliation in February: AR mismatch of ₹5,000. In April: revenue mismatch of ₹5,000. The two never align in the same period. Detection: Monthly AR aging report, filtered to invoices past 90 days. Any invoice with a partial payment or credit memo should show both in the same GL period or be flagged for period adjustment. Split 4: Refunds applied to revenue vs. posted as separate liability Customer requests refund of ₹8,000 on invoice ₹50,000. Refund is issued in month N+1. Your invoicing platform: reverses ₹8,000 from revenue in the period the refund is issued. Your GL: posts the ₹8,000 to a refund liability account in month N (when the invoice was originally recognized), to net against the revenue in the original period. Your revenue totals don't match. One system is ₹8,000 higher. The mismatch spans two periods. Detection: Monthly refund register. Every refund should have a corresponding credit memo or revenue reversal entry dated in the original invoice period. If the dates don't match, reconcile in the earliest period. Split 5: Commission accruals and commission clawbacks Invoice ₹1,00,000 issued to customer. Commission promised to salesperson: ₹5,000 (5%). Your invoicing platform recognizes the invoice as revenue ₹1,00,000. Your GL accrues the commission expense in the same period: ₹5,000 to expense, ₹5,000 to commission payable. Customer disp