T

The sales rep smiles. "We can customise that."

That sentence has cost Indonesian manufacturing subsidiaries more money than any license fee. It means: "we haven't done this before, and you will pay for our learning curve."

If you manage IT or operations at a Japanese or Korean-managed factory in KIIC, MM2100, Delta Silicon, or EJIP—you're dealing with a problem most ERP vendors don't acknowledge until after the contract is signed. Your factory operates under two sets of demands simultaneously, and the gap between them is where most implementations fall apart.

Two Masters, One System

The local finance team needs e-Faktur compliance for DJP, BPJS payroll calculations, PPh and PPN handling, and reconciliation with Indonesian bank formats. These are non-negotiable. Get them wrong and you're looking at tax penalties.

The parent company in Osaka, Nagoya, or Seoul needs management reports in their format, with their KPIs, on their timeline. None of the Indonesian regulatory output is relevant to them. What they want is operational visibility that fits into their global reporting structure.

Most ERP systems solve one of these reasonably well. Some solve neither. Almost none solve both without a significant customisation project on top of the base implementation.

The factories that appear to have it working usually maintain a dedicated person—sometimes two—whose job is translating ERP output into parent company format each month. That person is evidence of an ERP failure. Not a people problem. A requirements problem that wasn't caught before go-live.

What Japanese-Managed Factories Actually Need

Kaizen culture is a data requirement, not just a management philosophy.

Every improvement loop generates a structured record trail: who submitted the proposal, what the before-state was, what changed, when it was implemented, what the measured result was. Most ERP systems treat production as a numbers game—quantities, costs, lead times. Japanese manufacturers treat production as a documentation game where numbers are evidence of process discipline.

Gentan reporting. Gentan (減端) is production variance analysis at the line level. Not just "we produced 950 units against a plan of 1,000"—but a breakdown of where the 50 units went. Machine downtime, material defect, changeover time, each category has a code. The monthly report to the parent company contains this breakdown, formatted exactly as HQ wants it, because someone in Nagoya is comparing it against the same format from twenty other subsidiaries worldwide.

Standard ERP production variance reports exist. Gentan-formatted variance reports almost never exist out of the box. The delta is always a customisation project that didn't appear in the original quote.

Take time tracking. Actual versus planned take time per line, per shift, per day. This is standard operational visibility in Japanese manufacturing. Not exotic. Basic. Most ERP production modules don't surface this natively without configuration work.

5S audit logging. Audit results need to be recorded, scored, trended, and escalated within the system. Most factories still use paper forms for this even when they have a functioning ERP. That's not a culture problem. It's a capability gap the ERP vendor never acknowledged.

PDCA cycle visibility. Which kaizen proposals are in Plan, Do, Check, Act. Who owns each stage. What the completion rate is by department. Again: almost no standard ERP surfaces this without customisation.

What Korean-Managed Factories Actually Need

Korean manufacturing culture moves at a different pace. The reporting cadence is compressed.

Where a Japanese parent company reviews a detailed monthly management report, a Korean HQ often wants daily or weekly P&L visibility at the subsidiary level. Not approximate. Not "we'll close the books at month-end." Daily: what was produced, what did it cost, what was the revenue recognition. This requires an ERP that processes production costs in near real time, not one that batches everything into a month-end run.

MES integration. Korean-managed factories typically have stronger expectations around Manufacturing Execution System integration than their Japanese counterparts. The ERP is not the source of truth for production data—the MES is. The ERP needs to receive data from the MES cleanly, reconcile it against inventory and cost accounting, and produce management reports from the combined dataset. Vendors who treat MES integration as "we have an API" have not done this in production before.

Korean language support for auditors. Parent company auditors visit. They want to review transaction logs, approval workflows, and exception reports. If the ERP can't produce Korean-language output for key reports, every auditor interaction requires a translator standing next to the screen. This sounds minor until you're three days into an audit with a Seoul team and the translation is adding two hours to every session.

The Compliance Layer Nobody Gets Right

Both Japanese and Korean-managed factories share the same Indonesian regulatory requirements. This is where most implementations quietly fail.

e-Faktur. Indonesia's electronic tax invoice system requires specific XML formats uploaded to DJP's system. Every sale with PPN needs a valid e-Faktur. If the ERP doesn't generate e-Faktur-compatible output natively, someone is manually rekeying invoices into DJP's desktop application. In a factory with 200+ invoices per month, that's a part-time job that exists because of the ERP implementation, not despite it.

Imagine a mid-size automotive parts supplier in MM2100 that selected a European ERP with good production module credentials. The system had no e-Faktur support. The vendor's response at go-live: "we support e-Faktur for an additional implementation fee." That fee wasn't in the original contract. The finance team spent three months manually rekeying invoices while the customisation was scoped, negotiated, and built.

