intercompany report that ties to the trial balance

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that creating an intercompany report that ties to the trial balance can be a complex process, especially when dealing with historical data and intercompany transactions. Here are some key points that were discussed: 1. For intercompany AP and AR, it was suggested to create adjacent accounts that could store GL movements without a customer or vendor and load all the historic movements to that. Then, before going live, journal them out to the P&L and create the proper transactions hitting the P&L account. Any leftover amount in that account gets coded to unrealised gain/loss, and then re-run your revals to get back to the correct opening balance in your balance sheet. 2. For consolidated trial balance report, one user suggested running the Income Statement page and setting the column to subsidiary, and doing the same for Balance Sheet. This seemed to satisfy auditors as it showed each subsidiary's currency. 3. For historical intercompany transactions, it was suggested to post all the individual intercompany transactions as intercompany JE, so that payments can be applied when necessary and only those OPEN intercompany transactions will be automatically eliminated moving forward. 4. For finalized TB per subsidiary that includes intercompany transactions, it was mentioned that they don't need eliminating at the consolidated level because the HTB is already finalized, i.e., it represents results after elimination has been completed. 5. For open intercompany balances as of the cutoff date, they should be marked as Eliminate. 6. If you encounter an error like "Elimination settings for the journal line, account and name do not match", it was suggested to create separate AICJE for those intercompany ARs and APs, and populate the Name and Due To/From Subsidiary fields. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******