> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/accountants/setting-up/integrations/ramp.md).

# Ramp

Sync your Ramp credit card transactions, reimbursements, and bills directly into Kick.

{% hint style="info" %}
**Before you connect**

You must be an **admin** of your Ramp account to connect the integration.
{% endhint %}

### How to connect

You can connect Ramp from either of two places:

<div data-with-frame="true"><figure><img src="https://290614220-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiOfJtU5BnOhuPqTiOHth%2Fuploads%2Fgit-blob-01d422a86178dac1e28b7ad9b07fa0af65e814cb%2FCleanShot%202026-04-01%20at%2011.19.29.gif?alt=media" alt=""><figcaption></figcaption></figure></div>

**From the** [**Accounts**](https://use.kick.co/accounts) **tab**

1. Navigate to the **Accounts** tab.
2. Click **Add account** in the top right.
3. Select **Ramp** from the dropdown, or search for it.
4. Follow the prompts to authenticate with your Ramp admin credentials.

<div data-with-frame="true"><figure><img src="https://290614220-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiOfJtU5BnOhuPqTiOHth%2Fuploads%2Fgit-blob-8b2b11a3a444dcf1558848ef71e4821c2af3a3a5%2FCleanShot%202026-04-01%20at%2011.15.28.gif?alt=media" alt=""><figcaption></figcaption></figure></div>

**From the** [**Bill Pay**](https://use.kick.co/billing) **tab**

1. Navigate to the **Bill pay** tab.
2. Click **Connect Ramp**.
3. Follow the prompts to authenticate with your Ramp admin credentials.

Regardless of where you connect, all data types (credit card transactions, reimbursements, and bills) will sync.

***

### What syncs from Ramp

**Credit card transactions**

All Ramp virtual cards will appear as a **single credit card account** on your Balance Sheet. Credit card transactions sync on the Transactions tab and can be categorized and edited similar to transactions from any other integrated account.

**Reimbursements**

Reimbursements sync as a **separate account** under Other Current Liabilities on your Balance Sheet. When reimbursements are paid, they map to this liability account — so your Balance Sheet always reflects a live running balance of what is owed. Reimbursement-related transactions appear on the Transactions tab.

**Bills**

Bills from Ramp sync on the Bill Pay tab. For details on how Kick handles accounts payable reconciliation and bill pay insights, see [Bill Pay](/accountants/bookkeeping-workflows/bill-pay.md).

**Receipts**

All receipts from Ramp sync automatically and are matched to their corresponding expense transactions in Kick — no need to manage receipts in two places.

**Departments**

If you use departments in Ramp, they will automatically sync as Classes in Kick.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/accountants/setting-up/integrations/ramp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
