ERP Audit Consultant, Philippines

Why an ERP review matters after BIR registration

For many Philippine companies, registering a computerized accounting system with the BIR is a milestone that marks the end of the project. Configuration was documented, sample outputs were prepared and the system was approved for use. The risk is that the system then evolves while the documentation stays still.

An ERP audit compares the system as it runs today with how it was designed and registered. I list what has changed: new modules, custom fields on invoices, changed layouts, new branches, new integrations or reports. Your accountant or tax advisor judges whether a change must be reported or touches the registration; I simply hand them a complete and dated list rather than leave them to discover it.

It is worth being clear about what this review is not. Your external auditor examines the financial statements and expresses an opinion on them. Your tax advisor deals with BIR matters. An ERP audit sits beside both: it looks at software, setup and use. Typical triggers include a new finance head, preparation for a parent company review, adding branches or a new entity, and growing reliance on spreadsheets. If go-live itself went badly, the ERP rescue page for the Philippines fits better.

Branch invoice series, withholding and e-invoicing readiness

Philippine tax rules reach deep into ERP design, so this part of the review is detailed. I examine what the system does and record it with sample documents; your accountant confirms whether it is right.

• Invoice series by branch. Whether each branch and document type has its own series, how cancelled and voided documents are recorded, and whether any location still issues manual invoices that are later keyed into the system.
• Invoice content. Whether printed and electronic invoices show the details your advisor expects under current rules, including how VAT and non-VAT sales are presented.
• Withholding on purchases. How rates are assigned on supplier masters, whether withholding is calculated at the right stage and whether certificates for suppliers can be produced from the system.
• Withholding by customers. How tax withheld by your customers is recorded against receivables, and whether the certificates you receive are tracked so the credit is not lost.
• E-invoicing direction. How ready your masters, customer data and document structure are for electronic invoicing and sales reporting as the BIR extends it, with scope and timing confirmed by your advisor.

Each point becomes an entry in an accountant question log, kept separate from configuration fixes, so tax decisions and system changes do not get confused.

BPO billing, dollar books and margin by client

Philippine outsourcing and shared service operations often bill overseas clients in US dollars while paying salaries and most costs in pesos. That combination puts pressure on several parts of the ERP at once, and small configuration choices can distort margins without anyone noticing.

I review how client contracts, rates and billing cycles are set up, whether invoices are generated from time or headcount data in the system or assembled in a spreadsheet, and how collections in dollars are applied and revalued. I check the bank structure as well: dollar and peso accounts, transfers between them, and how exchange differences are posted.

The central question is usually margin. Leadership wants to know which clients, programs or sites make money once shared costs such as facilities, IT and support teams are allocated. I look at whether cost centers and allocation rules make that possible from the system, or whether finance rebuilds the view each month from exports. Where a parent company sets the reporting format, I check whether the local ERP can feed it without manual mapping.

Findings here tend to point to structural fixes such as cost center design or allocation rules. The multi-currency ERP page explains the design options in general terms.

Payroll links, integrations and access across shifts

Payroll in the Philippines usually runs in a separate system or with a provider that handles contributions to SSS, PhilHealth and Pag-IBIG and withholding on compensation. What reaches the ERP is a summarized posting. I verify where that posting goes by account, cost center and entity, whether contribution liabilities are cleared on remittance, and whether payroll totals are agreed to the general ledger every period rather than once a year.

I then list every other integration: bank files, time and attendance, CRM, ecommerce, warehouse tools and BI dashboards. For each, I note what it sends, how often, under whose credentials and how a failure would be noticed today. Silent failures matter most, because their errors build up quietly.

Access needs particular care where teams work in shifts or across islands. Shared logins between day and night teams, generic branch accounts and administrators who are no longer in the role are common risks in that setting. I export users and roles and test sensitive permissions:

• creating a supplier and paying it without a second person
• editing or voiding posted invoices
• reopening closed periods
• exporting employee or customer personal data, which your data protection officer should review against the Data Privacy Act

Spreadsheets, report trust, licenses and the findings report

Every audit includes an inventory of the spreadsheets that run beside the ERP. In a Philippine company these might be a branch sales summary, a withholding tracker, a client margin model or the monthly management pack. Behind each file sits an unmet need, and the full list maps out exactly where confidence in system numbers has worn away.

I trace the reports leadership actually uses back to their source. If a figure is exported, adjusted and re-entered before anyone sees it, I note where and why, and whether the cause is data, configuration or process.

License use gets a quick but useful check: paid users and modules compared with real activity across entities and branches, so the next renewal reflects what you need.

The final report ranks each finding by business impact and urgency and describes the situation, its business consequence, the probable root and a proposed remedy, with a suggested owner among your team, your implementer and your accountant. I present it to leadership in an online session. The method behind it is described under ERP health check, and the Philippines overview and ERP consultant page for the Philippines cover my wider work there.