> 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/common-workflows/bill-pay.md).

# Bill Pay

Kick's Bill Pay tab gives you a live view of your outstanding bills, AP aging, and vendor balances - synced directly from [Ramp](/integrations/ramp.md).

{% hint style="info" %}
Bill Pay in Kick currently requires a connected Ramp integration. Bills created in Ramp sync into Kick automatically.
{% endhint %}

***

### What you'll see

The Bill Pay tab shows all bills from your connected Ramp account, including vendor, amount, status, and due date.

Use the view toggle in the top right to switch between:

* **By vendor** - one row per vendor, with open amounts broken out by aging bucket (1-30 days, 31-60 days, 61+ days, overdue)
* **By bill** - one row per bill
* **By line item** - one row per line item, for detailed ledger review

***

### Filters

Filter by time period, entity, status, due date, or amount using the controls in the top right and top left. The tab defaults to bills from the last 90 days.

***

### Connecting Ramp

If you haven't connected Ramp yet, go to the **Accounts** tab → **Add account** → **Ramp**, or click **Connect Ramp** directly from the Bill Pay tab.

→ [Connect Your Accounts & Integrations](/setting-up/connect-your-accounts-and-integrations.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kick.co/common-workflows/bill-pay.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.