You rolled out Ramp or Brex. Expense reports are automated. Card spend shows up in a dashboard the moment it happens. Your Controller should feel like spending is under control.

So why doesn’t she?

Because 40 to 60 percent of business spending at a 100 to 500-person company doesn’t go on a card. It flows through vendor invoices. A vendor ships equipment and sends an invoice 30 days later. A contractor finishes a job and emails a bill. A parts supplier delivers MRO inventory on a blanket order and invoices the AP team at the end of the month.

If your company spends $3M annually with vendors and 50% of that flows through invoices rather than cards, your AP team is manually processing $1.5M in uncontrolled spend. No pre-approval. No budget check. No PO to match against. Just invoices landing in an inbox.

None of that shows up on a Ramp or Brex dashboard. And none of it has a card control attached to it.

At ProcureDesk, we work with Controllers and CFOs at mid-market companies who face exactly this problem. They’ve automated card spend, but half or more of their total spend is still uncontrolled. The invoice arrives, and nobody knows whether the purchase was approved, whether it was budgeted, or whether the price matches what was agreed.

Cards and purchase orders solve different problems. This article explains exactly where each one works, where each one breaks down, and why finance teams that want full spend control need both.

TL;DR

1. 40 to 60 percent of spend at a 100 to 500-person company flows through vendor invoices, not cards. That half of spending is uncontrolled without a PO system.
2. Cards control the payment method. They don’t control the decision to buy. A Ramp or Brex rollout doesn’t close the vendor invoice gap.
3. Purchase orders control spend before money moves: budget check, multi-level approval, and automated 3-way matching when the invoice arrives.
4. Set a dollar threshold between $250 and $500. Card below, PO above. Document it in the purchasing policy.
5. Manual invoice processing costs $9.40 per invoice. Automated 3-way matching drops it to $2.78. At 200 invoices a month, that gap is $22,560 a year.
6. Month-end close drops from 10 days to 4 days on average across ProcureDesk’s customer base after a PO process is added alongside the card program.
7. Cards and POs aren’t competing tools. They’re two layers of the same spend control framework. You need both.

What Corporate Cards Actually Control

Corporate cards are real-time spend tracking tools for card-based transactions. They’re good at what they do.

When an employee swipes a Ramp card for a $200 office supply run, the transaction shows up in the dashboard instantly. The receipt gets matched. The expense is categorized. The GL code is applied automatically or with a quick manual tag. If the purchase violates a spending policy, the card can decline it at the point of sale.

That’s a real improvement over the old model, where employees paid with personal cards and submitted expense reports two weeks later.

Here’s what cards handle well:

• Card swipes for day-to-day purchases (office supplies, meals, travel, subscriptions)
• Automated expense categorization and receipt matching
• Real-time visibility into money that has already been spent
• Merchant-level controls (block certain vendor categories or set per-card limits)
• Elimination of most manual expense reports and reimbursements

If your company’s spending consists mostly of card transactions, a tool like Ramp or Brex will give you strong visibility. No question.

But most mid-market companies don’t spend most of their money on card transactions.

What Corporate Cards Don’t Control

The gap starts with one word: invoices.

When a plant manager calls a parts distributor and says “send me 200 units of that bearing assembly we ordered last quarter,” no card is swiped. The vendor ships the parts and mails an invoice 30 days later. That invoice arrives in the AP team’s inbox with no purchase order, no approval record, and no budget check.

Corporate cards can’t control this because the transaction never touches a card.

Here are the common spending scenarios that bypass cards entirely:

• Vendor invoices for raw materials, MRO parts, and production supplies ordered by phone, email, or through a vendor portal
• Service invoices from contractors, consultants, and maintenance providers
• Recurring subscriptions and SaaS tools that auto-bill through invoices, not card charges
• Purchases approved verbally by a manager but never documented anywhere
• Specialty items ordered directly from manufacturer catalogs: Grainger for industrial supplies, Fastenal for fasteners, McMaster-Carr for precision parts

In a 150-person manufacturing, construction, or biotech company, these invoice-based purchases often represent the majority of total spend. A Controller at a company like this might see 40 percent of spending in Ramp and wonder where the other 60 percent went.

