Collecting past-due invoices from QuickBooks Online

The problem

Why the invoice gets written off

A business invoices a commercial customer for $14,000. The customer does not pay. The creditor calls, sends reminders, then hands it to outside counsel for a demand letter.

The attorney quotes $3,500 to $8,000 to send the demand, file suit if necessary, and see it through. On a $14,000 claim, that is a loss before accounting for the possibility of losing. So the invoice goes to bad debt. The creditor absorbs it. The customer keeps the money.

This is not a collection problem. It is a cost problem. The claim may be entirely valid. The contract may have been breached in every sense. The debtor may have no real defense. None of that matters when the cost to collect exceeds what collection returns.

Most QuickBooks users with commercial accounts receivable have a column of these in their aging reports. They sit there past 90, 120, 180 days because no economically rational next step exists.

The provision that changes the math

The clause that is already in the contract

Many commercial contracts contain a fee-shifting or prevailing-party clause — a provision that moves attorney fees, collection costs, or both from the creditor to the debtor if the creditor has to enforce the agreement. When one of these provisions is present and reachable, the creditor’s enforcement cost disappears from the creditor’s ledger. The claim that was economically irrational to pursue becomes economical.

Beyond the contract, some claims carry statutory rights that attach by operation of law: prompt-payment acts for construction and government work, mechanics lien rights, payment-bond claims. These do not require a clause in the agreement at all. On the right facts they are as powerful as anything the parties negotiated — and they go unread for the same reason the contract clause does, because reading every agreement by hand costs more than the claims are worth.

The workflow problem

The contract never gets read

Even a business that knows fee-shifting provisions exist does not read every contract against every aging invoice. A typical commercial creditor might have dozens of active accounts at any time, each governed by a different agreement, each in a different state with different statutory rules. Reading them all by hand, against the right jurisdictional law, checking the statute of limitations before every demand — that is itself a legal engagement, billed by the hour.

So the provisions sit unread. The invoices age. The accounts go to bad debt.

QuickBooks Online

How the connection works

Stipulate connects to QuickBooks Online through a standard OAuth authorization. After connecting, a threshold is set — the number of days past due at which the engine should run on a given account. When an invoice in the connected company passes that threshold, the engine reads the governing contract, checks the claim for fee-shifting leverage and applicable statutory rights, checks the statute of limitations, and produces the demand letter.

The letter goes into the creditor’s Stipulate account, addressed in the creditor’s name, referencing the specific provision found in the specific agreement. The creditor reviews it, signs it, and sends it. Nothing in the letter names Stipulate. The demand is the creditor’s own.

What it reads

Coverage across all 51 jurisdictions

Stipulate reads for the full range of provision types — prevailing-party and fee-shifting clauses, attorney-fee provisions, collection-cost language, contractual interest terms, and the venue and notice conditions that govern whether any of it can be invoked. On the statutory side it reads for prompt-payment acts, mechanics lien rights, and payment-bond claims where the facts support them.

Every finding includes the governing citation so it can be verified. Where the deadline cannot be established with certainty, the engine routes the account to a person rather than guessing. A claim near a deadline should be reviewed by counsel; the engine says so rather than drafting a letter that might be sent too late.

More on what it reads for and how it reports →