Your accounts receivable coworker

DSO stands for days sales outstanding — the average number of days it takes the business to collect cash after invoicing. A high DSO means working capital is locked up in unpaid invoices instead of funding payroll, growth, or operations. Cutting DSO in half effectively returns weeks of cash flow to the business without changing pricing or sales volume, which is why finance teams treat it as one of the highest-leverage operational metrics they can move.

Tone and cadence are the whole game. The coworker is built to sound like a thoughtful human, not a dunning bot. It matches tone to the relationship stage, escalates language gradually instead of all at once, and pulls in the account owner before sending anything sensitive. Done well, customers do not experience this as aggressive collections. They experience it as a finance contact who is organized and follows up reliably.

Yes. The team decides where approval is required. Many setups have the coworker send first-touch reminders autonomously and require account-owner or finance-lead approval before later, firmer messages go out. Higher-value invoices or strategic accounts can be gated entirely behind human review. The right boundary depends on the business's tolerance for autonomous action versus the volume of collections work that needs to happen.

The pattern works with whichever system holds the invoices and payment status, including Stripe, QuickBooks, Chargebee, Maxio, Recurly, and several others. The setup adapts to the customer's stack. Multi-system setups (for example, Stripe for self-serve plus QuickBooks for invoiced contracts) are supported by reading from both and reconciling the aging view across them.

The coworker escalates. Disputes, payment plan requests, contract questions, and anything that requires a judgment call get routed to the account owner or finance lead immediately, with the full conversation history attached. Automated dunning is the wrong tool for those situations. The value is in handling the high-volume reliable cadence work so humans have time to handle the exceptions properly.

Yes, as long as the billing system tracks the data in a structured way. The coworker reads invoice currency, customer locale, and any prior correspondence to adjust language, currency formatting, and tone. Time zone is respected when scheduling sends. For regions with specific collection norms or regulations, the cadence and language can be configured per region rather than running one global playbook.

Dunning is the basic version: scheduled reminder emails on a fixed cadence. A coworker handles the surrounding work too, including pulling customer context from the CRM, matching tone to the relationship, looping in account owners, logging every touch, and escalating accounts that need a real conversation. The difference is between a scheduling tool and a coworker who is actually running the collections function.

The cleanest starting point is one billing system, one CRM, and a defined cadence and tone for first-touch and follow-up emails. The first cycle is usually run in shadow mode: the coworker drafts the outreach for review without sending, so finance can sanity-check the tone and timing. After that, it moves into live mode with the team's preferred approval boundaries on higher-value or sensitive accounts.