Improve Bank Reconciliation Matching Using Due Dates and Flexible Date Windows
Xero should consider the later of the transaction date or payment due date when suggesting bank reconciliation matches, and allow users to specify a wider matching window.
Currently, Hubdoc correctly extracts both dates, but Xero relies on the transaction date for matching. This creates problems with recurring bills such as mortgages, utilities, and subscriptions, where statements are issued weeks before payment.
Example:
- Statement date: October 9
- Payment due date: November 1
- Actual ACH payment: November 1
Xero looks for a payment around October 9 rather than November 1, often failing to suggest the correct match.
Proposed solution:
1. Consider both the transaction date and due date, prioritizing whichever is closest to the actual bank transaction.
2. Allow users to configure a matching window (e.g., ±7, 15, or 30 days) to accommodate billing cycles and payment processing delays.
3. Improve matching based on payment amounts and payee information, not just dates.
Comparison to QuickBooks Online:
QuickBooks Online offers more flexible transaction-matching functionality, including searching for matches across a broader date range. Xero would benefit from similar flexibility.
This would eliminate unnecessary manual date changes, preserve accurate accounting records, and make Hubdoc's automatic publishing and Xero's reconciliation far more useful for businesses with recurring expenses.
Thanks for submitting your idea on Xero Product Ideas. We appreciate you taking time to let us know how we could improve Xero for you.
Your feedback will soon be reviewed by our Community team, and in the meantime this can begin to build support with votes from other community members.
If you're interested to see recent releases or get a pulse on what's coming soon see The Long and Short of it. 🙂
-
Geoffrey Billingsley
commented
It looks like auto-reconciliation is a hot topic, and this bug would always prevent me from being able to use it as it would most likely match the statement to the wrong transaction.