Overview
Accounts (aka Ledgers) classify all financial transaction records; Budgets, Bank Transactions, Invoices, Journals, Payments and so on.
Working with grouped Xero Organisations
When working with multiple Xero Organisations, a deduplicated set of Account Codes is created. Learn how to combine connections to group the data here.
The Account Names for deduplicated 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.
If your Account Names and Codes are not consistent across grouped connections this 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.
Data Dictionary
Field | Type | Notes |
Account Code | Text | The identifier for an Account e.g. 200. If this is empty (eg often the case for Bank Accounts) then the Xero Account ID is substituted here to avoid empty Codes. When multiple Xero Organisations are grouped, then the details of an account are taken from the master connection (the connection that the others are grouped under). |
Account Name | Text | The Account Name. e.g. Sales |
Add To Watchlist | Boolean | True if Add To Watchlist is set. |
Bank Account Number | Text | The Bank Account Number if this account is for a Bank Account. |
Bank Account Type | Text | e.g. {'', 'BANK', 'CREDITCARD', 'PAYPAL'} |
Class | Text | {'ASSET', 'EQUITY', 'EXPENSE', 'LIABILITY', 'REVENUE'} |
Class Sort Order | Integer | The sort order for Class. If you create your own Microsoft Power BI template, ensure that Class is sorted by Class Sort Order. |
Connection Name | Text | The name of the Connection. Typically the name of the Xero Organisation. |
Currency Code | Text | ISO 3 letter Currency Code for the Account. |
Data current as of | Datetime | When the Data was taken from Xero. |
Debit or Credit | Text | Debit or Credit |
Enable Payments To Account | Boolean | True if it is possible to make payments against this account. |
Has Attachments | Boolean | True if the account has attachments. |
Last Updated | Datetime | When the Account was last changed/created. |
Show In Expense Claims | Boolean | True if this is set to show in expense claims. |
Status | Text | {'ACTIVE', 'DELETED'} |
Tax Type | Text | The Tax Type associated with the Tax Amount. E.g. One of (in the UK) {'ECZROUTPUTSERVICES', 'EXEMPTINPUT', 'EXEMPTOUTPUT', 'INPUT2', 'NONE', 'OUTPUT2', 'ZERORATEDOUTPUT'} |
Type | Text | one of {'BANK', 'CURRENT', 'CURRLIAB', 'DIRECTCOSTS', 'EQUITY', 'EXPENSE', 'FIXED', 'LIABILITY', 'OTHERINCOME', 'OVERHEADS', 'PREPAYMENT', 'REVENUE', 'SALES', 'TERMLIAB'} |
Type Sort Order | Integer | The sort order for Type. If you create your own Microsoft Power BI template, ensure that Type is sorted by Type Sort Order. |