Xero to Excel

What is Xero to Excel?

Xero to Excel is the workflow of moving accounting data from Xero into Microsoft Excel for reporting, analysis, review, and board-pack preparation. It can be done manually through exports, through general data connectors, or through a native Excel add-in such as XO Report. The important distinction is whether the workbook remains connected after the first pull. A static export gives you data at one point in time. A live workbook can refresh values, tables, and reports when the underlying Xero data changes.

Finance teams still use Excel because it is where budgets, management reports, consolidation schedules, covenant models, cash forecasts, and audit workpapers often live. Xero is the system of record, but Excel is usually the modeling layer. The practical goal is not to replace Xero. It is to bring Xero data into the spreadsheet layer without turning every reporting cycle into a manual export exercise.

A durable setup has three layers. Xero remains the source layer for accounts, contacts, invoices, bills, payments, tracking categories, tax rates, currencies, budgets, and reports. XO Report is the access layer that retrieves those records or values. Excel is the workbook layer where finance users define layouts, checks, mappings, and commentary. Keeping those layers distinct makes the report easier to review and maintain.

With XO Report, the connection starts by installing the Excel add-in and authorizing Xero. The current install path is documented on the XO Report install page, and the first workbook steps are covered in the quick-start guide. Once connected, you can insert formulas, tables, or reports from the task pane. The result is a spreadsheet that keeps the finance logic in Excel while fetching the accounting data from Xero on demand.

Why Excel? The case for spreadsheet-native financial reporting

Excel remains the default finance workspace because it handles unstructured analysis better than most reporting tools. A Xero report is useful for statutory views and standard management summaries, but finance teams often need extra logic around the numbers: allocation rules, custom account groupings, scenario assumptions, rolling forecasts, non-financial drivers, commentary, and variance bridges. Those items rarely fit cleanly inside an accounting system report.

Accountants and advisors also need repeatability. A month-end pack may include a profit and loss, a balance sheet, an aged receivables review, a cash summary, and client-specific working paper tabs. The value is not only the raw data; it is the review structure around the data. For practices serving many clients, a workbook that can be reused and refreshed is more efficient than rebuilding the same model after every export. That is why XO Report has dedicated material for accountants and bookkeepers.

Spreadsheet-native reporting also preserves finance ownership. The person preparing the analysis can see the formulas, reconcile control totals, document adjustments, and tie outputs to source tabs. When a number looks wrong, the review trail is in the workbook. That matters for CFOs, controllers, and external advisors because reporting packs are not only produced; they are reviewed, challenged, explained, and reused. A live Xero-to-Excel workflow keeps that review discipline while removing the lowest-value part of the process: repeated manual data movement.

Excel also handles mixed-source analysis well. A monthly pack may combine Xero actuals with payroll headcount, sales pipeline, bank covenant calculations, board commentary, and forecast assumptions. Those items do not all belong in the accounting system. Pulling Xero into Excel lets the ledger stay clean while the workbook handles the management analysis around it.

The format is also familiar to finance governance. Named ranges, formula auditing, protected sheets, review comments, and versioned board-pack workbooks are already part of many close processes. A reviewer can trace a subtotal from a presentation tab back to a source report, then to a live Xero pull, without learning a new reporting canvas. That reduces adoption friction for teams where the pack is prepared by finance but consumed by executives, directors, auditors, or external advisors.

Manual export vs add-in vs data connectors

There are three common ways to get Xero data into Excel. The simplest is manual export: open Xero, run the report or list, export the file, save it, and paste or link it into a workbook. This can be acceptable for one-off analysis. It becomes fragile for recurring reporting because every period requires the same mechanical steps. If the date range, report option, or source file changes, downstream formulas can break or silently point to stale data.

