Operational Data Consolidation | BrizoConsol Documentation

What this article covers: How operational data held by individual entities is read together at group level — which datasets a group can see, how datasets from several entities are combined in dashboards, custom reports and operational reports, how values are translated into the group’s currency, and the datasets written automatically from connected accounting systems.

1. Which Datasets a Group Reads

Every dataset belongs to the entity that created it, and its values are in that entity’s currency.

Viewing from Datasets read

A consolidated entity Its own datasets and those of every other entity in the subscription

Any other entity Only its own datasets

A subsidiary’s dataset is read-only from the parent: edit, upload and delete are only available on the entity that owns it. See Operational Data.

2. Datasets Written from Accounting Systems

When a connector’s profit and loss by dimension is switched on, each entity also receives operational datasets written from it every month that is loaded.

Dataset Dimensions

Xero Tracking: <category> Tracking Option, P&L Line — one per tracking category

QuickBooks: Class Class, P&L Line

Zoho Tag: <tag> Reporting Tag Option, P&L Line — one per reporting tag

MYOB: Job Job, P&L Line

MYOB: Category Category, P&L Line

Behaviour Detail

Read-only Operational Data shows Written from the connected accounting system · rebuilt each month it is loaded. Edit, upload and delete are not offered.

Rebuilt by month Each load replaces the whole month, so a reload never leaves two figures for one row.

Scenario and currency Always Actual. Set to Average rate translation, except on the Standard edition.

Accounts A line is tied to the entity’s account where exactly one account matches it. Headings and subtotals carry no account. This is what the ledger validation on the Operational Data screen uses.

Removed on disconnect The datasets are deleted with the rest of the connector’s data when the connection is removed.

Setup for each connector: Xero Tracking Categories, QuickBooks Classes, Zoho Books Reporting Tags and MYOB Jobs & Categories.

3. Combining Datasets in Dashboards & Custom Reports

On a consolidated entity, datasets in different entities are offered as one data source when they share all of the following:

Must match Note

Name Case is ignored

Dimension labels The same labels in the same order

Scenario setting The same dataset-level scenario, or both taking the scenario from the file

Account setting No account, one account for the dataset, or an Account column

The source then reads every entity that holds it. In a custom report row, Include Entities lists those entities — untick one to read the rest. If one entity holds two matching datasets, only the most recently created one is read, so its figures are not counted twice.

A dataset written from an accounting system is offered one P&L line at a time: grouped by option, you choose the line; grouped by line, you choose the option. Lines are never added to each other.

4. Combining Datasets in Operational Reports

Each card in the Reports page’s Operational Data section is one source. A source combines datasets differently from dashboards:

Source Report

QuickBooks: Class One report covering every QuickBooks entity the group reads

MYOB: Job, MYOB: Category One report each, covering every MYOB entity the group reads

Xero Tracking, Zoho Tag One report per entity’s category or tag, because Xero and Zoho give each category or tag an ID unique to its organisation. The owning entity is named on the card.

Uploaded datasets One report per dataset

When a report covers several entities, the header shows the number of entities and Entity is available as a field to place on an axis or filter. See Operational Reports.

5. Currency Translation

When a group reads another entity’s dataset, each row is converted from the owning entity’s currency into the reader’s currency on its own — using that row’s month, scenario and the dataset’s translation setting — before any total is built.

Translation setting Rate used

No translation Values are read as uploaded — use for counts, units and other non-money measures

Average rate The month’s average rate

Closing rate The month’s closing rate

Currency translation is not included in the Standard edition; there, values are read as uploaded. Values are also read unchanged when both entities use the same currency.

⚠ Missing rate? If the group has no rate for a currency in a month, that month’s values are read untranslated rather than left blank. Check the rates under Exchange Rates before relying on a group total.

🌟 Tips for consolidating operational data

Give a dataset the same name and dimension labels in every entity so a group reads it as one source
Keep option and line names identical across entities — values only fall on the same row when the text matches
Set money datasets to Average rate or Closing rate; leave counts as No translation
Use Entity on an axis in an operational report to reconcile a group figure to each entity