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

# Reconciliation

> Matching incoming payments to drivers, and clearing unmatched and rejected transactions.

Reconciliation is the list of payments the platform has received and what it did with each one. Every payment carries an amount, a date and time, the sender, the matched driver, a confidence score, and a status.

## Statuses

<ResponseField name="Confirmed" type="status">
  The payment was matched to a driver and counts toward that driver's collections.
</ResponseField>

<ResponseField name="Pending" type="status">
  The payment is recognized and waiting to clear.
</ResponseField>

<ResponseField name="Unmatched" type="status">
  The payment arrived but the platform could not identify which driver it belongs to. It does not count toward collections until it is resolved.
</ResponseField>

<ResponseField name="Rejected" type="status">
  The payment was not accepted as a driver collection.
</ResponseField>

## The confidence score

The score shows how certain the match is, from 0% to 100%. A 100% match means the sender is unambiguously one of your drivers. A 0% match means the platform found nothing to go on, usually because the sender name does not appear on your roster.

## Clearing unmatched payments

<Steps>
  <Step title="Filter to unmatched">
    Use the status filter at the top of the screen.
  </Step>

  <Step title="Identify the sender">
    Compare the sender name and amount against your roster. A payment that matches a driver's daily amount exactly is a strong clue.
  </Step>

  <Step title="Confirm or dismiss">
    Dismiss the payments that are not driver collections, for example a transfer from a supplier or a refund. Leave anything you cannot place and raise it with Swapinga support rather than guessing.
  </Step>
</Steps>

<Warning>
  Dismissing a real driver payment removes it from that driver's record. If you are not sure who a payment belongs to, leave it unmatched and ask.
</Warning>

## Why payments arrive unmatched

The most common cause is that the driver paid from a mobile money account registered in another name, often a spouse or a colleague. Record the alternative sender name on the driver's profile so the pattern is visible to whoever handles reconciliation next.

Payments dated before your organization's reconciliation start date are never scanned. See [Organization settings](/setup/organization).