ERP Implementation, Philippines

Where Philippine implementations lose time

The issues that delay Philippine ERP projects are usually predictable. They come from dependencies nobody owned, not from the software.

• Registration discovered late. The system is configured and tested, then the team realizes registration documents, sample outputs and approvals still need preparing. Go-live slips while the old process continues.
• Branch differences ignored. Head office designs the process, and branches on other islands find their own invoice series, cash handling and delivery practices were never considered.
• Withholding left manual. Supplier withholding and customer certificates are handled in spreadsheets during the project, and the ERP never takes them over.
• Parent priorities versus local needs. A group template is rolled out on schedule, while local books and invoices need extensions nobody budgeted for.
• Testers unavailable. Finance staff, branch managers and BPO operations leads have full workloads, and UAT becomes a quick check by the implementer.

Each of these can be managed with early planning and clear ownership. That is the purpose of a client-side lead, and the approach behind my ERP implementation service.

Overseeing the implementer and keeping registration on track

The implementer configures, localizes and supports the system. I represent your company, making sure what is built fits your processes and that every dependency outside the implementer's scope is owned.

At the start, I combine the implementer's plan with the steps your accountant expects for registration: preparing system documentation, sample invoices and reports, and any approvals needed before the system takes over from existing books. These steps go into the same timeline as configuration and testing, with owners and dates agreed between your accountant and the implementer. I do not file anything with the BIR or interpret its rules; I keep the work visible so it does not become a last-minute surprise.

During the build, I review each area with process owners before configuration and after each iteration. For Philippine setups, that includes branch invoice series and layouts, how cancelled documents are kept, audit trail settings, withholding on supplier records and payments, and how certificates received from customers are recorded. Your accountant confirms the treatment; I check that the configuration reflects it.

Each week, your sponsor receives a short summary of progress, risks, decisions needed and change requests, written so it can be shared with a parent company if required.

Data migration from QuickBooks, Xero and local packages

Philippine companies often migrate from QuickBooks, Xero or a local accounting package, sometimes with manual or loose-leaf books for some areas and spreadsheets for branch stock. Each source needs mapping, cleansing and a reconciliation plan.

Working with finance and the implementer, I focus on the points that cause most rework:

• customer and supplier records with complete registered names, addresses and tax identification numbers, which invoices and withholding depend on
• supplier withholding settings captured on the record rather than remembered by the accounts team
• open receivables, including amounts customers are expected to withhold, so collections and certificates match later
• stock by branch and warehouse, including goods in transit between islands at cutover
• balances in pesos and in US dollars for BPO and export customers, with the rates your accountant specifies

With your accountant, I agree how much history to move and how the old records are retained for audit. Each trial load ends with sign-off by the owners of the figures: trial balance, ageing by customer and supplier, and stock by location. If you are leaving QuickBooks, ERP migration from QuickBooks describes typical pitfalls, and ERP data migration covers the method.

Cutover: invoice series, payroll and period timing

The switch to a new system in the Philippines touches documents that customers, auditors and the BIR all see, so the cutover plan needs particular care.

Invoice series. For each branch, we agree with your accountant the last invoice number issued from the old system or booklets and the first from the new one, how unused series are handled, and what records are kept. The new series should only go live once the registration steps your accountant requires are complete.

Timing. Starting on the first day of a month helps tax reporting and management accounts line up. A date near year-end adds strain, because the accounts team is still finalizing the old books for the auditors.

Payroll. Payroll, including government contributions, often stays with a payroll system or provider. The cutover confirms that payroll journals map to the new accounts, departments and, for BPOs, programs or clients.

Branches. Each branch has a cutover owner who confirms stock counts, cash on hand and open deliveries, and who knows how to reach support on the first day.

All of this goes into a checklist with timings and checks, reviewed at a go or no-go meeting before the switch. My ERP go-live support service describes the wider approach.

UAT, training and hypercare across branches and shifts

Testing must involve the people who will depend on the system: branch cashiers and sales staff, warehouse teams, accounts payable and receivable, and approvers. My scripts reflect Philippine operations, such as an invoice from a branch series followed by a cancellation, a supplier payment with withholding and its certificate, a customer receipt net of withholding, a USD client invoice for a BPO program and a stock transfer between islands. Every issue is sorted with the implementer into faults, design gaps, training needs or new requests, following the method on ERP testing and UAT.

Training reaches every location through recorded sessions and live calls. The engagement runs in English. Your trainers or the implementer translate and deliver sessions for staff who learn better in Filipino or a regional language.

Post-launch support is remote, built around a short daily call where key users and the implementer go through what broke the day before. Night-shift BPO teams use the shared log and recorded walkthroughs, so their issues are not lost between shifts. My part ends once the opening month has been closed and that period's tax reporting is produced in the new system. Companies still comparing platforms can read about my ERP selection work in the Philippines and the Philippines overview.