Key Takeaway
Indonesia's ERP market was worth USD 1.004 billion in 2024 and is projected to reach USD 2.978 billion by 2030, a CAGR of 18.64 percent. The landscape is split: large conglomerates run SAP, the mid-market runs regional or local products, and smaller firms often build custom.
Indonesia's ERP software market was valued at USD 1.004 billion in 2024 and is projected to reach USD 2.978 billion by 2030 at 18.64% CAGR. Behind these numbers is a fragmented landscape where large conglomerates run SAP, mid-market companies debate between Oracle, Microsoft Dynamics, and Odoo, and a significant portion of Indonesian SMEs are still running on Excel and WhatsApp. I come at this as a developer building ERP systems for Indonesian businesses — which means I see the market from the implementation side, not the analyst side. Here's what the ERP landscape actually looks like from where I sit.
The Three-Tier Indonesian ERP Landscape
Indonesia's ERP market has three distinct tiers. Tier 1 (large enterprises): SAP S/4HANA and SAP Business One dominate. Pertamina, Astra International, Unilever Indonesia, Telkom, and major manufacturing conglomerates run SAP. Oracle EBS appears at banks and large distributors. These implementations cost IDR 500 million to several billion rupiah and require dedicated SAP/Oracle consultants. Tier 2 (mid-market): Microsoft Dynamics 365, Odoo, and local ERP products compete for companies with 50–500 employees. Odoo has particularly strong traction due to its open-source foundation, modularity, and a growing Indonesian Odoo partner ecosystem. Tier 3 (SME): Custom-built systems (NestJS/Laravel backends with React frontends), lighter SaaS products like Mekari, HashMicro, or Jurnal.id, and frankly many businesses still using spreadsheets.
SAP's Dominance and Its Limitations
SAP is genuinely dominant at enterprise scale in Indonesia, but its dominance has limits. SAP implementations require expensive local consultants (SAP-certified consultants in Indonesia charge IDR 25–80 million per month), long implementation timelines (6–18 months for a typical S/4HANA implementation), and significant ongoing maintenance costs. Indonesian companies that have committed to SAP are largely locked in — the switching cost is enormous. This creates a stable but inflexible tier at the top of the market. SAP Business One has more flexibility and is the version most accessible to mid-market Indonesian companies.
Odoo's Growing Footprint
Odoo is the most interesting ERP story in the Indonesian mid-market. Its open-source Community edition allows free usage (with implementation costs), while its Enterprise edition adds modules and support. The Indonesian Odoo partner network has grown significantly — review-erp.com lists dozens of local Odoo partners offering implementation in Indonesia. What makes Odoo work in Indonesia: its accounting module handles Indonesian tax requirements (PPN, PPh, withholding tax) when properly configured; the HR module can manage BPJS contribution calculations; and the flexibility to add custom modules means it can be adapted to Indonesian business workflows. The limitation: Odoo requires proper implementation expertise — a poorly implemented Odoo is worse than a well-maintained Excel spreadsheet.
Indonesia ERP Market — Three Tiers (2025)
──────────────────────────────────────────────────────────────
Tier Target Key Products Cost (IDR)
──────────────────────────────────────────────────────────────
Tier 1 500+ emp SAP S/4HANA, 500M – several B
Oracle EBS (impl + license)
Tier 2 50–500 emp Microsoft D365, 50M – 500M
Odoo Enterprise, (impl + annual)
HashMicro
Tier 3 1–50 emp Odoo Community, 5M – 50M
Mekari (Jurnal.id), (impl only / SaaS)
Custom NestJS/Laravel
──────────────────────────────────────────────────────────────
Market size: USD 1.0B (2024) → USD 3.0B projected by 2030
CAGR: 18.64% — one of SEA's fastest-growing ERP markets
──────────────────────────────────────────────────────────────For developers interested in the ERP consulting space in Indonesia, Odoo development skills are currently in short supply relative to demand. The Odoo ecosystem uses Python (OWL framework for frontend, Odoo ORM for backend), which is accessible if you have general web development skills. An Indonesian developer who can build and customize Odoo modules has a clear, remunerative career path — Odoo consultants and developers in Indonesia earn IDR 15–40 million per month depending on experience and client portfolio.
Custom ERP: Why Indonesian Companies Build Their Own
A meaningful portion of Indonesian mid-market companies — particularly in distribution, trading, and manufacturing — build custom ERP systems rather than implementing packaged solutions. The reasons are specific to Indonesia: business processes often involve non-standard approval hierarchies, complex multi-entity structures (holding companies with dozens of subsidiaries), and local compliance requirements (BPJS payroll integration, Indonesian tax reporting formats) that standard ERPs don't handle out-of-the-box without expensive customization. Custom-built systems on NestJS + PostgreSQL or Laravel + MySQL allow complete flexibility at the cost of higher maintenance overhead. This is where custom software and consulting firms operate.
Indonesian-Specific ERP Requirements
Any ERP serving Indonesian businesses needs to handle: PPN (Value Added Tax at 12%, charged on a DPP nilai lain of 11/12 for non-luxury goods under PMK 131/2024, an effective 11%) and PPh (income tax withholding) calculations in invoicing and procurement; BPJS Ketenagakerjaan and BPJS Kesehatan contribution payroll deductions; Indonesian fiscal year reporting formats (SPT, e-Faktur); multi-currency with IDR as base (critical for companies with import/export operations); and the uniquely Indonesian practice of 'AP aging by due date' that differs from typical Western accounting conventions. Standard international ERPs often require significant local customization to handle all of these correctly — which is why local ERP vendors and custom development shops have a viable market.
# Indonesian ERP must-have requirements checklist
indonesian_requirements = {
"tax": {
"ppn": "VAT 12% on DPP nilai lain 11/12 for non-luxury goods (PMK 131/2024)",
"pph_23": "Income tax withholding on services (2%/15%)",
"efaktur":"e-Faktur XML built to DJP's Coretax import template",
"spt": "Annual tax return report generation",
},
"bpjs": {
"jht": "JHT payroll deduction: 2% employee + 3.7% employer",
"jp": "JP deduction: 1% employee + 2% employer (capped)",
"jkk": "JKK employer: 0.24–1.74% based on risk class",
"kes": "BPJS Kesehatan: 1% employee + 4% employer (cap IDR 12M)",
},
"currency": "IDR base, multi-currency for import/export ops",
"language": "Bahasa Indonesia UI for non-technical end users",
}
What Custom ERP Work Looks Like in Indonesia
Custom ERP projects in this space often use NestJS + TypeScript + PostgreSQL on the backend and React on the frontend, deployed on Docker. A typical project involves: requirements gathering and process analysis; development including accounting modules (AR/AP), HR (leave management, payroll), procurement, and inventory; UAT and training; then ongoing maintenance and feature requests. The hardest parts are always the business logic edge cases — Indonesian accounting practices have nuances that aren't immediately obvious to developers who haven't worked in this context before.
The most common ERP failure pattern I've seen in Indonesian implementations is overcustomization: a company implements SAP or Odoo, then requests so many customizations to match their existing (often inefficient) processes that the system becomes unmaintainable. The correct approach is ERP-led process improvement — you change your business process to fit the ERP's best practice, not the other way around. Every customization is a liability that must be maintained through every upgrade. Indonesian companies that resist this and insist on 100% process mirroring in software end up with systems that are expensive, fragile, and eventually abandoned.
Emerging Trends: ERP + AI in Indonesia
The ERP market is being reshaped by AI in ways that are just beginning to play out in Indonesia. SAP's Joule AI assistant is coming to S/4HANA, potentially transforming how finance teams interact with the system. Local ERP vendors and custom shops are experimenting with LLM-powered features: auto-categorization of expenses from receipt photos, intelligent anomaly detection in financial data, and natural language querying of ERP data. For Indonesian companies, the most immediately valuable AI application in ERP is document processing — extracting data from Indonesian invoices (e-Faktur format) and purchase orders automatically to reduce manual data entry.
Career Paths in the Indonesian ERP Market
The Indonesian ERP market offers several developer career paths: SAP consultant (highest earning potential, requires SAP certification, mostly enterprise sales cycles); Odoo developer/consultant (growing market, Python-based, strong local demand); custom ERP developer (broad full-stack skills, typically at consulting firms); ERP project manager (less technical, high demand, bridges business and IT); and ERP integration specialist (connecting ERP to other systems via APIs — increasingly important as companies add SaaS tools). All of these paths pay materially above the general developer average in Indonesia because ERP work requires deep business domain knowledge in addition to technical skills.