How Should Treasury Configure Accountable Form Series Before Live Use?

An accountable form series setup should begin with Treasury's verified physical inventory, not with a blank system range. Before live use, staff should confirm the accountable form type, inclusive serial numbers, quantity, assigned accountable officer or collector, supporting issue record, and any known defect or missing number. The digital configuration should then mirror those verified records, undergo overlap and boundary tests, and receive Treasury review before the range is used for actual collections.

A connected LGU treasury and collection records environment can support traceability and controlled access, but software does not confer legal custody, assign accountability on its own, or replace the records of the Commission on Audit (COA) and the Bureau of Local Government Finance (BLGF).

Why Should Setup Start With the Physical Accountable Forms Inventory?

The safest starting point is the accountable forms that Treasury has actually received, inspected, recorded, and placed under custody. COA guidance designates the local treasurer as the custodian of accountable forms requisitioned by the local government unit (LGU) and requires a complete record of their receipt, issuance, and transfer.

That means the system should not invent a range simply because the serial numbers appear to be sequential. Staff should first compare the proposed configuration with the LGU accountable forms inventory, including the form type, quantity, inclusive serial numbers, and custody record.

A system entry can look orderly even when the underlying booklet, pad, or batch has a defect or is unavailable for assignment. To ensure these issues are visible and managed consistently, staff should document any discovered defects or missing forms directly in the system. This may involve flagging the affected serial numbers, adding a brief description of the defect or exception in the setup record, and attaching supporting notes or scanned evidence when available. Clearly documenting defects at the point of setup helps Treasury keep accurate records and ensures that only authorized and usable forms are placed into active use.

Which Official Records Should Control the Initial Setup?

Treasury should use the official records that establish receipt, custody, and issuance as the source for configuration. The exact documents can vary, but the digital record should point back to authoritative evidence.

Local treasury guidance records accountable forms using information such as booklet or quantity details, serial numbers, the accountable officer to whom the forms are issued, dates, and inclusive serial numbers for received batches. A digital setup record can reference those same facts without replacing the official forms.

If the physical record and the proposed system range disagree, the discrepancy should be resolved before activation rather than hidden via a manual override without explanation.

What Should an Accountable Form Series Setup Record Contain?

A practical setup record can give Treasury one place to review the proposed series before live use. Recommended fields include:

• accountable form name, type, or code

• physical batch, booklet, pad, or source reference

• quantity covered by the proposed series

• inclusive serial number from

• inclusive serial number to

• accountable officer, collector, or cashier assigned under the applicable process

• issue or assignment reference

• date of assignment

• known defect, missing number, or exception note

• configuration status

• person who encoded or prepared the setup

• person who tested the configuration

• Treasury reviewer and review date

This is a recommended system-control record, not a new nationally prescribed COA or BLGF form. It is designed to support the proper maintenance and review of accountable forms in line with official requirements, but it does not replace or override the use of nationally mandated forms. Staff can be reassured that maintaining this record helps demonstrate compliance with national rules while ensuring that the official forms and procedures remain in full effect.

How Should Treasury Define the Serial Range Boundaries?

For an official receipt number series or another serial-controlled accountable form, the proposed starting and ending numbers should match the verified inclusive range under Treasury custody. Staff should also confirm that the quantity implied by the range is consistent with the underlying record.

For example, a proposed range from 120001 to 120050 appears to contain 50 serial numbers. That arithmetic check is useful, but it does not prove that all 50 forms are physically present or usable. Treasury still needs the source inventory and inspection evidence.

The range should also identify the correct form type; similar serial numbers do not make different accountable forms interchangeable.

What Should Happen When a Defect or Missing Number Is Found Before Activation?

The Local Treasury Operations Manual provisions quoted by the Supreme Court describe the inspection of accountable forms upon receipt and the segregation of books or pads with defects such as incorrect numbering series or missing leaves or sheets. That principle is important before digital activation.

If a known defect affects the proposed range, Treasury should not configure the series as though every number were normally available. The affected forms should follow the applicable inspection, reporting, and disposition procedures, while the system setup should reflect only what Treasury is authorized to place into use.

A hold status, exception note, or restricted activation is a local configuration choice, not a universal legal requirement. However, as a best practice, Treasury should adopt a standardized approach to handling exceptions by using a 'hold' status for any range or serial number with a known defect, a missing form, or an unresolved issue. This helps ensure that exceptions are clearly documented, consistently reviewed, and auditable in the future. Implementing a designated 'hold' process before activation promotes transparency and control over the inventory of accountable forms.

Who Should Own the Form Range Assignment?

COA guidance states that collectors or tellers requisition accountable forms from the treasurer and become accountable for the forms issued to them. It also prohibits direct transfers of accountable forms between collectors or tellers under that guidance.

For digital configuration, the form range assignment should therefore follow the approved Treasury issue and custody record. The system entry should identify the correct accountable officer or collector, rather than allowing staff to assign a series based solely on convenience.

ICT or system administrators may encode or configure authorized values, but technical access does not make them the legal custodian of the forms. Treasury remains responsible for the official custody and assignment process.

How Should Cashier System Configuration Separate Duties?

Cashier system configuration should distinguish among preparation, testing, review, and actual use whenever the LGU's staffing and controls allow. A user who types a range into the system should not automatically be treated as the person who authorizes its operational use.

A practical separation can assign one role to prepare the range, another to verify it, and a controlled account to use it. The record should show who performed each action.

Role-based access is useful here because it can reduce casual changes to serial-range settings. The access model should follow actual Treasury authority rather than create new authority through software permissions.

Which Pre-Live Tests Should Treasury Run?

Before collections begin, Treasury can run controlled tests to confirm that the configuration reflects the verified inventory.

1. Valid range test: confirm that one verified range is connected to the correct form type and authorized user.

