> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/reconciliation/matching/reconcile-your-card.md).

# Reconcile your own card transactions

Match the rows on your own card statement to your RollCredits transactions on the Reconciliation page.

Use Reconciliation to match your card statement rows to your transactions in RollCredits. Open it from **Reconciliation** in the sidebar. Department Heads, Cast and Crew and Card Holders see the version on this page. Owners, Super Admins and Managers see every row, as described in [Match card statements to transactions](/reconciliation/matching.md).

{% hint style="info" %}
If your company uses reconciliation, **Reconciliation** shows in the sidebar. You see statement rows only once an Owner, Super Admin or Manager assigns your cardholder name to you on Assign Cards.
{% endhint %}

## What you see

* **Credit Card Statement Rows** lists only rows whose cardholder name is assigned to you. Rows with no cardholder name don't show.
* **Rollcredits Transactions** lists only the unmatched transactions you can see on the Transactions page for this production, leaving out estimates.

If your rows are missing, ask an Owner, Super Admin or Manager to assign your cardholder name to you on [Assign Cards](/reconciliation/assign-cards.md).

Your rows show on every production in your company, so switch to the right one before you match. On a phone, the statement rows are above your transactions.

{% hint style="info" %}
You can't upload, delete or export statements. An Owner, Super Admin or Manager does that.
{% endhint %}

## Match rows to transactions

1. On the **Unmatched** tab, tick one or more rows in **Credit Card Statement Rows**.
2. Tick the matching transactions in **Rollcredits Transactions**.
3. Check that the totals above the tables show **Totals match**.
4. Select **Match Selected**.

You can match one row to several transactions, or several rows to one transaction, but not several to several. **Match Selected** also works when the totals don't match.

To clear your ticks, select **Reset selected**. On a phone, that button is hidden, so untick the boxes.

## Add a purchase that isn't in RollCredits yet

1. On the **Unmatched** tab, select the **...** menu at the end of the statement row.
2. Select **Add to RollCredits**.

RollCredits creates a receipt on this production from the row's vendor, amount, date and card number, and matches it to the row. Open it from the **Matched** tab to add the receipt file.

## Unmatch a row

1. Open the **Matched** tab.
2. Select **Unmatch** on the row. On a phone, it's an icon with no label, at the start of the row.

**Unmatch** takes effect right away, with no confirmation step. The statement row and the transaction each go back to the **Unmatched** tab once they have no matches left. If **Matched By** showed **AI**, RollCredits won't match that row automatically again, but you can still match it yourself.

## Add a receipt or coding

1. Select the eye button at the end of a transaction's row, in **Rollcredits Transactions** or on the **Matched** tab.
2. Edit it in the side panel. See [Review and edit a transaction](/transactions/transactions/edit-a-transaction.md) and [Code transactions](/transactions/transactions/code-transactions.md).
3. To close the panel, select the X at its top or press Esc.

On a phone, the panel fills the screen.


---

# 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://knowledge.rollcredits.io/reconciliation/matching/reconcile-your-card.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.