ACCAI · QuickBooks control agent In flight

The auditor that never sleeps.

And never touches your books without a signature.

ACCAI is an AI agent that watches a company’s QuickBooks Online books every night. It reads everything and changes nothing. When something needs fixing, it drafts the correction — and it only posts after a person approves it.

  • GET only · enforced at the wire
  • No AI in the nightly checks
  • One write path · one approved entry

Running read-only on one company’s books today. Not yet offered to others.

Render of ACCAI watching a ledger A fortified glass vault seen from the front. Its back wall is a ledger of sample rows. An ice-blue sentinel eye hangs from the ceiling and sweeps a scanning beam down the rows. Four rows are flagged: an uncategorised transaction, a month nobody entered, an entry changed after close, and a balance that moved. On the left, read requests pass a wire guard into the vault; write requests are crossed out at the guard. In the front corner sits a sealed write hatch with two locks and an empty signature line.
Render · sample rows, no real books. The hatch opens one way.

How it works

Code counts. The model explains. A person signs.

ACCAI splits the job three ways on purpose. Plain code does the arithmetic. Claude reads what the code found and says what it means. A person decides whether anything in the books changes.

  1. Watch, every night

    Plain code · no AI

    Deterministic control checks run against the books each night. Arithmetic doesn’t go through a model — an unbalanced entry is unbalanced, and the same books always give the same result. Alongside the checks, ACCAI keeps a change journal from QuickBooks’ own change data, so edits that nobody announced still get noticed.

  2. Read and rank

    Claude · analyst

    The analyst layer reads the night’s findings, puts them in order of what matters, cites the evidence for each one and writes it up in plain English. It never re-derives the numbers — the figures it quotes are the checks’ figures.

  3. Track what a lender tracks

    Plain code

    The ratios an underwriter computes — current ratio, working capital, leverage, debt-service coverage, the equity trend — are tracked over time, so a slide shows up long before a lender points it out.

  4. Draft a correction

    ACCAI

    When something needs fixing, ACCAI drafts a journal-entry proposal: what it would post, and which balances it assumed when it worked that out. A draft changes nothing.

  5. A person approves

    A named person

    Only a person can approve a proposal. Approve it, reject it, or leave it — until a name is on it, it goes nowhere.

  6. Post one entry

    The single write path

    The only write ACCAI can make is that one approved journal entry, carrying the proposal id in its memo so the books trace back to what was signed. It can’t delete, void or modify anything that’s already there.

Illustrative note, not from real books. The shape is the point: a priority, the evidence, plain English, and nothing changed.

LENDER METRICS · OVER TIMESHAPE ONLY
Current ratio
Debt-service coverage
Equity trend

The write path

Seven refusals

An approved proposal still has to get through the door. Seven checks stand in front of every posting, and any one of them is enough to stop it. A refusal isn’t an error to work around — it’s the door doing its job.

Render of the ACCAI blast door A round blast door with seven locking bolts, one for each refusal: wrong company, already applied, rejected, superseded, unapproved, malformed, and drifted preconditions. The drifted bolt glows amber. A handwheel sits at the centre, marked sealed. SEALED 7 CHECKS
  • Wrong company

    The proposal was drafted for a different QuickBooks company than the one connected. It never crosses between files.

  • Already applied

    This proposal has already posted once. It doesn’t post twice, however many times someone runs it.

  • Rejected

    A person said no. That answer stands.

  • Superseded

    A newer proposal replaced this one. Only the current version can post.

  • Unapproved

    Nobody approved it, or the approval has no person behind it. No name, no posting.

  • Malformed

    The entry isn’t a well-formed journal entry. It isn’t sent for QuickBooks to sort out.

  • Drifted

    Before posting, ACCAI reads every balance the proposal assumed again, live. If any has moved, the entry is refused — a correction worked out from figures that have since changed no longer corrects anything.The one that earns its keep

Read-only, enforced at the wire

It can only ask.

ACCAI’s own QuickBooks client can only make GET requests. Anything else is refused before it leaves the machine — including a write dressed up as a read. A bug in a check can’t touch the books, because the client underneath it can’t.

QuickBooks doesn’t offer a read-only permission for this kind of connection, so the guard lives in ACCAI’s own code. That’s exactly why it has to be real. The one approved entry goes out through a separate, narrow path that can’t send anything else.

The second lock

A name and a date.

Even an approved, sound, fresh proposal doesn’t reach the real books until production writes are switched on with a person’s name and a date. A lone on/off switch gets flipped while testing and forgotten. A name and a date have to be typed by someone willing to have typed them.

Nothing happens off the record.

Every proposal, approval, refusal and posting is appended to an audit trail. Lines are added, never edited or removed.

Illustrative lines with sample ids, not a real company’s trail. The kinds of event are the real ones.

What it catches

The quiet problems.

The trouble with books isn’t usually the loud mistake. It’s the thing nobody noticed — until a lender or an auditor did. These are the kinds of things ACCAI is built to notice first.

Found by the change journal

A month nobody entered.

Activity runs every month, and then one month is just… empty. Nothing was deleted — nothing was ever entered. A report shows you what’s there. It doesn’t point at what isn’t.

Illustrative. Sample months, no real activity.

  • Entries changed after close

    A transaction in a period you’d already closed was edited later. The change journal records that it moved, so it doesn’t quietly rewrite a month you’ve already reported on.

  • Balances that moved

    A balance isn’t where it was the last time ACCAI looked. It gets flagged for a person — and any proposal that assumed the old figure is refused at the door.

  • Uncategorised transactions

    Money sitting in uncategorised accounts: income and spending that nobody has put anywhere yet, and that a lender will ask about.

  • Arithmetic that should be zero

    Opening balance equity that isn’t zero. Journal entries that don’t balance. These are sums, so plain code checks them — never the model.

It says what it can’t see

Some things aren’t visible through QuickBooks’ connection at all — whether an account has been reconciled, for one. ACCAI says so on every run instead of staying silent, so nobody mistakes silence for a clean bill of health.

Who it’s for

For books that have to stand up.

ACCAI is for owners and comptrollers whose QuickBooks file has to hold up in front of a lender or an auditor. It’s built on the same rules as the rest of JARBIZ.

  • REDIS.4UFlagship · pre-launch, onboarding in waves

    QuickBooks-first. REDIS.4U treats QuickBooks Online as the book of record and pushes to it in real time. ACCAI watches that same kind of file from the other side.

    QuickBooks is the book of record
  • PAY-PROPlanned

    Humans release money. In PAY-PRO, AI can read, match and suggest, but only a named person releases a payment. ACCAI holds the same line for the books: it can draft a correction, and a person decides.

    AI suggests · a person signs

In flight · not yet offered

Nothing posts without a name on it.

ACCAI is running read-only checks on one company’s books today. It isn’t offered to other companies yet. If your QuickBooks file has to stand up to a lender or an audit, leave your email and we’ll tell you when it opens.

Tell us a little about your books if you’d like — what you run on QuickBooks, who you answer to. No sales call, no spam. We answer ourselves.