OOdyssey AI

Article

AI bookkeeping for hosted QuickBooks Desktop files

Your QuickBooks Desktop file runs on a hosting service. Here is how an AI agent posts receipts, bank lines and payments into it.

By Lincoln Powers

Your QuickBooks Desktop company file runs on a hosting service, so your team and your accountant can open it from anywhere. Someone still types in the receipts, bank lines and customer payments by hand, and many of the AI bookkeeping tools you look at connect only to QuickBooks Online.

You do not have to move to Online, and you do not have to bring the file back to a computer in your office. The Odyssey Bookkeeper Agent posts to QuickBooks Desktop files on a hosting service, the same way it posts to a file on your own computer or server. This post covers what the agent does with a hosted file, what stays the same for your team, and what a build involves.

Why a hosted file changes the question

A hosting service runs QuickBooks Desktop on a server instead of a computer in your office. Your team signs in to the host and opens the company file there. Many firms moved their Desktop file to a host instead of moving to QuickBooks Online.

The AI bookkeeping tools you find are mostly built for Online, for reasons we covered in AI bookkeeping for QuickBooks Desktop. So the question for a hosted file is not only "does it work with Desktop" but "does it work with Desktop where my file lives".

For the Bookkeeper Agent, the answer is yes. Connecting it to the company file on your host is part of the build, so the host and the file stay where they are.

What the agent does with your hosted file

The agent works through the same list a bookkeeper does, in the company file on your host.

Receipts: it reads receipts and vendor invoices from email attachments, scans and PDFs, and matches each one to the bank or card line it belongs to. The purchase is entered once, not twice.

Bank feeds: it works through your bank and card transactions and checks each one against your rules: which vendor goes to which account, class and job.

Customer payments: it matches each payment to the open invoice it pays and applies it there.

Accounts receivable: it pulls the overdue invoices, checks each account against your list of accounts in dispute, and queues a payment reminder for each account that is not on it.

Reconciliation: it reconciles your bank and card accounts against their statements and sends anything that does not match to your bookkeeper.

Reports: it produces the reports you read, such as a profit and loss, so the numbers are current when you open the books.

Every entry it posts carries a record of the source document, the rule it matched and the time it posted. To watch the agent work through a day of this in QuickBooks Desktop, see QuickBooks automation: a day of bookkeeping in 90 seconds.

What waits for a person

Routine entries are what the agent posts on its own:

  • Recurring vendor bills at their usual amounts
  • Card charges from known vendors, matched to their receipts
  • Customer payments matched to open invoices
  • Scheduled recurring entries
  • Bank fees, interest and transfers between your own accounts

New vendors, unusual amounts, charges with no matching document and entries that touch accounts you flagged go to a review queue instead of the books. Your bookkeeper opens the queue, sees the record and why it stopped, and posts it, corrects it or rejects it.

The agent does the bookkeeping, not the accounting. Month-end close, tax positions and judgment calls about the business stay with your accountant.

What stays the same on your host

  • Your company file stays with your hosting service, and your team signs in to it the same way.
  • Your chart of accounts, your vendor and customer lists and your history stay in that file.
  • Your accountant keeps working in the same file, with the same reports.
  • Your team stops typing in the entries the agent now posts, and works the review queue instead.

If you move to QuickBooks Online later, the agent can post there instead.

What a build looks like

Operations review: we look at where your receipts, bills and bank data come from, how your chart of accounts and classes are set up, and which entries your team types in by hand today.

Custom build: we connect the agent to the company file on your host and set it up with your chart of accounts, your classification rules and your list of accounts in dispute.

Live operation: the agent posts and your bookkeeper works the review queue. For the first few weeks we read that queue with you, and each case that keeps stopping gets a rule if a rule can handle it. The queue shrinks to the entries that need a person.

A simple build can be ready in a few days. A complicated one can take 90 days to design, build and test.

What it costs

The Bookkeeper Agent has a build fee from $5,000, then from $500 a month. The monthly fee covers AI model usage, monitoring and fixes, and the changes you ask for. More systems to connect, more volume and more complex rules raise a quote.

Who this is for

The agent makes sense when your records come from more than one place and there are enough of them each month that typing them in is a real cost. The typical case is a bank feed, a card feed, a job or order system and a stack of vendor emails. It also makes sense when the books are behind, because catching up months of unposted transactions is work the agent does quickly and a person does slowly.

See it work on your hosted file

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. If your QuickBooks Desktop file lives with a hosting service and your team still types in receipts and bank lines, book a call and we will look at how your file is set up and what the agent would post first.

See it on your file

Book a call and we will look at how your hosted file is set up.

A 30-minute Google Meet with co-founder Lincoln Powers. We go through the work you want automated and what an agent should take over first.

Book a 30-minute call