List all the reasons the following error could occur when doing a CSV import of Journal Entries: Invalid account reference key 123 for subsidiary 456 I already checked the field mappings in the CSV import template: They match the data in the CSV file being imported. The Account is associated with the Subsidiary (by root subsidiary including children), and both the child subsidiary it's associated to and the Account are active. So we can say that it is not an incorrect Name reference, it is not an invalid or incorrect subsidiary/account association. What permissions does the role of the person who is performing the CSV import need to have?

AI generated answer (using internal Slack threads):

The error "Invalid account reference key 123 for subsidiary 456" during a CSV import of Journal Entries could occur due to several reasons: 1. Incorrect Internal ID: The error message indicates that the system is unable to find the account with the internal ID 123 associated with the subsidiary with the internal ID 456. Ensure that the internal IDs used in the CSV file are correct. 2. Inactive Account or Subsidiary: The account or subsidiary might be inactive. Even though you mentioned that both the account and subsidiary are active, it's worth double-checking. 3. Access/Permissions: The role of the person performing the CSV import might not have the necessary permissions to access the account or subsidiary. The role should have 'Full' level permission for 'Lists -> Accounts' and 'Lists -> Subsidiaries'. Also, the role should have 'Create', 'Edit', and 'Full' level permissions for 'Transactions -> Make Journal Entries'. 4. Incorrect CSV Format: There might be an issue with the CSV file format or the way the data is structured. Ensure that the CSV file is properly formatted and the data is correctly mapped. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******