A school district purchasing card can make a small classroom purchase fast. It can also hide a missing receipt, a duplicate vendor payment, or two charges split to get around a local approval limit. A monthly statement that agrees with the general ledger proves the arithmetic; it does not prove that each purchase was authorized, received, and charged to the right program.
This guide shows how a U.S. K–12 business office can reconcile a P-card cycle from bank statement to receipt, approval, and ledger posting. It focuses on a specific close task rather than card-program design generally. For the larger program picture, see how districts manage procurement cards. Spending limits, sales-tax treatment, deadlines, and permissible card uses vary by state and district; use the current local policy for each decision.
Start with the right control objective
The Texas Education Agency’s current Financial Accountability System Resource Guide, Version 20, Module 5 calls a P-card a payment mechanism, not a procurement method. A card does not replace required competition, contract use, prior approval, or budget checks. The guide recommends limits, training, detailed receipts, a documented business purpose, separation of duties, and monitoring for suspicious patterns such as purchases just below limits. Those are Texas guidance and suggested practices, not a single nationwide P-card rule.
The 2025 GAO Green Book provides a broader internal-control framework. It says managers should separate incompatible duties or design alternative controls when a small office cannot do so. GAO’s purchase-card audit guide specifically describes independent receipt and acceptance and cardholder statement reconciliation as transaction-level controls. A district can adapt this framework while following its own board policy, state rules, and any applicable grant conditions.
Assign each step to a named person
Make the workflow visible before the billing cycle starts. The requester explains the need and identifies the funding source. An authorized person approves the purchase under district policy. The cardholder places the order and secures the itemized receipt. Someone with knowledge of delivery confirms the goods or services arrived. The cardholder matches each posted transaction to evidence and explains exceptions. An independent approver reviews the matched transaction, and accounting ties the approved card file to the statement, payable, and ledger.
TEA’s Module 5 says the same employee should not buy, receive, approve, and reconcile a card purchase. It also calls for separate employees to set up cardholders and reviewers in card and banking systems. A small district may need compensating review, such as a business manager independently inspecting receipts and card logs for an employee who both orders and receives. Document that review rather than leaving it implied. The broader district procurement process still governs how vendors and contracts are selected.
Build a transaction-by-transaction monthly bridge
Download the full issuer statement and detailed transaction export for the closed cycle. Preserve the statement period, cardholder, posting date, merchant, amount, credits, and transaction identifier. Obtain a receipt or invoice for every charge, plus evidence of business purpose, the approver, receiving confirmation, account coding, and any procurement or grant approval the purchase required. A card transaction without a receipt is an exception to resolve; a cardholder’s note alone is not always enough to substantiate the goods received or the price paid.
Match every statement line to one supporting transaction and one accounting entry. Reconcile gross charges and credits separately, then tie the net to the card payable. Look for issuer fees, disputed items, refunds posted in a later cycle, and transactions charged to a suspense account. If a vendor invoice was also entered through accounts payable, check that the card payment did not create a second disbursement. Keep a dated exception list with the cardholder, amount, reason, owner, and resolution date. Do not mark an unexplained item “reviewed” simply because the statement balance ties.
A $915 statement that still needs investigation
Suppose a district’s illustrative policy sets a $500 single-transaction limit. A cardholder has two charges from the same supplier on the same day: $480 at 10:12 a.m. and $470 at 10:24 a.m. A $35 return credit also posts during the cycle. The statement total is $480 + $470 − $35 = $915. The ledger shows $950 of supply charges and a $35 credit, so the card payable also equals $915. The arithmetic is correct.
The reviewer still asks whether the two charges were genuinely separate purchases or one $950 order divided to avoid the $500 limit. Compare itemized receipts, order numbers, delivery records, the request date, and any preapproval. Two charges near a limit are a flag, not proof of misconduct. If they were one order, route the exception through the district’s purchasing and supervisory process; do not create a retroactive approval that suggests the purchase was authorized beforehand. If they were separate, record the reason and evidence. The $35 credit should be linked to the original item and fund rather than buried as an unexplained reduction to the statement.
Review risk signals beyond the receipt
TEA’s purchasing guide recommends monitoring average spend by cardholder, unauthorized suppliers, purchases delivered to a cardholder’s home, amounts just below limits, declined authorizations, disputes, and lost-card reports. A useful monthly review combines automated flags with judgment. Repeated small purchases from one vendor may indicate an available district contract, a planning problem, or deliberate order splitting. A high-dollar charge may be ordinary for a cardholder with written emergency authority. Investigate the context instead of treating a threshold report as a verdict.
Also check that cardholder access remains appropriate. Compare the active-card list with HR changes and authorized positions, and promptly close cards for employees who leave or change roles. Review merchant-category and transaction limits against actual duties. TEA recommends annual review of P-card users and periodic districtwide spend analysis; a district can set a more frequent cycle when turnover or misuse risk warrants it.
Apply grant rules to the purchase, not the plastic
When a card charge is assigned to a federal award, the funding source deserves its own check. 2 CFR § 200.318 requires documented procurement procedures and records sufficient to detail the history of the procurement. 2 CFR § 200.403 includes allowability conditions such as necessary and reasonable costs, consistent treatment, and adequate documentation. The P-card does not turn a noncompliant purchase into an allowable grant expense. Confirm the procurement route, period of performance, budget authority, purpose, and supporting records before posting to the grant.
A refund, rebate, or vendor credit tied to a grant-funded card purchase needs careful coding. TEA’s Module 5 says rebates on purchases made with federal funds must be credited back to the program fund used for the purchase. Reconcile those credits to the underlying charge so the award is not left bearing the gross cost after the district receives a recovery. Consult the grant terms and SEA instructions where a particular credit has special treatment.
Close the cycle with an audit-ready package
At month-end, preserve the issuer statement, transaction export, itemized receipts, receiving evidence, approvals, account coding, cardholder certification if required by policy, independent review, exception log, credit documentation, and ledger-to-payable reconciliation. The package should let a reviewer trace a selected line in either direction: from statement to authorized purchase and ledger, or from ledger charge back to statement and receipt. Restrict changes to approved records and document later corrections. The district’s broader financial-risk controls should use recurring exceptions to adjust training, limits, or purchasing procedures.
Common mistakes include accepting a total-only receipt, letting the cardholder approve their own transaction, overlooking a credit that appears in the next cycle, paying a vendor invoice again through accounts payable, and treating two near-limit purchases as automatically legitimate because both were below the limit. Another is using a federal grant code without retaining the procurement and allowability evidence that the grant requires.
Monthly P-card reconciliation checklist
- Obtain the complete issuer statement and transaction export for every active card.
- Match each charge and credit to an itemized receipt, business purpose, receiving evidence, and account code.
- Confirm required prior approvals and the underlying procurement route.
- Flag missing evidence, duplicate invoices, split-purchase patterns, unusual merchants, and delayed credits.
- Resolve or assign every exception; retain the evidence and decision.
- Have an independent reviewer approve the transaction file and document any compensating control.
- Tie gross charges, credits, and net statement balance to the card payable and general ledger.
- Review cardholder access, limits, and repeat exceptions for program changes.
A complete card reconciliation answers two questions: Does the accounting tie? and Was each purchase proper? The first catches posting errors. The second protects district funds, procurement integrity, and grant compliance.