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

# Reconciliation

Reconciliation is the process of comparing your transactions in Kick against your actual bank or credit card statements to confirm everything is accounted for and accurate. It's typically done once a month at close, and is usually handled by your accountant - but understanding what it is and why it matters helps you work together more effectively.

***

### What reconciliation does

Every transaction in Kick comes from a bank feed or an import. Reconciliation verifies that the transactions Kick has on record for an account actually match what the bank has on record - same amounts, same dates, no missing transactions, no duplicates.

When reconciliation is complete for a period, those transactions are marked as reconciled. If your accountant then [locks](/working-with-your-team/locks.md) the period, the numbers are frozen and protected from accidental changes.

***

### Which accounts can be reconciled

* Checking accounts
* Savings accounts
* Credit cards
* Lines of credit

***

### How reconciliation works in Kick

#### Step 1 - Upload your bank statement

Open **Reconciliation** from the sidebar and select the account to reconcile. Upload the bank statement for the period as a PDF. Kick extracts the statement's opening balance, closing balance, and transaction list automatically.

#### Step 2 - Review matches

Kick pairs each statement line against the transactions already in your Kick account. Most will match automatically. For any differences - a transaction that's in the statement but not in Kick, or in Kick but not the statement - you review and resolve each one.

Common resolutions:

* **Add a missing transaction** - the bank has it but Kick doesn't (often from a disconnected account)
* **Remove a duplicate** - Kick has an extra transaction that doesn't exist on the statement
* **Mark as from a previous period** - a transaction that belongs to an earlier reconciliation

#### Step 3 - Finish

Once Kick's reconciled closing balance matches the statement's closing balance exactly, you can finish the reconciliation. The period is marked as reconciled and a record is saved.

{% embed url="<https://www.loom.com/share/71dab8a900494c3a894ed8f1f544c7e8>" %}

***

### Undo a reconciliation

The most recent reconciliation can be undone from the Reconciliation page if a mistake is found. Earlier periods cannot be undone - changes to those require your accountant to unlock the period and make corrections.

***

### Reconciliation and Import Transactions

If your bank statement has transactions that aren't in Kick - because the account was disconnected or the bank's Plaid history doesn't go back far enough - use Import Transactions first to bring them in, then reconcile.

→ [Import Transactions](/setting-up/universal-importer.md)

***

### FAQs

<details>

<summary><strong>Do I need to reconcile every month?</strong></summary>

It's best practice. Monthly reconciliation catches missing or duplicate transactions quickly, before they compound across periods. Your accountant will typically drive this as part of the monthly close.

</details>

<details>

<summary><strong>What if the closing balance doesn't match?</strong></summary>

It means there's a difference between what the bank recorded and what Kick has. Common causes: a missing transaction, a duplicate, an incorrect amount, or a transaction dated in the wrong period. Work through the unmatched items to find and resolve the discrepancy.

</details>

<details>

<summary><strong>Can I reconcile if my account has a connection error?</strong></summary>

No - fix the connection first, then reconcile. Go to the Accounts tab and click **Fix connection** on the affected account.

</details>


---

# 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/reconciliation.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.
