Connect the source
Authorise a supported QuickBooks Online or Xero organisation with read-only access. Access is revoked at the source platform at any time.
Daily Copy
An independent copy of your ledger data. Every run reports what it copied.
LedgerCopy maintains a dated, inspectable copy of supported QuickBooks Online or Xero data. Each run records its source, completion time, supported object groups, record counts, and exceptions, so copy status can be read outside the ledger platform that produced it.
The trial runs for 14 days. No credit card is required to start it.
Source organisation Copy status
Example Latest run Completed 09 Aug 2026, 02:14 UTC
Outcome: complete with exceptions
SourceQuickBooks Online
Run scheduleDaily · 02:00 UTC
Copy locationIndependent storage
| Object group | Records | Result |
|---|---|---|
| Accounts | 94 | Copied |
| Transactions | 17,906 | Copied |
| Contacts | 642 | Copied |
| Attachments | 1,284 / 1,301 | Review |
Coverage note 17 attachments are recorded as an exception on this run. A completed run is a record of what was copied, not a tested export.
Run report
What a run reports
A run report is a specification, not a status light. Every dated run records the same five things about the copy it made.
- Source
- Which platform the run read from, and which authorised organisation it read.
- Completion time
- When the run finished, recorded in UTC.
- Supported object groups
- Which object groups the run covered for that organisation.
- Record counts
- How many records were written, per object group.
- Exceptions
- What the run could not copy completely, and in which object group.
Mechanism
How the copy runs
Read-only at the source, independent in storage, and inspectable after every run.
Run the dated copy
LedgerCopy collects supported records into independent storage and records the result per object group.
Read the run report
Completion time, record counts, and exceptions stay together in one dated record.
Coverage and boundary
What the copy contains, and what it is not
What a copy contains
A run report is organised by object group. The groups below are the taxonomy a report uses. Which of them are covered for a given organisation is source-dependent and is confirmed in writing before a trial run.
- AccountsThe account structure the run read, counted per account record.
- TransactionsDated ledger entries, counted per record written.
- ContactsCustomer and supplier records, counted per record written.
- AttachmentsFiles held against records. Counts show files copied against files the source reported.
Where the boundary falls
- LedgerCopy is an independent operational copy. It does not replace QuickBooks Online or Xero.
- A completed run is a record of what was copied. It is not evidence of a tested restore.
- Export and recovery routes are described only where they have been tested, and are named per platform.
- Coverage is source-dependent. The supported object list for your organisation is confirmed in writing before a trial run.
Definition
What an exception is
An exception is a record or object group that a run could not copy completely, or copied with a difference that the source reported. It is raised against the group it belongs to, and it carries a count.
Causes are source-dependent: a permission the authorisation does not cover, a source API limit reached mid-run, or an object the source did not return. LedgerCopy names the group and the count rather than diagnosing the source.
An exception stays attached to the dated run that raised it. The following run retries the group, and a run that cannot complete is reported as incomplete rather than closed.
Pricing model
How LedgerCopy is charged
LedgerCopy is a recurring subscription per connected company file, not per seat. The price for your file is set during trial scoping, once the source platform and the object scope are known. People who read run reports are not charged for.
LedgerCopy trial
Request a trial and scope the copy.
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.
What to have ready
- Which organisation or company file the copy would cover.
- Who can authorise a read-only connection at the source platform.
- Which object groups you check at close.