Integrations
Three input connectors the bookkeeping loop carries end-to-end — the bank on the wire, the inbox the receipts already land in, and the point-of-sale per-day batch — wired in once, read-only per source, mapped onto the four back-office loops the operator already runs (cash flow monitoring, overdue-invoice chasing, nightly receipt reconciliation, and state sales-tax estimates). The full wire-once beat is on /how-it-works; the cash-flow watch the bank feed unlocks lives on /cashflow, the overdue-invoice chaser the inbox feed unlocks lives on /receivables, the nightly receipts reconcile on /reconciliation, and the state sales-tax peg on /sales-tax.
There are three input connectors the bookkeeping books won't tell you they need, but the operator's Tuesday-morning hours carry all the same — and they are paid in three open browser tabs and a stack of paper: the bank on the wire on the left monitor, the inbox the receipts land in sitting on a half-stack on the corner of the desk where the OCR scanner was supposed to read them last week, the point-of-sale per-day batch on the right. Stillpost carries all three under one wire-up, one OAuth per source, none of them written back to.
The first one — banks — is the one the eighty-percent of operators were going to half-build themselves, and it is the one that unlocks the cash-flow monitoring loop. Plaid reads the long tail of U.S. institutions in one connector; the direct connectors for Mercury and Stripe Banking and Brex sit beside it for the operator whose accounts live there; the rest of the retail half — Chase, Bank of America, the small-business checking the operator has had for years — fold into the same per-account ledger the 06:00 cash-flow watch reads. Read-only OAuth, one wire-up at the kitchen table, the source-of-truth bank stays exactly the way it was before Stillpost touched it.
The second one — email — is the inbox receipts come into, and it unlocks the overdue-invoice chasing loop AND the nightly receipt reconciliation loop, two back-office jobs the operator's bookkeeper used to run on a Tuesday morning. Gmail for the operator who forwards receipts to a dedicated address, Microsoft 365 for the operator whose domain already runs mail on Outlook, generic IMAP for the operator who set up the inbox themselves. The 09:00 chase reads what arrives, ages each invoice against the term the invoice itself carries, and queues the next nudge; the 20:00 receipts reconcile OCRs the day's mail into the costing ledger without an inbox hand-pass.
The third — point of sale — is the till the loop reads the per-day batch from, and it unlocks the nightly receipt reconciliation loop AND the state sales-tax estimates loop, the two jobs that used to take the operator's Sunday afternoons. Square for the corner store, Toast for the multi-rail restaurant, Lightspeed for the merchant with the mixed bag, ShopKeep for the smallest operation, SumUp for the operator who took the card swipe in the parking lot. The day's batch lands in the same per-account ledger the bank will reconcile against tomorrow; the per-till settlement feeds the 23:55 fifty-state sales-tax peg. Read-only per source. Same per-day batch, same read-only OAuth, none written back to.
Three input connectors the bookkeeping loop wires up, read-only — the bank on the wire, the inbox the receipts land in, and the point-of-sale per-day batch. Each card links to the vendor’s public page; the “Unlocks” tag list under every category names the back-office loop that connector feeds.
Banks
Plaid for the long tail of institutions plus direct connectors for the banks the loop already knows end to end — a read-only transaction pull into the same per-account ledger the cash-flow watch holds.
Plaid
The long tail of U.S. banks, one connector.
Mercury
The Mercury bank the operator runs operations from.
Stripe Banking
Stripe Treasury + Stripe-issued accounts, read into the loop.
Brex
Brex cards and Brex banking on the same per-account ledger.
Chase
The U.S. retail bank the operator already wrote checks out of.
Bank of America
The small-business checking the operator has had for years.
Gmail, Outlook, generic IMAP — the inbox the receipts already land in. Wired in once, the day’s mail OCR’d into the costing ledger without an inbox hand-pass from the operator. Inbound invoice pickup runs at the same step, aged against each invoice’s own term.
Gmail
The Gmail inbox the receipts the operator already forwards to.
Microsoft 365
The Outlook inbox the operator’s domain already runs mail on.
Generic IMAP
Any IMAP inbox the operator set up themselves.
Point of sale
The point-of-sale provider the operator already swiped cards on — read-only into the loop, the day’s batch folded against the costing ledger before the books go out. Per-till settlement feeds the fifty-state sales-tax peg; the per-card-network ACH bridges until it settles.
Square
Square’s per-day settlement report, posted at end-of-day.
Toast
Toast’s per-till settlement for restaurants on multiple rails.
Lightspeed
Lightspeed’s per-batch for retail and hospitality.
ShopKeep
ShopKeep’s per-day drawer read for the corner store.
SumUp
SumUp’s per-batch settlement for the small merchant.
Four back-office loops the bookkeeping loop runs, each one named by the connector that feeds it — the bank on the wire drives cash flow monitoring; the inbox drives overdue invoice chasing AND nightly receipt reconciliation; the point-of-sale drives nightly receipt reconciliation AND state sales-tax estimates.
A read-only transaction pull from Plaid (plus the direct connectors for Mercury, Stripe Banking, Brex, Chase, Bank of America) folds into the same per-account ledger the 06:00 cash-flow watch reads. The Sunday-morning four-tab tally becomes one number, refreshed every fifteen minutes, anchored to the operator’s main operating account.
Gmail and Microsoft 365 (plus generic IMAP) read what arrives, age each invoice against the term the invoice itself carries, and queue the next nudge at 09:00 — a polite chase on the day it ages past its term, not at the end of the week. Three touches (day 1, day 7, day 21), stops the moment the invoice is paid, parks on dispute.
The 20:00 reconcile step reads the day’s mail (OCR’d into the costing ledger from Gmail, Outlook, or IMAP) AND the day’s POS batch (per-day settlement from Square, Toast, Lightspeed, ShopKeep, SumUp), folds both against the costing ledger before midnight, and posts an audit trail the CPA opens on Monday without the operator rebuilding it.
The per-till settlement the POS posts at end-of-day feeds the 23:55 fifty-state sales-tax peg — per-state nexus threshold monitoring, per-state accrual, and the next remittance date flagged in the weekly margin digest. The estimator pulls from Avalara and TaxJar alongside the per-state DOR (Department of Revenue) feeds; the operator picks the upstream.
Integrations FAQ
What the wire-once covers, how the read-only OAuth keeps the source-of-truth system untouched, how the point-of-sale feeds the fifty-state sales-tax peg, what gets reconciled (and what the loop deliberately does not touch), and how to add a connector Stillpost doesn’t list yet.
Don’t see yours?
If the integration the operator’s books need is the one the operator’s bookkeeping team has been hand-managing for years, send a note and we’ll add it to the wire-up queue — direct connectors for the long tail of institutions, the per-till settlement for the POS the operator chose, the inbox the receipts already land in.
reply expected within one business day
5 integration questions answered · copy last refreshed alongside the Stillpost roadmap