Short Answer: A non-zero Difference means Books and Customer statement totals don't balance for the selected group — usually caused by wrong header row, incorrect amount orientation, or missing Reference/Identifier mappings.
PreRequisites
- You have a reconciliation run that shows a non-zero Difference on summary cards or table rows.
Steps
-
Open the results page and identify which card Total/Fully matched/Partially matched/Unmatched shows a non-zero Difference.
You know which group needs investigation. -
Open 'Matched transaction details' for specific rows to inspect individual lines and verify amounts and references.
You can see Books and Customer statement lines and the 'Match basis'. -
Open 'Configure file - Books' and 'Configure file - Customer statement' and verify header rows, Date and Debit/Credit mapping.
Mappings align so net amounts are calculated correctly. Notes show Net amount formula in each modal. -
Ensure the same identifier columns Invoice Ref / Invoice No. / PO No / Doc No are selected as 'Reference / Identifier' in both files.
Identifier selections are consistent across both files. -
Correct any mapping issues and re-run reconciliation to see if the Difference resolves.
Difference should update; if still non-zero, continue investigating unmatched transactions.
Troubleshooting
-
Totals shift sign positive/negative unexpectedly.
LikelyCause: Debit/Credit columns assigned to the wrong dropdown book vs statement interpretation mismatch.
Action: In each Configure modal verify the 'How is the amount represented in this file?' selection and the Debit/Credit dropdown assignments; re-run reconciliation. -
Row-level differences are zero but summary Difference remains non-zero.
LikelyCause: Some transactions are missing from match groups unmatched rows or were not included due to mapping errors.
Action: Review Unmatched and Partially matched tabs, open rows to inspect, and adjust mappings to include identifiers; re-run reconciliation.
Note: Use the 'Matched transaction details' modal to trace amounts back to the source rows for precise troubleshooting.