A general data connector is more automated. It can move data between systems on a schedule and may support many applications, not only Xero. That breadth is useful when the goal is a broad integration pipeline. It is less direct when the problem is finance reporting inside Excel. Connectors often deliver synced datasets rather than finance-specific Excel formulas or report outputs. The user still has to shape the data into the report pack, maintain transformations, and handle accounting-specific choices such as report basis, tracking filters, and account mapping.

A Xero Excel add-in sits closer to the finance workflow. It runs inside Excel and lets the workbook request the data it needs. XO Report supports both formula-based values and table or report insertion from the task pane. That gives you a choice: formulas for specific balances, budget values, and KPIs; tables for lists and transaction detail; reports for structured financial statements. The workbook remains the reporting layer instead of becoming a destination for copied files.

The maintenance work is different for each approach. Manual export depends on file naming, folder discipline, and repeated checks that the correct source file was used. Connectors depend on sync schedules, mappings, and permissions. Add-ins depend on workbook structure: live source tabs, clear control cells, and refresh before review. The best option is the one whose control work fits the team's normal reporting process.

Total cost of ownership usually shows up in review time, not only subscription cost. Manual export looks cheap until a controller spends an hour each month checking filenames, date ranges, pasted columns, and broken links. Connectors reduce some of that effort, but they introduce pipeline administration: who owns the sync, who can change mappings, what happens when credentials expire, and how quickly finance notices a failed run. An add-in keeps the control point in the workbook. The user refreshing the pack can see which tabs are live, which formulas reference which controls, and which outputs need review before the file is circulated.

Governance is the other axis. For a one-off analysis, a static export may be enough because the workbook is not expected to become a recurring reporting asset. For month-end packs, consolidation files, client templates, and rolling dashboards, repeatability matters more. The same workbook should answer the same question next month with updated dates and refreshed source data. XO Report is designed for that pattern: formula cells, inserted tables, and inserted reports can all be part of a documented review flow instead of separate files handled outside the model.

The right option depends on frequency and control. Manual export has the lowest tool cost but the highest recurring manual effort. General connectors suit teams that need cross-application data movement. A dedicated add-in suits teams whose main job is turning Xero numbers into Excel reporting packs. The detailed comparisons are split into focused pages: manual export, data connectors, and the broader buyer guide to Xero Excel add-ins.

• Use manual export for occasional, non-recurring analysis.
• Use a connector when scheduled data sync across many apps is the primary requirement.
• Use an Excel add-in when Xero reporting models need to refresh inside workbooks.

Live formulas: how XO Report works

XO Report exposes Xero data through the XO namespace in Excel. The function library has exactly 11 functions: XO.ORG, XO.COA, XO.CONTACTS, XO.TRACKING, XO.TAXRATES, XO.CURRENCIES, XO.BALANCE, XO.LACCOUNT, XO.LITEM, XO.BUDGET, and XO.PROFIT. Some functions return spilling tables, while others return a single value. The complete reference is maintained in the custom functions documentation.

The first function to understand is XO.ORG. It returns the connected organizations with an Org ID and Org Name. That Org ID becomes the first parameter for most other formulas. This keeps formulas stable even when a workbook covers several Xero organizations. A typical model puts the organization list on a control tab, then references the relevant Org ID from report tabs.

XO.BALANCE returns a single account balance. Its parameters are org_id, account, start_date, end_date, and optional tracking category and option pairs: category1, option1, category2, option2. For profit and loss accounts, the date range defines the period. For balance sheet accounts, the wizard treats the report as an as-of-date request and uses account metadata to guide the date input. Tracking filters allow up to two Xero tracking dimensions when the formula needs department, region, project, or similar cuts.

XO.PROFIT returns net income from the Xero profit and loss report for a date range. Its parameters are org_id, start_date, end_date, and the same optional tracking category and option pairs. It answers a different question from XO.BALANCE. XO.PROFIT gives the bottom line for the period, while XO.BALANCE gives the balance of one account. A dashboard can use both: revenue from XO.BALANCE, total profit from XO.PROFIT, and calculated margin inside Excel.

