Micro-Purchase Toolkit · Free Guide
GPC / P-Card IT Purchasing Playbook — Micro-Purchases up to $15,000
A fillable, audit-ready workflow for federal IT purchases up to the general $15,000 micro-purchase threshold — from authority and sourcing through receipt and reconciliation.
By Uniqcli Team ·
8 min read · Free PDF download · Print-friendly
What's inside
Key takeaways from this guide
- The general micro-purchase threshold rose to $15,000 effective October 1, 2025 — but agency, category, emergency, and cardholder limits can all set a lower ceiling
- The authority gate to clear before shopping: appointment, training, funds, single-purchase and cycle limits, merchant-category controls
- The stop rule — never divide a known requirement to stay under a threshold or card limit
- The sourcing sequence: FAR Part 8 mandatory sources, AbilityOne / FPI applicability, price reasonableness, §889 screening, and Section 508 in one pass
- The receipt-and-acceptance evidence that proves the government got what it bought — serials, licenses, warranty dates, property records
- An end-of-cycle reconciliation and dispute routine that leaves a purchase file a stranger could follow
Why the purchase card deserves a playbook
The government purchase card is the preferred method for micro-purchases when authorized — it's the fastest lawful way to buy IT the government has. It is also where small, avoidable process mistakes concentrate: a divided requirement, a missing receiving record, an unscreened camera, a statement reconciled late. None of these are exotic failures; they're file-hygiene failures, and they're what audits find.
The general micro-purchase threshold increased to $15,000 effective October 1, 2025 (see acquisition.gov's threshold changes and FAR 13.201). That's real purchasing power on a card — and it makes the discipline around each buy matter more, not less, because more of the agency's IT now flows through cardholders rather than contracting officers.
This playbook is the companion to our fillable PDF worksheet: seven gates, run in order, that take a card purchase from "can I even buy this?" through an audit-ready purchase file. It reflects the general federal framework — your agency's own thresholds, delegations, and local policy always control where they're stricter.
Gate 1 — authority and threshold, before shopping
- Cardholder is appointed, trained, and current; approving official is assigned
- Funds are available and certified; the requirement is official government business
- Single-purchase authority covers the total requirement — and the monthly/cycle limit is sufficient
- Merchant category and IT category are allowed under your card controls
- Agency/local micro-purchase limit confirmed — the $15,000 general threshold only applies where your agency hasn't set a lower one
- No known related need is being divided to fit under a threshold or card limit
Gate 2 — define the whole requirement, then pick the method
Write the complete need first: the bona fide need, the intended users and location, the full item/service/license/support-term specification, and the total estimated requirement. Only then decide whether the card is the right method. The order matters because it's what makes the split-purchase prohibition checkable — if the total known requirement exceeds the applicable threshold or the cardholder's authority, the answer is not two transactions; it's the contracting office or another authorized channel.
Name the roles while you're at it: requestor, cardholder, approving official, independent receiving official, property custodian. Only the authorized cardholder may use the account — the card, the number, and the approval responsibility are never shared. Separation of duties across those roles is the control an auditor looks for first.
Gate 3 — sourcing and compliance in one pass
- FAR Part 8 / agency mandatory sources checked; AbilityOne / Federal Prison Industries applicability confirmed
- Existing agency or governmentwide contract considered before open-market
- Price reasonableness documented — catalog, market, prior buy, or another stated basis (micro-purchases generally don't require competitive quotes when the price is reasonable, per FAR 13.203)
- NDAA §889 screening completed — the covered-equipment bar has no dollar threshold, so it applies to card buys too
- Section 508 / accessibility considered; cybersecurity or CISO approval where your agency requires it
- Software licenses, cloud/SaaS data handling, and any auto-renewal reviewed — FAR 52.232-39 makes unauthorized click-through obligations unenforceable, but the cleanest file avoids them entirely
- Tax-exempt treatment applied under agency policy; country-of-origin / domestic-preference checked when applicable
Gate 4 — place the order with complete controls
- Final total (with freight, fees, and tax visible) is within the threshold and the cardholder's delegated authority
- Exact items, quantities, SKUs, and prices match what was approved; the merchant matches the approved supplier
- Government ship-to and receiving contact are correct; delivery date and backorder status are acceptable
- No personal items, gifts, cash equivalents, or unapproved add-ons ride along
- No split or multiple-card workaround
- Order confirmation and receipt/invoice captured for the file — and sensitive card data is never stored in it
Gate 5 — prove the government received what it bought
- Quantity and exact SKU/model verified on arrival; condition and tamper/damage status inspected
- Serial numbers and asset tags captured; accountable/sensitive property recorded with the custodian
- Licenses and entitlements assigned to a government account — not a personal one
- Warranty and support start/end dates captured
- Partial shipments and remaining balances recorded; discrepancies reported to the cardholder promptly
- Independent receiving official used where required — the buyer shouldn't be the only person who says it arrived
Gates 6 and 7 — reconcile on time, file like you'll be audited
- Posted merchant and amount match the order record; a receipt/invoice supports every charge
- Credits, returns, cancellations, and partial shipments tracked to resolution; duplicate or fraudulent charges checked
- Cardholder reconciled and approving official reviewed within agency deadlines; disputes filed within issuer/agency timeframes
- Receiver/acceptance evidence, property or license records attached
- The finished purchase file is understandable to someone who wasn't involved — authority, requirement, sourcing, order, receipt, reconciliation, all in one place, retained under the records policy
How Uniqcli fits this workflow
Uniqcli accepts the GPC / purchase card and quotes with the cardholder's file in mind: itemized pricing with freight and tax visible before commitment, §889 and country-of-origin screening on every line, and the product evidence — serials, license terms, warranty dates — that Gate 5 asks for. Send a completed worksheet or a plain list of requirements to [email protected] and a specialist will return a quote built to drop into your purchase file.
Frequently asked questions
What is the federal micro-purchase threshold in 2026?
The general micro-purchase threshold is $15,000, effective October 1, 2025, following the FAR's periodic inflation adjustment (FAR 2.101, FAR 13.201). Different figures still apply in specific contexts, and agencies, card programs, and individual cardholder delegations can all set lower limits — the applicable ceiling for any given buy is the lowest of them.
Do micro-purchases require competitive quotes?
Generally no. Micro-purchases may be made without soliciting competitive quotations when the price is considered reasonable (FAR 13.203) — but you should document the basis for price reasonableness (catalog price, market comparison, prior purchase), distribute purchases equitably among qualified suppliers when practicable, and still check mandatory sources like AbilityOne first.
Can I split a purchase into smaller transactions to stay under the threshold?
No. Splitting a known requirement to fit under the micro-purchase threshold or a cardholder's single-purchase limit is prohibited. If the total known requirement exceeds the applicable threshold or the cardholder's authority, route it to the contracting office or another authorized acquisition channel — don't divide it.
Does NDAA Section 889 apply to purchase-card buys?
Yes. The §889 covered-equipment prohibition has no dollar threshold, so a $300 camera bought on a card is screened the same as a $3 million contract line. Cardholders should confirm the maker (and the modules inside rebadged gear) against the covered entities before buying video-surveillance or telecom equipment.
What belongs in an audit-ready purchase-card file?
Enough that someone uninvolved can reconstruct the buy: the authority and threshold confirmations, the complete requirement (not split), the sourcing and compliance checks with price-reasonableness basis, the order confirmation with exact items and totals, receipt/acceptance evidence with serials and property records where applicable, and the reconciled statement with any returns or disputes resolved — retained under your agency's records policy.
About the author
Uniqcli Team
Uniqcli's newsroom, buying guides and glossary are produced by our in-house team — seven procurement and technology professionals who source, screen and integrate IT and security hardware every day, working with two editors. Practitioners draft from live sourcing and integration work; editors review every piece for accuracy and plain language before it publishes.
More about the Uniqcli TeamReady to put this into practice?
Talk to a Uniqcli specialist, or send a bill of materials for a TAA-verified quote — no payment up front.