The answer: it went through vendor invoices. And cards don’t touch those.This is the core distinction. Cards control the payment method. They don’t control the decision to buy. A card can tell you that money was spent. It can’t tell you whether the purchase was authorized before the money moved.

What Purchase Orders Actually Control

A purchase order (PO) is the opposite. It controls the decision to buy, before any money moves.

Here’s the sequence. A maintenance supervisor at a manufacturing plant needs to order $5,000 in replacement parts from a distributor. Instead of calling the vendor directly, they submit a purchase request through a system like ProcureDesk. The request captures what they want to buy, from which vendor, at what price, and against which budget.

That request then routes through an approval workflow. The system checks the budget. If funds are available and the amount falls within the employee’s spending authority, it gets approved automatically or routes to the right manager. If the purchase exceeds the budget or triggers a review threshold, it’s flagged before anyone places the order.

Only after approval does a purchase order get created and sent to the vendor. From that moment forward, the PO becomes the reference document for the entire transaction.

A PO-based process controls:

• Authorization: no purchase happens without documented approval
• Budget checking: the system verifies funds are available at the moment of request, not after the invoice hits
• Three-way matching: the PO, the goods receipt (confirming delivery), and the vendor invoice are compared automatically. If all three match, the invoice is approved for payment. If something doesn’t match, it gets flagged for review. (See our complete guide to implementing 3-way matching.)
• Audit trail: every step from request to payment is documented. Who requested it, who approved it, when it was delivered, and what was paid
• Committed spend visibility: your Controller can see outstanding POs and know exactly what invoices are coming, even before they arrive

This is the control layer that vendor invoices need. Without it, invoices arrive as surprises. With it, every invoice ties back to an approved purchase. If you’re unfamiliar with how purchase order approval workflows work in practice, we’ve written a detailed breakdown.

When Each One Fails on Its Own: Two Scenarios

These aren’t hypothetical. They’re composites from real conversations with Controllers we talk to every week.

Scenario 1: Cards Only, No POs (Manufacturing)

A 180-person food manufacturing company rolled out corporate cards last year. Card spend is clean. Travel, office supplies, and employee meals are tracked in real time.

Then three things happen in the same week. The production floor supervisor calls Grainger to order $6,200 in replacement conveyor belts. The maintenance lead emails a local machine shop to request $3,800 in custom fabricated parts. And the plant manager verbally approves a $12,000 order for packaging materials from a long-standing vendor.

None of those purchases go through a card. All three vendors ship the goods and send invoices two to four weeks later.

When those invoices land in the Controller’s inbox, there’s no PO number on any of them. AP has to track down each person who placed the order, verify what was ordered versus what was received, confirm whether the pricing matches, manually assign GL codes, and figure out which cost center or production line gets charged.

That’s $22,000 in uncontrolled spend in a single week. Across a full month, this Controller is manually reconciling 60 to 80 vendor invoices with no documentation trail.

The card program didn’t fail. It was never designed to handle this. Vendor invoices for production materials, MRO parts, and contract services need a PO, not a card.

Scenario 2: POs Only, No Card Program

A 120-person biotech company has a solid PO process. Lab supplies, equipment, and vendor contracts all run through purchase orders. Approvals are documented. Invoices match POs.

But employees still use personal credit cards for small purchases: a $45 Uber to a client meeting, a $120 rush order for printer ink, a $300 team lunch. They submit expense reports at the end of the month. Some forget. Some lose receipts. Some miscategorize.

The AP team spends days reconciling these reports. Month-end close gets delayed while they chase down missing receipts and match card statements to GL codes.

The PO process didn’t fail either. It’s doing its job on vendor spend. But small card purchases need a different tool.

Both scenarios are real. And both have the same solution: use both tools, each for the type of spending it was designed to control.

The Spending Threshold Rule: How Cards and POs Work Together

Companies that run both systems don’t leave the boundary to guesswork. They set a dollar threshold.

The logic is straightforward. Below a certain amount, card purchases are fast, low-risk, and self-documenting. Above that amount, the purchase involves enough money that it needs pre-approval, a PO, and a three-way match before the invoice gets paid.

