Ramp + Go Fig
Connect Ramp to Go Fig so card spend, expenses, bill pay, and accounting coding flow into the Excel package your finance team already uses, reconciled and standardized across every portfolio company.
Ramp runs corporate cards and spend management (expenses, bill pay, and accounting automation) for fast-moving, PE-backed companies, but the answers a fund controller or fractional CFO actually needs (spend by category and entity, who is over budget, uncoded transactions, committed but unpaid bills across the portfolio) live behind the Ramp dashboard and have to be exported, re-keyed, and pivoted before they tie to the GL. Go Fig does not replace Ramp. It connects to the Ramp REST API, syncs transactions, cards, reimbursements, bills, and accounting categories, reconciles them against the GL, and loads fresh, standardized, traceable data into the Excel your team already works in, automatically, every day. Celeste, Go Fig's AI analyst, can then answer questions like 'which portfolio companies are running hottest on T and E this quarter' with a full audit trail back to the originating transaction. Your financial data stays in your environment. It is never pasted into a public chatbot and never used to train an outside model. Celeste works only on your data, with a complete audit trail.
Key facts
- System
- Ramp corporate cards and spend management
- Sync grain
- Transaction, reimbursement, and bill level
- Multi-entity
- One Ramp business per portfolio company
- Historical backfill
- Up to 3 years of transaction and bill history
- Auth
- OAuth via the Ramp REST API
What you can do with Ramp data in Go Fig
Spend management across the portfolio
Card and reimbursement spend rolled up by category, department, and entity, compared against budget, so the spend management conversation happens against live data instead of a stale export. See which portfolio companies are over and where the overage is coming from.
Coding and accrual completeness
Uncoded or miscoded transactions surfaced by entity before close, with the GL category, merchant, and cardholder intact. The standardized package no longer waits on someone re-keying Ramp exports into a spreadsheet.
Committed AP and bill pay visibility
Bills and scheduled payments from Ramp's bill pay aged by vendor and entity, reconciled against the AP balance in your GL, so committed spend and the controller's payables tie across every portfolio company.
Data available from Ramp
Go Fig extracts and normalizes the following data from your Ramp account:
How to connect Ramp
Authorize Ramp via OAuth
Connect Ramp in Go Fig through the OAuth flow and grant read access to the transaction, card, bill, and accounting data you want exposed. No API keys to manage by hand. For PE groups, authorize each Ramp business separately so entity-level isolation is preserved.
Connect each entity's Ramp business
Each portfolio company typically runs its own Ramp business. Connect them one at a time in Go Fig. The source business is preserved as a column so you can report by entity, consolidate across the portfolio, or roll spend up into one standardized package.
Pick the historical window
Ramp's API exposes timestamps on transactions and bills, so Go Fig backfills history once and then syncs deltas incrementally. One to three years of transaction and bill history is typical for portfolio companies rebuilding spend and accrual trends.
Wire up the standardized spend package
Celeste ships starter flows for spend by category and entity, budget versus actual, coding completeness, and committed AP. Point them at your Ramp connections and the standardized package lands in Excel on day one, with drill-down back to the originating transaction and bill.
Authentication: Ramp provides a REST API with OAuth. Go Fig connects through the OAuth flow with read-scoped access to your Ramp business, exchanges the authorization for a token, and refreshes it automatically. Each Ramp business (entity) is connected separately, which keeps entity-level isolation clean for portfolio roll-ups.
Common Questions About Ramp Integration
Does Go Fig replace Ramp?
No. Your team keeps swiping cards, submitting expenses, and paying bills in Ramp exactly as they do today. Go Fig connects to the Ramp REST API, reconciles spend against the GL, and loads fresh, standardized data into the Excel your finance team already uses, automatically, every day. Ramp stays the system of record. Go Fig makes its data consolidate and tie out across the portfolio.
How does Go Fig consolidate Ramp across multiple entities?
Each portfolio company's Ramp business is connected separately, and the source business is preserved as a column on every row. You can report spend by entity, consolidate the whole portfolio by mapped chart of accounts, or roll category spend up into one standardized view. PE groups with many entities typically build a mapping table in Go Fig that translates each Ramp accounting category into one shared reporting structure, so the roll-up finally ties.
Can Go Fig reconcile Ramp coding to the general ledger?
Yes. Go Fig joins Ramp transactions and bills against the GL by accounting category and entity, then surfaces uncoded or miscoded items before close. A typical reconciliation catches transactions posted to the wrong category, reimbursements that never hit the ledger, and bills marked paid in Ramp that are missing from the GL, all with a trace back to the originating record.
Is our financial data safe and private?
Yes. Your Ramp data stays inside your Go Fig environment. It is never pasted into a public chatbot and never used to train an outside model. Celeste, Go Fig's AI analyst, works only on your data and leaves a full audit trail for every answer, so you can see exactly which transactions and bills a number came from.
How fresh is the Ramp data inside Go Fig?
Daily incremental sync is the default, keyed on the timestamps Ramp exposes for transactions and bills. Portfolio companies with heavy card volume can dial sync more frequently if the on-call analyst needs near-real-time visibility. A full reindex runs on a regular schedule so nothing drifts.
