How it works
Three wires — the bank, the inbox, and the point-of-sale — and a six-cadence loop that runs after you connect them: nightly receipts reconcile, real-time cash-flow watch, the-day-past-due chasers, weekly margin digest, a Friday-afternoon weekly summary, and monthly sales-tax pegged to each state's remittance calendar. The long version is the Sunday-night editorial; this is the short version, with the loop spelled out beat by beat. The Sunday-night editorial walks the same wire-once beat in prose; the buyer FAQ answers the eleven questions operators ask before they pick a tier; and the remittance calendar names the date each state’s sales-tax obligation actually comes due.
Three read-only connects — the bank, the inbox the invoices arrive at, and the till the card batch closes through — and the loop carries itself from there. OAuth into the bank with scope set read-only; OAuth into the mailbox the same way; the POS posts a per-day summary the loop watches. No double-entry, no migration; the same tools the operator already runs, only now they share one source of truth.
One wire, one OAuth handshake, one vault token — the merchant account connects through Stripe and Square if those are what the card proceeds settle against, through Mercury and Brex for treasury and direct-bank rails, through Plaid for the long tail of institutions. The loop gets a read-only transaction pull and writes nothing back; the source-of-truth bank stays exactly the way it was before Stillpost touched it.
The inbox the paper invoice arrives at, the one the bank-side ACH notification sits in, the one the remittance advice shows up in. OAuth into the mailbox, scope set to read-only, the loop watches for vendor invoices and ACH confirmations and threads each to the line in the books it goes against — same inbox the operator already opens in the morning, only now the line reads itself before the operator does.
Square reads the daily settlement report; Stripe reads the per-day payout; Shopkeep, Clover, Lightspeed, and the long tail read whatever the connector surfaces as the day-end summary. The till posts a per-batch settlement, the loop holds it separately from the bank balance until the ACH settles — typically one to two business days for the card networks, occasionally longer on weekends. The supported vendors and connectors live on /integrations — one card per partner.
Each beat fires on its own cadence — midnight, every fifteen minutes, the day an invoice goes stale, Monday morning before the brief, Friday afternoon before the weekend opens, the date each state’s remittance calendar pegs it. Together they retire the seven recurring jobs the Sunday-night operator used to do by hand.
Mail, POS exports, and the day’s processor statement get matched line-by-line against the costing ledger — refund offsets, tip lines, chargebacks that landed on Tuesday’s statement but Wednesday’s bank — before midnight, every night. By morning the spreadsheet is the file, not the work.
What lands in the morning is a reconciliation file you can read at /reconciliation, not a stack of statements to chase.
Bank, processor, POD, inbox ACH — pulled in parallel, folded into the operating account the operator picks during wire-up. Authorized holds are subtracted from posted balances, the in-flight ACH is held separately, and the per-source reading is rebuilt every fifteen minutes.
The single-tab read lives on /cashflow — same four feeds, one position, no Sunday arithmetic.
Same email the operator would have sent — only it fires the moment an invoice ages past its term, at the hour the inbox would rather not be checking it, and follows up until the bill clears or thirty days pass, whichever comes first.
Lives on the receivables deep-dive at /receivables, where you can see what is outstanding, what has been nudged, and which customer has gone quiet.
Revenue, COGS, net margin, week-over-week delta — landed in the operator’s inbox before the briefing on Monday. If a guardrail trips, the alert names the line, the week, and the customer so the surgery starts at the right place, not somewhere in the middle of the spreadsheet.
The per-week guardrail walk lives at /margin-alerts — the digest the operator opens before the staff meeting.
Each state's remittance calendar runs at its own cadence — California on the last day of the month (not the 20th most states default to); Texas on the 20th, with the optional 1.75% single-rate use-tax election; a few on the 15th. The estimator reads each one separately and pegs the next liability to the date it actually comes due — not to a fixed weekday.
State-by-state permalinks live on /guides/sales-tax-remittance-calendar — one for every state where the loop has a customer, each with the next two due dates baked in.
Revenue, COGS, net margin, outstanding receivables, the per-state sales-tax snapshot — rolled into a single one-pager the loop compiles and lands in the operator’s inbox Friday afternoon, before the weekend opens. One read; the per-week guardrail walk and the deep-dive margins in the same scroll instead of across four tabs.
The per-week guardrail walk sits on /margin-alerts; the state-by-state cadence the summary pegs next is on /guides/sales-tax-remittance-calendar.
The four automated loops
Each loop fires on its own beat — overdue invoice chasing the day a bill ages past term, receipts reconciling before midnight every night, sales tax pegged to each state’s remittance calendar, the weekly margin digest before Monday’s brief. The wiring stays identical; what changes is the cadence the loop keeps.
Same email the operator would have sent — only it fires at the hour the inbox would rather not be checking it, and follows up until the invoice clears or thirty days pass, whichever comes first. Outstanding queues self-clear; the customer who goes quiet escalates themselves on the cadence the loop has been running for months.
See in workspace → /app/invoices
Mail, POS exports, and the day’s processor statement match line-by-line against the costing ledger — refund offsets, tip lines, chargebacks that landed on Tuesday’s statement but Wednesday’s bank — before midnight, every night. By morning the spreadsheet is the file, not the work.
See in workspace → /app/cash-flow
Each state runs at its own cadence — California on the last day of the month, Texas on the 20th (with the optional 1.75% single-rate use-tax election), a few on the 15th. The estimator reads each state separately and pegs the next liability to the date it actually comes due, not to a fixed weekday.
See in workspace → /app/sales-tax
Revenue, COGS, net margin, week-over-week delta — landed in the operator’s inbox before the briefing on Monday. If a guardrail trips, the alert names the line, the week, and the customer so the surgery starts at the right place, not somewhere in the middle of the spreadsheet.
See in workspace → /app/margin-alerts
What the kitchen table notices in the first seven days — and what the Sunday-night ritual looks like six months in. Two parts of the same operator’s story, side by side, so a buyer reading the page can place themselves in the column they’re moving into.
The first seven days are the wire-up vindicating itself — the loop runs, the streams come back, the dashboard reads what it said it would. The Sunday-morning tally that used to take four tabs and a sticky note becomes a number the operator opens in one tab. Nothing else about how the shop operates has changed yet. The bookkeeping chores that were always going to be automated just stopped being on the spreadsheet.
Six months in, the loop is invisible. The Sunday-night tax is the past tense the operator used to write it in. The hour the bookkeeping book kept is on the business — the customer the chaser couldn’t reach, the line the margin digest flagged, the state calendar the sales-tax estimate pegged next quarter. That is what wire-once earns: the part of the books the bookkeeping book was never going to reach on its own. The Friday nights that used to live on the laptop moved to the bleachers with the kid’s game. The bookkeeping hour is on the business because the bookkeeping loop carries it now.
Once the period closes, the loop compiles a CPA-ready monthly report — revenue, expenses, net margin, outstanding receivables, and sales-tax liability by state — and makes it available as a single PDF artifact. No operator input; it runs the moment the month ends. The sample below reflects the same structure the loop generates in production.
Stillpost Demo Co. · July 2026
Monthly back-office report
Sales-tax liability by state
This is what the loop generates at month-end — a CPA-ready artifact with every line the loop touched, period-close to state remittance, downloaded as a single PDF.
The next step
Starter carries the chaser, the receipts reconcile, and the weekly margin digest. Pro layers the multi-state sales-tax estimate on top. Managed hands the period close to a human. Three tiers, no surprise implementation fee — pick the one that fits your ops.
Wire it up today.
Cancel any month · switch tiers at the next renewal · reply within one business day on any question.
Pick a tier →not ready to pick a tier? Send a note →
reply expected within one business day
The next sit-down read on the per-state cadences lives on the sales-tax remittance calendar — every shipped state, the next two due dates, the local-add-on notes — the per-state cadence the loop pegs next on the operator’s behalf.