How to Roll Out Ramp Corporate Cards in Two Weeks
Ramp is a corporate card and spend management platform — virtual and physical cards with built-in policy limits, receipt capture and automatic accounting sync. A sensible rollout runs two weeks: connect accounting, define spend policies by role, pilot with 10 people, then invite the rest.
The pitch is that receipts catch themselves and coding happens as the transaction lands. Mostly true. The friction moves to policy design, which nobody warns you about.
What does Ramp actually replace?
A manual expense process: employee pays, photographs a receipt, files a report, waits three weeks. Ramp issues the card, applies the limit, captures the receipt from the mobile app or forwarding an email, and posts to your ledger with a category.
Base pricing for the card product is free with Ramp; the paid tiers (Ramp Plus, around $15/user/month) add automation and controls. Revenue comes from interchange, which is why the card is free — worth knowing when you evaluate the terms.
Step 1: connect accounting before issuing any card
Settings → Accounting supports QuickBooks, Xero, NetSuite and Sage Intacct. Connect this first.
Do not skip the mapping step: map Ramp categories to your chart of accounts before the first transaction. Retroactively recoding 300 transactions because every card expense landed in a single “Uncategorized” account is a bad week, and it’s the most common first-month complaint.
Step 2: define policies by role, not by person
Ramp policies are limit sets attached to groups. Build four:
| Policy | Monthly limit | Receipt required above |
|---|---|---|
| Founder / exec | $25,000 | $75 |
| Manager | $8,000 | $50 |
| IC — travel | $4,000 | $50 |
| IC — software only | $500 | any amount |
Add merchant category restrictions to the software policy: block travel, hardware and cash withdrawals. A card that can’t be used wrong needs no policing.
Step 3: pilot with 10 people, one week
Invite your most expense-heavy people — usually sales and engineering leads. Give them physical cards plus virtual cards for SaaS subscriptions.
The reason to pilot rather than launch company-wide: your written policy will be wrong in at least two places, and finding out with ten people costs less goodwill than finding out with ninety.
Expect to discover things like: the $50 receipt threshold doesn’t cover a $60 client dinner, so everyone is photographing receipts anyway. Adjust during the pilot, not after.
Step 4: decide who gets a physical card
Virtual cards are unlimited and free. Physical cards cost you a mailing cycle and a human to chase lost plastic.
Give physical cards to people who travel or entertain clients. Everyone else: virtual card for each recurring vendor. That’s also how you stop the “one card for all SaaS” mess where a contractor’s cancelled subscription charges your card for eight months.
Step 5: set the receipt and approval rules honestly
ramp auto-matches receipts from Gmail and from photos in the mobile app. Matching works well for hotels and airlines, less well for a receipt emailed as a screenshot from a personal address.
Two rules that keep the books clean:
- Receipt required above $50, enforced — the transaction is flagged in the ERP export until resolved.
- Anything above $2,000 requires a second approver, regardless of policy limit.
How long until the old expense process can be switched off?
About 30 days after the pilot ends. Keep the old system for one full cycle after the last person gets a card, then stop. Running both for a quarter tells people the new system is optional.
Where Ramp doesn’t fit
Companies whose accounting lives in a system with no supported integration, or with a strict requirement that card data never leave a specific region. Also companies that want a card and nothing else — the spend management layer is the product, and if you’re not using it, a plain bank corporate card is cheaper.
For a 20-person startup spending $60k a year on cards, the receipt capture and auto-coding genuinely save a bookkeeper’s day per month. That’s the case to test.
Quick Summary
- Ramp = corporate cards plus spend policies, receipt capture and accounting sync; the card is free, Ramp Plus ~$15/user/month.
- Connect and map accounting first — uncoded transactions are the number-one first-month pain.
- Four role-based policies beat per-person limits; block merchant categories rather than policing them.
- Pilot with 10 heavy expense users for a week and expect to fix two policy thresholds.
- Physical cards for travellers only; virtual cards per vendor for everything recurring.
Related guides
- Set up Rossum invoice capture for AP automation — the incoming-invoice side of the same accounting pipeline.
- Cut Rossum exception rates on messy invoices — keeps the AP side moving once card spend is automated.
