How to Fill Out and Submit a P-Card Exception Request Form

A PCard exception request form is a written waiver you submit before a purchase so your employer’s purchasing card will cover a transaction that falls outside normal rules — over the single-transaction limit, from a blocked merchant category, or outside a preferred-vendor contract. There is no universal template. Federal agencies, universities, and private employers each build their own, but the fields, the approval chain, and the purpose are consistent across programs.

Fill it out before you swipe the card. An approved exception creates the paper trail that keeps the transaction out of an audit finding; a purchase made first and justified later usually reads as misuse.

When You Actually Need to File One

Three situations drive most exception requests.

The first is a purchase that exceeds your card’s single-transaction limit. Federal PCards are generally tied to the micro-purchase threshold, which rose to $15,000 on October 1, 2025.¹ State agencies and universities often cap cards lower. If your purchase is above your cap but below the amount that would require formal procurement, the exception form asks for a temporary limit increase.

The second is a blocked Merchant Category Code. Every PCard has a profile of approved and restricted vendor types, keyed to four-digit codes assigned by the card processor. The Department of Defense, for example, hard-blocks a Tier 1 list covering casinos, wire transfers, dating services, political organizations, and tax payments, so the issuing bank automatically declines any attempt to charge a vendor tagged with those codes.² When a vendor’s code is blocked but the purchase is legitimate, the exception form is how you get that code temporarily unblocked for your account.

The third involves preferred or mandatory-use contracts. Most organizations negotiate discounts with specific suppliers for recurring needs like office supplies and IT equipment. Buying from a non-contract vendor when a contract vendor exists violates policy. The form justifies the bypass — typically because the contract vendor cannot deliver on time, does not stock the item, or costs more for a specialized product.

Emergencies Get Their Own Lane

Declared emergencies create a separate exception path. When a threat to life, public safety, or property requires immediate procurement, many programs allow expedited or retroactive processing. FEMA guidance permits non-competitive, sole-source purchasing during emergencies when competitive bidding would cause dangerous delays, but still requires written justification for every sole-sourced contract, a description of the goods and their necessity, and documentation of any known conflicts of interest.³ Organizations receiving federal grant funds must return to competitive procurement once the emergency period ends. Framing a routine deadline as an “emergency” is something auditors catch.

What the Form Asks For

Templates differ, but after comparing forms used by federal agencies and universities, the same core fields show up on nearly every one:

Cardholder information: your name, department, and the last four digits of your PCard number.⁴
Vendor details: merchant name, website, and whether the vendor is domestic or foreign. Foreign vendors may require an attached W-8.⁵
Transaction details: dollar amount including tax and shipping, whether the charge is one-time or recurring, and the date you need the exception active.
Funding source: the budget, program, or project number that will absorb the charge.
Business justification: a written explanation of why the purchase cannot go through normal channels.
Supporting documents: quotes, invoices, or specifications if available. Some forms simply ask whether a quote exists and request you attach it.⁴

Note what is generally not required: three competitive bids on letterhead, the vendor’s tax ID, or a cost-benefit analysis. Some programs ask for price comparisons on large purchases, but that is the exception rather than the default. Check your own form before assembling a documentation package you may not need.

Writing the Justification

The justification paragraph is where most requests succeed or fail. Reviewers want a specific explanation that answers three questions: what you need, why the standard process cannot provide it, and why this vendor is the right choice.

A weak justification reads “needed for operations” or “vendor is better.” A strong one reads: “The department’s existing Xerox maintenance contract does not cover the Ricoh plotter in Room 214. Ricoh’s authorized service partner, ABC Imaging, quoted $1,800 for the repair including parts. No other local vendor is authorized to service this model without voiding the warranty.” That version names the gap in normal procurement, identifies the specific vendor, and explains why alternatives will not work.

