Website

One System, Several Countries: Designing Invoicing and Tax for a Business in Indonesia and Singapore

November 11, 2026 · 6 min read · Etzal Group Team

A trading group runs a custom order and invoicing system built for its Indonesian company. It opens a Singapore entity and asks the developers to "add Singapore". They find the Indonesian value added tax written into forty places in the code, every amount stored as a rupiah integer, an invoice number format tied to one company, and a tax report that assumes one tax office. The estimate for "adding Singapore" approaches the cost of the original system. Multi-country invoicing is cheap to design in at the beginning and expensive to retrofit.

This article describes design principles. Tax rules differ by country and change. Confirm every rule with qualified tax advisers before building.

Start with the legal entity

The central object is the legal entity, not the system.

Each entity has:

  • Country and tax registration details.
  • Base currency.
  • Tax scheme it operates under.
  • Invoice numbering sequences.
  • Document templates and language.
  • Fiscal calendar.
  • Bank accounts.

Every transaction belongs to exactly one entity. A user may work in several. Reports can be per entity or consolidated. If this structure exists from day one, a new country is mostly new configuration.

Tax as data

Never write a rate or a rule into program logic.

A tax table

  • Tax code: a named treatment, such as standard rate, zero rate, exempt, out of scope.
  • Rate and the effective date range.
  • Country and entity it applies to.
  • Accounts it posts to.
  • How it is reported.

Rules that select the code

The right treatment depends on facts about the transaction:

  • Who is selling, and whether registered.
  • Who is buying: business or consumer, registered or not, in which country.
  • What is sold: goods or services, and their category.
  • Where it is supplied or delivered.

Store these as rules that finance can maintain with their advisers, with the system proposing a tax code and allowing an authorised override with a reason.

Dates matter

When a rate changes, invoices issued before the change keep the old rate. Credit notes usually follow the original invoice. The system must select by the correct date and never recalculate history.

Calculation details

  • Tax-inclusive and tax-exclusive pricing, both supported.
  • Rounding per line or per document, as each country requires.
  • Withholding on payments where applicable, which is a different mechanism from sales tax and needs its own handling.

Currency

  • Store amounts with their currency, in a decimal type suited to money. Never assume one currency.
  • Respect decimal places. Some currencies are used without minor units in practice, others with two decimals.
  • Record the exchange rate used on each foreign currency transaction, and its source.
  • Keep both amounts: the transaction currency and the entity's base currency.
  • Revaluation and exchange differences for open balances at period end.
  • Tax in the required currency. A country may require tax to be shown in its own currency on an invoice issued in another, sometimes at a prescribed rate.

Invoices that meet each country's rules

An invoice has legal content requirements that differ by country.

  • Mandatory fields: seller and buyer details, registration numbers, dates, descriptions, tax breakdown, specific statements.
  • Numbering: sequential, without gaps, sometimes with a prescribed format or numbers allocated by the authority.
  • Language and currency requirements.
  • Credit and debit notes linked to the original invoice.
  • No deletion. An issued invoice is corrected by a further document, never edited.
  • Retention for the legally required period.

Build document templates per entity, driven by the same underlying data.

Electronic invoicing connectors

More countries each year ask businesses to send invoice data to a government system or through an approved network, in a structured format, sometimes before the invoice is valid.

Design for it even if not yet required.

  • A structured invoice model inside the system, from which a document and an electronic message can both be produced.
  • One connector per country, separate from the core, since formats and procedures differ.
  • Status tracking: submitted, accepted, rejected, with the reference returned.
  • Error handling: a rejected invoice goes to a queue with the reason.
  • Resilience: what happens when the official platform is unavailable.

Indonesia operates an electronic tax invoice regime through the tax authority's system. Singapore is introducing requirements for GST-registered businesses to transmit invoice data through its InvoiceNow network in phases. The details and dates change, so confirm the current position with advisers.

Intercompany transactions

When entities trade with each other:

  • Each side records its own document: a sale in one, a purchase in the other.
  • Both carry a shared reference so they can be matched.
  • Tax applies as it would between separate companies, according to each country's rules.
  • Pricing between related entities should follow a documented policy, which is a tax matter to settle with advisers.
  • Elimination on consolidation.

Reporting

  • Tax returns per entity, built from tax codes, in each country's structure.
  • Drill-down from every figure on a return to the invoices behind it.
  • A lock on filed periods.
  • Consolidated management reports in one currency.
  • Audit trail of who changed tax configuration and when.

Master data that travels

  • Customers and suppliers with country, tax registration and classification.
  • Products and services with a tax category that maps to a tax code in each country.
  • Validation of registration number formats where possible.

Poor master data is the main cause of wrong tax on invoices.

A sensible build order

  1. Entity, currency and tax-as-data in the core, from the start.
  2. First country fully configured and tested with advisers.
  3. Second country as configuration: tax table, templates, numbering, connector.
  4. Intercompany and consolidation.
  5. Each further country follows the same pattern.

Test with real scenarios supplied by finance: domestic sale, export, sale to a consumer, credit note after a rate change, foreign currency invoice, intercompany sale.

Common mistakes

  • Tax rates in code.
  • One currency assumed everywhere.
  • Amounts stored in floating point.
  • No effective dates on tax rules.
  • Recalculating old invoices with new rates.
  • Editable issued invoices.
  • One numbering sequence for all entities.
  • E-invoicing bolted on later with no structured model.
  • Treating withholding like sales tax.
  • Building without the tax adviser in the room.

We design and build finance and operations systems with entity, currency and tax configuration at the core, as part of Enterprise Software. If your system was built for one country and the group is growing, contact us.

Summary

A system that serves several countries is organised around legal entities, each with its own currency, tax scheme, numbering and templates. Tax rates and rules are data with effective dates, never code. Amounts carry their currency and exchange rate, issued invoices are never edited, and electronic invoicing is handled by a connector per country fed from one structured invoice model. Build the first country with advisers, and each further country becomes configuration.

Frequently asked questions

Why can a single-country system not simply be reused in another country?

Because it usually embeds assumptions in code: one tax with one rate, one currency, one invoice layout, one numbering scheme and one reporting format. A second country differs on each of these. Unless tax rules, currency and document formats are stored as configuration per legal entity, every new country requires changes to the program itself.

Should tax rates be hard-coded in the software?

No. Rates, the rules for when they apply and their effective dates should be stored as data that authorised finance staff can update, with a history. Tax rates and rules change, sometimes at short notice, and a change must not require a new software release or alter invoices that were already issued.

Does the system need to connect to government e-invoicing networks?

Increasingly, yes. Several countries require or encourage invoices to be reported or exchanged through an official platform or network in a structured format. The requirements, scope and timing differ by country and change, so design a separate connector per country and confirm the current obligations with a tax adviser.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Website Development

Fast, SEO-ready websites that turn visitors into customers.