The phrase "AI bookkeeping" gets used for two very different things. One is a feature inside accounting software that guesses a category for a bank transaction and asks you to click accept. The other is an agent that does the bookkeeping: it reads what came in, checks it against your rules, posts the clean entries to QuickBooks, and puts the ones it is not sure about in front of a person.
We build the second kind. This post explains where the line sits between what the agent posts on its own and what still goes to your accountant, because that line is the whole product. Draw it in the wrong place and you either get a bot that asks about everything, which saves nothing, or a bot that posts everything, which nobody should trust.
What the agent reads
The Odyssey Bookkeeper Agent takes in the same records a person would open on a Monday morning:
- Bank and card feeds
- Vendor invoices and receipts, as PDFs, scans, or email attachments
- Operating records from the systems that run the business, such as a job or order system, a field-service tool, or a point-of-sale export
- Journal entries that recur, like depreciation or accruals, on the schedule you set
It reads each one into a structured record: date, amount, counterparty, description, and any reference numbers or line items the source carried.
What it checks
Every record goes through the checks you would want a careful bookkeeper to run before posting:
The chart of accounts. Each transaction gets matched to an account based on rules written during the build. Some rules are simple, like "this vendor is always software subscriptions." Some depend on the details, like "fuel purchases on this card go to the vehicle account for the truck the card is assigned to."
Classification rules. Class, location, customer, job, or project, wherever your books use them. A contractor's books might tag every expense to a job number pulled from the invoice. A multi-location business tags by location from the card that was used.
Duplicates and matches. An invoice that arrived by email and the card charge that paid it get matched, not posted twice. A bank feed line that corresponds to a check already entered gets reconciled, not re-entered.
Amount and vendor sanity. A charge from a known vendor for roughly the usual amount is routine. A first-time vendor, or a known vendor for ten times the usual amount, is not.
What it posts on its own
Transactions that pass every check post straight to QuickBooks Desktop or QuickBooks Online, with the source document attached and an audit line recording where the record came from, which rules it matched, and when it posted.
In practice, for most businesses, that is the large majority of monthly volume:
- Recurring vendor bills at their usual amounts
- Card charges from known vendors matched to their receipts
- Customer payments matched to open invoices
- Payroll journal entries from the payroll provider's report
- Scheduled recurring entries
- Bank fees, interest, and transfers between your own accounts
None of these needed a decision. They needed someone to look, confirm, and type, and that is what took up the bookkeeper's week.
What goes to the review queue
Anything that fails a check, or that the rules say always needs a person, goes to a review queue instead of the books. The person opens the queue, sees the record and the reason it stopped, and posts it, corrects it, or rejects it. The agent learns nothing from that on its own; if the same case keeps stopping, we change the rule.
The cases that stop, by design:
- New vendors and new customers. Someone confirms who they are and what account they belong in before the first entry posts.
- Unusual amounts. Outside the range the rules set for that vendor or account.
- Anything with no matching document. A card charge with no receipt, or an invoice with no payment.
- Entries that touch accounts you flagged. Owner draws, loans, fixed assets, intercompany, anything with tax consequences.
- Partial payments, credits, refunds, and disputes. These need a decision about what the money is for.
- Records the agent could not read cleanly. A blurry scan, a receipt with the total torn off, an email that mentions three invoices.
The queue is where the accountant's time goes. Instead of touching every transaction, they touch the ones that needed them.
What always stays with your accountant
The agent does the bookkeeping. It does not do the accounting. These stay with a person:
- Month-end and year-end close. Reviewing the reconciliations, adjusting entries, and signing off.
- Tax positions. What is deductible, how something is depreciated, when revenue is recognized.
- Judgment calls about the business. Whether that deposit was revenue or a loan from the owner is a question for the owner, not a rule.
- Anything a rule has not been written for yet. New situations go to the queue, and the rule gets written after a person has decided.
If a vendor tells you their AI bookkeeping software closes your books without an accountant, ask them who signs the tax return.
The audit trail is the point
Every posted entry carries a record of the source document, the rules that matched, the timestamp, and whether a person touched it. Every review-queue decision carries who made it and when.
That trail is what makes the arrangement safe to run. Your accountant can sample the auto-posted entries and see exactly why each one posted. If a rule was wrong, you can find every entry it produced and fix them together, rather than hunting through the ledger.
How the line moves over time
At launch, the rules are conservative and the review queue is busy. That is deliberate. The first few weeks are spent reading the queue with your accountant and asking, for each case, whether a rule could have handled it. Most of the time the answer is yes, the rule gets written, and that case stops appearing.
Over a couple of months the queue shrinks to the things that genuinely need a person. The line between "posts alone" and "goes to review" ends up where your accountant is comfortable with it, not where a vendor decided it should be.
Who this is for
An AI bookkeeping agent built this way makes sense when the volume is high enough that the administrative tasks become a real cost, and when the records come from more than just one place. A business with a bank feed, a card feed, a job system, and a stack of vendor emails is the typical case. A business with thirty transactions a month does not need it.
It also makes sense when the books are behind. Catching up months of unposted transactions is exactly the kind of work the agent does at full speed and a person does at a crawl.
Where this runs
Odyssey builds and runs the Bookkeeper Agent from our office in Colleyville, Texas, in the Dallas-Fort Worth area, for businesses across the United States. Each build is configured to your chart of accounts, your classification rules, your source systems, and your QuickBooks file, and we tune the rules with your accountant after launch. If you want to see it post against a sample of your own transactions, book a call and we will set it up.