
- Who has to follow federal procurement rules
- The procurement thresholds
- Documentation requirements
- Sole-source procurement: when you can skip competitive bidding
- Cooperative purchasing: a shortcut that's actually compliant
- Building a procurement policy your auditor will respect
- How Ramp supports nonprofit procurement compliance
If your nonprofit organization receives federal funding, directly or as a sub-recipient, your purchasing decisions are governed by the OMB Uniform Guidance (2 CFR 200). This means competitive procurement above $10,000, documented vendor selection for every significant purchase, and an auditable paper trail. Non-compliance can result in disallowed costs, which means returning money to the funder.
Who has to follow federal procurement rules
The rules apply to any organization that receives federal awards:
- Direct recipients: Nonprofit organizations with federal grants from agencies like HHS, DOE, DOL, or USDA
- Sub-recipients: Organizations that receive pass-through federal funds from a state agency, university, or another nonprofit organization
- Contractors under federal awards: Organizations hired to deliver services on a federal contract
If you're unsure whether your funding includes federal dollars, check your grant agreement. Sub-awards carry the same procurement requirements as direct awards.
The procurement thresholds
2 CFR 200.320 defines procurement methods based on dollar amount:
Purchase amount | Required method | What it means |
|---|---|---|
Below $10,000 (micro-purchase) | Reasonable price determination | You don't need quotes, but the price should be fair |
$10,000 to $250,000 (small purchase) | Price or rate quotes from at least two sources | Get written quotes. Document why you selected the winner |
Above $250,000 (formal) | Sealed bids or competitive proposals | Full competitive process with public solicitation and documented selection |
These thresholds are cumulative: if you buy $5,000 of supplies from the same vendor four times in a year ($20,000 total), the small purchase threshold applies.
Documentation requirements
The procurement rules require documentation at every step:
- Need justification: Why is this purchase necessary for the grant's mission?
- Competitive process: Written quotes (small purchase) or formal solicitation (large purchase)
- Selection rationale: Why you chose this vendor over alternatives
- Conflict of interest disclosure: No program staff or board member with a financial interest in the vendor can participate in the selection
- Contract or purchase order: Written agreement for services above the micro-purchase threshold
- Receipt of goods/services: Confirmation that what was delivered matches what was ordered
- Payment documentation: Coded to the correct grant budget line
Missing any of these creates a finding in your single audit. Multiple findings can trigger a "material weakness" designation, which jeopardizes future federal funding.
Sole-source procurement: when you can skip competitive bidding
2 CFR 200.320(c) allows sole-source procurement in limited circumstances:
- The item or service is only available from a single source
- There's a public emergency
- The federal awarding agency expressly authorizes it
- After solicitation, competition is determined inadequate
Sole-source justification must be documented in writing. "We've always used this vendor" isn't valid.
Cooperative purchasing: a shortcut that's actually compliant
Cooperative purchasing programs (like OMNIA Partners, which is already an active Ramp channel for nonprofit organizations) let you buy from vendors who've already gone through a competitive bidding process. The cooperative ran the RFP. Multiple vendors competed. The winning contracts are available to member organizations.
This satisfies federal procurement requirements because the competitive process already happened. Your documentation is simpler: show that you purchased under a cooperative contract and that the pricing was per the agreed terms.
Building a procurement policy your auditor will respect
Your organization should have a written procurement policy covering:
- Dollar thresholds for each procurement method
- Approval authority: Who can approve purchases at each dollar level
- Conflict of interest requirements: Disclosure and recusal procedures
- Documentation standards: What records to maintain
- Emergency procurement procedures
Procurement software that enforces these policies through approval workflows makes compliance automatic. Every purchase request routes through a single intake-to-pay flow with custom forms, approval routing, and vendor due diligence. Three-way matching catches discrepancies between POs, invoices, and receipts.
This article provides general information about federal procurement requirements. Consult your grants management office or legal counsel for guidance specific to your awards.
How Ramp supports nonprofit procurement compliance
Ramp creates a documented approval trail for every purchase:
- Purchase request workflows: Program staff submit requests that route to the correct approver based on amount and category
- Spend limits by grant: Corporate cards with grant-specific limits block non-compliant spending before it happens
- Vendor management: Track vendors, contracts, and pricing in one place
- Automatic documentation: Every request, approval, and payment is timestamped and stored
- QuickBooks and Sage Intacct sync: Purchases code to the correct grant before they hit your accounting system

FAQs
Only organizations that receive federal awards (directly or as sub-recipients). State-funded and privately-funded nonprofit organizations follow their own board-adopted procurement policies.
The auditor can flag findings in your single audit. Findings can result in disallowed costs (returning money to the funder), corrective action plans, or suspension from future federal awards.
$10,000 under 2 CFR 200. Purchases below this amount require a reasonable price determination but don't need competitive quotes.
Yes. Purchases under cooperative contracts satisfy competitive procurement requirements because the cooperative already conducted the competitive process.
Don't miss these
“Browserbase builds infrastructure so AI agents can do real work. Ramp is doing the same for finance. It’s not another tool. It’s a system purpose-built for AI-driven finance, and that’s why we chose Ramp as our financial operating system from day one.”
Paul Klein IV
Founder & CEO, Browserbase

“We used to pay up to $20k a year for our AP platform. With Ramp, we’re earning back well over that amount. That's money that belongs to the mission now, not to the back-office software.”
Heidi Coffer
Chief Financial Officer, Boys & Girls Clubs of San Francisco

“We're accountable to our funders, our partners, and the families we serve. That accountability starts with how we manage every dollar. Ramp makes it easy for our team to spend wisely, track in real time, and keep overhead low so more resources reach the families navigating infertility.”
Rachel Fruchtman
CFO, Jewish Fertility Foundation

“Each member of our team has an outsized impact due to our focus on using high-leverage tools like Ramp.”
Lauren Feeney
Controller, Perplexity

“With Ramp, we haven’t had to add accounting headcount to keep up with growth. The biggest takeaway is that instead of hiring our way through it, we fixed the workflow so we can keep supporting the organization as we scale.”
Melissa M.
VP of Accounting at Brandt Information Services

“In the public sector, every hour and every dollar belongs to the taxpayer. We can't afford to waste either. Ramp ensures we don't.”
Carly Ching
Finance Specialist, City of Ketchum

“Compared to our previous vendor, Ramp gave us true transaction-level granularity, making it possible for me to audit thousands of transactions in record time.”
Lisa Norris
Director of Compliance & Privacy Officer, ABB Optical

“We chose Ramp because it replaced several disparate tools with one platform our teams actually use—if it’s not in Ramp, it’s not getting paid.”
Michael Bohn
Head of Business Operations, Foursquare





