T

Rp 1.74 billion.

Most Finance Directors look at that number twice. Then they open a browser tab and start searching for what they're actually paying for, whether there's a cheaper alternative, and why their peer at a factory in Cikarang told them they regretted it.

This article is for that search. The honest version—not the one written by an SAP partner, and not the one written by an SAP competitor trying to sell you something else. SAP Business One is the right ERP for some companies. A 200-person single outlet bakery in food and beverages industry in Jakarta, Bandung or Karawang is usually not one of them. Here's the math.

What Rp 1.74 Billion Actually Buys

The headline number from SAP Business One for Indonesian manufacturers breaks down into two parts: roughly Rp 820,000,000 in license fees and Rp 920,000,000 in consulting and implementation.

The license covers 15 named users—people who can log in and use the system simultaneously. The modules included at the base level are inventory, accounting, purchasing, and sales. That's the core operational layer.

The implementation fee covers the local SAP partner's time to configure the system for your factory, migrate your data from whatever you're running now, train your team, and go live. Implementation quality varies significantly between SAP partners in Indonesia, and there are far fewer SAP-certified consultants in the country than the sales deck implies. Scarcity has a price. Certified SAP consultants in Indonesia bill at Rp 3,000,000 to Rp 6,000,000 per man-day, depending on seniority and specialisation.

At 15 users and the modules listed above, the system handles what a mid-size distributor or trading company needs reasonably well. A manufacturing company with production planning, quality control, MRP, and shop floor visibility needs more—and "more" is where the number starts moving.

What the Quote Doesn't Include

This is the section SAP partners leave out of the initial presentation.

Annual maintenance. SAP charges 18 to 22 percent of the license fee annually for software maintenance and support. On an Rp 820,000,000 license, that's Rp 147,600,000 to Rp 180,400,000 per year. Across five years, that's Rp 738,000,000 to Rp 902,000,000 on top of the initial investment—before a single customisation is touched.

Indonesian tax compliance. SAP Business One's base configuration is not built for Indonesian tax requirements. e-Faktur integration, PPh 21 and 23 calculations, PPN handling, and reconciliation with DJP's reporting formats all require customisation. Some SAP partners include a localisation package in their implementation quote. Others scope it separately after the contract is signed. Ask which version you're looking at before signing anything.

Users beyond 15. If your factory grows, or if the initial count was optimistic about how many people actually need system access, additional named user licenses are billed per seat. The per-user cost at the SAP Business One tier is not small.

Customisation for manufacturing-specific requirements. Production variance reporting, BOM management, quality inspection workflows, batch traceability—these are common in manufacturing and commonly not included in the base implementation scope. Each one is a change request with a man-day estimate attached.

Upgrade costs. SAP Business One undergoes periodic major version changes. Staying on a supported version requires upgrade projects, which your SAP partner will quote separately.

Imagine an automotive parts supplier in EJIP 500 employees, two production lines—that signed an SAP contract at Rp 1.2 billion for 10 users. By the end of year two, the total spend was Rp 2.1 billion. Not because of mismanagement. Because e-Faktur customisation, four additional user licenses for quality and warehouse staff, and an upgrade project weren't in the original scope. Each item had a logical reason to exist. None of them were in the number they signed.

The Hidden Cost That Compounds Quietly

Consultant scarcity is the cost nobody models.

Indonesia has a limited pool of SAP-certified consultants relative to the implementation demand. When your system needs modification—a regulatory change, a new module, a bug in the customisation—your partner's availability is not guaranteed. Projects get queued. Timelines slip. Per Horváth & Partners' analysis, SAP implementations run an average of 30% longer than initial estimates. That overage is billed.

If your local SAP partner loses the consultant who built your customisations, or if that partner is absorbed, restructured, or simply deprioritises smaller clients as they win larger ones, you face a re-implementation risk. Moving your configuration documentation to a new partner is possible. It's not free and it's not fast.

This is a real operational risk for a single-plant factory in Karawang. It's a manageable risk for a multi-plant multinational that has SAP expertise in-house across the group.

When SAP IS the Right Answer

To be clear: SAP Business One is a capable system, and SAP HANA at the enterprise tier is what it is for a reason.

SAP makes sense when your factory is part of a group that runs SAP globally. Consolidation, intercompany transactions, group-level reporting, shared master data. These work cleanly within the SAP ecosystem. If your Tokyo or Seoul headquarters runs SAP and expects subsidiary financial data to flow into the same system, the cost of integration across different platforms often exceeds the cost premium of SAP itself.

SAP also makes sense for multi-plant operations with genuine complexity: multiple warehouse locations, interplant transfers, consolidated MRP across production facilities, multi-entity accounting. At that scale and complexity, SAP's depth is an asset rather than an over-engineered burden.

