Can end-user offices encode their own purchase requests?
Yes. Authorized office users raise purchase requests in the Procurement System, attach specifications, and submit them for the configured approval path.
Procurement System
Purchase Request Automation
Route purchase requests from end-user offices to BAC without spreadsheet chasing.
End-user offices raise purchase requests against the approved PPMP. Approvals, attachments, and status stay in one workflow instead of printed routing slips.
Purchase request automation gives municipal and provincial offices a single place to encode items, quantities, ABC, and charging details. Each PR can be checked against the PPMP before it moves to the next signatory, so BAC and Budget see the same record the end-user office submitted. Status, remarks, and supporting documents stay attached to the request — ready for RFQ, bidding, or alternative methods when the procurement activity starts.
Questions BAC offices ask
Does purchase request automation replace the PPMP?
No. PRs are checked against the PPMP so planned items, quantities, and timing stay aligned with the Annual Procurement Plan.
Related procurement capabilities
Purchase Order Generation
After award, generate purchase orders from the same items, prices, and supplier records used in bidding or shopping — then send them onward for obligation and delivery.
PPMP Consolidation
Offices submit PPMPs. BAC and Budget consolidate them into the APP, then use that plan to validate purchase requests and schedule procurement activities.
TWG Reports
The Technical Working Group records eligibility, technical, and financial findings against the bid documents, then submits a report the BAC can use for award.
NOA, NTP, and BAC Resolution Generator
After the BAC awards a procurement, generate the resolution, Notice of Award, and Notice to Proceed from the same supplier, amount, and project details.