How to track a promise to pay without losing the next follow-up
Turn “we’ll pay Friday” into a clear record with amount, date, approval, verification, and ownership. Includes a payment commitment log and follow-up examples.
Track a payment promise as a specific amount, payment date, invoice, contact, approval state, and next review action. A promise is not a payment: keep the invoice open until the receipt is verified, and stop generic reminders while an approved commitment is being monitored.
What counts as a useful promise to pay?
“We’re working on it” is an update. “We will pay $1,850 against invoice #1103 on November 6” is a specific commitment that can be checked. Both belong in the account history, but only the second gives the team a clear verification date.
Ask for the missing detail without turning the exchange into an interrogation. If the client says Friday, confirm the calendar date. If the client says “a payment,” confirm whether it covers the full balance or a partial amount.
Also distinguish what the client proposes from what your firm has accepted. Staff may be authorized to acknowledge a request but not to extend terms or approve an installment plan. That approval status should be visible to anyone who might contact the client next.
A payment commitment log you can copy
| Field | Fictional example |
|---|---|
| Client and invoice | Westbrook · #1103 |
| Outstanding invoice balance | $1,850 |
| Amount promised | $1,850 |
| Proposed payment date | November 6, 2026 |
| Client contact | Authorized billing contact |
| Approval state | Approved by account owner |
| Source | Client email, October 29 |
| Next action | Verify payment after the agreed date |
| Internal owner | Billing coordinator |
| Outcome | Pending verification |
Keep the original email or call note linked to the record. Someone reviewing the account should be able to see what was actually said, rather than relying on a shortened note that leaves out conditions.
The log is an operating record, not a replacement for the invoice or your accounting system. Do not erase the original due date to make the balance appear current unless an authorized change has been made through the correct process.
Confirm the agreement in one clear message
Once the responsible person approves the proposed arrangement, send a short confirmation:
Hi [name],
Confirming our agreement for payment of [amount] against invoice [number] on [date]. Your payment link is [link].
We’ll check the payment record after that date. If anything changes, please let us know.
If approval is still pending, say so. “I’ve recorded your request and will confirm with our account owner” is different from “That’s fine.” The difference matters when other systems decide whether to keep sending reminders.
For a partial payment, state the amount covered by this commitment and what remains to be decided. Do not imply that paying part of an invoice automatically settles the balance.
What should reminders do while you wait?
Pause the generic overdue sequence for the approved commitment and create a specific verification task. The invoice should remain visible as outstanding, with the commitment attached, so a paused reminder does not become a forgotten account.
Set a review date that reflects the payment method and the agreed terms. Payment initiation and settled receipt may occur at different times. The team should know whether it is waiting for a transfer to appear or for the client to act.
One shared record is important. If the billing system, a staff spreadsheet, and an outside service each have their own reminder schedule, an approved extension in one place may not stop the others. Decide which system controls outreach and how updates reach it.
What to do when the promised date passes
Check the payment record first. Look for an unmatched receipt, a partial payment, or a reference that differs from the invoice number. If payment cannot be verified, contact the client about the specific commitment:
Hi [name], we had noted [date] for payment of [amount] against invoice [number]. Our records still show the amount outstanding. Has payment been sent, or is there something we should review?
Record the response and route any new request to the appropriate owner. Do not silently roll the promise forward each week. Repeated changes should be visible so a person can decide whether the current plan still makes sense.
If the client raises a dispute, move the account into a review state. A payment-promise workflow should not keep treating a disputed bill as a simple missed date.
Measure promises kept, not promises collected
Track the amount promised, amount actually received, and whether it arrived within the defined window. Specify your measurement rule: an installment paid in full is different from an invoice paid in full.
For an illustrative group of ten commitments, eight fulfilled commitments would produce an 80% commitment-completion rate under that definition. This says nothing by itself about the total dollars recovered; one unfulfilled large commitment can outweigh several small ones. Look at both count and value.
The broader aging report should still show the outstanding exposure. A promise is useful context for the next action, not a reason to count the cash early.
Where Cake fits
Cake is being built to bring client commitments forward, follow an approved plan, and check for payment. The intended handoff is specific: a person approves a decision, while the agent maintains the next action and checks the outcome. BillCake’s current examples are simulated, and integrations remain planned.