From a request a business posted
Delivery tickets matched to invoices
Month-end reconciliation of PODs and scale tickets against invoices, chasing lost paperwork and weights that do not match the load.
Accounting and bookkeeping
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 does what
What you get
Draft for review
The rules it follows
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.
What it learns when your team adjusts 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
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
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
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.
What has to be true
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.
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.
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
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.
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.
Senior engineers agree the rules with the bookkeeper, test on past cases and set approval limits and a way to switch it off.
Work with the agent in Slack, Teams or text messages. We fix problems and adjust it as unusual cases come up.
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
The fit test checks this first. If one of these covers your case, we tell you, and you keep the map of the work.
Honest limits
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.
More use cases
From a request a business posted
Month-end reconciliation of PODs and scale tickets against invoices, chasing lost paperwork and weights that do not match the load.
From a request a business posted
Bookkeepers spend hours in spreadsheets breaking each Shopify, Amazon, PayPal and Square payout into sales, fees and refunds.
From a request a business posted
Re-typing every line of a customer's PDF request, hunting each part in the catalog, then looking up the approved price.