For QuickBooks.
AI workflows that keep the customer ledger clean.

It maps every app that touches the customer ledger — ServiceTitan / Jobber / Housecall Pro on the field side, Gusto on payroll, Stripe and Square on payments — to the line in the chart of accounts that the sync actually writes to, and to the Class / Location that the multi-trade firm needs to keep straight. Trade-specific notes call out which Classes map cleanly to a multi-trade firm (one per trade: HVAC, plumbing, electrical, etc.), what recurring transactions to wire on day one (monthly owner draw, quarterly estimated tax, recurring vendor bill), and what stays in a manual monthly entry because no integration does it well yet. The point is not "here are the apps"; it is "here is what each app actually writes to QBO and where the controller needs to check the books after every sync".

The field-service sync prompt walks the controller through a partial-sync reconciliation — the dispatched job that landed on the FS board but the invoice export hung mid-stream, the payment that posted two days after the invoice was created, the void the field tech made in the FS app that the QBO side never saw — and gives a one-page reconciliation checklist the controller runs the morning after the sync. Designed for the moment the multi-trade firm wakes up to a QBO inbox full of half-posted invoices and a Tuesday morning deadline: what to clear by hand, what to leave alone so the next daily sync retires it, and what the FS vendor support queue needs in order to fail the sync forward at the source.

The multi-trade rollout ships as a QBO-shaped 30/60/90 — week one runs on the single trade that brings the largest revenue, with the FS-platform sync already in place (typically ServiceTitan or Jobber) and a single Class for that trade. Day thirty adds the second trade with its own Class, day sixty adds Gusto payroll sync, 1099-NEC prep, and a daily Stripe / Square reconciliation cadence against Undeposited Funds, and day ninety lands the multi-Trade coordination pattern (one chart of accounts, two-to-three Classes, one Items list, and a recurring-transaction schedule for owner draws, estimated tax, and the recurring vendor bills every multi-trade firm has). The plan stays QBO-specific — Class mapping, Items setup, Chart-of-Accounts nudges — not a generic SaaS adoption curve.

The duplicate-invoice prompt runs the moment the controller opens QBO to the duplicates — read the FS board to confirm the void posted there first, read the QBO side to confirm both invoices are present, reverse the duplicate the wrong direction (a credit memo, not a delete, so the audit trail holds), and post the same reconcile script the next morning as a recurring task until the FS vendor pushes the void across. The script is trade-specific: ServiceTitan voids land on the QBO side in different shapes than Jobber voids, and Housecall Pro sometimes pushes a void as a brand-new invoice rather than as a reversal — so the controller sees the right void for the platform that produced it.

Four, each with a one-page prompt the controller runs the morning after close: (1) the duplicate-invoice loop covered above; (2) GL-mapping drift across re-imports — the moment a re-import re-maps the same ServiceTitan invoice to a different Income account and silently doubles the month's revenue; (3) the unapplied-cash pile-up — Stripe and Square payments landing in Undeposited Funds without an invoice match and quietly aging past 30 days until the controller catches them on the next reconciliation; (4) the Class-on-a-job-when-there-shouldn't-be-a-Class audit — a field tech adds a Class on a routine service call and the multi-trade firm's P&L silently splits the trade. Each prompt is a quick scan, not a full audit — designed to run before the books close.

The QBO-team rollout ships as a 30/60/90 adoption plan — week one runs on two champions (one controller, one bookkeeper), day thirty adds the rest of the bookkeepers, day sixty adds the payroll person running the Gusto sync and the 1099-NEC prep, day ninety lands the multi-trade coordination pattern across the whole shop. The plan stays QBO-specific: prompts are pre-mapped to the Ecosystem Overview's chart-of-Accounts nudges, the FS-platform sync's reconciliation cadence, the Failure-Modes prompts the controller runs after close, and the Rollout's Class / Items setup milestones so each rollout wave lands a workflow the shop actually runs rather than a generic SaaS checklist.