The parts of an Indonesian build that no global tutorial covers: tax rules an ERP must encode, how money actually moves, where to host, and what the data-protection law asks of your code.
By Matthews WongResearched on
Key takeaway
Software built for Indonesia has to handle four local layers: tax through DJP's Coretax system, payments through QRIS and Bank Indonesia's SNAP standard, hosting and data placement, and the UU PDP data-protection law. Each hub below explains one layer, dates its sources, and links the hands-on articles behind it.
Each hub is a written overview with a comparison table, a dated timeline of the rules that changed, and the articles that go deeper.
A fee table with every cell linked to its source, a glossary of the local terms, and two calculators that show their formulas.
The most recently updated articles across the four hubs.
I build ERP and web systems for Indonesian businesses. Most of the hard problems were local: a tax ID that changed length, an invoice number that no longer exists until the tax office returns it, a payment that arrives as a QR string rather than a card token.
English-language material on these topics is thin, and much of what exists is written to sell a product. This section collects what I learned into guides with dated, linked sources, so you can check every claim and see how old it is.