Why are transactions unmatched even though reference IDs look identical?

Short Answer: Common causes: wrong 'Reference / Identifier' mapping, incorrect 'Header row' or 'Sheet', differing amount fields or sign differences, or records excluded by 'Records to include' rules.

PreRequisites

1. You have run reconciliation and observed Unmatched results

Steps

1. Open 'View format' for each report and confirm the same 'Reference / Identifier' column is selected e.g., 'shipment_id' vs 'order_release_id'.
   Both reports use the same ID token for matching.

2. Verify 'Sheet' and 'Header row' so the preview rows align with your file headers.
   Preview displays correct columns under the mapped tokens.

3. Confirm the 'Amount' mapping is the correct column and that signs negative/positive are consistent for returns vs sales.
   Amounts show expected sign and values in preview.

4. Ensure 'Include all records' is ON if you expect every row to be considered.
   Rows are no longer excluded as 'Excluded by rule'.

5. Re-run reconciliation and inspect the 'Unmatched' tab or open a given row's 'Matched transaction details' for exact values.
   You can see why rows did or did not match.

Troubleshooting

1. IDs look identical but transactions stay unmatched.
   LikelyCause: ID column chosen differs between reports, or IDs contain whitespace/case differences.
   Action: Select the exact same 'Reference / Identifier' token for both reports and clean the source ID values by trimming whitespace and normalizing case before uploading.

2. Amounts close but don't match exactly.
   LikelyCause: Rounding, tax fields or different amount columns used.
   Action: Use the same 'Amount' field across reports and inspect 'Matched transaction details' to find which rows cause the discrepancy.

Note: Use the 'Data preview (sample rows)' in 'View format' to compare how each file presents IDs and amounts before running reconciliation.