ERP Rescue Consultant, Malaysia

How Malaysian ERP projects end up needing rescue

Recognizing the kind of trouble a project is in helps decide the right response. In Malaysia, some patterns are closely tied to the local context.

• A compliance deadline set the go-live date. The MyInvois phase applying to the company fixed the date, and testing, data cleansing and training were squeezed to fit it.
• A connector bolted on in a hurry. E-invoicing middleware was added to an existing or new system without agreed rules for rejections, cancellations or consolidated submissions.
• Factory complexity underestimated. Bills of materials, subcontracting and lot tracking were treated as a later phase, so production carried on in spreadsheets and stock figures drifted.
• The old package never switched off. AutoCount or SQL Account kept running for one function after another, and staff now enter some transactions twice.
• Language and training gaps. Training and guides were prepared in one language for a workforce that uses several, so key users never fully adopted the new flows.

None of these means the platform was wrong. They do mean the current plan cannot simply be pushed harder. The general approach is on my ERP recovery page; the sections below apply it to Malaysian conditions.

Stabilizing MyInvois, SST and the monthly close

The first priority in a Malaysian rescue is to keep the company billing, filing and closing correctly while everything else is sorted out. I agree the approach with your finance lead, tax agent and accountant, who decide on tax treatment. My job is to make the system side of each decision clear and controlled.

Once those controls are in place, I help finance run a recovery close with a short checklist: bank and intercompany reconciliations, payroll journals from the payroll provider, stock and work in progress, accruals and e-invoice status. Every temporary measure is recorded with an owner and the condition that ends it. A clean close is the clearest sign to the directors that recovery is working.

Repairing stock, costing and master data in the right order

Manufacturers and distributors in Malaysia feel a bad go-live most in the warehouse and on the production floor. Stock figures stop matching physical counts, product costs swing for no visible reason and planners go back to spreadsheets. Fixing this needs a sequence, because correcting transactions on top of faulty masters only creates new errors.

1. Masters first: customers and suppliers with complete tax and identification details for e-invoicing, items with correct units, SST codes and costing methods, and bills of materials that reflect real consumption.
2. Opening position: stock quantities and values, receivables and payables reconciled back to the legacy package, with differences explained and approved.
3. Transactions since go-live: receipts, issues, production orders and subcontract movements corrected in batches, each batch checked before the next starts.
4. Physical confirmation: a count of high-value or high-movement items to confirm the corrected position.

Where corrections affect figures already reported for SST or e-invoicing, your tax agent decides how they are handled. The repair also prepares the ground for switching off the old package: once stock and balances are trusted in the ERP, each remaining parallel process can be retired with confidence. For more on factory requirements, see manufacturing ERP.

Resetting with your implementer, or handing over

Your implementer may well have been working under the same compliance pressure as you were. Where that explains the trouble, a fair reset often works better than a change. The implementer knows your configuration, and a new team would need time to learn it.

A reset rests on a shared view of the work. I compile every open item, label it as contracted, added later, contested or now unnecessary, and bring that list to a working session with the implementer. Together we agree what stable operation requires, what can wait for a later phase, how each item will be accepted, and who on each side is responsible. The discussion stays on evidence, because blame tends to slow everyone down.

If the relationship cannot continue, the handover needs planning before anyone gives notice. You will want administrator access, configuration and customization records, connector settings and credentials, migration files and the full issue history. I help you list these and check they are received. Questions about notices, retention, payments or remedies under the contract belong with your lawyer, and I support that review with a factual record rather than legal opinion. My client-side implementation role in Malaysia can then continue with whichever team delivers the next phase.

Continue, re-scope or re-platform: the directors' decision

When the business is no longer firefighting, the directors can ask the larger question calmly: is this still the right project, on the right system, at the right size? I answer it with three written options. None comes with invented cost or time estimates; each describes the work involved, the risks carried and the disruption expected.

• Keep going with today's platform and scope under a rebaselined plan. This suits a system that fits your processes, where the damage came from a compressed timeline, weak data or a thin team.
• Shrink the first release to finance, sales, purchasing, stock and e-invoicing working properly, then add production planning, another entity or regional subsidiaries in later steps.
• Move platforms if testing shows that your manufacturing or group structure can only be supported through customization that would be costly to maintain.

Whatever the choice, e-invoice submissions must continue without a gap, so every option spells out how that continuity is protected during the change.

Vendors and implementers pay me nothing, in fees, commission or referrals, so the recommendation is shaped by your circumstances alone. For a structured review of a system that is live but underperforming, see the ERP audit page for Malaysia, or read about my work with Malaysian companies more broadly.