Daily Copy
Coverage is defined per platform and per object group. The supported object list for a given organisation is confirmed in writing before a trial run, and every dated run reports the same list back.
This statement is dated because coverage changes when a source platform changes. When it changes, the statement is reviewed and the date above moves.
Object groups
A run report is organised by object group. Each group has a state, and each state below is stated explicitly rather than implied.
No object group carries the first state on this page today, because no per-platform matrix is published yet. The two tables below give every row its current state.
| Object group | What a run reports for this group | State |
|---|---|---|
| Accounts | The account structure the run read. The count is one per account record. | Not yet published |
| Transactions | Dated ledger entries. The count is one per record written in the run. | Not yet published |
| Contacts | Customer and supplier records. The count is one per record written in the run. | Not yet published |
| Attachments | Files held against records. The count is read as files copied against files the source reported, so a shortfall appears as an exception. | Not yet published |
Every row below is not copied. None of it belongs to an object group a run report uses, so no run produces a count for it and no exception is raised against it.
| Record type | Why it sits outside a run | State |
|---|---|---|
| Payroll | Payroll sits outside the ledger object groups a run report uses, so a run does not read it. | Not copied |
| Bank feeds | A bank feed is a live connection held by the source platform, not a ledger record the run can copy. | Not copied |
| Users and permissions | Who can sign in to the source platform, and what they can do there, stays at the source. | Not copied |
| Report layouts | A run copies records. Saved report customisations and views are rendering settings, not records. | Not copied |
| Connected apps | A run reads the authorised organisation at the source platform and nothing held outside it. | Not copied |
Per-platform coverage
Coverage is defined per platform, because each platform exposes a different set of objects. Two platforms are in scope: QuickBooks Online and Xero.
A public coverage matrix for QuickBooks Online is not published. The supported object list for your organisation is confirmed in writing before a trial run, and each dated run then reports that same list with counts and exceptions.
A public coverage matrix for Xero is not published. The supported object list for your organisation is confirmed in writing before a trial run, and each dated run then reports that same list with counts and exceptions.
How this section changes A matrix is published for a platform once the supported object list and the tested export boundary for that platform are settled. Until then this section says so, rather than describing coverage that is not fixed.
The boundary
Copying a record means one thing. LedgerCopy holds an independent, dated copy of that record, written to storage outside the platform that produced it, and the run report states the group it belongs to and the count it was part of.
It does not mean an export of that record has been tested. It does not mean the record can be returned to QuickBooks Online or Xero. LedgerCopy does not write to a source platform, so nothing on this site describes a route back into one.
Export and recovery routes are listed on this page per platform, and only where they have been tested end to end. If no route is listed for a platform, no route is tested. Treat the absence of a listing as the answer, not as an omission.
Current state No export or recovery route is listed for QuickBooks Online or for Xero. A trial run produces an inspectable copy and a dated run report. It does not produce a tested export.
If that boundary matters to how your team plans continuity or review work, the next step is a scoping conversation. A trial request records your source platform and object scope, and the reply states what is supported for your organisation.
Request a trialLimits
Fit
Four situations where LedgerCopy is the wrong tool. Reading them now is cheaper than finding out during a trial.
Common questions
A run copies records that belong to a supported object group and writes them to storage independent of the source platform. The object groups a run report uses are accounts, transactions, contacts, and attachments. Which of those groups are supported for your organisation is source-dependent, and the supported list is confirmed in writing before a trial run. Records outside every supported object group are not copied.
LedgerCopy reads one authorised organisation at the source platform with read-only access. The connection is an authorisation granted at the source platform, not a stored password, and LedgerCopy does not write to the source. You revoke it at the source platform, in the same place it was granted, and a revoked authorisation stops the next run.
The copy is an independent, dated copy of supported records, held outside the platform that produced it. It is not a restore path. LedgerCopy does not write to QuickBooks Online or Xero, and a completed run is a record of what was copied rather than evidence that an export has been tested. Export and recovery routes are listed on this page per platform, and only where they have been tested.
An exception is a record or object group that a run could not copy completely, or copied with a difference the source reported. It is raised against the group it belongs to and carries a count, so the size of the gap is readable without opening the source. The following run retries the group. LedgerCopy names the group and the count; the cause sits in the source platform and is resolved there.
LedgerCopy is a recurring subscription per connected company file, not per seat. People who read run reports are not charged for. The price for your file is set during trial scoping, once the source platform and the object scope are known.
A run that cannot complete is reported as incomplete rather than closed. Its dated record still states what was copied before the run stopped, per object group, so the last known copy state stays readable. Each run is recorded separately and dated, so an incomplete run does not replace the last completed one.
LedgerCopy trial
A trial conversation establishes four things: the source platform you use, the ledger objects that matter to you, the cadence you need, and the review or continuity workflow the copy has to fit.