Accounting and bookkeeping

Bank and card transactions matched to the books

A bookkeeper keeps the books for a company with seven bank and card accounts, matching and coding each line as it lands in QuickBooks Online. The owner emails about purchases days before they post, so the context sits in one inbox and the charge shows up later in the bank feed.

Who it is forAccounting and bookkeeping firms with 5 to 50 staff, and bookkeepers working inside a client business
Who decidesThe bookkeeper
Where the work livesBank and card feeds, owner emails → QuickBooks Online
BuildTen business days
A desk with a printed bank statement marked with highlighter, three company credit cards fanned beside it, a small stack of supplier invoices with one wallpaper sample clipped to the top, and a coffee mug.

Who does what

The hours go into lines the books have already seen before.

Coding recurring lines Proposes the account and class for vendors the client pays every month, using how the same vendor was coded before.The agent
Linking purchase emails Reads the emails the owner and staff send about purchases and holds each one until a matching charge appears in a bank or card feed.The agent
The open list Groups the lines it cannot place and drafts one message to the owner with the date, amount and vendor for each.The agent
Review and judgment Checks the proposed coding, decides the unclear lines and anything that touches a job or a loan.The bookkeeper
Month-end reconciliation Reconciles each bank, card and loan account and signs off the month.The bookkeeper

What you get

Each new bank and card line arrives with a proposed category, class and match, plus a short list of lines it could not place and the question to ask about each.

Draft for review

Card charge
A charge from a wallpaper supplier on one of the company cards, showing up in the QuickBooks Online bank feed four days after the owner emailed about it.
Draft
Coded to job materials, class set to the job named in the owner's email, with the email linked to the transaction.
Based on
The owner's email naming the buyer, supplier and job, and the client's rule that supplier purchases for a job go to job materials.
How sure it is Moderate
Why a person decides The amount on the email and the charge differ slightly, likely shipping, so the bookkeeper checks the job and the split before it posts.

The rules it follows

It follows each client's chart of accounts from the first day.

These are your company's own rules, written down and confirmed with your team during the build. It works on its own only within limits you set.

  • Each client's chart of accounts, classes and job list as set up in QuickBooks Online.
  • Which vendors map to which account or class for that client.
  • The amount below which a recurring line needs no review.
  • The month-end checklist for each bank, card and loan account.

What it learns when your team adjusts its work

Useful from the first day, and it keeps getting better. The bookkeeper reviews its work.

The busywork it takes off the bookkeeper. It takes the line-by-line coding of familiar vendors and the hunt through old emails off the bookkeeper. That time goes back to the work only they can do.

What it starts out knowing

  • The client's chart of accounts and classes
  • How each vendor was coded in past months
  • Which of the seven accounts belong to which entity or purpose
  • Who at the client emails about purchases

It works from these sources, shows which one an answer came from, and asks when the answer is not there.

Who reviews its work, and when review can stop

The bookkeeper reviews every proposal at first. For a routine type, such as monthly fuel or software charges, review stops once its record on them is good and the firm and client agree.

Unclear charges, job allocations, loan entries and the month-end sign-off keep going to the bookkeeper.

It no longer needs review once its record on them is good and you agree, one type of task at a time. New, unusual and high-stakes work stays with a person.

When your team adjusts its work

When the bookkeeper changes a hardware store charge from office supplies to job materials for one client, the change is saved as a rule for that client, and next month the same vendor is proposed as job materials. The bookkeeper decides whether it becomes a rule, a single example or an exception.

It learns how your company does this job. It does not watch, rate or profile your employees. Your team decides what it learns. You can read everything it has learned and remove anything. Whoever runs it, your team or our engineers, makes sure on a regular cycle that what it learned stays inside the bounds you agreed.

From a request a business posted

A remote bookkeeper for a small company, on a bookkeeping forum.

The bookkeeper handles data entry, matching and reconciliation in QuickBooks Online across seven bank and card accounts, from several states away. The owner and three others email about purchases for specific jobs, but the charges post days later, and by then those emails are buried. The bookkeeper codes the obvious lines and sends the owner a running list of charges that need more detail.

Paraphrased from a public post, not quoted, and not a client engagement.

From first principles

Which account, class and job does this line belong to, and is there anything we already know about it?

Before we build anything, we take the work down to what has to be true. What is left over is habit. Habit gets deleted, not automated.

  1. What has to be true

    • Every bank and card line ends up in the right account and class.
    • Job costs land on the job they were bought for.
    • Each account reconciles at month end.
  2. What is only habit

    Reading every line by hand, including the gas station and the monthly software bill, is only habit. So is keeping purchase context in scattered emails and rebuilding it from memory when the charge posts.

  3. What we delete before building anything

    We stop treating recurring vendors as new decisions each month. Lines that the client's own history already settles should not reach the bookkeeper as open questions.

  4. What is left

    The agent. We build an agent that proposes a category, class and match for each new line from the client's history and rules, and links it to any email that mentioned the purchase. It holds back the lines it cannot place and drafts the question for the owner.

    A person. The bookkeeper reviews the proposals, answers the open lines with the owner, and signs off the reconciliation.

The kind of work: Checking and matching. Checking and matching is the work of holding one record against another: a bank line against the books, a delivery ticket against an invoice, a payout against the sales behind it, a customer's request against the price list. People still do it by hand because the records never line up exactly, and someone has to decide what each mismatch means.

What the engagement needs

What we need from you, and how it runs.

The engagement needs read access to the client's QuickBooks Online file and its bank and card feeds, and access to the inbox where purchase emails arrive. It also needs a few months of coded history and the client's month-end checklist.

How the engagement runs

  1. 01

    Fit test first

    We check the time this job takes, access to your systems and how you would review the result. If a ready-made tool is enough, we say so.

  2. 02

    Build in ten business days

    Senior engineers agree the rules with the bookkeeper, test on past cases and set approval limits and a way to switch it off.

  3. 03

    Ninety days of support, included

    Work with the agent in Slack, Teams or text messages. We fix problems and adjust it as unusual cases come up.

  4. 04

    Keep improving it, with your choice of operator

    You own the agent and keep its source, tests and guide either way. Your team runs it, or our engineers run it with a monthly report. Learning continues on your own servers, in your own cloud account or in our data center.

When we'd point you elsewhere

Sometimes a ready-made tool is enough.

The fit test checks this first. If one of these covers your case, we tell you, and you keep the map of the work.

  • A client has one or two accounts and mostly recurring vendors with no job costing. The bank rules built into the accounting software are usually enough.
  • The main gap is getting receipts from staff, not coding. A receipt capture app connected to the accounting software may be enough.

Honest limits

What this page does not claim.

A person reviews its proposals, and lines without history or an email behind them still need someone to ask the owner.

The situation is drawn from a public request a business posted, paraphrased, not a client engagement.

Show us the work

More use cases

More work of the same kind: checking and matching.