How to Build the Business Case for a Corporate Card Program

A corporate card business case shows the CFO what the current way of paying for small purchases costs, what a card program would save and earn, which risks remain and how they're managed, and how the rollout would run.

Most card business cases I've seen get sent back for the same reason. They open with the rebate, quote a vendor's savings percentage, and leave the CFO wondering what the catch is. The cases that get approved start with the money finance already spends processing reimbursements and small invoices, and they name the risks before anyone else can.

Key Takeaways

• A complete case covers the current-state cost, the expected savings and rebate, the control gains, a risk register, a phased rollout, and the decision being asked for.

• Measure your own current-state cost per expense report and per small invoice. Published benchmarks are thin, and the CFO will trust your numbers more than anyone else's.

• Lead with process savings. In public-sector evidence, processing-cost avoidance has exceeded the added rebate many times over.

• Name the risks, including card liability, misuse, dormant cards, and supplier pushback, with the control that manages each.

• Fit the request on one page, with the model and the risk register as attachments.

What goes into a corporate card business case?

A corporate card business case has six parts, running from what the current process costs to the exact decision you need. Each part answers one question the CFO will ask.

The structure matters because it keeps the case from turning into a feature list. If you want a refresher on the products themselves, a guide to corporate card types and benefits covers purchasing, travel, and virtual cards. Your business case shouldn't spend its words there.

Who should own the business case?

The controller or the finance lead who will run the program should own the business case, with input from AP and procurement, plus HR and IT for card issuance. The owner needs to be someone who will still be accountable for the numbers a year after launch.

That last point gets skipped. A case written by someone who won't run the program tends to promise the vendor's numbers, and CFOs can tell the difference in about a paragraph.

How do you measure what the current process costs?

Measure the current process by counting how many expense reports and small invoices you handle each year, timing each step for a sample of them, and multiplying by loaded labor cost. Add the payment cost and the hidden costs that never show up in a time study.

What does reimbursement and invoice processing cost today?

Reimbursement and small-invoice processing cost whatever your team's hours and payment fees add up to, and the only reliable figure is one you measure. Sample 30 to 50 expense reports and 30 to 50 small invoices, and time every touch from submission to payment.

Count the employee's time to build the report, the manager's approval, AP or payroll's review, the payment, and any follow-up on missing receipts. For small invoices, count every step from the purchase order through matching to payment. The employee expense reimbursement process lays out each step if you need a checklist for the time study.

The payment leg is the easiest piece to price. According to AFP's 2022 Payments Cost Benchmarking Survey, as reported in its January 2022 release, the median cost to issue a check runs $2 to $4. Companies that still reimburse by check, or pay small vendors by check, can find the true cost of paper checks is higher once staff time is counted.

For a public reference point, Delaware's state auditor reviewed several studies of purchasing card savings in its Fiscal Year 2019 Purchase Card Performance Metrics inspection and used $44 per transaction, the most conservative estimate it found, as the processing-cost saving of a card over a traditional payment. Use it as a sanity check on your own number, not as a substitute.

Which hidden costs belong in the baseline?

The hidden costs are employee float, late accruals, and compliance exposure from receipts that arrive late. None appears in a time study, and each is real.

Employee float is the money employees front for the company until they're reimbursed. For many people that's a genuine strain. According to the Federal Reserve's report on the economic well-being of U.S. households in 2024, only 63% of adults would cover a $400 emergency expense using cash or its equivalent. A traveling employee carrying a $2,000 hotel and airfare balance for six weeks is lending the company money, and it shows up later as frustration, late submissions, and turnover risk.

Late receipts carry a tax angle, too. Under the accountable plan rules in IRS Publication 463, accounting within 60 days and returning any excess within 120 days are safe harbors that count as a reasonable time. Missing them doesn't automatically make a reimbursement taxable, since a longer period can still be reasonable on the facts, but a process that runs chronically late makes the accountable-plan position harder to defend and adds cleanup.

How do you estimate rebates and process savings?

Estimate process savings as transactions moved to cards times the per-transaction saving you measured, and estimate rebates as expected card spend times a conservative yield. Subtract program fees and the cost of running the program.

How much rebate should the case assume?

Assume a rebate at the lowest tier you're confident of reaching in year one, not the tier the issuer shows on its best slide. Rebate rates rise with annual volume, so the yield on a program that's still ramping is lower than the yield it'll reach later.

For a public reference, GSA SmartPay's FY2025 program statistics show $471 million in refunds earned on $39.4 billion of federal card spend, about 1.2% of spend. Commercial programs with different volume and mix will land elsewhere.

The rebate comes out of interchange, the fee the supplier's bank pays on each card transaction. According to Visa's interchange reimbursement fee schedule effective April 18, 2026, its standard commercial card-not-present rate is 2.70% plus $0.10, and large-ticket rates are much lower. Understanding how interchange and card rebates connect helps you explain to a skeptical CFO why the issuer can pay one at all.

Show the rebate in its own row so it can be challenged without unwinding the whole case. Programs that consolidate cards and supplier payments with one issuer usually reach higher tiers sooner. A plan for rebate optimization on AP spend belongs in year two of the case, once the employee cards are running.

Commercial cards success story

See how commercial cards transformed expense management and reporting for a finance team — turning a manual burden into measurable savings and a more strategic AP function.

Read the success story

Why should process savings lead the case?

Process savings should lead because they're larger and more certain than the rebate. The rebate depends on volume you haven't moved yet, and the processing cost is money you're already spending.

According to the same Delaware inspection, moving 5% of the state's checkbook transactions under $2,500 to purchasing cards would avoid an estimated $2,674,760 in processing cost a year, against $50,218 in added rebates. That's a government program, with government processing costs, but the shape of the result holds for most companies.

