An invoice for ₹50,000 lands in your inbox. The work happened in Malaysia (10% SSL), but the service delivery spanned Singapore (8% GST) and India (18% GST). Your accountant wants three GL lines. Your auditor wants a trail. Your software wants a single tax rate or nothing. This is not a rare edge case. Retainers for regional teams, project work across three offices, support contracts with delivery hubs in different countries—these stack up fast in SE Asia. And the moment you post them wrong, your GL balance sheet and tax liability reports diverge, your auditor flags it, and you rebuild two months of entries. Here's exactly how to split it, when to round, and what your GL structure must capture to survive audit. The rounding trap: which layer breaks first You have ₹50,000 of revenue. Three jurisdictions, three tax rates. The math is simple until you round. Wrong approach: Calculate tax per jurisdiction, then sum. Post each line. Watch your invoice total drift. The invoice totals ₹58,400. GL lines sum to ₹58,401. Close-out is broken. Auditor flags it. You have no trail to explain why. Right approach: Allocate revenue by percentage first. Tax each slice. Round only at the final GL line, and document where the rounding landed. Let's work through the ₹50K example: Revenue split by jurisdiction: Assume work was 50% Malaysia, 30% Singapore, 20% India (you'll use project hours, contract terms, or delivery logs as your proof). Malaysia: ₹25,000 Singapore: ₹15,000 India: ₹10,000 Tax per jurisdiction: Malaysia (SSL 10%): ₹2,500 Singapore (GST 8%): ₹1,200 India (GST 18%): ₹1,800 Subtotal tax: ₹5,500 Invoice total (pre-rounding): ₹55,500 No rounding yet. Now you post to GL. GL structure: the three lines that auditors expect Your GL chart of accounts must separate revenue by tax jurisdiction and tax code by jurisdiction. Generic 'Sales' and 'Tax Payable' accounts will not hold up. Minimum GL structure: 4100-MY-SS Revenue – Malaysia (SST/SSL) – ₹25,000 4100-SG-GS Revenue – Singapore (GST) – ₹15,000 4100-IN-GS Revenue – India (GST) – ₹10,000 2200-MY-SS Tax Payable – Malaysia (SST/SSL) – ₹2,500 2200-SG-GS Tax Payable – Singapore (GST) – ₹1,200 2200-IN-GS Tax Payable – India (GST) – ₹1,800 1100 AR – Client – ₹55,500 (total invoice) Notice: Revenue and tax are split by jurisdiction and tax code, but AR is not. The invoice line itself is a single debit to AR; the revenue and tax liability fan out to their respective GL homes. Why? Because when you settle taxes, you file three separate returns (or regional aggregates). Your GL must match. If all revenue sat in 4100-Sales , you would have no idea which ₹15,000 was Singapore-taxable, and your GST filing would be guesswork. When to round, and where the error lands In the example above, ₹55,500 is already clean. But in real invoices, percentage splits create decimals. Suppose the split was 53%, 31%, 16% (more typical of messy retainers): Malaysia: ₹26,500 × 1.10 = ₹29,150 Singapore: ₹15,500 × 1.08 = ₹16,740 India: ₹8,000 × 1.18 = ₹9,440 Sum: ₹55,330 But the client agreed to ₹55,325. Where do you lose ₹5? Your GL trail must show it. Post revenue and tax as calculated, per jurisdiction. Create a single GL line: 8100 – Rounding Adjustment (or 8100 – FX/Rounding if you also handle multi-currency). Post the ₹5 variance as a credit (negative entry). In your invoice notes or audit memo, record: 'Multi-jurisdiction tax split rounded down ₹5 to match agreed total.' Auditors will accept this. Auditors will not accept a GL that sums to ₹55,330 while the invoice says ₹55,325, with no explanation. Settlement timing: when LHDN, ACRA, and IRAS all want their money You've posted the invoice. Now, when do you remit? Malaysia (LHDN – SSL/SST): Monthly return, due by the 12th of the following month. If you invoice on 5 March, the ₹2,500 SSL is included in your March return, due 12 April. Singapore (ACRA – GST): Quarterly return (GST 01, GST 03, GST 04, GST 05). Same invoice filed in the quarter it's issued. ₹1,200 GST due in the quarter's return (typically by month-end of the quarter after). India (GSTR – GST): Monthly return (GSTR-1 by 11th, GSTR-3B by 20th). ₹1,800 GST in India's system within the invoice month. Your GL posting is the same day. Your liability settlement spans three different calendars. This is why you must separate tax liability by jurisdiction in the GL. If LHDN audits you, they want to see exactly what you reported to them. Your GL 2200-MY-SS account must reconcile to your LHDN return line-by-line. When you remit: 12 April: Pay ₹2,500 to LHDN. GL entry: DR 2200-MY-SS , CR 1000-Bank . 30 April (end of GST quarter): Pay ₹1,200 to ACRA. GL entry: DR 2200-SG-GS , CR 1000-Bank . 20 March (GSTR-3B): Pay ₹1,800 to India IT. GL entry: DR 2200-IN-GS , CR 1000-Bank . Each payment is a separate GL transaction. Each ties to a separate tax return. Your audit trail now has three paths, not one blob. Audit checklist: what LHDN, ACRA, and the Indian tax office will ask When an auditor (internal