If only one vendor can supply what you need, you are making a sole-source argument. For federally funded purchases, the justification must fall into one of a few recognized categories: the item is available from a single source, an emergency prevents competitive solicitation, or the federal awarding agency has expressly authorized noncompetitive procurement.³ Even outside federal programs, document the due diligence you performed. Reviewers scrutinize sole-source claims more than any other type, so the more specific you are about alternatives considered, the faster the approval.

Submitting the Form and Getting Approval

Submit the completed form and attachments through whatever channel your program uses: procurement software, a SharePoint workflow, or a designated email address. Lead time matters. Texas State University requires forms at least 48 hours before the planned purchase and gives cardholders 10 days after approval to complete the transaction.⁶ Other programs are more generous. Confirm your own policy’s requirement.

The form typically routes through at least two levels of review. Your immediate supervisor or department head reviews first, confirming the purchase serves a legitimate business need and aligns with policy.⁷ It then moves to central procurement or finance, where a compliance officer evaluates regulatory and financial risk. In federal programs, OMB Circular A-123 requires that a cardholder never approve their own transaction, so the reviewer is always someone outside your control of the purchase.⁸

If a reviewer spots a vague justification, a missing quote, or a funding code that does not match the department, expect the form to come back for clarification rather than an outright denial. At the University of Oklahoma, denied requests include an explanation and guidance on completing the purchase through an alternative method.⁵ A denial usually means the purchase needs to go through formal procurement instead of the PCard, not that it cannot happen at all.

After Approval

Approved exceptions come with a window. Texas State allows 10 days. The University of Oklahoma approves exceptions as either one-time or up to a full year, with the PCard team reaching out a month before expiration to ask about renewal.⁵ Complete the purchase before the exception expires. A lapsed approval means starting over.

Once the transaction posts, attach the approved exception form and your receipt to your monthly PCard reconciliation. Federal policy requires cardholders to reconcile transactions with supporting documentation no later than 30 days after the end of the billing cycle.⁸ A charge on your statement without a matching approved exception looks indistinguishable from an unauthorized purchase to an auditor.

Keep a copy of the approved form and supporting documentation for the retention period your organization requires. Timelines are not universal. Penn State requires PCard documentation posted to general accounts to be retained for two years after the end of the fiscal year, while records tied to grants or contracts must be kept for three years after the agreement ends.⁹ Store your own copy somewhere you control. Procurement systems get migrated and archived; if an auditor asks about a transaction two years later, you want to produce the approval in five minutes rather than wait on an IT restore.

Do Not Split the Purchase to Avoid Filing

If a purchase runs over your limit, do not break it into two smaller charges to stay under. Federal acquisition rules define split purchasing as intentionally breaking down a known requirement to stay within a cardholder’s single-purchase limit or the micro-purchase threshold, and treat it as a compliance violation on par with misuse.¹⁰ Nearly every non-federal program applies the same rule. Audit teams look specifically for patterns like multiple charges to the same vendor on the same day.

The consequences for misuse are real. Under federal rules, cardholders are accountable officials and can be held personally liable for the full dollar amount of unauthorized purchases, with disciplinary actions ranging from counseling to demotion, removal, or criminal prosecution for fraud or repeated violations.¹¹ Non-federal programs impose their own penalties, typically outlined in the PCard manual you signed when you received the card: card revocation, retraining, repayment, and formal write-ups in your personnel file. The form takes 15 minutes. A misuse investigation takes considerably longer.

1
Acquisition.GOV. Threshold Changes – October 1st, 2025
2
Acquisition.GOV. Merchant Authorization Controls (MAC)
3
FEMA. An Exception to the Rules During Emergency or Exigent Circumstances
4
Bowling Green State University. P-Card Exception Request
5
University of Oklahoma Health Sciences Center. Pcard Exception Request Process
6
Texas State University. Procurement Card (P-Card) Exception Request Form
7
Stephen F. Austin State University. P-Card Manual for SAP Concur
8
The White House. Issuance of Revised Appendix B to OMB Circular A-123
9
Penn State University. Financial Records Retention Schedule
10
Acquisition.GOV. Split Purchases
11
Acquisition.GOV. Liability of Cardholders and Billing Officials