Skip to main content
Setting Up Multi-Entity Consolidation

Telemetry supports the consolidation of multiple ERP instances into one reporting suite.

Michael Rodriguez avatar
Written by Michael Rodriguez
Updated over 5 months ago

Telemetry supports the consolidation of multiple ERP instances into one reporting suite. For example, if you operate a parent and a sub, manage multiple real estate properties, are consolidating after an M&A transaction, or perhaps a private equity roll-up, you can now easily merge them together.

Consolidation works across any of Telemtry’s integrated ERP types. You can consolidate any combination of QuickBooks Online, QuickBooks Desktop, Xero and NetSuite instances together into one.

To add additional ERP entities

  • Head to Settings > Integrations.

  • Click Add an Integration, and choose ERP Software.

  • Select the new instance type and follow the same connection process as normal.

Note that you are prompted to give the new instance a name. This way you can distinguish data amongst your different ERPs elsewhere in the platform. It also may be a good idea to rename your original ERP for the same reason. Once the data from your new ERP finishes downloading, you'll immediately be able to see the history from each system individually and combined.

To create a multi-entity custom plan in Excel

  1. Simply lay out your statements in Excel as you'd like to present them with your preferred line item labels, structure, and forward-looking projections.

  2. In the next step, you tell Telemetry how your chart of accounts for each of your connected ERPs fits inside of this structure.

  3. Once you publish, you'll find your consolidated financial statements available into Telemetry looking just as you selected. This works across the P&L, balance sheet, and cash flow statement.

Once completed, note all of Telemetry's great data discovery features like drill down, variance, customer, and supplier reporting has been enhanced so that you can see the full detail that makes up your numbers appropriately segmented so you know from which entity it is sourced.

Did this answer your question?