And SAP is worth considering if your finance team already has SAP-trained staff and you're replacing an older SAP version rather than starting fresh. Retraining costs are real, and teams that know the system are faster.

The company profile where SAP is overkill: single-plant, under 300 employees, one entity, primarily serving the Indonesian domestic market, with parent company reporting that requires management summaries rather than consolidated group accounting. That describes a significant portion of the factories in KIIC and MM2100.

The Mandate vs. Fit Problem

Here's the dynamic nobody talks about directly: many Karawang and Cikarang factories run SAP not because someone evaluated SAP against alternatives and concluded it was the best fit, but because the Japanese or Korean parent company uses SAP globally and mandated it for all subsidiaries.

The mandate and the fit question are completely separate. They almost never get separated in the conversation.

A parent company in Nagoya may use SAP HANA for global consolidation. That doesn't mean SAP Business One is the right system for a 200-person subsidiary producing auto parts in West Java. The consolidation interface between SAP HANA and SAP Business One is real. So is the same interface between SAP HANA and several other mid-market ERP systems. The assumption that the subsidiary must also use SAP, because HQ uses SAP, often goes unexamined.

This matters because questioning the mandate requires a conversation with the parent company—and most IT leads or Plant Managers in Indonesia don't want to have that conversation. It's easier to accept the mandate and argue about implementation budget than to push back on the platform choice. The result is a system selection that was never actually evaluated.

If you have room to have the conversation, have it. Ask HQ specifically what data they need from the subsidiary, in what format, at what frequency. Then ask whether that data can come from a system other than SAP. The answer is usually yes. The question is whether the parent company IT team will support the integration work.

The Real 5-Year Number

A more honest accounting for a 200-person Karawang factory, based on the figures above:

• Initial investment (license + implementation): Rp 1,740,000,000
• Annual maintenance (years 2–5, 20% of license): Rp 656,000,000
• e-Faktur & tax localisation (if not included): Rp 150,000,000 – Rp 300,000,000
• Additional users over 5 years (3–5 licenses): Rp 75,000,000 – Rp 150,000,000
• One major version upgrade project: Rp 200,000,000 – Rp 400,000,000
• Ad-hoc customisations & regulatory updates: Rp 200,000,000 – Rp 500,000,000

Conservative 5-year total: Rp 3,021,000,000
Realistic 5-year total: Rp 3,746,000,000

That's the number to put next to the Rp 1.74 billion quote. Not because SAP is a bad system. Because the decision deserves real numbers, not sales deck numbers.

Before you sign anything, model your exact headcount, module requirements, and maintenance trajectory using our Enterprise ERP TCO Calculator. The math does not lie.

FAQ

Q: Is biaya SAP Business One negotiable in Indonesia?

A: The license fee has limited negotiability—SAP sets floor pricing and partners work within it. The implementation fee has more room, particularly if you're willing to commit to a faster timeline or accept less customisation in the initial scope. Getting multiple quotes from different SAP partners in Indonesia is worth doing. Implementation quality and price vary more than the license tier does.

Q: What happens if we can't afford the annual maintenance and stop paying it?

A: You lose access to software updates, bug fixes, and security patches. The system continues to function on the version you have, but you're running unsupported software. At the next Indonesian regulatory change that requires an SAP update—e-Faktur format revision, BPJS rate change—you're either paying back maintenance to reinstate support or paying a consultant to patch it manually.

Q: Can SAP Business One handle Indonesian e-Faktur natively?

A: Not in the base international version. Indonesian localisation for e-Faktur requires either a localisation package from your SAP partner or a third-party add-on. Confirm exactly how this is handled—and who maintains it when DJP changes the format—before signing.

Q: What's a realistic timeline for SAP Business One implementation at a 200-person factory?

A: Six to nine months for a well-scoped implementation. Twelve to fifteen months is common once manufacturing-specific customisations, data migration from legacy systems, and user training are included. Vendors quoting three to four months for full go-live at a factory of this complexity are scoping a minimal viable implementation, not a working one.

Q: What are the main alternatives to SAP Business One for factories in this size range?

A: Odoo Enterprise is the most commonly quoted alternative—but the TCO math is less favourable than the per-user-month pricing implies. Over five years at 50 users, Odoo Enterprise total cost often exceeds SAP Business One's total cost once implementation and annual subscription are both counted. Custom-built ERP on modern infrastructure, with a flat implementation cost and no per-user or annual license fee, is a third option that most factories never model because they don't know it exists.

The Rp 1.74 billion number is the starting point, not the final answer. Any Finance Director or Plant Manager making this decision deserves to see the 5-year total before they sign—and they deserve to have the mandate vs. fit conversation before assuming SAP is the only option on the table.