XO.BUDGET returns the budget amount for a date range using org_id, budget_name, account, start_date, and end_date. That makes variance schedules straightforward: actuals from XO.BALANCE, budget from XO.BUDGET, and variance formulas in the workbook. XO.LACCOUNT and XO.LITEM provide lookups for account and item properties, while list functions such as XO.COA and XO.CONTACTS spill reference data into tables. Date parameters should use cell references containing dates, which avoids regional date-format ambiguity in shared workbooks.

The functions are intentionally narrow. XO.PROFIT does not try to return a full income statement, and XO.BALANCE does not try to replace every Xero report view. They answer specific questions that are useful in spreadsheet models. When the workbook needs complete rows, columns, or report sections, the Tables and Reports mode is the better tool. This keeps formulas readable and avoids using hundreds of cells where one refreshable table is cleaner.

Organization IDs are deliberately cell-reference friendly. A workbook can keep XO.ORG on a setup sheet, use named cells for each entity, and point report tabs to those cells. Changing a model from one connected organization to another should then be a controlled input change, not a hunt through formulas. The same approach works for dates, account codes, tracking categories, and budget names: keep the controls visible, reference them from XO formulas, and let Excel show the dependency chain during review.

Error handling is part of the model design. If an account code is missing, archived, mistyped, or not available from Xero, the formula returns a standard Excel error with a hover message rather than silently substituting a number. That means a report can wrap risky lookups in IFERROR where a fallback is intentional, while leaving control checks strict where a missing account should stop review. For example, a 404-style missing account response should be investigated, not hidden inside a board-pack subtotal.

Refresh behavior differs by output type. Formula cells update when Excel recalculates, while tables and reports are refreshed from the task pane using their stored workbook metadata. Spilling functions such as XO.ORG and XO.COA expand into adjacent cells, so they belong on source or control sheets with enough space around them. Inserted tables behave more like managed source tabs: they refresh in place, preserve supported custom columns to the right, and keep manual analysis on separate sheets safer.

Report types you can build

XO Report supports formula-driven models and task-pane report insertion. The report workflow is useful when you want a structured output rather than individual formula cells. Reports are inserted into Excel with their selected organizations, dates, and options stored in workbook metadata, so they can be refreshed later without rebuilding the setup from scratch.

The core management statement is the Profit & Loss report. It uses a date range and supports comparison periods, tracking filters, cash basis, sign options for costs and expenses, hide-totals behavior, and display modes for comparison output. It is suited to monthly management packs, departmental P&L reporting, and trend analysis where the workbook adds commentary or variance calculations around the Xero output.

In practice, the P&L is usually the recurring cadence report. A finance team may refresh it monthly for board packs, weekly for operating reviews, or by tracking category for departmental accountability. The comparison settings are useful when the workbook needs prior months, quarters, or years beside the current period, while Excel handles the variance formulas, commentary, and charts. The Xero report remains the source; the workbook becomes the review and presentation layer.

The Balance Sheet report is an as-of-date report showing assets, liabilities, and equity. It supports period comparison and tracking filters where Xero allows them. Balance sheet reporting often needs a different review rhythm from P&L reporting: month-end positions, working capital movements, debt schedules, and balance sheet reconciliations usually tie to a specific reporting date rather than a transaction period.

Date handling is a major design choice. Date-range reports such as Profit & Loss and Bank Summary use from/to periods. As-of reports such as Balance Sheet, Trial Balance, Executive Summary, Aged Receivables by Contact, Aged Payables by Contact, and Budget Summary use a single reporting date. XO Report supports smart presets, fixed dates, and cell-referenced dates, so a template can either roll forward automatically or lock to an archival period. That distinction helps prevent a month-end balance sheet from accidentally behaving like a year-to-date activity report.