The exact number depends on your company’s size, risk tolerance, and transaction volume. Most mid-market companies set their PO threshold somewhere between $250 and $500. Finance professionals on the Proformative community recommend starting around $250 to $500 for companies with active PO processes, factoring in that the cost of creating and routing a PO (estimated at $65 to $100 for a manual process) should be less than the value of the control it provides.

Here’s how it works in practice:

• Purchases under the threshold (for example, under $500): employee uses a corporate card. The transaction is tracked in real time, receipts are captured automatically, and the card program handles categorization and compliance.
• Purchases above the threshold: employee submits a purchase request. The system checks the budget, routes it for approval, creates a PO, and sends it to the vendor. When the invoice arrives, it gets matched to the PO and the delivery receipt automatically.

Some companies also set category-based thresholds. Capital equipment might require a PO at any dollar amount. In manufacturing, raw materials and MRO parts often require POs regardless of size because of cost-center tracking and inventory management. Office supplies might have a higher card threshold since they’re low-risk and low-dollar.The threshold rule eliminates the argument that cards and POs compete with each other. They don’t. They’re two layers of the same spending control framework. Your purchasing policy documents the threshold and tells employees exactly which process to follow for each type of purchase.

What This Means for Month-End Close

Month-end close is where incomplete spend control shows up as actual pain.

If your company only uses corporate cards, your card data is clean. Transactions are categorized. Receipts are matched. But vendor invoices are a different story. AP teams are manually chasing down approvals, matching invoices to email threads, and trying to figure out whether each invoice was actually authorized. The card side closes fast. The invoice side drags.

If your company only uses POs, vendor invoices close quickly. Every invoice matches a PO. But card-based expenses are a mess. Expense reports trickle in late. Receipts are missing. GL coding is inconsistent. Close gets delayed by the card side.The cost of that manual invoice work adds up fast. According to Ardent Partners’ 2024 AP benchmarks, the average cost to process a single invoice is $9.40. Best-in-class AP teams get that down to $2.78. The difference? Automation. Companies still manually matching invoices to POs are paying more than three times what they should for every invoice they process.

When both systems are in place, every transaction has a home.

• Card transactions are tracked and reconciled automatically by the card program.
• Vendor invoices match to POs and receipts through automated 3-way matching.
• No invoices arrive without a corresponding PO. No card expenses sit unreconciled.

The audit trail is complete before close even starts. Across ProcureDesk’s customer base, month-end close drops from 10 days to 4 days on average after automated matching is in place. AP teams stop spending time on manual reconciliation and focus on exceptions only.

When your close process is predictable, your Controller isn’t burning hours on reconciliation. She’s doing actual financial analysis. That’s the shift from firefighting to control, and it only happens when both sides of spend (cards and invoices) are covered.

Choosing the Right Tools for Each Side

For Card-Based Spending

Several strong options exist for corporate card management. Ramp and Brex are the most popular choices for mid-market finance teams. Both offer real-time spend tracking, automated receipt matching, and card-level controls. Corpay (formerly Comdata) and traditional company-issued Visa or Mastercard programs are also widely used.

Pick the card program that fits your company’s size, spend volume, and bank relationships. The specific brand matters less than making sure the program integrates with your accounting system so card data flows into the same GL as your vendor invoice data.

For Vendor Invoice and PO Control

This is where tools like ProcureDesk come in. ProcureDesk is a procure-to-pay platform built for finance teams at mid-market companies (100 to 1,000 employees) that need spend control before the invoice arrives. It handles the full cycle that cards can’t touch: purchase requests, multi-level approval workflows, PO creation, vendor communication, goods receipt confirmation, and automated 3-way matching.

Here’s what matters for this use case:

