Glossary
Xero
Xero is a cloud-hosted general ledger — the system where a business's transactions are recorded, bank accounts reconciled, and financial statements produced. For an accounting firm, it holds a client's books, not the firm's own operations; running the firm — staffing, deadlines, billing, the client relationship — is a separate practice-management layer, distinct from Xero Practice Manager, Xero's own separate product for that purpose.
What Xero is and what it is not
Xero is the ledger — the system of record for a client’s transactions, reconciliations and financial statements. It’s a specific instance of cloud accounting: hosted online, with bank feeds that update automatically and access that follows the user rather than one machine.
For a firm, the important line is between what Xero is responsible for and what it is not:
| Xero handles | It does not handle |
|---|---|
| A client’s transactions and ledger | Which staff member is assigned to which client |
| Bank reconciliation | Whether this month’s close is on schedule |
| Financial statement generation | Task deadlines across a client roster |
| The client’s own accounting records | Time tracking, billing, or firm-side capacity |
Everything in that second column is a firm-operations question, and it does not disappear because the ledger is good software — it lives in a different layer entirely.
Xero versus Xero Practice Manager — the distinction that matters
Because both products carry the Xero name, it’s easy to assume they’re the same tool wearing two hats. They aren’t. Xero is the general ledger described above — client books, financial statements, reconciliation. Xero Practice Manager (XPM) is a separate product built for a different job entirely: running the firm’s own operations — job tracking, staff timesheets, billing the firm’s clients for the firm’s own services. A firm can run every client’s books in Xero and still choose a completely different practice-management platform for the firm side of the work, and many do, because the two decisions — which ledger a client’s books live in, and which system runs the firm around those books — are independent choices.
Where a firm’s own operations layer comes in
A firm serving clients on Xero needs a layer above the ledger to coordinate the recurring work across a whole client roster: whose books are due, who’s assigned, what’s overdue. That’s workflow automation and, more broadly, practice management software — purpose-built for the firm’s internal operations rather than for a client’s accounting records.
Whichever practice-management tool a firm chooses, the connection to the ledger is what determines whether the firm re-enters client data by hand or not. See the Xero + Uku integration for how that connection is meant to work: Xero stays the system of record for the numbers, and the practice layer stays in sync with the client list without duplicate entry.
Why this matters more at volume
A single business on Xero only has to manage its own books. A firm running dozens or hundreds of clients on Xero has a different problem: keeping every one of those separate ledgers moving on schedule, which is a coordination problem the ledger was never built to solve. Firms delivering outsourced bookkeeping feel this most directly — the service is the recurring monthly cycle repeated across every client, and the firm needs its own cross-client view to know whether that cycle is actually running on time.
Serving clients on more than one ledger
Most firms don’t get to standardize every client onto one ledger — clients arrive already on whichever software they chose. A firm also serving clients on QuickBooks Online needs its internal workflow to look identical regardless of which ledger a given client’s books sit in, which is the practical reason many firms pick practice-management software that connects to both rather than committing to a single vendor’s ecosystem for the firm-side tooling as well.
What onboarding a Xero client actually involves
Connecting a client’s Xero file is a software step; onboarding the client is a firm-process step, and the two get conflated more often than they should. Access has to be granted at the right level, an engagement letter signed, a recurring cycle scheduled, and the client given a route to send documents and ask questions — none of which Xero itself handles. Firms that treat the ledger connection as the whole of onboarding tend to find the gap later, when a client has a question nobody was assigned to answer. A repeatable client onboarding checklist is what keeps the ledger connection from being the only step that actually happened.
The firm’s view versus the client’s view
Xero is scoped to a single company’s books, which is the right scope for the business owner using it directly. A firm serving that client needs a second, wider view: not just this client’s ledger, but where this client sits relative to everyone else on the roster — whose close is late, whose invoice is overdue, whose engagement is coming up for renewal. That cross-client view is what a practice-management layer adds on top of the ledger connection — neither Xero nor Xero Practice Manager alone was built to answer “how is the whole firm doing this month,” because both are scoped to a narrower question than that.
How Uku handles xero
Last updated September 19, 2026 Reviewed by Rain Allikvee
