If you synchronised Cleemy with banking traffic, this is automatically reconciled with expenses created using character recognition. Bank traffic resulting in reconciliation includes:
- Transactions using Anytime payment cards for Cleemy.
- Synced expenses from your bank using the Budget Insight aggregation service.
How reconciliation works
Cleemy performs reconciliation by comparing the amounts and date detected on the receipt when it is captured using the mobile app and those sent by the bank. The nature of the expense is not a reconciliation criterion because the bank often only has incorrect data.
You can tell when an expense is the result of automatic reconciliation by viewing its source:
What happens if Cleemy reconciles a receipt and transaction by mistake?
Employees submitting expenses can cancel reconciliation as long as they did not modify the expense. If you cancel reconciliation, you end up with two expenses: one created using receipt data and the other using bank data.
Is Cleemy always able to reconcile transactions?
Even if character recognition worked perfectly, automatic reconciliation is not always possible. Such purchases have a payment date that is different from the date on the receipt.
This is the case for train tickets purchased in advance: the bank transaction will appear in Cleemy in real time or the next day and will show the payment date, while the receipt will show the day of the trip.
Reconciliation may also fail when the artificial intelligence that reads the receipt data makes a mistake.
What can you do if reconciliation fails?
In this case, the easiest solution is to open the expense from the bank and add the receipt to it. You will have to verify or fill in the fields usually provided by character recognition but not by the bank: the nature and VAT.
Next, delete the expense created by automatic recognition of receipts.