Learn what to do when you encounter issues while selecting the transaction ID from the data.
I can not identify a column that represents the transaction ID
First, verify that this information is available. If so, obtain an updated general ledger export containing this information.
If you are unable to verify the information, the Data Review step of the import process can be used to test the data integrity of different transaction ID options. MindBridge will, most often, recommend a transaction ID based on the imported data.
The goal here is to have most transactions comprised of 2-4 entries with no single entry transactions. Your selected transaction ID should pass the six integrity checks on the page.
Alternatively, consider applying a custom running total on different column arrangements to create a suitable transaction ID. This requires an understanding of how the transactions have been recorded to know the order in which your data columns should be sorted.
Troubleshooting by data integrity check
Unbalanced or single-sided transactions
There are a number of reasons why transactions within a general ledger may be unbalanced, such as entry errors, incomplete data, or weakness in internal controls.
- Select View Details on the integrity check to display which transactions are unbalanced using the selected transaction ID.
- Check whether the overall balance of debits and credits sums to zero ("0").
- If there is an overall imbalance in your data, cross-check whether this is due to these unbalanced transactions. If the entire ledger is unbalanced solely due to these unbalanced transactions, you can acknowledge the imbalance in the data and continue with the import.
- If the overall balance sums to zero, you have likely selected a transaction ID that is grouping unrelated entries, thus resulting in individual transactional imbalances. Ensure you have identified the correct transaction ID or if there is a better identifier available in the data.
Some financial ERPs do not automatically export entries from all general ledger accounts, while others may incorporate opening and closing balances as entries.
Ensure you have enabled the export of all general ledger accounts as well as removed export of opening and closing balances.
Large multi-entry transactions (with >1000 entries)
The transaction ID you have selected is not granular enough, and is thus grouping batches of unrelated entries together in single transactions. Although the large transaction may balance to zero, this situation is not ideal because large transactions do not allow for a high level of fidelity when it comes to performing a risk analysis.
Select View Details on the integrity check and verify whether the large transaction is acceptable or not (for example, payroll vs. batch transactions).
If the large transactions are not expected, consider running the Smart Splitter.
Transactions with multiple effective dates
This could be an indication that unrelated entries have been grouped together under the applied transaction ID.
- Select View Details on the integrity check to identify which transactions occur over multiple dates.
- Check the related entries in the raw data to confirm whether related entries over multiple dates have been recorded.
If this is not the case, verify whether you have identified the correct transaction ID or if a more suitable identifier is available.
Missing mandatory information and ignored rows
Rows have been found where the selected transaction ID uses fields where all values are blank. This will result in those rows being ignored in the analysis. However, if you have joined multiple columns, and not all values in any given row are blank, that is acceptable.
Missing mandatory data could also indicate that certain line entries are missing a required transaction date, account ID, or amount/debit and credit value.
Select View Details on the integrity check and identify which missing information is required for the respective entries to be included in your analysis.