2. Overlap test: try a second proposed range that intersects an existing assignment and confirm that the conflict is identified for review.

3. Boundary test: check the first and last serial numbers and confirm that no number outside the authorized range is treated as part of it.

4. Exception test: confirm how a known defective, unavailable, or excluded number is represented under the LGU's approved configuration.

5. Role test: verify that users who should only view the setup cannot alter the series.

These tests are recommended controls. They do not establish that every ERP product automatically performs the checks. If your system does not include features to run these checks, staff should perform them manually before activation. This includes reviewing configurations for overlaps, boundary issues, and defects, and ensuring proper assignment to accountable officers by comparing system entries with physical and official records. Manual checks help ensure accuracy and compliance when automated tools are limited or unavailable.

How Can Treasury Handle an Overlapping Range During a Setup Rehearsal?

Suppose Cashier A is prepared for serial numbers 310001 to 310050. During a rehearsal, another setup entry assigns Cashier B the range 310041-310090. The second form range assignment overlaps the first by ten numbers.

Treasury should prevent the second setup from going live until the source records have been checked. Staff can compare the physical forms, issue records, and authorized assignments to determine the intended range. If Cashier B should actually receive 310051-310100, the configuration can be corrected and retested before activation.

The important control is the review process, not the assumption that software alone will discover every error.

How Should Treasury Verify the Official Receipt Number Series Before Go-Live?

For an official receipt number series, Treasury should verify the form type, the beginning and ending serial numbers, the quantity, the accountable officer, and the supporting issuance information against the source record. Staff should also confirm that the same serials are not active under another current assignment.

If the system is being configured before a new cashier starts collecting, the test should use controlled sample transactions rather than consume or alter the actual accountability trail without proper authority.

The final review should answer a simple question: does the system show the same accountable-form identity and custody relationship as Treasury's official records?

What Evidence Should Be Kept Before Activation?

Before approving the setup for live use, Treasury can retain a small evidence pack containing the source inventory reference, proposed range, assigned user, configuration screenshot or export when appropriate, test results, exceptions found, corrections made, and reviewer sign-off.

Republic Act No. 12254 supports government records systems that manage the creation, processing, tracking, storage, verification, authentication, and archiving of records, subject to existing laws and policies. That supports the use of traceable digital evidence, but it does not change the underlying rules for accountable forms.

The evidence pack should make the setup understandable later without creating unnecessary duplicate records. For audit and compliance purposes, Treasury should retain the evidence pack for the period specified by applicable LGU record-keeping or COA retention guidelines, which is typically at least 5 years, unless a longer retention period is required for pending audits or legal matters. Always refer to official retention schedules to ensure alignment with current requirements.

How Can Connected Records Support Treasury Control?

GoLGU's public product information lists Accountable Form Inventory under Treasury and Cashier functions, while its ERP page describes traceability, centralized data, and role-based permissions. Those capabilities are relevant to an accountable form series setup because authorized users may need to review custody references, range details, and user access in one connected workflow.

They should not be described as proof that GoLGU automatically validates every serial range, determines accountability, blocks every overlap, or replaces Treasury's COA and BLGF records. The LGU still needs verified source information, authorized roles, and a documented pre-live review.

Conclusion

An accountable form series setup is safer when Treasury starts from verified physical and official records, configures only authorized serial ranges, assigns them to the correct accountable users, and tests the setup before actual collection begins. The strongest controls connect the LGU accountable forms inventory to the digital record without treating the system as the source of legal authority.

A clear cashier system configuration also separates preparation from review and keeps exceptions visible. If a range overlaps, contains a known defect, or does not match the custody record, resolve the discrepancy first and activate only the verified configuration.

Review Your Treasury Setup Workflow

If your LGU is reviewing how accountable-form inventory, cashier assignments, serial ranges, and Treasury records should connect before live use, you can request a GoLGU demo to discuss how your existing workflow could be mapped into a connected system.

Frequently Asked Questions

Can Treasury create a serial range in the system before the physical forms arrive?

The safer approach is to base live configuration on accountable forms that Treasury has actually received, inspected, and recorded. A planning or test record should not be mistaken for an authorized live range.

Who is accountable for forms issued to a cashier or collector?

COA guidance makes collectors or tellers accountable for forms issued to them through the Treasury process. The digital assignment should reflect that official custody relationship rather than create a separate one.

What if two proposed ranges overlap before activation?

Hold the conflicting setup for review; compare both entries against the source inventory and issue records; correct the incorrect range; and retest before live use.

Does every missing serial number mean staff can skip it in the system?

No. A missing, defective, lost, or otherwise unavailable form can require a specific official process. The system should reflect the authorized treatment rather than silently remove the number from history.

Can an ICT administrator approve the accountable-form assignment?

Technical access does not automatically create Treasury authority. An administrator may configure approved values, but the assignment and operational authorization should follow the LGU's applicable Treasury and accountability procedures.

Is pre-live testing the same as reissuing surrendered accountable forms?

No. Pre-live testing checks an initial configuration before actual use. A range that has already been issued, surrendered, accepted back, and considered for another issue involves a different custody event and should follow the applicable Treasury process.

References

• Republic Act No. 7160, Local Government Code of 1991

• Commission on Audit Circular No. 92-382 — Accountable Forms Custody and Requisition Provisions

• Bureau of Local Government Finance — Local Treasury Operations Manual, 2nd Edition, 2019

• Supreme Court E-Library — Decision Quoting LTOM Accountable-Form Control Provisions

• Republic Act No. 12254, E-Governance Act

Disclaimer

This material provides general operational information for Philippine LGUs. It does not replace COA rules, BLGF treasury guidance, local issuances, accountable-officer requirements, audit instructions, or legal advice.