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

# Receipt Matching

> Automatic matching between receipts and corporate card transactions, so every purchase becomes one expense — not two.

<Note>
  **This applies to the following countries**

  * All countries
</Note>

Receipt Matching is a new version of our matching service that connects receipts, existing expenses, and corporate card transactions in a smarter and more dynamic way. Whether your receipt arrives as a photo, a forwarded email, or a PDF attachment, it is matched to the right card transaction instantly. If the transaction arrives after the receipt, it is automatically linked to the existing receipt or expense.

All users with a connected card in the service get better control and accuracy in their expense reporting, and the risk of submitting the same purchase more than once is reduced.

## Before you start

* You have a **connected corporate card** in the service.
* Works in both the **mobile app** and the **web interface**.

## How it works

Receipts and transactions rarely arrive in the system at the same time. Transaction data from banks can be delayed by several days due to clearing cycles, while users often snap photos of receipts immediately or forward them by email sporadically. Without an automated bridge, the system would treat the receipt and the transaction as two separate entities, forcing you to link them manually.

The matching engine reads the **purchase amount**, **transaction date**, **purchase date**, **merchant name**, and **card number** to find the right pair between the receipt and the transaction.

Matching happens in three directions:

* **Expense to transaction** — You have already created an expense. When the card transaction arrives, it is automatically linked to the expense.
* **Transaction to expense** — The card transaction arrives first. When you later add the receipt, it is linked to the transaction.
* **Email receipt to transaction** — A receipt forwarded by email is matched against an existing or incoming card transaction.

## Good to know

* A purchase should become **one** expense. If you see duplicates, the matching is off — contact support.
* Receipt Matching is a key step toward our vision of expense management on autopilot: the expense is created for you without you having to handle receipts from multiple sources.
* Matching works regardless of whether the receipt comes in as a photo, email, or PDF.

## Next steps

<CardGroup cols={2}>
  <Card title="Corporate cards" icon="credit-card" href="/en/corporate-cards-users">
    How to use your connected corporate card in the service.
  </Card>

  <Card title="Expenses and receipts" icon="receipt" href="/en/expense-and-reports-users">
    How to create expenses and manage receipts.
  </Card>
</CardGroup>

## FAQ

<AccordionGroup>
  <Accordion title="Which fields are used for matching?">
    Purchase amount, transaction date, purchase date, merchant name, and card number.
  </Accordion>

  <Accordion title="What happens if the transaction arrives several days after the receipt?">
    The match still happens. When the transaction comes in from the bank, it is automatically linked to the existing receipt or expense.
  </Accordion>

  <Accordion title="Does it work with forwarded email receipts?">
    Yes. Receipts sent in by email are matched the same way as photographed and uploaded receipts.
  </Accordion>

  <Accordion title="What do I do if the same purchase has ended up as two expenses?">
    Contact support. A purchase should become one expense — duplicates mean the matching needs to be reviewed.
  </Accordion>
</AccordionGroup>