id: "89" title: "SAP at Rp 1.74 Billion: Is It Actually Worth It for a 200-Person Factory in Karawang?" date: "2026-06-03" category: "ERP" readTime: "8 MINS" tags: ["ERP", "SAP", "MANUFACTURING", "OPEX", "TCO"] description: "SAP Business One costs Rp 1.74B for 15 users in Indonesia—but that's the opening number. Here's the full 5-year cost before you sign anything."

T

Rp 1.74 billion.

Most Finance Directors look at that number twice. Then they open a browser tab and start searching for what they're actually paying for, whether there's a cheaper alternative, and why their peer at a factory in Cikarang told them they regretted it.

This article is for that search. The honest version—not the one written by an SAP partner, and not the one written by an SAP competitor trying to sell you something else. SAP Business One is the right ERP for some companies. A 200-person single-plant factory in Karawang is usually not one of them. Here's the math.

What Rp 1.74 Billion Actually Buys

The headline number from SAP Business One for Indonesian manufacturers breaks down into two parts: roughly Rp 820,000,000 in license fees and Rp 920,000,000 in consulting and implementation.

The license covers 15 named users—people who can log in and use the system simultaneously. The modules included at the base level are inventory, accounting, purchasing, and sales. That's the core operational layer.

The implementation fee covers the local SAP partner's time to configure the system for your factory, migrate your data from whatever you're running now, train your team, and go live. Implementation quality varies significantly between SAP partners in Indonesia, and there are far fewer SAP-certified consultants in the country than the sales deck implies. Scarcity has a price. Certified SAP consultants in Indonesia bill at Rp 3,000,000 to Rp 6,000,000 per man-day, depending on seniority and specialisation.

At 15 users and the modules listed above, the system handles what a mid-size distributor or trading company needs reasonably well. A manufacturing company with production planning, quality control, MRP, and shop floor visibility needs more—and "more" is where the number starts moving.

What the Quote Doesn't Include

This is the section SAP partners leave out of the initial presentation.

Annual maintenance. SAP charges 18 to 22 percent of the license fee annually for software maintenance and support. On an Rp 820,000,000 license, that's Rp 147,600,000 to Rp 180,400,000 per year. Across five years, that's Rp 738,000,000 to Rp 902,000,000 on top of the initial investment—before a single customisation is touched.

Indonesian tax compliance. SAP Business One's base configuration is not built for Indonesian tax requirements. e-Faktur integration, PPh 21 and 23 calculations, PPN handling, and reconciliation with DJP's reporting formats all require customisation. Some SAP partners include a localisation package in their implementation quote. Others scope it separately after the contract is signed. Ask which version you're looking at before signing anything.

Users beyond 15. If your factory grows, or if the initial count was optimistic about how many people actually need system access, additional named user licenses are billed per seat. The per-user cost at the SAP Business One tier is not small.

Customisation for manufacturing-specific requirements. Production variance reporting, BOM management, quality inspection workflows, batch traceability—these are common in manufacturing and commonly not included in the base implementation scope. Each one is a change request with a man-day estimate attached.

Upgrade costs. SAP Business One undergoes periodic major version changes. Staying on a supported version requires upgrade projects, which your SAP partner will quote separately.

Imagine an automotive parts supplier in EJIP—110 employees, two production lines—that signed an SAP contract at Rp 1.2 billion for 10 users. By the end of year two, the total spend was Rp 2.1 billion. Not because of mismanagement. Because e-Faktur customisation, four additional user licenses for quality and warehouse staff, and an upgrade project weren't in the original scope. Each item had a logical reason to exist. None of them were in the number they signed.

The Hidden Cost That Compounds Quietly

Consultant scarcity is the cost nobody models.

Indonesia has a limited pool of SAP-certified consultants relative to the implementation demand. When your system needs modification—a regulatory change, a new module, a bug in the customisation—your partner's availability is not guaranteed. Projects get queued. Timelines slip. Per Horváth & Partners' analysis, SAP implementations run an average of 30% longer than initial estimates. That overage is billed.

If your local SAP partner loses the consultant who built your customisations, or if that partner is absorbed, restructured, or simply deprioritises smaller clients as they win larger ones, you face a re-implementation risk. Moving your configuration documentation to a new partner is possible. It's not free and it's not fast.

This is a real operational risk for a single-plant factory in Karawang. It's a manageable risk for a multi-plant multinational that has SAP expertise in-house across the group.

When SAP IS the Right Answer

To be clear: SAP Business One is a capable system, and SAP HANA at the enterprise tier is what it is for a reason.

SAP makes sense when your factory is part of a group that runs SAP globally. Consolidation, intercompany transactions, group-level reporting, shared master data—these work cleanly within the SAP ecosystem. If your Tokyo or Seoul headquarters runs SAP and expects subsidiary financial data to flow into the same system, the cost of integration across different platforms often exceeds the cost premium of SAP itself.

