Why teams add Dunwright on top of QuickBooks.
Every small service business using QuickBooks is a Dunwright candidate. QuickBooks stays the ledger of record; Dunwright runs the chasing + dunning + settlement layer QuickBooks itself does not.
Side by side
What Dunwright adds on top of QuickBooks.
QuickBooks is the ledger of record; Dunwright is the chasing and dunning layer. Each row names the artifact a Dunwright trial would walk you through.
| Capability | Dunwright | QuickBooks Online |
|---|---|---|
| Always-on dunning | DunningSequence model + editor at /app/sequences; nightly cron `dunning-sender` at 0 2 * * * (polsia.toml) walks the queue and delivers. | No native dunning sequence — QB Online invoices are sent once or on a manual reminder; no email/SMS escalation ladder. |
| Ledger of record | Reads QB Online so the dunning queue is exactly what is currently overdue; never duplicates the chart of accounts. | Source of truth for invoices, customers, payments, and chart of accounts. |
| TCPA / CAN-SPAM quiet hours | ComplianceSettings.quietHoursStart/End per owner (default 21:00–09:00, HH:MM, wall-clock); editor at /app/settings; dunning-sender holds every send that would land inside the window. | No TCPA-aware send window in the QB Online invoice workflow; reminder cadence is operator-driven. |
| Stripe settlement write-back | /api/stripe-billing/verify receives the cleared payment and writes it back to the matching Invoice; short-pays and partial splits are flagged inline. | Bank-feed reconciliation only — cleared card payments match by amount, not by invoice id; partial splits buried in a weekly reconcile job. |
| Daily cash digest | DigestRun model with per-owner lastSentAt cursor; cron `daily-digest` at 0 7 * * *; Slack-delivered summary of what fired overnight. | No native daily AR digest; visibility limited to QB dashboard widgets and ad-hoc reports. |
Every Dunwright cell above maps to a shipped feature: a Prisma model, a cron in polsia.toml, or a route handler you can audit in the repo.
See the full feature rundown on the features page.
How it works
Three steps, QB at the center.
01
QuickBooks stays the ledger of record.
Dunwright reads the same overdue-invoice set QB Online holds. No duplicate chart of accounts, no parallel customer records.
02
The nightly `dunning-sender` cron walks the queue.
The DunningSequence model at /app/sequences holds the four-step ladder; polsia.toml schedules the cron at 0 2 * * *. TCPA quiet hours from ComplianceSettings gate every send before it leaves.
03
Stripe settlement writes back through `/api/stripe-billing/verify`.
Cleared payments hit the matching Invoice by id; short-pays and partial splits are flagged inline on the row rather than buried in a weekly reconcile job.
Why teams switch
The first week is where the gap opens up.
QuickBooks Online is great at holding the ledger — invoices, customers, payments, chart of accounts. What it does not run is the chasing itself. TheDunningSequenceeditor at/app/sequencesholds the four-step ladder; the nightlydunning-sendercron at0 2 * * *walks the queue while the team sleeps, applies the template + channel + offset, and writes a per-customer escalation row so the morning inbox shows what actually fired.
Reconciliation is where the second gap appears. QuickBooks Online stays the ledger of record and Dunwright reads it so the dunning queue is exactly what’s currently overdue — not what an export said last night. Stripe settlement flows back through/api/stripe-billing/verify, which writes the cleared payment to the matching invoice; short pays and partial splits are flagged inline rather than buried in a weekly reconciliation report.
The third piece is the morning digest and the quiet-hours window that keeps it safe. Thedaily-digestcron at0 7 * * *reads the per-ownerDigestRun.lastSentAtcursor and delivers the summary to Slack — and theComplianceSettingseditor at/app/settingsgates every send inside the owner’s quiet window before it ever reaches the customer.
Ready to add Dunwright on top of QB?
Pick the plan that fits your week.
No seat fees, no per-invoice penalty, no commitment — cancel from the dashboard any time.
Prefer email? dunwright-5@polsia.app.
Compare with
Two more side-by-side reads.
QuickBooks accounts receivable is one of three comparisons in the /vs/ tree. The other two answer adjacent questions for teams shopping their collections layer.
Browse all alternativesLedgerUp
Dunwright vs LedgerUp.
Always-on dunning, QuickBooks-native reconciliation, the daily cash digest, TCPA quiet hours, and per-account pricing with no seat fees.
Read the LedgerUp comparisonParaglide
Dunwright vs Paraglide.
Paraglide is a customer-success / health-score tool, not a collections product. Dunwright adds the aging-report dunning ladder, Stripe settlement write-back, and the daily cash digest Paraglide does not.
Read the Paraglide comparison