• Approval workflows with budget checking. When an employee submits a purchase request, the system checks the budget and routes the request for approval based on your company’s rules. The CFO doesn’t have to approve every $200 request. Department heads handle routine approvals, and senior management reviews only the purchases above a threshold you set. (We covered the design logic in our purchase order approval process guide.)
• Automated 3-way matching. ProcureDesk compares the PO, goods receipt, and vendor invoice automatically. Matched invoices move to payment without manual review. Mismatches get flagged and routed to the right person. Coast Flight Training, a ProcureDesk customer, documented a 30% reduction in invoice processing time after setting up automated matching. (Full case study here.)
• 200+ punchout catalog integrations. Employees can shop from suppliers like Amazon Business, Grainger, Fastenal, and Thermo Fisher directly within ProcureDesk. The shopping experience feels like a normal ecommerce site, but the cart routes through your approval workflow instead of checking out with a credit card.
• ERP-native integration. ProcureDesk connects natively (bidirectional sync, not just API) with QuickBooks (Online, Desktop, and Enterprise), NetSuite, Sage Intacct, Xero, Microsoft Business Central, and Bill.com. Approved invoices sync automatically. No re-keying data. (See how the QuickBooks AP automation integration works.)
• Done-for-you implementation in 2 to 4 weeks. ProcureDesk’s team handles setup. No IT project. No six-month deployment. Most customers go live within two to four weeks.

Both Tools Feed the Same GL

The most important design decision is making sure your card program and your PO system both integrate with the same accounting software. Card transactions go into the GL from one direction. Matched vendor invoices go into the GL from the other. Your Controller sees everything in one place.Without this, you end up with two data streams that don’t talk to each other, and month-end close is spent trying to stitch them together manually. With it, your Chart of Accounts is populated from both systems automatically, and your invoice matching process ties every vendor payment back to an approved purchase.

Corporate Cards vs. Purchase Orders: Side-by-Side Comparison

Frequently Asked Questions

Your First 90 Days: What Changes When You Add a PO System

If you already have a card program and you’re adding PO and AP automation, here’s what the first 90 days typically look like.

Weeks 1 to 3: Setup

ProcureDesk’s team configures your approval workflows, sets up budget structures, onboards your vendors, and connects to your accounting system (QuickBooks, NetSuite, Sage Intacct, or whatever you use). You define your card-vs-PO threshold and document it in your purchasing policy. Employees get a brief walkthrough. No formal training required.

Weeks 4 to 6: First Full Month Live

Purchase requests start flowing through the system instead of email and Slack. POs go to vendors automatically after approval. Your AP team starts seeing invoices arrive with PO numbers on them for the first time. The first round of automated 3-way matching runs. Invoices that match cleanly move straight to payment. Exceptions get flagged and routed.

Your Controller notices the difference immediately: she’s not chasing down what was ordered. The PO tells her.

Weeks 7 to 12: The Compounding Effect

Month-end close gets shorter because vendor invoices are already matched. Your AP team spends less time on data entry and more time on exception handling (which is the only work that actually requires human judgment). The Controller has committed spend visibility for the first time: she can see outstanding POs and know what invoices are coming before they arrive.

The numbers to track at the 90-day mark:

• Invoice processing time. How many hours per week does your AP team spend on invoice reconciliation now versus before? Coast Flight Training saw a 30% reduction.
• Month-end close duration. How many days does close take now? ProcureDesk customers average a reduction from 10 days to 4 days after automated matching is in place.
• PO coverage rate. What percentage of vendor invoices now arrive with a matching PO? Your target is 80%+ within the first quarter.

If you want a deeper look at the full purchasing automation process, our purchase order management guide walks through each step. And our guide to automating purchase orders covers the technical setup.

Cards Solve Card Spend. POs Solve Vendor Spend. You Need Both.

Corporate cards solved a real problem. They automated expense tracking, eliminated paper expense reports, and gave Controllers real-time visibility into card-based spending.

But they didn’t solve vendor invoices. They weren’t designed to.

A purchase order system solves the other half: the vendor invoices that arrive without approval, the budgets that get blown because spending wasn’t checked before the order was placed, and the month-end close that drags because AP teams are matching invoices by hand.

If your company processes more than 50 vendor invoices a month and you don’t have a PO system in place, that’s the gap that’s costing you time, money, and control.

Cards and POs aren’t competing tools. They’re complementary layers in a complete spend control framework. One controls the card. The other controls the invoice. Together, they give your Controller what she actually needs: full visibility into every dollar before it’s spent, not after.

Ready to close the vendor invoice gap?

If most of your spending flows through vendor invoices and you don’t have a PO process, book a 20-minute demo to see what that looks like in ProcureDesk. We’ll show you the approval workflow, 3-way matching, and how it integrates with your accounting system. No pressure, no long sales pitch.