ERP Rescue, Philippines

Where Philippine ERP projects get stuck

A rescue is warranted when the project has lost its shape and more effort on the current plan will not restore it. Philippine projects have a few failure points that are worth naming.

• Registration left too late. The system was built and tested, but the steps needed before it could issue official documents were not planned, so go-live waited while the business kept using the old setup.
• A split go-live. Some branches moved to the new system while others stayed on the old one or on manual invoices, leaving finance to merge two sets of records every month.
• Withholding treated as a detail. Supplier rates, certificates and customer withholding were left for later, so payments and receivables are now reconciled by hand.
• A template that did not fit. The parent company's ERP template arrived with little room for branch series, local withholding or peso and dollar handling, and every local need became a change request.
• Decision owners missing. The implementer waits for answers that nobody on the client side has the authority to give.

A troubled project may carry more than one of them. The point of naming them is not to assign blame but to fix the actual causes, which my ERP recovery service sets out in general terms.

Keeping invoices, withholding and the close correct during recovery

While the project is being reset, customers must still receive valid invoices, suppliers must still get their withholding certificates and the books must still close. So the first part of the rescue sets interim rules that keep those obligations safe.

With your finance head and accountant, I agree for each branch and document type which system issues it during recovery, how invoice series are protected from overlap or gaps, and how any manual documents are captured and reconciled. If part of the business runs on the old system while the new one is fixed, I help design the monthly reconciliation between them. Your accountant or tax advisor decides the BIR treatment of anything unusual, such as a change in series or a correction to issued documents; I make sure the system side is documented and the interim steps have owners.

Month-end gets a recovery checklist: bank reconciliations in pesos and dollars, payroll journals from the payroll provider, withholding payable and receivable, intercompany balances and branch transfers. The goal is one close that finance is willing to stand behind. That close often does more to restore confidence in the project than any status report, because it proves the numbers can be trusted again. Related methods appear on my go-live support page, which deals with the weeks after a switch-over.

Repairing data after a difficult cutover

Data problems in a troubled Philippine go-live can often be traced to migration from QuickBooks, Xero, a local package or spreadsheets kept at branch level. Typical issues are duplicated customers and suppliers, missing tax identification numbers, wrong withholding settings on supplier records, opening balances that never agreed and stock or receivables that differ by branch.

I organize the repair into a sequence, because correcting transactions while faulty masters remain in use only creates new errors:

1. Masters: customers, suppliers and items, with tax details, withholding settings, branches and currencies made consistent.
2. Starting balances: general ledger, customer, supplier and stock figures reconciled to the legacy records, each difference investigated and signed off.
3. Postings made after cutover: documents posted to the wrong branch, wrong series, wrong currency or wrong tax setting, corrected in batches.
4. Verification: a check after each batch so finance can confirm the position before the next one starts.

Where a correction touches documents already issued or figures already reported, your accountant decides how it should be handled. The ERP migration checklist explains the controls that help avoid repeating the problem in later rollouts.

Resetting with the implementer and the parent company

In the Philippines, a rescue can involve three parties rather than two: the local entity, the implementer and a parent company team that owns the template or the budget. A reset only works if all three agree the same picture.

I prepare by building one list of open items and marking each as originally contracted, added later, disputed or no longer needed. For template-driven projects, I add a fourth view: which items are genuine local requirements, such as branch series, withholding and peso and dollar handling, and which are local preferences that could adapt to the template. In the reset session, we agree what stable operation needs, which items can wait, the test each item must pass and the person entitled to decide on each side. I keep the discussion on facts, because a party that feels blamed rarely helps solve the problem.

If the implementer relationship has to end, the handover is planned before notice is given: administrator access, configuration and customization records, integration settings, migration files, registration documents and the issue log. I put together a plain record of the agreed scope, the accepted deliverables and the gaps. Termination, retention or payment questions under the agreement go to your lawyer, who interprets the contract; my part is the evidence file.

Deciding the path: continue, re-scope or re-platform

Once branches are billing correctly and the books close, leadership can step back and decide what the project should become. I prepare a short options paper for the local board and, where relevant, the parent company.

The paper talks about effort, exposure and disturbance to daily work in plain language, never in speculative cost or schedule figures. Where re-platforming is considered, the paper also notes what registration and document series changes would follow, for your accountant to confirm.

Only the client pays me; I take nothing from vendors or implementers by way of commission or referral, so the recommendation tracks your circumstances. If your system is running but disappointing, the ERP audit page for the Philippines describes a structured review, and my client-side implementation support can carry the next phase.