
Hey Cedric,
Your idea of dumping incremental monthly trial balances into "dummy" BC companies for consolidation can work, but there are trade-offs. Let’s break it down:
Quick & Simple – If you just need financial consolidation and don’t want to overhaul systems right now, this is a fast way to bring numbers together.
Minimal Disruption – You’re not forcing legacy systems into BC, just pulling in high-level financials.
Works Well for Financial Reporting – If your main goal is consolidated P&L, balance sheets, and cash flow, this method does the job.
Intercompany Transactions – Since transactions happen outside BC, manually eliminating intercompany activity could be a pain. If two entities trade but only one reports in BC, balancing things might take extra effort.
No Granular Data – You won’t get customer/vendor insights at the group level because the “dummy” TB companies only have summary numbers. If you need deep financial analysis (e.g., margins by customer, product trends), this method won’t be enough.
Scalability – Doing this manually month after month could become tedious. If the group expands, maintaining it will be a headache.
For Now: What you're doing is fine if it's just about high-level financials. Power BI can still help with dashboards, but it won’t be a complete picture. You can import the dummy TB data into Power BI and blend it with inventory insights from your Dynamics-based application.
Long-Term: The API route from OEM software to BC is definitely better. It would automate things, allow deeper analysis, and reduce errors.
If you're open to a middle-ground solution, maybe Power Automate or an ETL tool (like Azure Data Factory or Power Query) could help automate the TB imports rather than doing it manually.
Regards,
Dr. Gomathi S