Own your cash position, bank reconciliation, and AP/AR aging in one system.

We replace. We build. We optimize.

Every line of code we write is yours at cutover. No license. No annual increase. No lock-in.

What does a custom treasury system actually do for daily cash management?

It aggregates balances from every bank account automatically, matches transactions against AP/AR records, and gives the CFO a single cash position figure before the first meeting.

The system connects to Philippine bank portals — BDO, BPI, Metrobank, RCBC, Unionbank, and others — via host-to-host file transfer or direct API where the bank supports it. Every debit and credit is ingested, tagged to a cost center or entity, and matched against open payables and receivables. The CFO sees total available cash, pending disbursements, and expected inflows on one screen. The controller's job shifts from assembling the number to reviewing exceptions the system already flagged.

How does the system handle multi-bank cash position visibility across all accounts?

All accounts — current, savings, time deposits, and dollar accounts — feed into a single consolidated position updated on the bank's cut-off cycle.

Bank statements arrive as MT940 files, CSV exports, or API responses depending on the bank. The system normalizes them into a single ledger. Each account is tagged by entity, currency, and purpose — operating, payroll, tax, capex. The treasury dashboard shows the consolidated peso-equivalent position, broken down by entity and by bank, with drill-through to individual account balances and pending transactions. Time deposits maturing within 30, 60, and 90 days are surfaced separately so placement decisions are made before the deadline, not after.

How does automated bank reconciliation work, and how quickly does it clear?

Transactions are matched against GL entries and AP/AR records as each bank file arrives — not once a week. Unmatched items are queued for controller review, not left to accumulate.

Matching rules are configured to your chart of accounts and payment workflows: payroll runs, vendor batch payments, collection deposits, inter-entity sweeps. High-confidence matches clear automatically. The controller reviews only the exceptions — typically 3–8% of transaction volume — which takes minutes rather than hours. The reconciliation is current at any point in the day. Month-end close accelerates because the outstanding items list is short and aged at most a few days, not weeks.

Can the system produce a rolling cash flow forecast, not just today's position?

Yes. The system projects cash flow 30, 60, and 90 days forward by combining confirmed AP due dates, AR expected collection dates, and recurring obligations.

Forecast inputs come from three sources: open purchase orders and vendor invoice due dates from the AP aging, customer invoice due dates and collection history from the AR aging, and fixed obligations entered directly — loan amortizations, rent, payroll cycles, quarterly taxes. The model weights AR by historical collection rate per customer, so a 60-day receivable from a client who routinely pays at 75 days is reflected accurately. The forecast updates daily as new invoices are posted and payments clear. The CFO can see where the cash floor falls and plan drawdowns or placements accordingly.

How does the system handle intercompany transfers and multi-entity cash pooling?

Inter-entity loans, sweeps, and transfers are recorded on both sides simultaneously, keeping the consolidated and standalone positions accurate at all times.

Philippine multi-entity groups — holding company, operating subsidiaries, distribution arm — often pool cash informally through intercompany advances. The system treats each transfer as a bilateral transaction: a loan receivable in the lending entity and a payable in the borrowing entity. The consolidated cash view nets these out correctly. Notional pooling structures, where bank balances offset each other for interest purposes without physical movement, are also supported. The intercompany aging report shows outstanding balances by entity pair so settlement decisions are based on data, not memory.

Does it integrate with BIR reporting for VAT and tax-related cash movements?

Yes. VAT output and input tax settlements, withholding tax remittances, and quarterly income tax payments are tagged cash events with due-date tracking built in.

The system tags each disbursement to a BIR obligation category: expanded withholding tax (EWT) on vendor payments, creditable withholding tax (CWT) on collections, output VAT settlements, and quarterly/annual income tax payments. Due dates from the BIR tax calendar are loaded by fiscal year so the cash forecast includes every mandatory remittance. The controller sees the tax cash requirements 30 days out and can plan funding without scrambling. The system does not file the return — BIR eFPS or eBIRForms handles that — but it feeds the correct figures to the filing.

What about FX exposure and dollar-denominated bank accounts?

Dollar accounts are tracked at transaction currency, revalued daily at BSP reference rates, and the peso-equivalent position reflects unrealized FX gains and losses.

Philippine firms that import goods, service USD-denominated loans, or collect in dollars need to see their FX exposure alongside the peso cash position. The system holds each transaction in its original currency — USD, EUR, JPY, or other — and applies the BSP reference rate published each banking day for the consolidated peso view. Unrealized gains and losses on USD balances are computed automatically, consistent with PFRS 9 requirements. Forward contracts and FX hedges can be logged as pending transactions so the hedged and unhedged exposure is visible separately. The system does not execute trades; it gives treasury the position data to decide.

What does a treasury system implementation look like from contract to go-live?

Twelve to eighteen weeks from contract: bank connectivity first, then reconciliation rules, AP/AR aging feeds, and forecast model — each phase with sign-off before the next begins.

Week one and two are spent mapping your bank accounts, entities, and chart of accounts. Bank file formats are confirmed with each institution; host-to-host enrollment typically takes two to four weeks with Philippine banks, so that process starts immediately. Weeks three through six build the reconciliation engine against your actual transaction history. Weeks seven through ten connect AP and AR aging from your ERP or accounting system. Weeks eleven through fourteen build the cash forecast model and run parallel with the existing Excel process so discrepancies can be explained before cutover. The last two to four weeks are stabilization and controller training. Optional ops support at ₱50K–250K/month covers monitoring, reconciliation exception triage, and system updates after go-live.