> ## Documentation Index
> Fetch the complete documentation index at: https://help.campfire.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Overview
> How Ramp and Campfire keep spend and the ledger in sync: card transactions, bills, reimbursements, and vendor credits in, and your accounting structure out.
The Ramp integration connects your Ramp spend to your Campfire ledger. Card transactions, bills, reimbursements, and vendor credits flow from Ramp into Campfire, and Campfire keeps your chart of accounts, vendors, departments, and tags in sync so every transaction is coded in Ramp against your Campfire structure. You can also push Campfire bills to Ramp to pay them there.
To connect Ramp, or cut over from another accounting system, see [Migration & Setup](/integrations/expense-ap/ramp/setup).
## What syncs
Ramp is your system of record for spend; Campfire is your system of record for the ledger.
```mermaid theme={null}
sequenceDiagram
autonumber
actor U as Your team
participant C as Campfire
participant R as Ramp
C->>R: Sync coding options: accounts, vendors, departments, tags, tax codes
U->>R: Spend and code transactions in Ramp
R->>C: Coded spend posts to the Campfire ledger
opt Pay in Ramp
C->>R: Push Campfire bills to Ramp
end
```
Each record type posts differently. See the per-record flow in [Card transactions](/integrations/expense-ap/ramp/card-transactions), [Bills & bill pay](/integrations/expense-ap/ramp/bills-bill-pay), and [Reimbursements](/integrations/expense-ap/ramp/reimbursements).
| Data | Direction | What Campfire creates |
| -------------------------------------------------------- | --------------- | --------------------------------------------------------------------- |
| Card transactions | Ramp → Campfire | Credit card journal entry |
| Bills (vendor invoices) | Ramp → Campfire | Bill, plus a payment once paid in Ramp |
| Reimbursements | Ramp → Campfire | Reimbursement bill (accrual) or a categorized bank transaction (cash) |
| Vendor credits | Ramp → Campfire | Debit memo, auto-applied to the bill |
| Chart of accounts, vendors, departments, tags, tax codes | Campfire → Ramp | Coding options in Ramp |
| Bills to pay in Ramp | Campfire → Ramp | A bill in Ramp, paid there |
## How the sync runs
* **Real time.** Campfire subscribes to Ramp webhooks, so new and changed card transactions, bills, and reimbursements post as they happen.
* **Every three hours.** A scheduled cycle reconciles anything missed, pulls vendor credits (which have no webhook and sync only on this cycle), and pushes your latest coding options to Ramp.
* **On demand.** Manually trigger a sync from the connection in Campfire.
* **Start date.** Only records dated on or after the connection's **Pull From** date sync, so activity from your previous system is never double-counted.
* **No duplicates.** Every record is matched to Ramp by its Ramp ID, so a re-sync never creates a second copy.
If your team turns on **Enable Sync Buttons in Ramp**, Campfire stops pulling
card transactions and reimbursements automatically and instead syncs them when
someone clicks Ramp's **Sync** button on the Transactions or Reimbursements
page.
### What the scheduled sync looks back on
The scheduled cycle pulls each record type within a rolling window, not your full history, so a record that ages out of every window is not picked back up automatically. Every window is also bounded by your **Pull From** date.
| Record type | Automatic lookback window |
| ----------------- | --------------------------------------------------------------------------------------------------------------- |
| Bills | Issued in the last 60 days, created (pushed to Ramp) in the last 30 days, or paid in the last 30 days |
| Card transactions | Cleared, with a transaction date in the last 60 days |
| Reimbursements | Submitted in the last 60 days, plus a 30-day buffer for late approvals; 6 months on the connection's first sync |
The three bill windows work together so a bill still syncs if any one of them applies: an old bill that is paid today still syncs its payment through the paid-in-30-days window, and a bill pushed to Ramp today syncs even if it was issued months ago.
If a record is older than these windows and never synced, marking it with
Ramp's **Sync** button (with **Enable Sync Buttons in Ramp** on) sends it to
Campfire regardless of the lookback window.
## How each record posts
Each object type posts differently, which matters when you reconcile.
* **Card transactions** post as a credit card journal entry once coded and marked **Ready to Sync** in Ramp. See [Card transactions](/integrations/expense-ap/ramp/card-transactions).
* **Bills** debit the expense accounts on each line and credit accounts payable. They are paid by matching the bank feed or through a clearing account. See [Bills & bill pay](/integrations/expense-ap/ramp/bills-bill-pay).
* **Reimbursements** post on an accrual or cash basis depending on your settings. See [Reimbursements](/integrations/expense-ap/ramp/reimbursements).
* **Vendor credits** post as a debit memo on the next scheduled cycle, which Campfire automatically applies against the matching bill. See [Vendor credits](/integrations/expense-ap/ramp/bills-bill-pay#vendor-credits).
## What Campfire sends to Ramp
Campfire keeps Ramp's coding options aligned with your ledger, so spend is categorized in Ramp using accounts and dimensions that already exist in Campfire:
* Chart of accounts, vendors, departments, and tags
* Tax codes (optional)
* Bills you choose to push to Ramp for payment
See [Sync settings](/integrations/expense-ap/ramp/setup#sync-settings) for what each toggle does.
## Not yet synced
Ramp purchase orders and 3-way match, and Ramp treasury or business-account transfers, do not sync into Campfire.
## Explore
Cut over from your previous system, connect Ramp, and verify the sync.
Every connection toggle and what it controls.
How card spend is coded, posted, and amortized.
Bills in and out of Ramp, payments, vendor credits, and clearing accounts.
Accrual and cash treatment for employee reimbursements.