By using this website, you agree to our Terms of Use (click here)
Watching this video:ย
Does this mean that the purpose of Consolidations is to import data from your subsidiaries into a reporting Ledger in your parent company, but that reporting Ledger won't give you the complete consolidated position because Actuals in your parent company isn't included in the reporting Ledger?
In other words, you still need to build a report to combine Actuals in Parent with all imported subsidiary data?ย
And where do eliminations enter the equation?
And if your CofA aligns between your parent and subsidiary, do you still need to assign the Consolidation Account on the CofA in your subsidiary? Same questions also applies for Segment Values. I would hope that if you didn't setup a mapping, it just uses the original source value.
I am not able to import any data from subsidiary - it completes with no message and no Transaction to release.ย
I can answer all of these questions myself now.ย 😀ย
I will do so if anyone is interested in Consolidations. The help documentation on this topic isn't much help.ย
Yes please!
Thanks for sharing this info Royce
I think you would just define the Account mapping in an Excel table in order to use Velixo Reports for consolidations.
Still don't see how it adds any value over something like Power BI. It's an excel reporting tool. Reminds me of nVision from my PeopleSoft days. ๐
The trick with consolidations is combining data from Tenants with different financial calendars and also eliminating inter-company purchases and sales when the data is consolidated (but not eliminating when viewing data for a single Tenant).ย
I am solving these within Power BI, but the calendars is the most challenging because i need to calculate ending balances (YTD) for one Tenant to align it to the other Tenant's calendar.ย
So to sum up, with consolidations, the data model is the hard part, not the reporting tool ๐
For the YTD across multiple calendars, it sounds like you get to have some fun with DAX ๐
