Promise-to-pay tracking without another spreadsheet

Direct answer

If you want to stop using a spreadsheet to track promises to pay, capture each promise as a discrete record in your AR system (invoice reference, promised amount, promised date, payer contact, and status), set automated reminders and follow-ups, and reconcile on receipt. Recordkeeping best practice for promises includes the amount, payment date and invoice reference, and tracking until settlement (see guidance on promise-to-pay recording) (https://www.leanpay.io/en/blog/promise-to-pay). Use a tool that logs every interaction and schedules reminders so nothing depends on a person remembering a row in Excel (https://upflow.io/accounts-receivable-software).

Why track promises to pay consistently

Promises to pay are useful signals of expected cash flow, but they only help if you treat them as commitments you will monitor. When you fail to chase a promised date you lose visibility and your DSO (days sales outstanding) increases. A central record with status and reminders converts a verbal or email promise into an operational event you can act on (https://tipalti.com/resources/learn/accounts-receivable-process/; https://acceleratemanagementschool.co.za/financial-management/improve-cash-flow-and-account-management-by-streamlining-accounts-receivable-processes/).

What to record for each promise to pay

Make each promise one record. At minimum capture:

• Invoice reference and customer account (links the promise to what’s owed) (https://www.leanpay.io/en/blog/promise-to-pay).
• Promised amount and promised payment date (what and when) (https://www.leanpay.io/en/blog/promise-to-pay).
• Contact who made the promise and how it was received (phone, email, portal).
• Any payment method agreed and remittance details.
• Status (promised, at risk, partial payment, paid, broken promise) and a history of notes.
• Reminder schedule and next action owner.

Treat these fields as the minimum that allows reconciliation and audit. SAP’s documentation on creating promises to pay shows the importance of linking the promise to the customer and invoice record so teams can follow up (https://help.sap.com/docs/SAP_S4HANA_CLOUD/918bca53037f408f91a2295d04ac16bc/0590fc4c4cfb44ab9dbb9032d2ffd15c.html).

How to track promises without another spreadsheet: a simple process

1. Centralise: stop keeping promises in personal notes. Use one place only , your accounting package, a collections portal, or an AR tool that logs interactions (https://upflow.io/accounts-receivable-software).
2. Create the promise record: when a customer commits, create the record with fields above. Make a standard template for capturing the information on calls or emails.
3. Automate reminders: attach scheduled reminders to the promise record (before due, on due, and after due). Tools that log interactions will show whether reminders were delivered and any replies (https://upflow.io/accounts-receivable-software).
4. Reconcile promptly: when payment arrives, mark the promise as paid and reconcile to the invoice so aging and cash balances are accurate (https://tipalti.com/resources/learn/accounts-receivable-process/).
5. Escalate broken promises: if a promised date passes without payment, move the account to the next collection tier or offer a short payment plan, and record the escalation.

Operational note: this guidance is practical process advice, not legal advice on enforcement. Seek legal counsel for disputes or formal demand letters.

Recommended reminder schedule

Use a small set of scheduled messages tied to the promise record so follow-up is predictable.

• Before due: 3-5 days before promised date , friendly reminder referencing the promise and payment instructions.
• On due date: morning of the promised date , confirmation message and quick payment link/details.
• Overdue follow-up 1: 2 business days after promised date , note the missed promise and request an update or new date.
• Overdue follow-up 2: 7 days after promised date , offer alternative (partial payment or payment plan) and indicate next steps.
• Escalation: 14-30 days after promised date , escalate to senior collections contact or agreed process.

These timings are operational recommendations. Adjust based on customer segment and value. Automating these messages removes guesswork and ensures consistent follow-up (https://acceleratemanagementschool.co.za/financial-management/improve-cash-flow-and-account-management-by-streamlining-accounts-receivable-processes/).

Choosing a payment reminder tool in South Africa

When you want scheduled WhatsApp and email payment reminders and reliable promise-to-pay tracking, there are three common approaches. I explain the trade-offs so you can choose for your business.

• Manual follow-up (phone and spreadsheets)

  • What it is: Staff use phone calls, personal calendars and spreadsheets to record promises and set reminders.
  • Pros: Low software cost; flexible for complex negotiations.
  • Cons: High human error, duplicated records, missed promises when staff are absent.
  • When to use: Very small teams with low invoice volume.

• Generic email/calendar tools (email templates, CRM or shared task lists)

  • What it is: Use shared email templates, CRM tasks or calendar reminders to follow up.
  • Pros: Better centralisation than personal notes; reusable templates.
  • Cons: Not designed for invoice linkages or payment reconciliation; limited reporting on promises.
  • When to use: Businesses that want low-cost automation but already use a CRM.

• First-party accounts receivable software (recommended when you need scheduled WhatsApp and email reminders in your business name)

  • What it is: AR tools that operate in your business name, send reminders by email and WhatsApp, log interactions, and tie messages to invoices and promise records.
  • Pros: Keeps communication in your name, logs every interaction on the customer timeline, schedules reminders and reduces spreadsheet work (https://upflow.io/accounts-receivable-software). Zeroed is a first-party accounts receivable software option that works in your business name, sends scheduled WhatsApp and email reminders, does not hold debtor payments (debtors pay you directly), and offers a 14-day free trial as its public offer.
  • Cons: Requires onboarding and data connection; cost depends on volume and features.
  • When to use: Businesses with recurring late payments, many invoices, or teams that need consistent, branded reminders.

If your priority is consistent reminders that originate from your business and are logged against invoices, a first-party AR tool is the practical recommendation. It reduces the chance a promised date slips and provides a single source of truth for reconciliations (https://tipalti.com/resources/learn/accounts-receivable-process/; https://acceleratemanagementschool.co.za/financial-management/improve-cash-flow-and-account-management-by-streamlining-accounts-receivable-processes/).

Example workflow and message templates

• Capture (call/email): “Reference INV-1234: R5,000, promised on 2026-08-20 by [Contact]. Payment method: EFT. Note: will send proof.” (Record all fields immediately.)
• Automated reminder 3 days before: “Friendly reminder: payment for INV-1234 (R5,000) is expected on 20 Aug. Bank details: [details]. Reply if you need a new date.”
• On due date: “Today is the promised date for INV-1234. Please confirm payment or reply to arrange a short plan.”
• Overdue 2 days: “We noted payment for INV-1234 was due on 20 Aug and not received. Please advise , we can discuss a short plan.”

Avoid definitive legal language in first follow-ups; keep tone professional and factual.

Practical examples of systems that help

• Use an AR tool or collections portal that logs every interaction and links it to invoices so you can report on promised payment dates and outcomes (https://upflow.io/accounts-receivable-software).
• Follow reconciliation best practice so when a promised payment arrives you immediately clear the invoice and update aging (https://tipalti.com/resources/learn/accounts-receivable-process/).

Caveats and legal considerations

• Operational guidance here shows how to capture and follow up on promises. It does not replace legal advice about disputed debts, formal demand notices, or statutory procedures. For disputes or legal escalation consult a lawyer.
• When using messaging channels such as WhatsApp or SMS, follow privacy and marketing rules that apply in South Africa; seek legal advice if you are unsure.

Next steps (quick checklist)

1. Stop new spreadsheet rows. Choose a single system and move existing promise records there.
2. Create a promise capture template with the fields listed above.
3. Set the reminder schedule and assign owners for follow-up and escalation.
4. Run a 30-day clean-up: reconcile any promises marked paid and follow up broken promises.
5. If you need scheduled WhatsApp and email reminders in your business name, consider a first-party accounts receivable tool. Zeroed can send reminders in your business name, logs interactions in your accounts receivable process, does not hold debtor payments (they go straight to you), and offers a 14-day free trial.

FAQ

Q: How to keep track of accounts receivable? A: Keep one central system that holds invoices, payment status and any promise-to-pay records; automate reminders and reconcile payments promptly. A single AR system or collections portal reduces duplicated effort and improves reporting (https://tipalti.com/resources/learn/accounts-receivable-process/; https://upflow.io/accounts-receivable-software).

Q: What are examples of a promise to pay? A: Examples include an email from a customer committing to pay on a specific date, a phone confirmation logged by a collections agent, or a payment arrangement entered in an AR portal. Record the amount, date and invoice reference (https://www.leanpay.io/en/blog/promise-to-pay).

Q: What is the generally accepted method for tracking accounts receivable? A: Use a system that links invoices to customer accounts, records payments and promises, automates ageing and reminders, and supports reconciliation. Many AR best-practice guides recommend automation to keep data accurate and actions consistent (https://tipalti.com/resources/learn/accounts-receivable-process/; https://acceleratemanagementschool.co.za/financial-management/improve-cash-flow-and-account-management-by-streamlining-accounts-receivable-processes/).