The Trial Balance report gives account balances as of a selected date. It is useful for audit support, mapping exercises, consolidation bridge files, and control checks against management statements. Xero API limitations mean tracking is not available on trial balance output, so teams that need tracking-filtered analysis usually combine P&L and balance sheet outputs with their own workbook logic.

Trial balance usage is usually more audit-oriented than presentation-oriented. It can support account mapping, opening balance checks, year-end schedules, and tie-outs between the management pack and the underlying ledger. Because it is an as-of-date view, it is well suited to control totals and bridging files. A workbook can use the trial balance as the reconciliation base, then use report tabs or formulas for the more tailored management views.

Treat inserted reports as controlled source tabs. Put summaries, commentary, and variance bridges on separate sheets, then add checks that tie back to the inserted report totals. For example, a P&L summary can tie net income to the source P&L, while a balance sheet review can tie assets, liabilities, and equity to the source balance sheet. This makes refresh results easier to validate.

Receivables review can use the Aged Receivables report, which is an as-of-date aging view by contact. The Xero endpoint requires a selected contact, so it is best for focused customer review rather than a full open-items dump. For budget-vs-actual review, the Budget Variance report combines XO.BUDGET and XO.BALANCE on the same account so the variance can be computed in Excel — the underlying Xero Budget Summary endpoint returns the budget figures only, and XO Report supplies the cell-level pattern that derives the variance. Together, formulas and reports cover the common finance pattern: use Xero for source data, then use Excel for layout, review, calculations, and presentation.

Tutorials: workflow walkthroughs

The pages above cover whatreports to build. The tutorials below are end-to-end walkthroughs of the workflow patterns that make those reports refreshable — from the very first formula through scheduled refresh automation. Each tutorial is intentionally search-first: the entry point is the problem an analyst is trying to solve, not the product feature being demonstrated. Pick the tutorial closest to the question in front of you. The first-report walkthrough builds a complete variance table end-to-end if you are new to live Xero data in Excel. The how-to-export tutorial compares all five ways to get Xero data into Excel side by side if you have used the add-in already and are deciding which method fits a specific report. The scheduled-refresh tutorial covers the three honest patterns for automated workbook refresh (XO Report itself is pull, not push) if your model already works but someone asked "can it refresh overnight?" The cheatsheet rounds out the cluster with a printable reference card for the 11 XO formulas — handy for new team members and for the moments when you cannot remember whether XO.BUDGET needs the budget name as the second argument or the third.

• How to export Xero to Excel — five methods compared, with live formulas walked through end-to-end.
• Live Xero data in Excel — the control-cell pattern: change one input, refresh the whole workbook.
• Scheduled Xero report refresh — realistic patterns for automated workbook refresh (Task Scheduler, Excel for Web, workflow tools).
• Your first Xero report in Excel — beginner walkthrough from install to a working variance table.
• Xero Excel formulas cheatsheet — all 11 XO functions with signatures and examples, plus a free PDF download.

Templates

A good Xero-to-Excel template separates source data, control cells, calculations, and presentation. Keep dates, organization selectors, and key assumptions in visible control areas. Keep Xero tables and reports on dedicated sheets, then reference them from analysis tabs. This makes refresh behavior predictable and reduces the risk that a growing table overwrites manually entered commentary or formulas.

Templates should also make refresh ownership clear. If a pack contains formulas, reports, and transaction tables, note which tabs are live and which tabs are user-maintained. Avoid copy-pasting XO table outputs into another sheet as if they were still connected. A copied output is only a snapshot and will not refresh like the original tracked table.

For combined transaction views, use workbook formulas rather than manual stacking. The documented merge workflow shows how to combine invoices and bills with VSTACK while preserving each source table as a separately refreshable object. The same principle applies to templates generally: let XO Report own the source pulls, and let Excel own the analysis layer that references those pulls.

Avoid templates where live source data and manual decisions sit in the same rows. Source tabs should be replaceable on refresh. Analysis tabs should make it obvious whether a number came from Xero, a workbook formula, or a finance adjustment. This simple separation prevents many month-end review errors.

