Integration Consultant, Philippines

Integration and BIR-registered systems

In the Philippines, the system that produces invoices and books of accounts is subject to BIR rules, and computerized accounting systems generally go through registration before use. That gives integration work an extra dimension: a new interface that creates invoices, posts journals or changes how records are produced may affect the registered system, and your accountant needs to know about it before it goes live.

I make this part of the design rather than an afterthought. For each proposed flow, the specification states whether it creates or modifies accounting entries in the registered system, which documents it generates, how numbering and audit trails are preserved and what reports are affected. Those points become a list of questions for your accountant, who advises whether any notice, update or review is needed.

The direction toward electronic invoicing adds another reason to keep data structured. The BIR has been introducing electronic invoicing and sales reporting for selected taxpayers, with scope and timing that are still developing. Integrations designed now should keep customer TINs, addresses and invoice lines clean and consistent, so a future submission route does not require rework. Which obligations apply to your business is a question for your tax advisor.

None of this is about slowing projects down. It is about avoiding the situation where a well-built integration goes live and finance later discovers that the registered system no longer behaves as described. The general method is on my system integration page.

Banks, e-wallets and payment gateways

Collections in the Philippines arrive through more channels than many accounting setups expect: bank transfers, over-the-counter deposits, cards, e-wallets and payment centers. Electronic channels often settle through a gateway in batches, after deducting fees, and the bank statement shows one credit where your receivables ledger expects many.

The integration design focuses on how each payment is identified and matched. I specify which settlement reports and statements are imported, how often, and the reference that links each payment to an invoice or customer. Rules then cover partial payments, one deposit paying several invoices, payments net of withholding tax deducted by corporate customers, refunds and fees.

On the outgoing side, I confirm what your banks offer for your account type, whether payment files, portal uploads or APIs, and keep authorization clear so an automated file never skips a required approval. Payroll disbursements follow the same discipline, with bank files generated from the payroll system and the corresponding journal posted to the ERP.

For BPOs and other firms paid by overseas clients in dollars, the design also captures exchange rates and bank charges on inward remittances, so peso receipts reconcile against dollar invoices without manual adjustment. The aim is that finance starts each day with a current receivables position and a short list of genuine exceptions, rather than a pile of unmatched deposits.

BPO and shared service flows: from hours worked to client invoices

For outsourcing and shared service operations, the most valuable integration is often the one between operations and billing. Revenue depends on hours, seats, transactions or outcomes recorded in timekeeping and workforce systems, while invoices are issued from the registered accounting system. When the link between them is a spreadsheet, billing is slow and disputes are hard to settle.

I design that link with operations, finance and account managers together:

• which system is the source for billable units, and when data is final for the billing period
• how rate cards, minimum commitments and adjustments in each client contract are applied
• who approves billable data before it becomes an invoice
• how dollar invoices are produced while books are kept in pesos
• how costs are allocated so margin by client or program can be reported

Where the Philippine entity serves a foreign parent, the design also covers intercompany charges and the reporting file the parent expects, mapped to the group chart of accounts with agreed currency rules. That turns a monthly manual exercise into a repeatable feed with checks. Tax treatment of cross-border services is for your advisor to confirm. If the commercial side of these client relationships also needs work, my CRM consulting for Philippine companies covers pipelines and handoffs.

Branches, POS, marketplaces and logistics across islands

Distributors and retailers with operations across Luzon, Visayas and Mindanao face integration problems that a single-site business never sees. Branches may run their own POS, connectivity can be unreliable, and stock spends days in transit between islands.

For POS integration, the design states how sales, returns and payments are sent to the ERP, what happens when a store is offline, how each branch's invoice series is respected and how takings reconcile with bank deposits. For inventory, it agrees item and branch codes, how transfers are recorded at dispatch and receipt, and how stock in transit is shown so it is neither lost nor counted twice.

Online channels add their own flows. Marketplace orders, returns and settlements need to be mapped so that fees, vouchers and payouts can be separated and reviewed by your accountant. Couriers and logistics providers can return tracking and delivery confirmations, which helps customer service and supports collection on delivered orders.

For each of these flows, I document the trigger, timing, field mapping and failure handling, and test with real samples from more than one branch. The goal is that head office sees one consistent picture of sales and stock, while each branch keeps the documents its own registration requires.

Methods, monitoring and ownership after go-live

I separate design from build from the start. I take responsibility for the integration design, who owns which master data, the interface specifications, the recommended method and the test plan, and I review what the builder delivers against them. The builders may be your implementer, in-house developers, the parent company's IT group or an independent developer. A handful of flows can be handled with a standard connector or a small low-code automation, and I can usually configure those within the engagement.

The method is chosen per flow, not per project. Bundled connectors are the cheapest option when they genuinely fit. An integration platform, for example Make, n8n or Zoho Flow, helps when the same records travel between many systems, but somebody in the company must administer it. Custom code makes sense for heavy volumes or unusual logic, and then needs an owner for hosting and fixes. Plain scheduled files remain sensible for bank uploads, payroll and parent reporting, as long as nobody has to move them by hand.

Test cases include the awkward ones: a branch that was offline for a day, a payment received twice, a bank file the bank refuses, a revised client rate and a timekeeping correction after cutoff. Finance ties out samples, and your accountant looks at anything touching registered records before sign-off.

Afterwards, each interface has a person who receives its alerts, a troubleshooting note and a support clause naming who repairs it. Delivery is remote, in hours that overlap with the Philippine working day. The Philippines hub and my ERP consulting for Philippine companies describe related support.