Micro-purchase documentation for nonprofits

Micro-purchases are meant to reduce burden for small federal grant purchases. They let staff buy routine goods or services without a full quote process when the price is reasonable. But simple does not mean undocumented.

A micro-purchase file should let a reviewer answer four questions: Was the purchase under the threshold? Was it allowable for the award? Was the price reasonable? Did the organization avoid favoring one supplier when other qualified suppliers were practical?

Use this guide with the 2 CFR 200 procurement file checklist.

Confirm the threshold first

2 CFR 200.320 ties micro-purchase rules to the micro-purchase threshold. Your nonprofit should not assume the highest federal ceiling is available for every award. The controlling threshold is the lowest applicable rule from:

• Federal regulation
• Award terms
• Pass-through entity rules
• State or local law
• Your written procurement policy

Write the threshold in your policy. If your policy says $10,000, use $10,000 even if another federal source allows more.

Do not split purchases

Do not break one known need into smaller buys to stay under the threshold. If a program needs $18,000 of laptops, buying them in three $6,000 batches does not make them micro-purchases.

Base the method on the known need at the time of purchase. If needs grow later for a valid reason, document what changed.

Check allowability

Before buying, confirm the cost fits the award. The item should support the program, fall within the approved budget or allowed cost category, and meet the basic cost tests in 2 CFR 200.403.

For example, office supplies for grant staff may be allowable if allocated correctly. Gift cards for participants may need specific award support and strong controls. Food, incentives, travel, and equipment often need closer review.

Document price reasonableness

Micro-purchases do not need competitive quotes when the price is reasonable. The file still needs a reasonableness note.

Good support can be short:

• Website or catalog price
• Prior invoice for the same item
• Screenshot from a market search
• Published rate sheet
• Staff note based on recent purchase history
• Explanation that the item is standard and priced at normal retail

The note should be dated. It should name the person who reviewed the price.

Watch equitable distribution

2 CFR 200.320 says micro-purchases should be distributed equitably among qualified suppliers to the maximum extent practical. This does not mean every purchase needs a new vendor. It means the organization should avoid steering all small federal purchases to one supplier without a reason.

Use a vendor log if your team makes frequent micro-purchases. Review it quarterly. If one vendor dominates, document why. A valid reason might be warranty support, location, required compatibility, or a standing discount.

Keep approval simple

Micro-purchase approval can be light. Use a purchase card approval, supervisor approval, or accounting review. The file should show who approved the purchase, when, and which award paid for it.

If the buyer is also the approver, add a second review during monthly close. Small teams need practical controls, but one person should not have unchecked control over federal purchases.

Store the support

A complete micro-purchase file includes:

• Receipt or invoice
• Award or cost center
• Allowability note if needed
• Price reasonableness support
• Approval
• Payment proof
• Vendor rotation note if relevant

Keep it with the grant cost record. Do not leave it only in an email inbox or purchase card portal.

Use purchase cards carefully

Purchase cards are common for micro-purchases, but they need controls. Card statements alone do not prove allowability or price reasonableness. Keep the itemized receipt, award code, business purpose, and approval. If the receipt is missing, follow your written missing-receipt process and avoid making exceptions routine.

Review card activity each month. Look for split purchases, weekend charges, sales tax when the organization is exempt, personal items, and vendors used too often without a reason. Small charges can still become findings when the pattern shows weak control.

Train program staff on the basics

Program staff often make micro-purchases because they know what the project needs. Give them a short rule sheet. It should explain the threshold, when to ask finance, what receipt to keep, how to write the business purpose, and which costs may need prior approval.

Training does not need to be long. Ten minutes during project kickoff can prevent months of cleanup. Keep the rule sheet with the award file so new staff get the same instructions.

Review vendor patterns

At least quarterly, sort micro-purchases by vendor and award. Look for repeated buys from one supplier, many purchases just under the threshold, or costs that look like one larger need. These patterns do not always mean a rule was broken, but they deserve review.

If the pattern is valid, document it. If the pattern shows the team should have used a higher procurement method, fix the process before the next purchase.

How GrantPipe can help

GrantPipe can attach receipts, price notes, and approvals to the grant cost record. That makes micro-purchases easier to review during month-end close and easier to defend during an audit sample.

DEFINITION

Micro-purchase

A purchase below the controlling micro-purchase threshold that may be made without competitive quotes if the price is reasonable.

DEFINITION

Equitable distribution

A procurement practice of spreading micro-purchases among qualified suppliers when practical instead of favoring one vendor without reason.