> 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/exception-handling.md). # Exception Handling Understand how Juspay Hyperswitch captures, classifies, and manages reconciliation exceptions—including Mismatched and Expected transaction anomalies—to maintain financial data integrity. ### Overview The Exception Module is responsible for capturing, classifying, and managing anomalies detected during the reconciliation process. This module ensures that no transaction is lost and that financial data integrity is maintained between the internal data (Left Side) and the external partner/gateway (Right Side). ### Exception Classifications Exceptions are categorized into two distinct types based on the presence of counterpart data and the result of the matching logic. #### Type A: Mismatched (Data Integrity) * **Definition:** Records exist on both sides, and the system has attempted reconciliation. However, the comparison logic failed because key attributes do not match. * **Reconciliation Status:** `MISMATCHED` * **Business Context:** This represents a data integrity error requiring investigation (e.g., amount discrepancies, status discrepancies, or metadata corruption). #### Type B: Expected (Timing/Availability) * **Definition:** These are one-sided transactions. The system has a record on one side (e.g., Internal Ledger), but the corresponding record on the other side (e.g., Bank Statement) has not arrived yet. * **Reconciliation Status:** `EXPECTED` * **Business Context:** This is often a temporary state caused by processing latency, batch cut-off times, or network delays. --- # 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/exception-handling.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.