Every peso traces
back to the authority
to spend it.

On the live service today: the UACS Revised Chart of Accounts — 888 eight-digit posting accounts, 828 of them active — seeded and shared by every agency, per-agency adoption of that chart, and a double-entry, append-only ledger with period locks and an audit trail underneath it. Three things we will not overstate. The UACS dimension masters (funding source, organization, location, PAP, responsibility center, cash authority and the 7 fund clusters) and the government fields on bank accounts and employees are built and merged but not yet deployed. The GAM statement cascade is implemented and tested but not yet wired into the Reports screen, which still shows the commercial statement titles. And the transaction modules — ORS/BURS, disbursement vouchers, claims, payments, collections, payroll, cash advances, inventory and PPE — are built and merged, each with its own register and posting rules, but they are on the same footing as the masters above: not yet applied to the live database, so no agency can record one today. If your evaluation depends on any of those, ask us and we will show you the working code.

The COA Government Accounting Manual for National Government Agencies, Volumes I to III; the UACS Revised Chart of Accounts and Sub-Object Code masters published by uacs.gov.ph; COA Circular No. 2020-001 (Revised Chart of Accounts, updated 2019); and COA Circular No. 2022-002 for later conversion guidance. The account codes, titles, normal balances and statement mappings come from those sources rather than from our own naming.

No. It is accounting software built to the GAM and UACS rules — it is not a COA accreditation, and it does not substitute for your agency's own compliance with the effective COA, DBM, BTr and UACS issuances for your fiscal period. Your accountant and your resident auditor remain responsible for what the agency reports.

They are separate series, always. A disbursement voucher number is never reused as a JEV number: the DV keeps its own number and the accounting entry receives a JEV number from the JEV series, linked back through a source-link record. One source transaction can produce several JEVs, several source documents can be summarised into one JEV, and a manual adjusting entry gets a JEV number with no source document at all. Reversals and corrections take new JEV numbers and reference the original.

It is reversed or adjusted, never deleted. Approved and posted government documents are immutable; a correction is a new document with its own number that links back to what it corrects, so the audit trail shows both the original entry and the fix. Cancelled and voided numbers stay in the trail and are not recycled.

That is the specified behaviour and it is what the expenditure modules are being built to: allotment bounded by adjusted appropriation, obligation by available allotment, disbursement by the adjusted obligation, and payment by both the remaining approved DV and available cash authority — each checked before approval, with the document blocked rather than warned. Those modules are not in the product yet, so today the ceilings are a design commitment, not a control you can test.

No. Full procurement, BAC processes and PhilGEPS integration, and a full human resource information system, are deliberately outside Phase 1. The scope starts at the agency's approved annual financial plan and covers the accounting cycle from budget authority through to the statutory and financial reports.

An administrator provisions them. There is no self-serve sign-up and no public registration — an account has to be created for it to work at all, and roles are assigned per user, so an agency controls exactly who can record, certify, approve and post. Contact us to set your agency up, then your people sign in with the credentials they are issued.

Yes. Every read is scoped to your entity by row-level security in the database, and every write goes through a server-side function that re-checks the caller's permission in the database itself — not in the browser. A user signed in to one entity cannot read or write another's records, whatever the client sends.

Yes. Ledgers, statements and registers export while your access is active, so your agency's records are portable and can be handed to your auditor or your own systems.