BPJS payroll. BPJS Kesehatan and BPJS Ketenagakerjaan calculations change when government regulation changes. An ERP payroll module that isn't actively maintained for Indonesian regulatory updates creates compliance risk every time a BPJS contribution rate changes or a PPh 21 calculation rule is revised. Ask the vendor who handles these updates. The answer should be "our local team, included in maintenance." If it's "you submit a change request," that's a queue, not a guarantee.

Multi-currency. JPY for parent company reporting, IDR for local operations, sometimes USD for commodity purchases. The ERP needs exchange rate management, currency revaluation for month-end, and parent company reporting in the home currency—without requiring a manual reconciliation step in Excel. This sounds standard. In practice, the multi-currency module and the management reporting module often don't talk to each other cleanly, and the gap gets filled with a spreadsheet.

The Report That Still Lives in Excel

Here's what most ERP vendors don't tell you before you sign: the ERP goes live, the local team uses it, operational data flows through it—and the monthly report that goes to Nagoya or Seoul is still built in Excel.

Not because the ERP can't generate reports. Because the report format the parent company requires doesn't match any standard ERP output, and nobody budgeted for the customisation needed to make it match.

So someone—usually the finance manager or a dedicated reporting analyst—exports data from the ERP, pastes it into a master Excel template, spends two days reformatting it, and sends it to HQ. Every month. For years. Sometimes for the entire lifespan of the ERP implementation.

The ERP became a data entry system. The actual management tool is the Excel file.

I've seen this pattern at more than one factory. And it's not a technology failure, exactly. It's a requirements failure that happened in the weeks before implementation started, when nobody asked the specific question: "Show me the exact format of the report that needs to go to HQ, and walk me through how your ERP produces that format today."

If you ask that question in the demo and the answer is "we can customise that"—you now know what you're walking into.

Questions to Ask Before Signing

These separate the vendors who have genuinely done this before from the vendors who believe they can.

"Show me an existing implementation at a Japanese or Korean-managed factory in Indonesia." Not a reference. Not a logo on a slide. A live demo with the management reporting flow included, from ERP to the format HQ receives.

"How does your system generate e-Faktur output? Is it native or a third-party add-on?" If it's an add-on, ask who maintains it when DJP changes the spec.

"How does MES integration work in your system—what data flows in, at what frequency, and how does it reconcile against cost accounting?" A real answer takes five minutes to explain. A vague answer about "API connectivity" is a warning sign.

"What does producing parent company reports in JPY or KRW look like at month-end? Walk me through the process." If they describe a process that involves exporting to Excel at any point, ask why.

"Who maintains Indonesian regulatory updates—e-Faktur format changes, BPJS rate adjustments, PPh revisions? Is that included in your annual maintenance fee or billed separately?" Get the answer in writing.

FAQ

Q: Can SAP Business One handle Japanese factory reporting requirements in Indonesia?

A: Some of it, yes. But Gentan-format variance reporting and take time tracking typically require customisation on top of the base implementation. The larger question is whether a Rp1.74 billion investment is justified for a single-plant subsidiary. SAP's real strength is multi-plant, multi-country consolidation. For a standalone Karawang factory reporting to one HQ, the system is usually oversized for the problem it's solving.

Q: Is there a ready-made ERP built specifically for Japanese manufacturing in Indonesia?

A: Some Japanese ERP vendors—OBC, PCA, and others—have Indonesian versions, but they still require localisation work for Indonesian tax compliance and parent company reporting. There's no fully turnkey option. The real question is whether you're paying for customisation that's been done before and documented, or customisation that's being figured out at your expense.

Q: What's a realistic ERP implementation timeline for a 200-300 person factory?

A: Six to twelve months for a phased rollout. Any vendor quoting three months for full go-live at a factory of this size is scoping something very limited, or hasn't accounted for data migration, user training, and the inevitable back-and-forth on parent company reporting formats. Per Horváth & Partners 2025 data, SAP implementations run an average of 30% longer than initial estimates.

Q: How do we handle the handoff between Indonesian operational data and Japanese HQ reporting?

A: Design it explicitly before go-live, with the actual HQ report template in hand. The handoff is a data transformation process—from ERP output to HQ format—and it needs to be built into the implementation scope, not discovered after the system is live. If it's not in scope, it defaults to Excel. That's not a metaphor. That's what happens.

Q: Should we implement ERP all at once or module by module?

A: Module by module is almost always right for manufacturing subsidiaries of this type. Start with inventory and production tracking where the core operational data lives. Add financial consolidation once that data is clean and trusted. Add parent company reporting last, when you know what the ERP actually produces and where the gaps are. Replace one piece at a time, validate it, then move to the next.

The factories that end up with a working ERP—one that's actually used for management decisions rather than as a data entry layer under a spreadsheet—started the vendor conversation differently. They brought the actual Nagoya or Seoul management report template to the first meeting. They said: this is the output. Show me how your system produces it.

Most vendors can't answer that in meeting one. The ones worth continuing with either demonstrate it or tell you honestly what the gap is and what closing it will cost.

That's a different conversation than "we can customise that."