# Getting Started With Ledge Reconciliation

Ledge streamlines finance & payment operations by centralizing data form a company's entire stack, and automating workflows on a single user-friendly platform.

Reconciliation ensures your external transactions align with internal records. This can range from straightforward tasks, like matching bank statements to invoices to update accounts receivable, to more complex workflows, such as reconciling transactions across buyers, platforms, and sellers in marketplace environments.\
Ledge’s platform operates through four key stages:

[<mark style="color:green;">Ingestion</mark>](/sources/data-ingestion.md)\
Seamlessly import transaction and payment data from any bank, payment processor, or financial system.

[<mark style="color:green;">Matching</mark>](/transaction-matching/matching-rules.md) <mark style="color:green;">&</mark> [<mark style="color:green;">Payment Flows</mark>](/reconciliation/payment-flows.md)\
Reconcile transactions with flexible 1-to-1 or many-to-1 matching, using either pre-built or custom rules. The Payment Flows feature enables multi-step reconciliations across various data sources and financial institutions.

<mark style="color:green;">Exception Management</mark>\
Identify and resolve discrepancies with a collaborative tool designed to streamline exception handling within finance & payments teams.

<mark style="color:green;">ERP Posting</mark>\
Automatically post reconciliation results to your ERP system, including journal entries, cash applications, and more.

With Ledge, finance teams can reduce manual work, improve accuracy, and scale operations with confidence.


---

# Agent Instructions: 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.ledge.co/getting-started-with-ledge-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.