Local ERP vs Foreign ERP: Which Fits an Indonesian Business?

There is a pattern that repeats when a growing business starts shopping seriously for a system. The owner researches, finds the big global names — software used by giant corporations, slick interface, convincing demo videos. Three months later: the annual subscription is paid, and the cashiers are still on the old app. Why? “There’s no QRIS. Restaurant tax has to be hacked in manually. Support answers email in three days, at 11 p.m. our time.”

Good software in the wrong context is like a good shoe in the wrong size. The shoe is not bad — you still cannot walk in it.

Difference one: here, tax is not an add-on

In foreign-built software, Indonesian taxation is usually treated as “customization”: the PB1/PBJT restaurant tax whose rate varies by city and regency, the final income tax scheme for small businesses, VAT-registered versus non-registered status, electronic tax invoices. All of it can be bolted onto a foreign ERP — through consultants, at implementation cost, and every time a regulation changes you depend on the consultant again.

In a system born for the Indonesian market, all of that is default behavior. Restaurant tax computed per transaction at your city’s rate, reports shaped for what actually gets filed, and when the rules change, the vendor is affected too — so the update arrives without you asking. We walked through one example in our piece on restaurant PB1 tax.

Difference two: how Indonesians pay and communicate

Two things almost guaranteed to be missing from foreign software: QRIS and WhatsApp.

QRIS is not “one of the payment methods” — in many businesses it is already half of all transactions. A register that cannot display a dynamic QRIS code (amount filled in automatically, no customer typing) feels broken from day one.

WhatsApp is even more extreme. Elsewhere, business communication runs on email; here, invoicing a customer by email is functionally the same as not invoicing them. Digital receipts, payment reminders, booking confirmations, loyalty programs — they all live on WhatsApp. An ERP that does not treat WhatsApp as a first-class channel will always need patch tools running beside it.

Difference three: support in your time zone and your language

Sounds trivial until your POS misbehaves on a Saturday at 7 p.m., right when the queue is longest. A local vendor picks up during Indonesian hours, in Indonesian, and understands what “the card terminal won’t settle” means in context. A foreign vendor replies through a ticket, in English, at dawn tomorrow.

Documentation and training follow the same logic. Training a new cashier from English-only materials is a struggle nobody needs.

So where does foreign ERP win?

To be fair: the big global suites excel at genuinely global needs. If your company operates in five countries, needs multi-currency consolidation across different accounting standards, or your parent company mandates a specific system — the global candidates make real sense. Their consultant ecosystems are vast, which is a plus for corporations with in-house IT teams.

But look at that profile: large, multinational, with an IT department. If that description is not you, the advantages are irrelevant — while the disadvantages (tax, QRIS, WhatsApp, support) are things you feel every single day.

A checklist for the decision

Instead of being dazzled by demos, test your candidates with specific questions:

• Can it compute PB1 at my city’s rate, automatically, per transaction?
• Dynamic QRIS straight from the register, no extra device?
• Receipts, reminders, and notifications over WhatsApp?
• Does the register keep working when the internet drops, then sync itself?
• What hours can I reach support on WhatsApp, and in what language?
• Is pricing in rupiah and sane for my scale — or in dollars per user per month that hurts to convert?

The offline point deserves emphasis because it is so often missed: power flickers and unstable connections are operational reality in many of our cities, and a system that dies with the internet means the queue walks out. We covered the details in an offline POS for when the internet cuts out.

One last thing: “local” does not automatically mean good, just as “foreign” does not automatically mean advanced. There is sloppy local software, and there is foreign software that takes Indonesia seriously. What you are really shopping for is not the vendor’s passport but the answer to one question: who built this product while thinking about a business like mine? Tenavora, for instance, was designed from the start for Indonesian SMBs — but whatever you choose, run it through the checklist above and insist on a trial with your real data before signing for a year.