SAP also makes sense for multi-plant operations with genuine complexity: multiple warehouse locations, interplant transfers, consolidated MRP across production facilities, multi-entity accounting. At that scale and complexity, SAP's depth is an asset rather than an over-engineered burden.

And SAP is worth considering if your finance team already has SAP-trained staff and you're replacing an older SAP version rather than starting fresh. Retraining costs are real, and teams that know the system are faster.

The company profile where SAP is overkill: single-plant, under 3000 employees, one entity, primarily serving the Indonesian domestic market, with parent company reporting that requires management summaries rather than consolidated group accounting. That describes a significant portion of the factories in KIIC and MM2100.

The Mandate vs. Fit Problem

Here's the dynamic nobody talks about directly: many Karawang and Cikarang factories run SAP not because someone evaluated SAP against alternatives and concluded it was the best fit, but because the Japanese or Korean parent company uses SAP globally and mandated it for all subsidiaries.

The mandate and the fit question are completely separate. They almost never get separated in the conversation.

A parent company in Nagoya may use SAP HANA for global consolidation. That doesn't mean SAP Business One is the right system for a 200-person subsidiary producing auto parts in West Java. The consolidation interface between SAP HANA and SAP Business One is real. So is the same interface between SAP HANA and several other mid-market ERP systems. The assumption that the subsidiary must also use SAP, because HQ uses SAP, often goes unexamined.

This matters because questioning the mandate requires a conversation with the parent company—and most IT leads or Plant Managers in Indonesia don't want to have that conversation. It's easier to accept the mandate and argue about implementation budget than to push back on the platform choice. The result is a system selection that was never actually evaluated.

If you have room to have the conversation, have it. Ask HQ specifically what data they need from the subsidiary, in what format, at what frequency. Then ask whether that data can come from a system other than SAP. The answer is usually yes. The question is whether the parent company IT team will support the integration work.

The Real 5-Year Number

A more honest accounting for a 300-person Karawang factory, based on the figures above:

• Initial investment (license + implementation): Rp 1,740,000,000
• Annual maintenance (years 2–5, 20% of license): Rp 656,000,000
• e-Faktur & tax localisation (if not included): Rp 150,000,000 – Rp 300,000,000
• Additional users over 5 years (3–5 licenses): Rp 75,000,000 – Rp 150,000,000
• One major version upgrade project: Rp 200,000,000 – Rp 400,000,000
• Ad-hoc customisations & regulatory updates: Rp 200,000,000 – Rp 500,000,000

Conservative 5-year total: Rp 3,021,000,000
Realistic 5-year total: Rp 3,746,000,000

That's the number to put next to the Rp 1.74 billion quote. Not because SAP is a bad system. Because the decision deserves real numbers, not sales deck numbers.

Before you sign anything, model your exact headcount, module requirements, and maintenance trajectory using our Enterprise ERP TCO Calculator. The math does not lie.

FAQ

Q: Is biaya SAP Business One negotiable in Indonesia?

A: The license fee has limited negotiability—SAP sets floor pricing and partners work within it. The implementation fee has more room, particularly if you're willing to commit to a faster timeline or accept less customisation in the initial scope. Getting multiple quotes from different SAP partners in Indonesia is worth doing. Implementation quality and price vary more than the license tier does.

Q: What happens if we can't afford the annual maintenance and stop paying it?

A: You lose access to software updates, bug fixes, and security patches. The system continues to function on the version you have, but you're running unsupported software. At the next Indonesian regulatory change that requires an SAP update—e-Faktur format revision, BPJS rate change—you're either paying back maintenance to reinstate support or paying a consultant to patch it manually.

Q: Can SAP Business One handle Indonesian e-Faktur natively?

A: Not in the base international version. Indonesian localisation for e-Faktur requires either a localisation package from your SAP partner or a third-party add-on. Confirm exactly how this is handled—and who maintains it when DJP changes the format—before signing.

Q: What's a realistic timeline for SAP Business One implementation at a 200-person factory?

A: Six to nine months for a well-scoped implementation. Twelve to fifteen months is common once manufacturing-specific customisations, data migration from legacy systems, and user training are included. Vendors quoting three to four months for full go-live at a factory of this complexity are scoping a minimal viable implementation, not a working one.

Q: What are the main alternatives to SAP Business One for factories in this size range?

A: Odoo Enterprise is the most commonly quoted alternative—but the TCO math is less favourable than the per-user-month pricing implies. Over five years at 50 users, Odoo Enterprise total cost often exceeds SAP Business One's total cost once implementation and annual subscription are both counted. Custom-built ERP on modern infrastructure, with a flat implementation cost and no per-user or annual license fee, is a third option that most factories never model because they don't know it exists.

The Rp 1.74 billion number is the starting point, not the final answer. Any Finance Director or Plant Manager making this decision deserves to see the 5-year total before they sign—and they deserve to have the mandate vs. fit conversation before assuming SAP is the only option on the table.