Connectorly uses two complementary layers of automated validation to help ensure that financial and budget data remains consistent with Xero:

Together, these controls help identify unexpected differences in values, missing records and unintended changes to the reporting model.

These processes form part of Connectorly’s internal data-quality framework.

Connectorly retrieves Xero’s monthly Profit and Loss and Balance Sheet reports for the latest 12 months of available data. It also retrieves relevant budget information supplied by Xero.

Separately, Connectorly retrieves the underlying journal transactions and monthly budget entries, which are the transaction-level records that you use when building reports with Connectorly reports and support fine-grained reporting.

We then use these detail-level records to independently reconstruct the corresponding monthly financial and budget results.

These independently calculated values are then compared with Xero’s own outputs. This is performed systematically by Xero Organisation, Account and Month rather than through manual sampling.

For each Xero organisation, the automated process:

This process helps detect differences in calculated values as well as expected data that may be missing.

These systematic reconciliations and audit results are calculated every time your data changes and the results are available as tables in Microsoft Power BI.

For the Profit and Loss reconciliation, Connectorly independently aggregates the underlying Xero journal lines for each account and calendar month.

It then compares the calculated monthly result with the corresponding account value shown in Xero’s Profit and Loss report.

The comparison includes:

A full outer comparison is used during matching. This means the process can identify not only differences in value, but also accounts or periods that appear in one dataset and are absent from the other.

The Profit and Loss reconciliation results are available in the xero.profit_and_loss_audit table in Microsoft Power BI.

Balance Sheet reporting requires a different calculation from monthly Profit and Loss reporting because account balances are cumulative.

Connectorly aggregates the underlying journal data and calculates the balance for each account as at the end of every reporting month. It then compares that independently calculated balance with the corresponding account value shown in Xero’s Balance Sheet report.

Like the Profit and Loss reconciliation, the comparison is performed by Xero Organisation, Account and Month. The resulting audit information shows the Xero value, the Connectorly-calculated value and any monetary or percentage difference.

This helps validate that the journal-based reporting model produces balances consistent with Xero’s month-end financial statements.

The Balance Sheet reconciliation results are available in the xero.balance_sheet_audit table in Microsoft Power BI.

Connectorly applies the same independent-reconstruction principle to Xero budget data.

Again, like the Profit and Loss reconciliation, the comparison is performed by Xero Organisation, Account and Month. The calculated amount is then compared with the corresponding monthly budget value obtained from Xero.

The reconciliation records the Connectorly-calculated budget amount, the Xero budget amount, the monetary variance and the percentage variance.

As with the Profit and Loss reconciliation, a full outer comparison is used. This allows the process to identify both differences in value and budget records that are unexpectedly missing from either side.

The Budget reconciliation results are available in the xero.budget_audit table in Microsoft Power BI.

The three audit views, xero.profit_and_loss_audit, xero.balance_sheet_audit and xero.budget_audit are available in your dedicated Connectorly database.

You can query these views in Power BI in the same way that you can query all the other financial information.

For each audit type, the information includes:

Any unexplained difference can therefore be reviewed at account and reporting-period level rather than only as a difference in a report total.

In addition to live production reconciliation, Connectorly runs an automated test suite as part of its development and release process.

Before a release, regression and consistency tests are run across representative customer configurations and financial-data scenarios.

The tests cover areas including:

The tests use multiple representative builds and configurations rather than relying on one generic dataset. This helps identify problems that may occur only with particular reporting currencies, account structures or customer-specific configurations.

For example, the test suite queries the Profit and Loss and Balance Sheet audit outputs and fails when unexplained differences are detected. It also performs broader consistency checks across calculated balances and other derived financial values.

Connectorly retains the results of each automated test execution.

The retained information includes:

This history makes it possible to compare current test results with earlier successful executions. It also helps identify when a previously passing calculation or configuration begins to fail following a software or data-model change.

When investigating a failure, the development team can review it in the context of the relevant configuration and earlier test results rather than treating it as an isolated event.

The audit views and automated tests expose differences at the most relevant available level, such as company, account, month and budget.

This information allows Connectorly to investigate whether a difference is caused by:

Not every difference necessarily represents a Connectorly error. The purpose of the reconciliation is to make differences visible and provide sufficient detail for investigation.

Production reconciliation supports ongoing operational oversight, while pre-release testing is intended to identify unintended changes before deployment.

No. Connectorly performs systematic comparisons using the underlying Xero data and the corresponding Xero financial or budget outputs. Manual investigation may follow when an unexplained difference is identified.

The automated financial-report reconciliation selects the latest 12 months of available monthly Xero reporting data for each connection.

The current process covers monthly Profit and Loss reports, month-end Balance Sheet reports and budget data obtained from Xero.

Yes. Customers can query the relevant audit views in their dedicated Connectorly database using their read-only database user:

No. A difference may result from missing source data, reporting configuration, currency treatment, unusual records, timing or a difference between Xero’s underlying records and report output. The audit information provides the detail required to investigate the cause.

No. These are internal automated reconciliation and testing controls operated by Connectorly. They do not represent an independent audit, formal certification or external assurance opinion.

Connectorly uses two complementary control layers to support dependable Xero reporting:

Together, these processes help identify unexpected differences, missing data and unintended changes at a detailed account and reporting-period level.

If you have questions about a reconciliation result in your database, contact Connectorly support and include the Xero connection, account code, reporting period and relevant audit view.

Related article: Why Connectorly FX values may differ from Xero

Related guide: Xero Data Validation in Power BI: How Connectorly Checks Accuracy