How Should GSO Maintain a Partial Delivery Item Issuance Record?
A partial delivery item issuance record should keep every supplier delivery and every department release as separate dated transactions under one purchase reference. The General Services Office (GSO) should distinguish the quantity ordered, cumulative quantity delivered, cumulative quantity accepted, cumulative quantity issued, accepted stock still available, and quantity the supplier has not yet delivered. Issue items only from quantities already received and accepted under the applicable process. For teams using connected LGU procurement records, the system should preserve these relationships and not treat an undelivered purchase balance as inventory already on hand.
Why do partial deliveries create confusing inventory balances?
One purchase reference can remain open while several deliveries arrive on different dates and accepted items are already released to departments. If staff keep only one running "balance," they can confuse the quantity still owed by the supplier with accepted stock still available. The record should therefore preserve each movement separately.
Which quantities should GSO keep separate?
For each item under the purchase reference, GSO should distinguish at least these quantities:
Ordered quantity: the total quantity covered by the purchase reference.
Delivered quantity: the physical quantity presented in one delivery event.
Cumulative delivered quantity: all deliveries recorded so far.
Accepted quantity: the quantity cleared through the applicable inspection or acceptance process.
Cumulative accepted quantity: all accepted quantities across deliveries.
Issued quantity: the quantity released to a department or other authorized recipient.
Cumulative issued quantity: all authorized releases recorded so far.
Accepted stock available: accepted quantity not yet issued.
Undelivered purchase balance: ordered quantity not yet delivered by the supplier.
Two useful calculations are:
Accepted stock available = cumulative accepted quantity − cumulative issued quantity
Undelivered purchase balance = ordered quantity − cumulative delivered quantity
They answer different questions.
What should a partial delivery item issuance record contain?
A practical record should let another authorized reviewer reconstruct how the item moved from the purchase reference through each delivery and release. The following is a recommended traceability structure, not a claim that every LGU requires one national form with these exact fields.
Record:
purchase order, contract, or other authorized purchase reference
item code or sufficiently specific item description
ordered quantity and unit of measure
delivery sequence or delivery reference
delivery date
quantity delivered in that event
quantity accepted, rejected, or held, when applicable
receiving, inspection, or acceptance reference
storage or custody location, when relevant
department release date
quantity issued
recipient department or authorized recipient
issuance or release reference, such as an RIS where applicable
accepted stock available after the transaction
remaining undelivered purchase balance
How should GSO record the first partial delivery?
Start with the common purchase reference and ordered quantity, then create a separate entry for the first delivery rather than changing the original order quantity.
For example, if the purchase reference covers 100 office chairs and the supplier delivers 40, the ordered quantity remains 100. Record 40 as Delivery 1. If 38 are accepted and two are held or rejected under the applicable process, the cumulative accepted quantity is 38.
The undelivered purchase balance is 60, while accepted stock available is 38 before any issue. This is the first control in GSO partial delivery tracking: preserve the original order quantity while adding each delivery separately.
How should GSO link a department release to accepted stock?
A department release should point only to stock already valid for issuance under the applicable receiving and acceptance process. Undelivered quantity is not available inventory.
Continuing the example, assume GSO issues 25 of the 38 accepted chairs to Department A. The department item release record should show the release date, recipient, quantity, item, and relevant issuance reference.
The figures now become:
Ordered: 100
Cumulative delivered: 40
Cumulative accepted: 38
Cumulative issued: 25
Accepted stock available: 13
Undelivered purchase balance: 60
The release changes available stock, not the supplier's undelivered balance.
What happens when the next partial delivery arrives?
Add the next delivery under the same purchase reference without erasing either event's date, quantity, or acceptance result.
Suppose Delivery 2 contains 35 chairs and all 35 are accepted. The totals now become:
Ordered: 100
Cumulative delivered: 75
Cumulative accepted: 73
Cumulative issued: 25
Accepted stock available: 48
Undelivered purchase balance: 25
If GSO later releases another 20 chairs, cumulative issued becomes 45, and accepted stock available becomes 28. The supplier still has 25 chairs left to deliver.
This is the core of the partial-delivery inventory balance: each delivery and issue changes a specific quantity, not every quantity.
How should rejected or held quantities affect the record?
Keep delivered and accepted quantities separate. A quantity that arrived but has not been accepted should not automatically increase stock available for issuance.
If a delivery contains 20 units but only 18 are accepted, the delivery record should preserve both figures. The reason and supporting acceptance or inspection record should remain linked under the applicable process.
This article does not define inspection standards or decide whether to reject a delivered item. The separate receiving-to-issuance problem is outside this article. Here, the focus is on what happens after quantities are accepted and then issued while the purchase remains only partially delivered.
How should GSO reconcile the procurement delivery balance?
Check the procurement delivery balance against the original ordered quantity and every recorded delivery under that purchase reference.
At any review point, staff should answer:
How many units were ordered?
How many have physically arrived?
How many were accepted?
How many were rejected or remain unresolved?
How many accepted units have already been issued?
How many accepted units remain available?
How many units has the supplier not yet delivered?
If the record cannot answer all seven questions without staff reconstructing several spreadsheets, the trace is incomplete.
Why should each delivery and release remain a separate checkpoint?
Delivery, acceptance, and issuance are different events even when they occur on the same day. Each may have a different responsible office, date, user, or supporting record.
The guide on transaction checkpoints for ERP traceability explains why a current status alone may not show how a government transaction reached that state.
For partial deliveries, the checkpoint structure is especially useful because later releases should remain traceable to accepted stock that existed at the time of issuance.
Should GSO change the original purchase quantity after each delivery?
No. The original ordered quantity remains the baseline for determining how much is still undelivered.
If the authorized procurement requirement itself is formally changed, that is a different event and should follow the applicable procurement procedure. A partial delivery is not, by itself, proof that the purchase quantity was revised.
Pre-procurement planning changes are also outside this article's scope. The separate guide on PPMP version changes before procurement starts covers that earlier planning stage.
What does Philippine LGU authority mean for the record?
Section 490 of Republic Act No. 7160 assigns the general services officer responsibilities involving LGU property, records management, supply, and property management. This provides the local-government context for maintaining understandable custody and supply records.
Republic Act No. 12009 and its current GPPB-approved Implementing Rules and Regulations govern government procurement. GPPB formally advised in July 2026 that the separate "1st Edition, as of 31 March 2026" IRR had been withdrawn and should not be used. This article therefore relies only on the GPPB-approved IRR effective February 25, 2025, for procurement context.
The 2026 E-Governance Act IRR also provides for an auditable digital procurement and supply-chain environment covering contract management, delivery, acceptance, and payment, along with digital records creation, tracking, storage, verification, and authentication. These provisions support traceability but do not create the exact supplemental partial-delivery record proposed here.
How should GSO review the record before the purchase is complete?
Compare the running record with the purchase reference, delivery documents, acceptance results, stock or custody records, and department releases.
A useful review checks that:
every delivery belongs to the correct purchase reference;
cumulative delivered quantity equals the sum of recorded deliveries;
accepted quantity does not exceed the quantity supported by acceptance records;
cumulative issued quantity does not exceed cumulative accepted quantity;
accepted stock available agrees with the underlying stock or custody record;
the undelivered balance agrees with ordered quantity less cumulative deliveries; and
each release identifies its authorized recipient and reference.
Resolve differences before the next issue or before the final delivery closes the purchase record.
How can GoLGU support the trace?
GoLGU's public ERP page describes traceability, centralized and standardized data, role-based access, efficient workflows, and reporting. It also gives a procurement example in which staff can see requested items that have not yet arrived.
Those public descriptions are relevant to a partial-delivery workflow, but they do not establish that every calculation or field described in this article is automatically available or legally validated. An LGU should verify the actual configuration, record relationships, roles, and reports during implementation.
Teams reviewing how purchase references, partial deliveries, accepted quantities, releases, and balances connect can schedule a GoLGU consultation.
What is the practical rule for partial-delivery issuance tracking?
A partial delivery item issuance record should preserve one purchase reference while recording every delivery and every release as a separate event. Keep ordered, delivered, accepted, issued, available-stock, and still-undelivered quantities distinct.
The practical test is simple: another authorized reviewer should be able to identify what the supplier has delivered, what GSO accepted, what departments already received, what remains available for issuance, and what the supplier still owes without reconstructing the transaction from memory.
Frequently Asked Questions
Can GSO issue items before the supplier completes the full order?
This article does not authorize issuing early or partially delivered items. Where the applicable procurement, acceptance, property, and local procedures allow issuance of already accepted quantities, the record should clearly separate those quantities from items the supplier has not yet delivered.
Is undelivered quantity the same as stock still available?
No. Undelivered quantity is the portion of the purchase that has not physically arrived. Stock available for issuance is accepted inventory already on hand that has not yet been issued.
Should rejected items be included in available stock?
No. A delivered quantity should not automatically become available inventory when the applicable inspection or acceptance process has not accepted it.
Should every partial delivery create a new purchase order?
Not merely because the supplier delivers the order in several shipments, where several deliveries belong to one existing purchase reference, each delivery should remain linked to that common reference. Any contractual change should follow the applicable procurement procedure.
What should GSO check before issuing from a new partial delivery?
Confirm that the applicable receiving and acceptance records support the quantity intended for release and that the running accepted-stock balance is sufficient for the issue.
Does GoLGU automatically reconcile partial delivery balances?
The public GoLGU materials reviewed describe procurement visibility, traceability, centralized data, workflows, and reporting. Still, they do not verify every partial-delivery field or automatic reconciliation rule described in this guide. The LGU should verify the configured behavior directly.
References
Disclaimer
This guide provides general operational information for Philippine LGUs. It does not replace Republic Act No. 12009 and its current official IRR, Commission on Audit rules, inspection and acceptance requirements, property and supply procedures, contract terms, local ordinances, valid delegations of authority, or professional legal, procurement, accounting, and audit advice. Each LGU should verify the applicable records, forms, responsibilities, and approval procedures before issuing items from a partially completed delivery.
Comments