You post an invoice in your CRM. You reconcile it against your general ledger the next day. The totals match—line by line, tax included, payment received. Three weeks later, the auditor flags a discrepancy in your revenue GL account. When you trace back, you find that single invoice has been split across nine different GL codes. The revenue line went to 4100. Tax split between 2200 and 2205. Discount landed in 5050. Shipping hit 4500. The customer's withholding posted to a liability account you forgot existed. Nothing broke. Nothing errored. It all reconciled perfectly. Until it didn't. This is not a theoretical problem. It happens to most businesses running multi-country tax treatment, tiered discounts, or mixed billing models—and it happens silently. The invoice total matches the sum of GL postings. But the distribution of those postings across your chart of accounts is scattered, hard to audit, and vulnerable to both human error and compliance drift. This guide maps the nine most common GL splits, shows you why they diverge, and gives you a 90-minute audit checklist to catch them before your finance team—or a regulator—does. The nine GL splits that hide inside a single invoice Start with a real case: a B2B SaaS company invoices a Singapore customer for ₹1,00,000 annual license, with a 10% volume discount, plus shipping to Malaysia, and payment in two tranches with withholding tax. On the invoice, the customer sees one line item. In your GL, it becomes this: Revenue (primary): ₹90,000 to GL 4100 (Software License Revenue) Revenue (secondary tier): If tiered pricing applies, ₹15,000 might split to GL 4110 (Premium Support Revenue) Discount: ₹10,000 debit to GL 5050 (Customer Discounts) Shipping: ₹2,500 to GL 4500 (Service Revenue) or GL 4005 (Shipping Revenue) Sales tax (Singapore GST): ₹5,600 to GL 2200 (Sales Tax Payable) Tax withholding (customer-side, Malaysia rule): ₹9,000 to GL 2205 (Customer Withholding Payable) Currency adjustment (if invoiced in SGD, posted in INR): ₹300 gain or loss to GL 7100 (Foreign Exchange Gain/Loss) Payment terms discount: ₹2,000 early-pay incentive to GL 5051 (Early Payment Discount) Reversal or correction from previous month: ₹−500 reversal of accrual to GL 1200 (Accrued Revenue) Nine GL codes. One invoice. The invoice itself is perfectly clean. The posting is perfectly correct per your tax and accounting rules. But the split is real, the audit trail is fragmented, and if any one of those nine postings is wrong—wrong code, wrong amount, wrong sign—your reconciliation looks balanced while your actual revenue recognition is broken. Where divergence happens: the five structural failure points GL splits fail at predictable moments. Understanding where they break helps you audit faster. 1. Multi-country tax treatment Your customer is in Singapore, but you ship to Malaysia. Singapore uses GST; Malaysia uses SST. If your invoicing system uses the customer's country (Singapore), it posts GST to 2200. But if your fulfillment system uses the ship-to address (Malaysia), it posts SST separately to 2206. The invoice shows one tax line. Your GL shows two. This divergence is correct per tax law but easy to miss during reconciliation because most people scan by invoice number, not by GL code. 2. Discount application order Does your discount apply before or after tax? Most tax authorities say before. But if your invoicing system applies it after, or if you manually adjust after the fact, the discount amount in your GL won't match the line-item discount on the invoice. The total reconciles, but the composition is wrong. 3. Deferred revenue and accrual splits If you invoice annually but recognize revenue monthly, the GL split is automatic: one posting to Deferred Revenue (liability), then nine reversals over the following 12 months (one for each month's revenue). Most accounting systems handle this correctly, but if you invoice mid-month or use a custom billing schedule, the GL split can drift. One month you accrue ₹7,500; the next month ₹7,485. Over a year, the drift accumulates, and by audit time, you're chasing ₹180 of unexplained variance. 4. Payment method splits (for complex payment terms) If a customer pays half now and half in 30 days, some systems post both to revenue immediately (and create an AR accrual). Others defer the second half. If one invoice is split between two payment methods—50% credit card, 50% bank transfer—and your system records the two payments in different periods, your GL split diverges from the invoice date, creating a timing mismatch that reconciliation flags as an error even though it's technically correct. 5. Affiliate or commission reversal If a customer pays through an affiliate link, your invoicing system might post the full amount to revenue, then post a simultaneous reversal (or reduction) to account for the affiliate commission. The invoice shows the net amount to the customer. The GL shows gross revenue plus a commission expense. They reconcile in tot