A simple model makes the case concrete. The figures below are illustrative assumptions, not benchmarks, so replace every one with your own.

Even with a zero rebate, that example still pays, and a case built that way is much easier to approve.

What control gains can the case claim?

The case can claim controls that act before money moves, such as spending limits, merchant category blocks, and per-card restrictions, plus transaction data that arrives the day of the purchase instead of weeks later. Under reimbursement, finance usually finds a policy problem only after it has already been paid.

Describe the controls you'd actually configure, by role. A field technician's card might allow hardware and fuel merchants up to a daily limit, while a sales director's card allows travel and meals. Card controls and spend policies gives a full list of settings, and your travel and expense policy supplies the rules they enforce.

The visibility gain is easier to show than to describe. Pull last quarter's expense reports and count how many days passed between the purchase and the moment finance saw it. In my experience the median is two to four weeks, with a long tail past the close. Card transactions post daily, and Corpay connects card data to the ERP through more than 100 ERP integrations, including NetSuite, Sage Intacct, Business Central, and Acumatica, so coded transactions land in the ledger without a manual import.

Which risks should the case name, and how are they managed?

Name every risk a skeptical reviewer will raise, and pair each with the control that manages it and the person who owns that control. A case that lists its own risks reads as more credible than one that doesn't mention any.

Liability deserves a sentence of its own in the memo. Under Regulation Z's rules on unauthorized use, a cardholder's liability for unauthorized use is capped at $50 or less. When an issuer provides 10 or more cards to an organization's employees, the organization and the issuer can agree to different liability terms, while the employee's own exposure stays within the regulation's limits. Corporate liability puts the risk on the company, and that's a choice the CFO should make knowingly, not one buried in an issuer contract.

Misuse is the risk reviewers raise first, but reimbursement has its own. Padded mileage and duplicate receipts are harder to catch than card misuse, because a card leaves a merchant record. The expense fraud detection and prevention controls that work on cards mostly don't exist for out-of-pocket claims.

What rollout plan should the case propose?

Propose a phased rollout with a pilot, a defined set of success measures, and a decision point before each expansion. A phased plan lowers the size of the bet the CFO is approving.

1. Pilot with one or two departments that spend often on cards, such as field operations or sales, for one full close cycle.

2. Measure the pilot on spend moved to cards, receipt and reconciliation lag, policy exceptions, and cardholder feedback.

3. Expand to the remaining eligible employees in waves, updating limits and merchant categories from what the pilot showed.

4. Add virtual cards for supplier payments in a later phase, starting with suppliers that already accept cards.

5. Report the same measures to the CFO each quarter for the first year.

Vendor acceptance is the slowest phase, so plan for it. A vendor enrollment program for virtual cards needs outreach, and the timeline in the case should say so. Corpay runs that supplier enrollment as part of its managed service, and most card programs are live in weeks.

How do you write the one-page memo?

Write the memo as a single page that puts the decision first and the money second, then the risks. Attach the model and the risk register. A CFO should be able to approve or reject it from the first paragraph.

A structure that works:

1. The request. One sentence on the program scope, the budget, and the date you want to start.

2. The problem. Two or three sentences on current-state cost and the control gap, with your measured numbers.

3. The return. Net annual benefit, with process savings and rebate shown separately.

4. The risks. The two or three that matter most and how each is managed.

5. The plan. Pilot scope, success measures, and the decision point.

6. Attachments. The savings model, the risk register, and the issuer comparison.

Leave out the feature list and the issuer's marketing claims. If a number came from a vendor, say so, or better, replace it with your own. For the design decisions that come after approval, the guide to maximizing a corporate credit card program picks up where the memo stops.

One question no template answers is how much of the employee float argument to put in front of a CFO. Some see it as a retention issue worth real money. Others see it as soft. Know which kind of CFO you're writing for before you decide.

Build your card program case with Corpay

A card business case is only as good as the program behind it, and the biggest variables are how fast card data reaches the ledger and how many suppliers accept cards.

Corpay corporate cards give finance spending limits and merchant controls by role, receipt capture at the point of purchase, and card data that posts to the ERP already coded. Across Corpay commercial cards, Corpay's team handles supplier enrollment for virtual card payments, and single-use virtual cards keep each supplier payment locked to one invoice. AP teams save about 40% of the time they spend on payment processing, and Corpay pays its customers more than $800M in rebates each year, which belongs in your case as upside.

Frequently Asked Questions

What is the ROI of switching from expense reimbursement to corporate cards?

The ROI comes mostly from processing savings, since each expense report or small invoice moved to a card avoids hours of submission, approval, and payment work. Rebates add a smaller second return. Measure your own cost per report to calculate it, then subtract program costs.

What should a corporate card business case include?

It should include the current-state cost of paying for small purchases, the expected process savings and rebate, the control gains, a risk register, a phased rollout plan, and the specific decision being requested. Keep the summary to one page and attach the model.

How do you calculate savings from a corporate card program?

Multiply the number of transactions moved to cards by the per-transaction processing saving you measured, add the expected rebate at a conservative tier, and subtract program costs such as administrator time, training, and fees. Show each line separately so reviewers can test it.

What risks come with a corporate card program?

The main risks are liability for unauthorized charges and employee misuse, followed by dormant cards and supplier pushback on card fees. Low adoption and a rebate shortfall complete the usual list. Each has a standard control, such as merchant category blocks, dormancy sweeps, and conservative rebate assumptions.

Who approves a corporate card program?

The CFO usually approves a corporate card program, often with the controller as sponsor and input from AP, procurement, HR, and IT. Larger programs or new credit lines may also need treasury or board-level sign-off, depending on the company's delegation of authority.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

Commercial Cards

Expense management