The Local Purchase Order is the foundational transaction document for government IT supply in Nigeria. Before any federal ministry, state agency, or government-linked institution can receive goods or services from a vendor, the LPO must be issued, and it must be issued correctly. Mistakes in the LPO process are not administrative technicalities; they create payment delays, audit findings, and, in the worst cases, full disallowance of expenditure.
This article explains how the LPO process works in a public-sector context, where the critical decision points are, and how institutions can manage the process without the delays that have made it notorious.
What an LPO is and what it is not
An LPO is a formal purchase commitment issued by a buying organisation, in public-sector IT, typically a ministry, department, or agency (MDA), to a vendor. It specifies the goods or services being procured, the agreed price, the delivery terms, and any applicable conditions.
What it is not: an LPO is not payment, and it is not a contract by itself. It is an instruction to supply. Payment follows after delivery, inspection, and the processing of a payment voucher or invoice through the appropriate financial authority.
Vendors who treat an LPO as equivalent to cash, or institutions that treat LPO issuance as the completion of a procurement, create problems downstream.
The statutory framework
Public-sector IT procurement in Nigeria operates under the Public Procurement Act 2007 at the federal level, with state procurement laws governing state-level spending. The Bureau of Public Procurement (BPP) is the regulatory body for federal procurements, and all procurement above defined thresholds requires BPP no-objection before award.
Key thresholds (as structured in the Act; verify current figures with BPP as limits are periodically reviewed):
- Procurements below the competitive tender threshold may proceed by direct purchase or limited tendering, with appropriate internal approvals
- Procurements above the threshold require open competitive bidding, with a published notice, a defined evaluation process, and BPP no-objection before LPO issuance
- Emergency procurements have their own procedures but must still be documented and justified
Government agencies that bypass these thresholds, typically by splitting orders into smaller pieces, create the type of audit exposure that procurement officers spend careers trying to avoid.
The standard LPO process step by step
Step 1, Needs identification and specification
A department or unit identifies a requirement and submits a formal request, typically a Purchase Requisition or equivalent internal document, to the procurement unit. The requisition must describe the need in functional terms, not simply list a brand or model, and must be approved by the appropriate budget authority.
This step is where poor specifications enter the process. A specification that says "laptop computers" without minimum technical requirements is an invitation to receive the wrong equipment and have no basis to reject it.
Step 2, Budget confirmation
The Finance or Accounts department confirms that a budget provision exists for the purchase and that the funds are available or committed. No procurement should proceed without this confirmation in writing.
Step 3, Market survey and request for quotations
For competitive procurements, the procurement unit approaches qualified vendors with a formal Request for Quotation. At minimum three vendors should receive the same specification. The RFQ specifies technical requirements, delivery timeline, and the format in which quotations must be submitted.
A common failure at this step is receiving quotations that are not comparable, one vendor quotes the full specification, another quotes a lesser product, and the price difference reflects the specification gap rather than competitive pricing. An itemised specification prevents this.
Step 4, Evaluation and approval
The procurement unit evaluates quotations on a documented basis, price is a factor but not the only factor. The evaluation report is submitted to the appropriate approval authority:
- Low-value procurements: departmental or ministerial tender board
- Mid-value procurements: ministerial tender board
- High-value procurements: BPP no-objection, followed by ministerial approval
The evaluation report must document the scoring rationale, not simply identify the winner.
Step 5, LPO issuance
Once approval is received, the procurement unit generates the LPO. A properly structured LPO contains:
- A unique LPO number and issue date
- Full vendor details (name, address, CAC registration number, account details)
- An itemised list of goods with quantities, unit prices, and total values
- Delivery address and expected delivery date
- Payment terms and the applicable Withholding Tax rate
- Authorising signatures (typically two, procurement officer and a financial authority)
The LPO is then issued to the vendor. This is the point at which the vendor is authorised to supply.
An LPO without the correct authorising signatures is not a valid commitment, and a vendor who supplies against an unsigned LPO has no guaranteed basis for payment.
Step 6, Supply and delivery inspection
The vendor delivers against the LPO. Delivery must be to the address specified and within the timeline stated. The receiving institution's stores or IT unit inspects the delivery against the LPO:
- Quantity: are all items present?
- Specification: do items match what was ordered?
- Condition: are items undamaged and in original packaging?
- Identity: do serial numbers and model numbers match?
A Goods Received Note (GRN) is raised after successful inspection. The GRN is a critical document, without it, payment processing cannot begin.
Step 7, Invoice, payment voucher, and payment
The vendor submits their invoice, which references the LPO number and matches the GRN quantities exactly. The finance unit raises a payment voucher, which goes through internal approval before payment is processed.
For IT procurement of any complexity, this step frequently introduces delays. Understanding the institution's payment cycle, the cadence of voucher batches, treasury single account protocols, and payment committee schedules, allows vendors and procurement officers to plan realistic delivery timelines rather than building up a backlog of unpaid invoices.
Where the process breaks down
Several recurring failure points are worth identifying explicitly:
Specification gaps: Equipment delivered doesn't match what was actually needed because the specification was too broad. Inspection reveals the problem only at delivery.
Unauthorised supply: A vendor begins supplying before the LPO is formally issued, on the strength of a verbal commitment or draft document. When the LPO is delayed or modified, the vendor has no documented basis for the work already done.
Missing GRN: Stores or IT staff sign a delivery note but the GRN is never formally raised. Without the GRN, the finance unit cannot process payment, regardless of what was delivered.
LPO amount versus invoice mismatch: Price adjustments (FX movements, additional items) not formally documented through an LPO amendment create mismatches that require manual resolution and delay payment.
Budget year-end lapses: Government budgets lapse at year-end. LPOs issued in the fourth quarter that are not delivered and GRN-raised before the year closes may require re-issuance in the following year's budget, with no guarantee the provision will be renewed.
Practical guidance for institutions
- Issue the LPO only when budget, approval, and specification are all confirmed. Rushing the LPO before these are in place does not accelerate procurement; it creates rework.
- Specify delivery timelines realistically. An LPO issued in November with a 30-day delivery window must account for the December administrative slowdown and any year-end budget closure.
- Train stores and IT staff to raise the GRN correctly and promptly. The GRN is not optional paperwork, it is what converts delivery into a payment obligation.
- Retain all process documents, from the original requisition through to the GRN and payment voucher, in a procurement file. Auditors examine the completeness of the file, not just the final documents.
Frequently asked questions
Can a government agency issue an LPO without going through competitive quotation?
For procurements below the applicable threshold, single or limited sourcing with documented justification is permitted. Above the threshold, competitive bidding is required by law. Splitting orders to stay below the threshold is explicitly prohibited under the Public Procurement Act and constitutes a procurement irregularity.
What happens if a vendor delivers goods that don't match the LPO?
The institution's receiving officer should refuse to sign the delivery note for non-conforming items, raise a discrepancy report, and notify the procurement unit. The vendor is required to remedy the discrepancy, supply the correct items, before a GRN can be raised and payment processed.
How long does the LPO-to-payment cycle typically take?
This varies considerably by institution, payment volume, and the time of year. A well-managed MDA may complete the cycle in four to eight weeks after GRN. Institutions with backlogs, budget constraints, or manual payment systems may take significantly longer. Vendors supplying government institutions should factor this into their cash flow planning.
Is it possible to amend an LPO after issuance?
Yes, through a formal LPO amendment or supplementary LPO, which must go through the same approval chain as the original. Verbal agreements to change quantities or prices are not enforceable and create exactly the documentation gaps that generate audit findings.
