> 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/bookkeeping-workflows/bill-pay/ramp-chart-of-accounts-setup.md).

# Ramp Chart of Accounts Setup

Import your Kick Chart of Accounts to Ramp in three steps.

For bill to accounting ledger mapping to work smoothly across both platforms, your Kick Chart of Accounts needs to be uploaded to Ramp. When your team assigns accounts in Ramp, they sync directly to Kick — no duplicate work required.

***

### Export your chart of accounts from Kick

1. Navigate to **Accounting →** [**Chart of Accounts**](https://use.kick.co/chart-of-accounts)
2. Export as Excel

***

### Upload your Chart of Accounts to Ramp

1. In [Ramp](https://ramp.com/), go to **Accounting** and click **Get started now**
2. Scroll down and type **Kick** as your provider
3. Download Ramp's template — it requires two columns: account number and account name
4. Copy your Kick account numbers and names into the template
5. Upload the completed file and click **Continue**

***

### Configure your accounting settings

1. Select your monthly book close date
2. Map card transactions to your **Ramp** **credit card liability account** (enter the account name and ID from your Kick chart of accounts)
3. Choose your accounting date preference — **Clearing date** is recommended
4. Map statement payments to your **Credit Card Clearing** account
5. Map cashback to an income account (e.g., Other Income)
6. Map unpaid reimbursements and reimbursement payouts to your **Ramp reimbursements** account
7. Click **Continue** to complete setup

{% embed url="<https://player.mux.com/i008Tw8oZq7rLz5Q7ofQilqPkmumMLtIQCkuL02OEqzEw>" %}


---

# 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/bookkeeping-workflows/bill-pay/ramp-chart-of-accounts-setup.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.