> 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.md).

# Bill Pay

### What syncs here

Kick has a bill pay integration with Ramp. When Ramp is connected, bills sync to the Bill Pay tab automatically — including bill line item detail, vendor information, and payment status. GL account assignments made in Ramp sync into Kick automatically.

If your client uses multiple Ramp accounts across entities, the Bill Pay tab allows you to manage all of them in a single view.

The Bill Pay tab is available on all plans for clients with a Ramp integration connected.&#x20;

Plus plan clients have access to all features, including the Bill Importer, Accrual ledger categorization, and automated AP reconcilaition.

{% hint style="info" icon="right-long" %}
Bill.com integration is coming soon.
{% endhint %}

→ [Ramp Chart of Accounts Setup](/accountants/bookkeeping-workflows/bill-pay/ramp-chart-of-accounts-setup.md)

***

### Navigating the Bill Pay tab

Use the dropdown in the top right to toggle between three views:

* **By vendor** — one row per vendor with aggregated bill totals
* **By bill** — one row per bill
* **By line item** — one row per line item; the best view for Accrual ledger work when the Accrual ledger is enabled

<div data-with-frame="true"><figure><img src="/files/XnYl8XkZzmgVT7Laqyg4" alt=""><figcaption></figcaption></figure></div>

The chart at the top is interactive — click any status to filter the view below.

**Filters**

Filter by time period or entity using the filters in the top right. The Bill Pay tab defaults to bills created in the last 90 days. Additional filters are available in the top left.

**Saving custom views**

Configure your columns and filters, then click **Save** in the top right. Name your view and access it from the dropdown in the top left.

***

### Bill status

Each bill has two statuses:

| Status          | What it reflects                                               |
| --------------- | -------------------------------------------------------------- |
| External status | The paid or open status maintained in Ramp                     |
| Kick status     | Updated when you match a bill to a payment transaction in Kick |

In most cases these should stay in sync. Matching a transaction to a bill in Kick updates the Kick status but does not affect the external status in Ramp.

***

### Creating bills

Click **Create bill** in the top right. The dropdown includes:

* **Ramp** — opens the create bill flow in Ramp
* **Importer** — opens the Bill Importer (Plus plan only)

The Bill Importer lets you manually record bills in Kick for clients who aren't using Ramp for bill pay.&#x20;

You can enter bills one at a time or paste in rows from a spreadsheet if the columns match the required format.&#x20;

Bills created via the importer are for accounts payable reconciliation purposes — payments are handled in your client's bill pay software, not in Kick.

{% hint style="info" %}
The Bill Importer is available on the Plus plan. It's designed for clients who need AP reconciliation but aren't using Ramp for bill pay.
{% endhint %}

***

### Accrual ledger

When the Accrual ledger is enabled, two additional columns become available in the **By line item** view:&#x20;

1. **Accrual ledger**
2. **Payables account**.

These fields control how bill-related journal entries are generated on the Accrual ledger.

<div data-with-frame="true"><figure><img src="/files/QyUPx4f3TMJjD3IYWFod" alt=""><figcaption></figcaption></figure></div>

By default, all bill line items post to an expense account on the Accrual ledger side and Accounts Payable on the payables side. You can override either at the line item level:

1. **Accrual ledger account** — post individual line items to specific expense accounts. For example, a multi-line bill might have one line posted to Travel and another to Software.
2. **Payables account** — by default this is Accounts Payable, but you can create custom payables accounts to track AP by vendor, project, department, or any other dimension.

Classes can also be assigned at the line item level and flow through to your by class reports on the Accounting tab.

***

### Bill journal entries

Bills generate journal entries on the Accrual ledger for each entity. To view bill-sourced journals, filter for **Entry source → Bill** on the General Ledger.

<div data-with-frame="true"><figure><img src="/files/Gd4238BtwHt67JVXp1rk" alt=""><figcaption></figcaption></figure></div>

***

### AP reconciliation

When a payment goes out for an outstanding bill, Kick proposes a match between the transaction and the open bill. Confirming the match posts the transaction to Accounts Payable (or a custom Payables account) on the Accrual ledger rather than an expense account, preventing double-counted expenses.

You can also match manually: go to the transaction details panel on the Transactions tab and click **Find a match**.

<div data-with-frame="true"><figure><img src="/files/2DvMt3NjPJ6qFhtGbiX7" alt=""><figcaption></figcaption></figure></div>

→ [Accrual Tasks](/accountants/close-workflows/tasks/accrual-tasks.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/accountants/bookkeeping-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.
