Questions? We have answers.

Troubleshooting Transaction ID Selection

Article author
Jonathon Plowman-Samson
  • Updated

I can't identify a column that represents the transaction ID

The first step would be to verify if this information is available from your client. If so, obtain an updated general ledger export containing this information.


The first thing to do is to verify if the information is available anywhere that has not already been provided. If you are unable to verify the information, the Data Review stage of the data ingestion wizard 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.


Learn more about the custom running total and how to apply it to your import in our Knowledge Base.



Troubleshooting by data integrity check

Unbalanced or single-sided transactions

Problem: There are a number of reasons why transactions within a general ledger may be unbalanced. For example, entry errors, incomplete data, or weakness in internal controls.


Solution: Use the View Details button 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, and if there is an overall imbalance in your data, cross-check whether this value equates to the individual imbalances identified in your unbalanced multi-entry transactions. If they equal, you acknowledge the imbalance in the data and continue with your 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 a better identifier is available in the data.


Alternative Solution: Another common cause is that 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)

Problem: The transaction ID you have selected is not granular enough, 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.


Solution: Use the View Details button 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

Problem: This could be an indication that unrelated entries have been grouped together under the applied transaction ID.


Solution: Use the View Details button 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, please verify whether you have identified the correct transaction ID or if a moire suitable identifier is available.



Missing Mandatory Information and Ignored Rows

Problem: The selected transaction ID uses data that is not available for all entries within the general ledger. For example, if you use memo as your transaction ID, all line entries with no memo content will be ignored in the analysis. Missing mandatory data could also indicate that certain line entries are missing a required transaction date, account ID, or amount/debit and credit value.


Solution: Use the View Details button on the integrity check to identify which missing information is required for the respective entries to be included in your analysis.


Related Articles:

Share this:

Was this article helpful?



Please sign in to leave a comment.