Previous step: How to combine Connectorly data
When working with multiple Xero Organisations, a deduplicated super-set of Account Codes is created so that you can aggregate financial data across multiple Xero's.
The Account Names for the de-duplicated codes are taken from the Master Xero connection unless a Code doesn't exist in the Master connection's Chart of Accounts. In this case, the first Account Name found for the given Code is taken.
You don't need the Master Xero connection to include all of the Account Codes and Names across all Xero's in the group, but you do need to be consistent about any that overlap.
If your Account Names and Codes are not consistent across grouped connections it can lead to confusion.
Same Account Code, Different Account Names
Xero | Code | Name | July Sales |
A (Master) | 200 | West Coast Sales | 50,000 |
B | 200 | East Coast Sales | 20,000 |
When reporting across combined data, West Coast Sales will show as 70,000 for July and there be no value for East Coast Sales at all. To fix, change the Account Code in Xero B to something other than 200, eg 201.
After the fix, July sales will show as 50,000 for West Coast Sales and 20,000 for East Coast Sales.
Different Account Code, Same Account Names
Xero | Code | Name | July Sales |
A (Master) | 200 | North Sales | 40,000 |
B | 201 | North Sales | 50,000 |
When reporting across combined data, West Coast Sales will show as two separate entries for July, one for 40,000 and one for 50,000. To fix, change the Account Code in Xero B to 200.
After the fix, July sales will show as 90,000 for North Sales.
Best Practice
Using the same Chart of Accounts across different Xero Organisations means that it is possible to directly compare different Organisations, for example across types of Sales, or aggregate financial information across them.
In this way, a single Microsoft Power BI report can be used across multiple organisations, to help deliver financial insight and value at scale.