UACS alignment
Accounts are organized around the UACS framework, helping teams use a consistent structure from budget setup through reporting.
Compliance & Security
Controls you can examine, not badges you have to trust.
BMIS supports structured LGU budget operations and reporting. We describe exactly what the product does—and avoid claiming certifications it does not hold.
COA-aligned report templates
BMIS generates structured outputs designed around applicable COA and DBM reporting concepts. Template alignment does not imply blanket certification of the software.
Data hosting & security posture
Marketing, demo, and client environments are separated. Production deployment requirements should define encryption, backups, access, monitoring, and incident responsibilities in writing.
Multi-level access & audit-readiness
A visible role matrix maps module access across defined administrator and user levels. Audit logs, configuration controls, and activity visibility help reviewers understand who did what and when.
Template depth
How detailed are the templated reports?
Detailed enough to move from a fiscal-year summary to a filtered office or account view, reconcile each budget layer, and inspect the obligation rows behind the totals.
Reconciliation report
SAAOB
SAAOB by account
By category
By sector
By fund source
Transactions by payee
demo.bmis.online/reports/reconciliation
Municipal Government of Sample · FY 2026
Reconciliation of Budget vs. Obligations
ReportPDFPrint
Office
All offices
Account
All accounts
Month
All months
Appropriation control
Appropriation₱248,750,000
Supplemental₱12,500,000
Realignment₱2,250,000
Total appropriation₱263,500,000
Less: Allotment₱214,000,000
Balance of appropriation₱49,500,000
Allotment & obligation control
Total allotment₱214,000,000
Less: OBR₱142,885,300
Balance of allotment₱71,114,700
Less: PR₱17,580,000
Total available budget₱53,534,700
DateOBR no.PayeeAmountEncoderAuthorized by
03/04/2026OBR-2026-0184Sample Vendor A₱1,275,000Budget User 02Department Head
03/02/2026OBR-2026-0182Sample Payee B₱485,300Budget User 01Budget Officer
Scope controls
Fiscal year, office, account, and month filters preserve the exact scope of each report run.
Reconciliation chain
Appropriation, supplementals, realignments, allotments, OBRs, PRs, and available balances are shown as a traceable sequence.
Transaction support
Obligation rows retain date, OBR number, payee, amount, remarks, encoder, and authorizing role where recorded.
Output formats
Teams can review in-browser, open or download a PDF, and print a consistent report copy.
Compliance boundary
Detailed templates support compliance; they do not certify it automatically.
A compliant output still depends on correct and approved account mapping, complete source records, authorized review and sign-off, and validation against the current COA, DBM, and LGU requirements applicable to the reporting period.
BMIS makes the report logic visible and repeatable. The accountable officers remain responsible for the underlying records and final submission.
Reference basis: DBM-COA-DOF UACS Manual, DBM appropriations, allotments, obligations, disbursements and balances reports, and COA annual reports on allotments, obligations and disbursements.
Due-diligence ready
Questions your technical and finance teams should ask.
01
Where is our LGU data hosted and backed up?
02
How are accounts provisioned and access changes approved?
03
Can we retrieve audit history and supporting records?
04
How is the sandbox kept separate from client data?
05
What is covered by support, recovery, and update commitments?
Request the detail