Prorate tax SST PPN GST three countries invoice

Q: What if my invoicing platform doesn't support per-region prorating?

Calculate the proration and tax externally (use the formula above), then create three separate line items on one invoice, each with its region, revenue amount, and tax rate. Most platforms allow custom line items. This preserves audit clarity without requiring native multi-region support.

Q: Do I need three separate invoices for Malaysia, Indonesia, and Singapore?

No. One invoice with three line items (one per region, each with the correct tax rate) is cleaner, less confusing to the client, and easier to reconcile. The GL split happens internally; the invoice remains unified.

Q: How do I handle currency if the retainer is in USD but invoiced to three countries?

Convert the USD amount to the local currency (INR, MYR, IDR, SGD) on the invoice date. Apply the exchange rate consistently across all three regions so the total reconciles. Document the exchange rate in your invoice metadata for audit purposes.

Q: What if work in one region extends beyond 90 days?

The proration formula remains the same: (revenue allocation × percentage × days worked ÷ total contract days). If Indonesia work runs 100 days instead of 45, recalculate: ₹3,00,000 × 35% × (100 ÷ 90) = ₹1,16,666.67. This shows revenue recognized across quarters, which is correct under accrual accounting.

A client in your books pays a ₹3,00,000 quarterly retainer. Work is split: 40% in Malaysia (SST), 35% in Indonesia (PPN), and 25% in Singapore (GST). On day 45 of the 90-day quarter, they ask to pause the Indonesia engagement. Now you need one invoice that prorates revenue, calculates three different tax regimes, and splits the general ledger so your auditor doesn't have to reconstruct it. This is not a theoretical problem. Multi-country retainers are common in tech, consulting, and managed services across Southeast Asia. Most invoicing platforms either force you to create three separate invoices (which confuses the client and breaks your revenue recognition) or let you create one invoice with a single tax rate (which is wrong on two-thirds of it). Here's how to prorate one invoice correctly, calculate blended tax, split the GL, and prove it reconciles. The Math: Prorate by Region, Then Apply Each Tax Rate Start with the gross retainer amount and the time period. Then allocate by region and apply each jurisdiction's tax rate. Step 1: Calculate the daily rate and time prorated. Quarterly retainer: ₹3,00,000 for 90 days Daily rate: ₹3,00,000 ÷ 90 = ₹3,333.33/day Days worked (full quarter): 90 days Days worked (post-pause, Indonesia stops): 45 days Step 2: Allocate by region for the full 90 days, then prorate the Indonesia portion to 45 days. Malaysia (40%, all 90 days): ₹3,00,000 × 40% = ₹1,20,000 Indonesia (35%, prorated to 45 days): ₹3,00,000 × 35% × (45 ÷ 90) = ₹52,500 Singapore (25%, all 90 days): ₹3,00,000 × 25% = ₹75,000 Subtotal (revenue before tax): ₹1,20,000 + ₹52,500 + ₹75,000 = ₹2,47,500 Step 3: Apply the correct tax rate in each jurisdiction. As of 2024–2025, standard rates are: Malaysia SST 6%, Indonesia PPN 11%, Singapore GST 9%. Malaysia: ₹1,20,000 × 6% = ₹7,200 Indonesia: ₹52,500 × 11% = ₹5,775 Singapore: ₹75,000 × 9% = ₹6,750 Total tax: ₹7,200 + ₹5,775 + ₹6,750 = ₹19,725 Invoice total: ₹2,47,500 + ₹19,725 = ₹2,67,225 Building the Invoice: Line Item Transparency Do not hide the tax in a single rate. Your client needs to see why each region's tax is different, and your auditor needs a clear audit trail. Golden rule: One line per region. One tax rate per line. Tax amount shown explicitly. This is not just cleaner—it's what passes audit and survives a tax authority review. Here's an invoice template structure: INVOICE #2024-Q2-MULTI Description Qty Rate Subtotal Tax Rate Tax Total Retainer – Malaysia (90d) 1 120,000 120,000 6% SST 7,200 127,200 Retainer – Indonesia (45d) 1 52,500 52,500 11% PPN 5,775 58,275 Retainer – Singapore (90d) 1 75,000 75,000 9% GST 6,750 81,750 ──────── ─────── 247,500 Total tax 19,725 267,225 Each line shows the region, the number of days worked, and the applicable tax code. This is standard practice in multi-jurisdictional invoicing and makes reconciliation trivial. The General Ledger Split: Three Accounts, One Invoice Now your accounting side. You need to post revenue to the correct GL accounts and ensure tax liability lands in the right buckets for each country's filing. GL structure: 4100 – Revenue – Malaysia Services 4110 – Revenue – Indonesia Services 4120 – Revenue – Singapore Services 2100 – Tax Payable – Malaysia SST 2110 – Tax Payable – Indonesia PPN 2120 – Tax Payable – Singapore GST 1100 – Accounts Receivable Journal entries (one invoice number, multiple GL lines): Account Debit Credit Note 1100 A/R 267,225 Total invoice amount 4100 Revenue – Malaysia 120,000 Malaysia portion 4110 Revenue – Indonesia 52,500 Indonesia portion (prorated) 4120 Revenue – Singapore 75,000 Singapore portion 2100 Tax Payable – SST 7,200 Malaysia SST 6% 2110 Tax Payable – PPN 5,775 Indonesia PPN 11% 2120 Tax Payable – GST 6,750 Singapore GST 9% Proof: Debit 267,225 = Credit (120,000 + 52,500 + 75,000 + 7,200 + 5,775 + 6,750) = Credit 267,225. ✓ This structure means your finance team can reconcile to each country's tax return independently. When Malaysia's SST audit comes, you pull account 2100 and it ties cleanly to your invoice. Same for Indonesia (PPN) and Singapore (GST). Prorating Mid-Cycle: When Work Stops Before Month-End The Indonesia engagement stopped on day 45. But what if it stopped on day 47, or in the middle of the month? The principle stays the same: prorate revenue by the exact number of days worked, not by month-end rounding. Example: If Indonesia work ended on day 47 (not day 45): Indonesia revenue: ₹3,00,000 × 35% × (47 ÷ 90) = ₹54,916.67 Indonesia tax: ₹54,916.67 × 11% = ₹6,040.83 Many accounting tools round to the nearest rupee, which is fine. The key is consistency: use the same rounding rule (round half up, or truncate) across all three regions so that your GL reconciles. If you're using an invoicing tool that doesn't allow per-region prorating, you'll need to calculate it externally and manually enter the line amounts. This is where a platform like Orin's billing module helps—you can set revenue recognition rules per engagement region and let the system prorate