> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/other-features/payments-modules/reconciliation-product.md).

# Reconciliation

Explore Juspay Hyperswitch Reconciliation module to eliminate revenue leakage through automated matching across order management, PSP, and bank systems

Are you truly confident that every customer payment lands in your bank account? For most businesses, the path from transaction to settlement is a complex maze of different providers, inconsistent data, and manual checks—a system ripe for revenue leakage, reporting errors, and compliance risks.

The reconciliation problem is further compounded by following factors:

* Different acquirers provide files in inconsistent formats, with uneven settlement schedules, varied fee structures, and unpredictable reversals
* Refunds, disputes, and partial settlements often follow fragmented workflows, while providers use different terminology for the same status, making it hard to maintain a clear audit trail
* Banks further complicate matters with lump-sum deposits, posting delays, hidden charges, and partial or reversed credits

Our Reconciliation Module is built on a powerful, accounting-grade ledger, applying the precision of double-entry bookkeeping to your entire payment flow.

### Jump to:

| [Core Concepts](/other-features/payments-modules/reconciliation-product/core-concepts.md)                           | [How Reconciliation Works](/other-features/payments-modules/reconciliation-product/how-reconciliation-works.md) |
| ------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| [Example: E Commerce](/other-features/payments-modules/reconciliation-product/example-e-commerce.md)                | [Exception Handling](/other-features/payments-modules/reconciliation-product/exception-handling.md)             |
| [Statuses in Reconciliation](/other-features/payments-modules/reconciliation-product/statuses-in-reconciliation.md) | [Roadmap](/other-features/payments-modules/reconciliation-product/roadmap.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/other-features/payments-modules/reconciliation-product.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.