Liminality MCP is in open beta. The first 3 solves on any key are free. Connect the MCP →

How can AI help with bookkeeping, reconciliation, and sales tax?

AI can match your POS sales to bank deposits, calculate tax across states, and flag where purchased goods don't match what arrived, by reading the same records you would and doing the cross-checking faster. The judgment still matters: deposits come in net of fees, tax rules differ by state, and a short shipment isn't always an error. The honest answer is that the work is mostly tedious matching, not hard math.

Last updated 2026-06-14 · Physea Labs

Bookkeeping is mostly matching. You have one record of what happened (sales rung up, a purchase order sent, tax owed) and another record of the result (money in the bank, goods on the shelf, tax remitted), and the job is to confirm the two agree. When they don’t, you find out why. This sounds simple and usually is, line by line. What makes it hard is volume and the fact that the records are never in the same format. A POS exports one way, the bank statement another, the supplier invoice a third. You spend the time reconciling formats and chasing small gaps, not doing arithmetic.

What actually decides the outcome

A few real judgment calls separate a clean reconciliation from a frustrating one.

Fees and timing, not the gross number. When you reconcile Toast or Square sales against a QuickBooks bank deposit, the deposit is net of processor fees and often lags by a day or batches several days together. If you match gross sales to the deposit, nothing will ever tie out. The right comparison accounts for the fee skim and the deposit cut-off first.

Nexus before rates. For multi-state sales tax on Shopify or anywhere else, the first question is not “what’s the rate” but “do I even owe tax here.” That turns on nexus: physical presence, or crossing a state’s economic threshold. After that comes product taxability (clothing and groceries are exempt in some states), destination versus origin sourcing, and whether a marketplace already collected on your behalf.

A short count isn’t automatically a problem. With inventory, comparing a purchase order to what physically arrived, the gaps are often legitimate: a partial shipment with the rest backordered, a unit-of-measure mismatch (cases versus eaches), or items damaged on arrival. The real check is the three-way match between the PO, the receiving document, and the supplier invoice. Pay only for what you ordered and actually got.

Materiality. Not every penny is worth an hour. A $0.40 rounding gap across a thousand transactions is noise; a single $400 deposit that never showed up is a signal. Knowing which mismatches to ignore is half the work.

How to do it by hand

For POS-to-bank reconciliation: pull the sales report for the period, pull the matching bank statement, and pull the processor’s fee and payout report. Group sales by payout date, subtract fees, and line each net figure up against the corresponding deposit. Anything left over is your discrepancy list to investigate.

For multi-state sales tax: list every state you shipped to, check your sales and transaction counts against each state’s threshold to see where you have nexus, confirm which of your products are taxable there, and then apply the destination rate. Net out anything a marketplace already collected before you remit.

For inventory: line up the purchase order, the receiving log, and the supplier invoice side by side. Match quantities and units across all three. Flag any line where they disagree, then decide whether it’s a backorder, a wrong item, damage, or a billing mistake to dispute.

Where it goes wrong

Comparing gross sales to net deposits and concluding money is missing when it’s just fees. Forgetting that a marketplace facilitator already remitted, then over-paying the state. Treating every inventory short as theft instead of a partial shipment. Reconciling only month-end, so a problem from week one isn’t found until week four when the trail has gone cold. And the quiet one: doing it correctly but skipping it when things get busy, which is exactly when errors pile up.

Doing it yourself vs. handing it to Physea

The manual approach is correct and not complicated. The problem is that it is repetitive and easy to drop under load. Reconciling 200 deposits, sorting tax across a dozen states, or matching a week of receiving documents is the same small task done over and over, and the moment you fall behind, mismatches compound silently.

Physea’s Liminality runs the whole job end to end across your own connected tools, over MCP. It reads your POS, bank, processor, store, and inventory records where they already live, performs the fee-aware and timing-aware matching, applies the right tax logic per state, runs the three-way inventory match, and hands you the short list of genuine discrepancies with the explainable ones already cleared. It stays grounded in your actual data and reuses the route each period, so you get the result instead of the chore. The thinking you’d want a sharp bookkeeper to do still happens; the hours of formatting and line-by-line matching don’t land on you.

Common questions

Why don't my POS sales match my bank deposit?
Almost always because the deposit is net of processor fees. Square, Stripe, Toast, and similar systems take their cut before the money lands, so a $1,000 sales day might deposit as $972. Timing is the other big one: Friday's sales often arrive Monday, and several days can be batched into a single deposit. Tips, refunds, and chargebacks shift the number too. Once you account for fees and timing, the two usually reconcile. Physea can run this match across every deposit for the period automatically.
Do I have to collect sales tax in every state I ship to?
No. You only collect where you have nexus, meaning a physical presence (an office, warehouse, or staff) or enough sales to cross a state's economic threshold. After the 2018 Wayfair ruling, states set their own thresholds, often around $100,000 in sales or a transaction count, though the rules keep changing. Many marketplaces (Amazon, Etsy, and Shopify acting as a facilitator) already collect and remit for you, so you don't double-remit. Check where you've crossed a threshold, then register only there.
What's the difference between a discrepancy and an error?
A discrepancy is any mismatch between two records; an error is a discrepancy with no legitimate explanation. A partial shipment, a processor fee, or a Friday-to-Monday timing lag are all discrepancies that resolve once you understand them. A missing deposit, a deposit larger than recorded sales, or goods billed but never received are the ones worth chasing. The skill is sorting the explainable from the genuine. Physea flags the unexplained ones so you spend time only on those.