> ## Documentation Index
> Fetch the complete documentation index at: https://docs.withacclaim.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reconciliation

> Match incoming payments to your internal records. Track funds across payment requests and virtual accounts with structured data and reporting.

Reconciliation is the process of **matching incoming funds to your internal records**.

Acclaim provides structured data across payment requests, payers, and virtual accounts so you can **track, match, and report on payments accurately**.

***

## How reconciliation works

Every incoming payment is recorded with consistent identifiers and metadata.

You can use this data to:

* Match payments to invoices, claims, or internal records
* Track payment status and outcomes
* Reconcile totals across balances and reports

***

## Reconciliation by collection method

### Payment requests

Payment requests provide structured, one-to-one mapping between a request and a payment.

* Each request defines the expected amount and currency
* Completed payments are linked directly to the request
* Metadata can be used to associate payments with internal systems

This makes reconciliation straightforward for request-based payments.

***

### Virtual accounts

Virtual accounts enable reconciliation of **incoming bank transfers**.

* Each account can be assigned to a payer or workflow
* Incoming transfers are linked to the virtual account
* Reference data can be used to identify the purpose of a payment

This reduces ambiguity when receiving bank transfers.

***

### Saved payment methods

When using saved payment methods:

* Payments can be associated with a stored payer
* Reuse of payment methods ensures consistent payer identification
* Payment history can be tracked across multiple transactions

***

## Key reconciliation data

Each payment includes structured data to support reconciliation:

* Payment ID
* Amount and currency
* Status (e.g. **Succeeded**, **Failed**)
* Payer (if available)
* Payment method
* Metadata (custom fields)

Use this data to match payments to your internal records.

***

## Using metadata

Metadata allows you to attach your own identifiers to a payment.

Common use cases:

* Internal invoice ID
* Claim or policy reference
* Customer identifier

Including metadata at the time of creation improves reconciliation accuracy.

***

## Reporting and exports

You can export payment data from the Console for reporting and reconciliation.

Exports typically include:

* Payment details and status
* Amounts and currencies
* Payer information
* Timestamps and identifiers

This data can be used in:

* Accounting systems
* Internal reconciliation workflows
* Financial reporting

***

## Webhooks and automation

Webhooks allow you to automate reconciliation workflows.

Use webhooks to:

* Detect when a payment **succeeds**
* Update internal records automatically
* Trigger downstream processes

This reduces manual reconciliation effort.

***

## Best practices

* Include **metadata** for every payment request
* Assign **virtual accounts strategically** to reduce ambiguity
* Track payments using unique identifiers
* Use **webhooks** to automate reconciliation
* Regularly export and review payment data

***

## Summary

* Reconciliation matches incoming payments to your internal records
* Payment requests and virtual accounts provide structured tracking
* Metadata improves accuracy and automation
* Webhooks and exports enable efficient reconciliation workflows