Writing down every payment promise

This story shows a practical response to every promise on a call goes into a register and is checked the next day.

Before

A written rule changes the choice: write the amount and date of every promise, then check the next working day. The difficulty is applying the rule to real exceptions. The routine depends on the accountant knowing which call, slip or instruction matters. Records exist in Tally customer ledger, invoice copies, credit notes and receipt confirmations, but another person cannot reliably reconstruct the decision. This is the problem behind writing down every payment promise.

A request arrives and somebody responds to the loudest part first. The original source is left in a folder or WhatsApp chat. Later, when the owner or sales manager needs to review it, people reconstruct what happened from memory. The missing piece is often invoice due date, undisputed amount, customer contact, promised date and receipt. By the time it is found, another person has already acted on an assumption.

The cost is visible as interrupted work, repeated checking or a promise that needs correcting. No saving or improvement figure is claimed here. The point is to change one repeatable action so that the next case can be handled without a chain of calls.

Why it was like that

The previous method relies on informal permission and experience. Staff may understand the right thing to do, but not where to record it or who can approve an exception. Adding a shared spreadsheet without clarifying authority would leave the same bottleneck in place.

In this example, the control that is missing is write the amount and date of every promise, then check the next working day. An urgent request can legitimately break the normal rule. The exception still needs a named decision-maker, a reason and a source reference. Otherwise the exception becomes the usual way of working.

The change

The replacement is a one-page daily collections and promise register. Write promised amount, date and payer contact. This is the required check before an instruction moves to the next person. Check bank next day. Finally, escalate broken promises. Each line retains the evidence needed if the decision is challenged later.

Copyable rule for this team

Example register rows, for illustration only:

Reference	Amount (example)	What needs checking	Owner	Next review
S078-01	₹42,000	Write promised amount, date and payer contact	accountant	Next morning
S078-02	₹8,600	check bank next day	owner or sales manager	Before payment

The owner can set a sample limit, but it should be based on actual financial exposure, not copied from another firm. A rule that touches statutory dues, credit, worker pay or electrical safety also needs a qualified reviewer.

After

In the revised composite routine, the first person records the incoming request once. Another team member can see its source, status and next action without recontacting everybody. The owner or sales manager sees only the cases needing judgement. Routine cases move under written delegated authority.

For the specific case in this article, the first visible change is write promised amount, date and payer contact. The next person can then check bank next day. At the end, escalate broken promises. That sequence matters because each part leaves a record that the next role can verify.

A weekly check samples a few entries rather than trusting the tick column. The manager looks for cases marked closed without supporting evidence, repeat exceptions and requests that still depend on the owner. Those are reasons to revise the rule.

What to watch out for

Staff may start filling the register after the event. Check the time and reference against the source.
The authorised manager may approve an exception by phone and forget to record it. Ask for the decision to be added to the same entry.
The team may treat every request as urgent. Compare actual deadlines and commercial or safety effects before changing priority.

Separate disputed balances from undisputed ones. Do not threaten a customer over an unreconciled ledger.

Copy it

Use the table above as a starting point. Replace the example entries with two current cases. Mark unclear evidence as Open, then name the next person to check it. Keep the source record, owner, next review date and reason for any override. An example exposure of ₹42,000 or 12 units is illustrative only; set limits from your own business records.

Start with Payment promise register. If you need the full sequence, use Recording payment promises. Measure open exceptions and missed commitments for four reviews before deciding whether the change holds.