Why does the Fully matched card show a non-zero Difference?

Short Answer: A non-zero 'Difference' within Fully matched usually indicates small rounding differences, different amount columns or tax/fee fields counted differently across the two reports.

PreRequisites

1. You can access the reconciliation results and 'Matched transaction details'

Steps

1. Click the 'Fully matched' card or tab to list matched transactions.
   Table of fully matched rows is visible.

2. Open the 'Matched transaction details' modal for rows likely contributing to the small Difference.
   Compare amount-related columns e.g., 'Final_Amount', 'igst_amt'.

3. Identify whether rounding, tax fields, or a wrong amount mapping cause the gap.
   You find the specific source of the difference.

4. Correct mappings or normalize amounts in source files and re-run reconciliation if needed.
   Difference should update after fixes and re-run.

Troubleshooting

1. Difference persists after inspecting a transaction.
   LikelyCause: Amounts may include taxes or fees on one side that are not present on the other side.
   Action: Ensure both reports point to the same net/total amount column or perform pre-processing to align the columns, then re-run reconciliation.

Note: In the example results the 'Fully matched' card shows 'Difference 1.04' — inspect transaction-level details to find contributors.