Introduction
During an import, the ZoneReconcile SuiteApp offers the option to match automatically against unreconciled transactions. The matching algorithm that is used, can be defined for each bank account configuration individually. When the matching rate isn’t as expected, the first step is to start identifying why this happens. The matching logic works with a fixed logic and due to this is often easy to identify why the system wasn’t able to identify the expected transaction. We recommend in this situation to start with creating a document where mismatches are recorded with detailed information on why it did not match. After a certain period, this document should give insides in which situations are most often encountered, and based on this information a next enhancement step can be taken.
Creating insights
The first step is to identify the mismatches and see why the mismatch happened. After a fixed period of monitoring the most common situation can be identified and from there it is possible to investigate if there is a potential way to enhance the matching. For recording this information we suggest creating a document with the following layout:
| Statement ID/Link | Line Number | Reasons Why It Didn't Match | Reasons Why it Did Select an Incorrect Transaction |
| Example ID 1 | 12 | Invoice number prefix was not present in the bank description | |
| Example ID 4 | 5 | Invoice number was only the last 5 digits | |
| Example ID 6 | 3 | Incorrect amount was paid | |
| Etc. | Etc. | Etc. | Etc. |