Guides
LedgerCopy guides
Each page below settles one question about holding a copy of ledger data outside the platform that produced it. They are written to be usable whether or not you ever run LedgerCopy.
Who each page is for
One line per page: who it is written for, and the question it answers.
- Verify a ledger copy is complete
For a controller who already holds a copy of ledger data.
How do you confirm a copy holds what it should, without taking anyone's word for it?
- Backup, export, or independent copy
For anyone about to evaluate a vendor and wants the terms straight first.
What is the difference between a backup, an export and an independent copy, and which one does a finance team actually need?
- Ledger copy coverage check
For anyone accountable for a copy who wants a short self-check, with nothing to sign up for.
Do we have a usable independent copy today, and which condition is missing?
- Ledger data for auditors and lenders
For a controller who has to hand a copy of ledger data to an auditor or a lender.
What does the requester actually want, and how do you hand it over so they can rely on it?
LedgerCopy trial
Scope a copy against the questions above.
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.