Broken Promise.
A promise to pay that the customer did not fulfill in the agreed amount or by the agreed date.
Reviewed August 2026 3 minute read
Plain-language definition
What is Broken Promise?
A promise to pay that the customer did not fulfill in the agreed amount or by the agreed date.
Reminders, calls, notices, promises, and documented customer responses. For a small business, the useful question is not only what broken promise means, but which record supports it and what action—if any—should happen next.
- Broken Promise should always point back to a specific customer record, invoice, Account, or reporting period.
- Keep the dates, amounts, source documents, responsible person, and approvals that explain how the label was applied.
- Use broken promise to organize a decision or next step—not as proof that payment or a legal result is certain.
Business context
Why broken promise matters to a small business
Reminders, calls, notices, promises, and documented customer responses. Understanding broken promise helps an owner see how that work affects cash flow and staff time.
A consistent definition lets billing, sales, bookkeeping, and collection staff discuss the same customer facts instead of working from different assumptions.
Clear source records and ownership reduce the risk of inconsistent follow-up or undocumented consequential actions.
Receivables context
What broken promise means in accounts receivable
A promise to pay that the customer did not fulfill in the agreed amount or by the agreed date.
In day-to-day receivables work, use this term only when the underlying invoice, customer, amount, date, and status support it. That keeps reports understandable and prevents staff from treating a label as a substitute for the record.
Operational view
How it works
- 1
Identify the Account condition that makes Broken Promise relevant and verify the current balance and status.
- 2
Use promise recorded to place Broken Promise at the correct point in the collection workflow.
- 3
Prepare payment due from approved facts and require authorization for any consequential communication.
- 4
Record promise missed, including the date, owner, response, and supporting document.
- 5
Set next action approved so the Account never loses a dated next required action.
Worked illustration
Broken Promise in a small-business example
Pine Ridge Landscaping has a $15,450 invoice that is 82 days past due. The owner assigns the next action, records the customer response, and keeps the account history together.
Result: The business can now explain what Broken Promise means for this record, what evidence supports it, who owns the next step, and what still needs review.
- StartPromise recorded
Promise recorded in the fictional Broken Promise example
- Day 13Payment due
Payment due in the fictional Broken Promise example
- Day 33Promise missed
Promise missed in the fictional Broken Promise example
- Day 69Next action approved
Next action approved in the fictional Broken Promise example
View the accessible data and explanation
| Example point | Illustrative value | How to read it |
|---|---|---|
| Promise recorded | Start | Promise recorded in the fictional Broken Promise example |
| Payment due | Day 13 | Payment due in the fictional Broken Promise example |
| Promise missed | Day 33 | Promise missed in the fictional Broken Promise example |
| Next action approved | Day 69 | Next action approved in the fictional Broken Promise example |
Compare Broken Promise with related terms
Use these plain-English meanings to tell similar accounts-receivable concepts apart.
| Term | What it means in plain English |
|---|---|
| Broken Promise | A promise to pay that the customer did not fulfill in the agreed amount or by the agreed date. |
| Promise to Pay | A customer's documented commitment to pay a specific amount by a specific date. |
| Follow-Up Date | The scheduled date when someone should next review or act on an unpaid account. |
Practical checklist
What a small business owner should do
Use accurate account facts and record the customer’s response.
Record how Broken Promise applies to this Account instead of relying on memory or an undocumented label.
Set the next review date and preserve later corrections as new history.
Practical guardrails
Common mistakes and better practices
Common mistakes
- Using Broken Promise without defining the Account population, time period, or source system.
- Treating a dashboard label as proof when the underlying invoice, payment, or document record has not been reconciled.
- Overwriting history instead of recording a dated correction, reversal, approval, or status change.
- Assuming that a favorable operational indicator guarantees payment, legal enforceability, or a particular accounting result.
Better practices
- Write down the Business’s definition of Broken Promise and use it consistently across teams and reports.
- Assign an owner and a dated review point whenever the concept identifies work that remains open.
- Link the conclusion to source records and preserve an append-only activity and approval history.
- Ask qualified legal, tax, accounting, or financial professionals to review conclusions that require professional judgment.
Related TORO tool: Messages and Document Generator
How TORO Recovery can help
- Where to look
- For Broken Promise, use the Account Workflow together with Tasks, Messages, Letters, and the Account timeline to see the current step and the next required action.
- What you can do
- Review the balance and history, complete or schedule the work, and record the customer's response so the next user has a clear, dated record.
- What TORO does not decide
- TORO may recommend a next step, but a user approves consequential communications, holds, escalations, settlements, referrals, and closures.
Frequently asked questions
Questions about broken promise
Is Broken Promise the same for every Business?
The core concept may be widely used, but policies, systems, contracts, industries, and jurisdictions can change how a Business applies it. Document the definition and scope used in your organization.
Does Broken Promise predict whether an Account will be collected?
No. It can provide useful operational context, but collection outcomes depend on the debtor, documentation, disputes, timing, execution, applicable law, and other circumstances.
What records should support Broken Promise?
Use the records relevant to the concept, such as invoices, agreements, delivery evidence, customer communications, payment activity, approvals, and reconciled ledger data. Avoid collecting information that is not necessary for the Business purpose.
How can TORO Recovery help with Broken Promise?
TORO can organize Receivables, Account activity, Tasks, documents, messages, payments, disputes, Settlement Plans, reporting, and approved Attorney Handoff workflows where those capabilities are relevant and included in the Business’s subscription.
Sources and review notes
This explanation is educational and uses original TORO Recovery wording. It was last reviewed on August 15, 2026.
Important: This page provides general educational information for U.S. businesses. It is not legal, tax, or accounting advice. Laws and requirements vary, and businesses should consult a qualified professional about their circumstances. TORO Recovery is a technology platform, and reading this page or creating an account does not create an attorney-client relationship.
Put this into practice
Organize your receivables in one clear place
Create a free Business workspace to begin monitoring Receivables and next actions, subject to current Free plan limits. Messages and Document Generator and other advanced tools may require a paid plan.