Acuvant Ledger integrity checks
Check opens soon
01 — The handover

A verdict on the file you have just been handed.

A Xero General Ledger Detail export goes in. A verdict on that file comes back. No connection to your Xero, no access granted, nothing installed.

Tell me when it opens

One email when the check opens. Nothing else, and no access to your Xero is ever requested.

Mechanic
01 Export the General Ledger Detail from Xero.
02 Upload the file. No signup, no permissions dialog.
03 Read the verdict. The file is deleted on a schedule.
02 — Two ways in

I'm a bookkeeper or accountant

You are about to quote on a file you did not build, or you have just inherited one. Run the export before you write the scope of works, before the pre-BAS pass, before it becomes your problem to have missed.

See the four moments →

I'm assessing a business

Someone else's books, before you buy or before you rely on the numbers. Ask for the export, get a read on the file before your accountant starts the clock.

Why a file, not a login →

Same engine, same file, same output. The difference is the framing, not the product.

03 — Four moments

Nobody health-checks a file they already trust.

01

Quoting a prospect

You cannot connect an app to books you do not control, but you can ask for an export. Price the mess before you commit to it.

02

The takeover

A new client's file, an onboarding, a year-end ledger arriving from someone else. Trust is lowest exactly when you inherit the data.

03

Due diligence

Reviewing a vendor's books before buying the business, when the seller's bookkeeper is not the one you will be asking.

04

The pre-lodgement gate

A point-in-time read on whether the file is sound, before BAS or before year-end goes out the door.

04 — Access

The files that most need a verdict are the ones you have no relationship with yet.

Tools that connect to an organisation need access, authority and an ongoing relationship. That works well for the books you already manage.

This runs on a file. Nothing is connected. Nothing is granted. The file is uploaded, checked, and deleted on a schedule — and you did not have to ask anyone for a login to do it.

05 — What it checks

It reads the file the way a reviewer would.

Not keyword matching, and not a scan for a list of known bad words. Each check is a question about the ledger that has a defensible answer, reasoned against Australian accounting standards.

We publish what it looks at and how many questions it asks. We do not publish the questions — the library is the thing being built, and it is not for sale on the front page.

15 checks run against every file, at three severities. The count and the library version are stated with every result.
What it looks at
Whether the file itself is complete
Coding and classification that contradicts itself
Suspense and clearing residuals
Duplicates
GST coding and control account tie-out
Departmental allocation gaps
Chart of accounts inconsistency
Balances that should not be possible
The kind of thing it says

An account named for wages, typed as revenue.

A clearing account that has never cleared.

Illustrations of the judgment, not entries from the library.

06 — How it decides

The question a professional actually has is whether this can go in front of a client.

01

Deterministic, not AI

Every finding traces to a named, versioned rule. Ask why something was flagged and there is a real answer, the same one every time.

02

Nothing leaves

No external model is called. Your client's data is not sent to an AI, does not train anything, and is deleted on a stated schedule.

03

It stays quiet unless it is certain

Precision over recall, deliberately. If it finds nothing, it says nothing. There are no manufactured red flags to make the result feel worth the upload.

04

Grounded in the standards

Findings are reasoned against Australian accounting standards, and the basis for each one is recorded rather than asserted.

05

Built by an accountant

Twenty-five years in the profession, writing the rules for the files he has had to clean up himself.

Every transaction in the export is placed, deliberately excluded and counted, or surfaced for review. Nothing is silently dropped.

07 — What you get back
The check

A verdict on the file: what was found, by category and severity, with enough detail to know the problem is real and not an artefact of the export.

If the file is clean

You get that in writing — a dated record that this export was checked against 15 checks and passed. Attach it to the quote, or file it in the workpapers.

The full report

Exact locations for every finding, down to the transaction, and remediation guidance for each one.

That is the whole difference between the two. The check tells you the file has a problem; the report tells you where it is and what to do about it.

08 — The ask

I am looking for twenty bookkeepers to break this before anyone else has to rely on it.

Practice tier free for life. In exchange I would like you to run it over real files, with your client's authority, grade every finding honestly, and tell me bluntly where it is wrong. What I want most are the ugliest takeover files you have.

I have been an accountant for twenty-five years. I built this because I kept being handed files I could not trust and had no fast way to read. If that is your week too, I would like your file and your criticism.

Apply to the founding cohort Ash — Acuvant
09 — Questions

How is this different from tools that connect to Xero?

Those tools monitor an organisation you already have access to, continuously. This reads a single file from an organisation you may have no relationship with at all. If you manage the books, a connected tool is a reasonable thing to own. If the books have just been handed to you, there is nothing to connect to.

What happens to my client's data?

The export is processed and deleted on a schedule. No external model is called, nothing is sent to an AI service, and nothing you upload trains anything. Hosting location and the retention schedule are stated in the privacy terms.

Do I need my client's permission?

Yes. You warrant that you have authority to upload the file. We would rather say that here than bury it in the terms.

Is this an audit?

No. It produces informational data-quality observations on the file you supply. It is not an audit, a review or an assurance engagement, and it does not replace your professional judgment.

What file do I need?

The Xero General Ledger Detail export, for the period you care about. In Xero it sits under Accounting → Reports → General Ledger Detail; export it and upload the file as it comes out.

What if it finds nothing?

Then it says nothing, and you get the record that it checked. A quiet result is the point, not a wasted upload — it is the thing you can put in the workpapers.

Can I see the list of checks?

No. You get the count and the library version with every result, and the plain-English description of what it looks at, above. The list itself is not published — it is the thing being built, and publishing it is the one way to make it worth less. If that is disqualifying for you, it is a fair reason not to use this.

Be told once, when it opens.

One email when the check opens. Nothing else, and no access to your Xero is ever requested.

Tell me when it opens