AutoCount Customer Story
IndoFood (M) Sdn Bhd Customer Story
Indofood (M) Food Industries Sdn Bhd needed to meet Malaysia’s e-Invoice requirements without replacing or extensively customising its existing SAP ERP environment. AutoCount was implemented as a middleware platform to manage submission while keeping the core SAP workflow intact.
How the integration works
The compliance process is separated from the core SAP environment, reducing disruption to established operations.
The business requirement
Compliance had to be added without disturbing a major ERP platform.
Indofood needed a practical way to process e-Invoices while continuing to use its established SAP environment.
Integration challenge
Add an e-Invoice compliance layer
The new process needed to receive transaction information from SAP, manage e-Invoice submission and avoid disrupting the existing ERP workflow.
- A full SAP replacement would introduce unnecessary disruption.
- Extensive SAP custom development would increase implementation risk and cost.
- The compliance layer needed to work alongside the core ERP, not replace it.
Business background
Keep the existing SAP workflow
The company already relied on SAP ERP for its operational processes. Replacing the platform, or extensively customising it, would have increased implementation complexity and cost.
The AutoCount solution
A middleware approach built around controlled data transfer.
AutoCount became the e-Invoice processing platform while SAP remained the main operational ERP.
AutoCount as the e-Invoice middleware platform
AutoCount handled the compliance process as an additional layer between SAP and LHDN.
- SAP continued to serve as the existing ERP environment.
- AutoCount received transaction information for e-Invoice processing.
- The compliance workflow was separated from the core operational system.
SAP-to-Excel import flow
Transaction information was exported from SAP into Excel before being imported into AutoCount through a controlled import process.
- Existing SAP transactions remained the original source.
- Excel provided a controlled transfer format.
- AutoCount received the data without replacing SAP.
LHDN e-Invoice submission
AutoCount managed the e-Invoice submission process after receiving the transaction information from the existing SAP environment.
- Imported transactions were prepared for submission.
- AutoCount handled communication with LHDN.
- The compliance process remained separate from SAP.
No SAP customisation required
The middleware approach allowed Indofood to preserve its established SAP processes without modifying the core ERP environment.
- No custom development was required inside SAP.
- Existing operational workflows remained unchanged.
- Implementation risk, complexity and disruption were reduced.
Operational workflow
Four clear stages from ERP transaction to e-Invoice submission.
The process was designed to preserve the existing SAP workflow while adding a separate compliance route.
Prepare in SAP
Transactions continue to originate from the existing SAP ERP environment.
Export to Excel
Transaction information is exported into a controlled Excel format.
Import into AutoCount
The import plugin transfers transaction data into the middleware platform.
Submit to LHDN
AutoCount handles the e-Invoice submission without altering SAP.
usiness outcome
A practical route to e-Invoice compliance with less disruption.
The middleware approach simplified implementation while allowing Indofood to keep its established SAP processes.
SAP retained
The company preserved its established ERP workflow instead of replacing a major enterprise platform.
Controlled transfer
Transactions could move from SAP through Excel into AutoCount for submission.
Automated submission workflow
AutoCount provided the e-Invoice submission process while reducing implementation complexity and disruption.
Need e-Invoice compliance without replacing your main ERP?
A middleware approach can connect an established enterprise system to an e-Invoice submission workflow while reducing disruption to core operations.