Product documentation
The reconciliation process is a combination of logic and assumptions. Sometimes, the logic or assumption is clearly wrong, and it needs to be fixed. Those situations are relatively easy: it is an improvement to everybody, and the fix can go into the mainstream solution.
In other cases, the improvement is not as clear cut. Customers that have been using software for a while have gotten used to the behaviour, even if it might not have been doing what they expected it to do in the beginning. But they grew into it, and might even have started exploiting some of the quirks. In those cases, a change in logic of assumptions could impact them negatively. And we want to avoid that.
When reviewing the original code of the Reconcilition function, we stumbled upon a couple of these situations. And because we did not want to impact existing customers, but still wanted to provide an even better experience to new customers, we introduced an alternative reconciliation function. We called it Reconciliation V2, and it can be activated in the Bank Reconciliation parameters. If the parameter is set to 'Yes', and users click the reconcile button in their general journals, this new reconcilition function is used. And not the original one.
In the original reconciliation (v1) a line was marked 'Orange' if multiple invoices were found.
In V2, a line is marked 'Orange' when the system can not find any open invoice for the given payment note, but can find an open invoice, using the amount paid and the customer.
Possibility to use the Trace logger for Reconciliation.
The class structure has been refactored, to have a cleaner implementation, and allow for extension points.