Multi-org consolidation

Multi-organization reporting is one of the main reasons finance teams move beyond manual export. A single Xero company can be handled with a standard report. A group, advisory practice, or multi-client workbook needs consistent extraction across entities, plus a repeatable way to identify which rows and values came from which organization. XO Report addresses the extraction layer by including Org ID and Org Name in table outputs and by using organization IDs in formulas.

The starting point is XO.ORG, which lists connected organizations. From there, formulas can reference different Org IDs on different rows or tabs. The formula builder can also generate combined list formulas for multiple organizations by stacking outputs and dropping duplicate header rows. In table and report workflows, selected organizations are stored with the output so refreshes know which entities to pull.

Consolidation still needs finance logic. XO Report does not replace chart-of-accounts mapping, intercompany eliminations, ownership calculations, foreign currency translation, or management adjustments. It gives the workbook reliable source pulls so those consolidation steps can be documented and repeated in Excel. For accountants managing multiple clients, this distinction matters: the add-in retrieves the data, while the advisor controls the reporting policy and review process. The accountant workflow is described further on the accountants page; the multi-entity composition pattern in detail is on the Consolidation in Excel guide.

Multi-org templates should avoid mixing source tables and manual analysis on the same worksheet. Place source outputs on dedicated sheets, keep the consolidation bridge on separate tabs, and use clear columns for organization, account, period, and adjustment type. For transaction-level combinations such as invoices and bills, follow the merge workflow so each source table remains refreshable and the combined view stays transparent.

A consolidation model should also separate operational grouping from accounting grouping. Xero tracking categories can support department, region, or project reporting, but group reporting may need separate mappings for statutory entity, management unit, ownership percentage, and elimination category. Keep those mappings visible in Excel and reference the live Xero outputs from them.

Intercompany eliminations are a workbook policy decision, not an extraction feature. XO Report can bring each organization's source accounts, reports, and transactions into one file, but the elimination entries still need clear ownership, evidence, and approval. A practical template keeps elimination inputs on a separate schedule with columns for source entity, counterparty, account, period, reason, preparer, and reviewer. That makes it possible to refresh Xero data without overwriting the finance judgments that sit on top of it.

Currency translation follows the same principle. Xero provides organization-level source data, but group reporting may need a presentation currency, translation rates, and reserve logic that depend on management policy or statutory requirements. Keep those rates and assumptions visible in Excel, then reference the live Xero outputs. Ownership-stake annotations also belong in the workbook: a parent may need 100%, 80%, or equity-accounted views of different entities, and those percentages are user-driven reporting inputs rather than data pulled from Xero. That setup also supports partial consolidation views without changing the source extraction or rebuilding each entity tab.

Comparison summary

For a buyer-intent view, use the full Xero Excel add-ins comparison. This page is a workflow guide, so the summary here is deliberately brief. The main alternatives are manual exports, general data connectors, Scott's Add-ins, and Flex Financial Reporting.

Manual export is the easiest starting point and has no software subscription cost. Its limitation is repeatability: every new period needs another export, another file, and another review for copy-paste or mapping errors. Data connectors are broader. They can sync many applications and may be right when the goal is an integration pipeline, but they usually do not provide accounting-specific Excel formulas.

Scott's Add-ins is the established Xero Excel add-in with a long track record and access to Journals / GL transaction data. Its limitations for this comparison are pricing at higher organization counts and no multi-org data in a single formula. Flex Financial Reporting is a strong Xero app with report-builder strengths, data tables, and Journals / GL access. Its model is less formula-led than XO Report, and its entry price is higher for one-organization users.

XO Report is most relevant when the workbook itself is the reporting model: formulas, source tables, review checks, and management presentation in one Excel file. It is not the right replacement for every connector or every competitor feature, but it is focused on live Xero reporting inside Excel.

Frequently Asked Questions