> 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.md).
# Match card statements to transactions
Match rows from your card and bank statements to RollCredits transactions, review and undo matches, and export the results.
Use the Reconciliation page to check your card and bank statements against your RollCredits transactions. Owners, Super Admins, Managers, Department Heads, Cast and Crew and Card Holders can open it from **Reconciliation** in the sidebar.
{% hint style="info" %}
Reconciliation appears only if your company uses it. Owners, Super Admins and Managers open this page from **Reconciliation > Matching** instead. This page is for Owners, Super Admins and Managers, who see every statement row. Everyone else sees only the rows for the cardholder names assigned to them on [Assign Cards](/reconciliation/assign-cards.md). See [Reconcile your own card transactions](/reconciliation/matching/reconcile-your-card.md).
{% endhint %}
## How the page works
The **Unmatched** tab shows the statement rows and transactions that still need a match, side by side. The **Matched** tab lists the matches already made. Owners, Super Admins and Managers also see **Export** above the tabs.
Statement rows come from uploaded statements, the Amex transaction feed if your company uses it (see [Set up the Amex transaction feed](/reconciliation/amex-sft-config.md)), and purchases on RollCredits cards, which arrive already matched.
Statement rows belong to your company, so every production shows the same unmatched rows. The **Rollcredits Transactions** table shows only this production's unmatched transactions, leaving out estimates. Once a row is matched, it leaves the **Unmatched** tab on every production, and the match shows on the **Matched** tab of the transaction's production.
## In this section
* [Upload card statements](/reconciliation/matching/upload-statements.md): add a card or bank statement file, and delete statement rows or a whole statement.
* [Reconcile your own card transactions](/reconciliation/matching/reconcile-your-card.md): the cardholder's view, limited to your own card rows and transactions.
## Choose a statement file
1. At the top of either tab, select the statement file dropdown.
2. Choose a file, or choose **All** to see every row.
Each file is listed with two counts in brackets, such as `June statement.csv - (12/40)`. The first is the file's matches on this production, and the second adds the file's rows that aren't matched yet. Files that still have rows to match come first.
The file you choose:
* Filters the **Credit Card Statement Rows** table and the **Matched** tab. It doesn't filter the **Rollcredits Transactions** table.
* Stays chosen when you switch tabs.
* Limits what **Export** includes.
The dropdown appears once your company has at least one statement file. Rows that didn't come from a file, such as P-Card rows, show **\[No File Name]** and appear only under **All**. While a file is chosen, Owners, Super Admins and Managers can delete the whole statement with **Delete Statement**. See [Upload card statements](/reconciliation/matching/upload-statements.md).
## Read the tables
The **Credit Card Statement Rows** table shows each row's **Vendor**, **Date**, **Amount**, **Card #** (the end of the card number), **File Name** and **Card Program**, which is **P-Card** for purchases on RollCredits cards and empty otherwise. **Acc #** (the end of the account number) and **Cardholder** appear only when some rows have them.
The **Rollcredits Transactions** table has the same columns as the table on the Transactions page. See [Find and edit transactions in the table](/transactions/transactions/find-and-edit.md).
Both tables keep a total row at the top. It adds up every row that passes the table's **Quick filter...** box and column filters, on all pages.
## Match statement rows to transactions
1. On the **Unmatched** tab, tick one or more rows in **Credit Card Statement Rows**. The checkbox in the header ticks every row that passes the table's filters, on all pages.
2. Tick one or more transactions in **Rollcredits Transactions**.
3. Compare the totals in the box above the tables. The statement rows' total is on the left and the transactions' total is on the right, with **Totals match** or **Totals do not match** under them.
4. Select **Match Selected**.
RollCredits shows "Matched!", and the matches move to the **Matched** tab.
* You can match one statement row to several transactions, or several statement rows to one transaction. You can't match several rows to several transactions at once. **Match Selected** is greyed out and a warning asks you to select one row and many transactions, or the other way round.
* **Match Selected** works even when the totals don't match, so check them before you select it.
* The box also counts what's ticked in each table. Select **Reset selected** under a count to clear that table's ticks. On a narrow screen the counts and **Reset selected** are hidden, so untick the rows instead.
## Add a statement row as a new transaction
Use this when a statement row has no transaction in RollCredits yet.
1. On the **Unmatched** tab, select the **...** menu at the end of the row in **Credit Card Statement Rows**.
2. Select **Add to RollCredits**.
RollCredits adds a receipt to this production with the row's vendor, amount, date and card number, and matches the row to it. It shows "Credit card statement added as a new RollCredits transaction". A vendor that isn't in RollCredits yet is added. The new receipt has no file, so open it with the eye button on the **Matched** tab to attach the receipt and code it.
The same menu has **Delete** for Owners, Super Admins and Managers. See [Upload card statements](/reconciliation/matching/upload-statements.md).
## Open a transaction
1. Select the eye button at the end of a transaction's row, in the **Rollcredits Transactions** table or on the **Matched** tab.
2. The transaction opens in the side panel, beside the tables. On a phone, it fills the screen. For what you can do there, see [Review and edit a transaction](/transactions/transactions/edit-a-transaction.md).
3. To close the panel, select the **X** at its top or press Esc. Switching tabs closes it too.
## Review matches
The **Matched** tab has a row for each match, so a statement row matched to three transactions takes three rows. It shows only matches to this production's transactions. The columns are:
* **Matched By**: **AI** when RollCredits made the match automatically, **User** when someone matched it.
* **Matched At**: the date and time of the match.
* **Credit Card Statements**: the statement row's **Vendor**, **Amount**, **Acc #**, **Card #**, **Date**, **Cardholder**, **File Source** and **Card Program**. **Acc #** and **Cardholder** appear only when some rows have them.
* **RollCredits Transactions**: the transaction's **Vendor**, **Amount**, **Card #**, **Date** and **Category**. **Category** shows **Multiple categories** when the transaction is coded to more than one.
## Undo a match
1. On the **Matched** tab, find the match.
2. Select **Unmatch** at the start of its row. On a phone, the button shows only an icon.
{% hint style="warning" %}
**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.
{% endhint %}
* If RollCredits made the match automatically, it won't match that statement row automatically again. You can still match it yourself.
* When one statement row is matched to several transactions, each **Unmatch** removes one of those matches. To undo the whole match, select **Unmatch** on each of its rows.
## Automatic matching
Purchases on RollCredits cards come into Reconciliation on their own. Each purchase arrives as a statement row already matched to its card transaction, with **P-Card** in **Card Program** and **AI** in **Matched By**. You don't need to upload statements for these cards. To attach their receipts, see [Match receipts to card transactions](/transactions/transactions/match-card-receipts.md).
{% hint style="info" %}
If your company uses automatic matching, RollCredits also matches your other statement rows for you:
* Right after you upload a statement with new rows.
* When RollCredits finishes reading a newly uploaded document.
* About every 30 minutes, while your company has a production that isn't wrapped and had a transaction added in the past week.
It matches one statement row to one transaction with the same amount when their dates are close or their vendor names are alike, on any of your company's productions that aren't wrapped. These matches show **AI** in **Matched By**. Check them on the **Matched** tab and unmatch any that are wrong.
{% endhint %}
## Export the reconciliation
Owners, Super Admins and Managers can download this production's reconciliation.
1. To export one statement only, choose its file in the statement file dropdown. Leave **All** to export every file.
2. Select **Export** above the tabs. RollCredits shows "Your file download will begin shortly. Please wait..." while it builds the file, then downloads it.
The download is a zip file that holds:
* `reconciliation.xlsx`, with three sheets:
* **Matched**: each match on this production, with the statement row's details, then the transaction's.
* **Unmatched Credit Card**: your company's statement rows that aren't matched yet.
* **Matched (Quickbooks)**: the same matches with the columns Item, Date, Vendor, Description, Job, Job Number, Acctg Code and Amount.
* The files attached to the matched transactions, in a folder for each card.
{% hint style="info" %}
If your company uses a custom export layout, **Export** downloads a single Excel file of the matches instead, without the attached files.
{% endhint %}
---
# 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.md?ask=&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.
