When a Government Payment Is Late: The Escalation Path That Works

A certified bill that is not being paid is a different problem from a bill stuck in process, and it has a different remedy. Getting the diagnosis right first saves months.

First, establish where it is

Before escalating, find out which stage the bill has actually reached:

• Not measured. Not a payment problem. Request measurement in writing. See running account bills.
• Measured, not checked. A process problem, resolved by follow-up.
• Checked, not passed. Usually a query, a document, or a budget question.
• Passed, not paid. A payment problem, and the escalation below applies.

Escalating a bill that has not been measured wastes the escalation. Departments respond to specific, correct requests.

The escalation path

In order, in writing at every stage, keeping copies:

1. The engineer in charge. A written request stating the bill number, date submitted, amount, the stage reached, and asking for the position.

2. The head of the office or the executive engineer. Attaching the first letter, noting the interval.

3. The next administrative level, and the accounts officer in parallel where the bill is at accounts.

4. The department's grievance mechanism, where one is published. See the grievance route and its limits.

Most matters resolve at step one or two. The reason to do step one properly is that steps three and four are only as strong as the record behind them.

The MSME route

This is the most consequential difference between a registered and an unregistered supplier, and it is why Udyam registration matters after award and not only at bid stage.

A registered micro or small enterprise has a statutory route in respect of delayed payment for goods supplied or services rendered, under the Micro, Small and Medium Enterprises Development Act 2006. The Act provides for payment within a stated period and for interest on delayed payment, and provides a facilitation council mechanism for reference of disputes.

The MSME Samadhaan portal is the route through which a registered enterprise files a delayed payment reference.

Two practical points:

Registration must predate the supply for the protection to apply to it. Registering after a payment goes bad does not retrospectively cover it.

The existence of the route changes the negotiation, often before it is used. A buyer aware that a supplier can refer the matter tends to engage differently.

See what Udyam registration is actually worth.

Interest

Where the contract provides for interest on delayed payment, claim it in the correspondence rather than mentioning it later. Where the MSMED Act route applies, the Act's interest provisions are part of what the mechanism addresses.

Contractors rarely claim interest, which is part of why delays persist. A written claim, made early and consistently, is treated differently from a complaint made at the end.

What actually works

Beyond the formal routes, the things that move files:

• Complete submissions. A bill returned for a missing document restarts the clock.
• Specific requests. "Please advise the current stage of RA bill 4 dated [date]" gets a reply. "Please release our pending payments" often does not.
• A named recipient and a copy up one level. Not an accusation, just visibility.
• Persistence at intervals, rather than either silence or daily calls.
• A clean relationship on site. Departments process bills from contractors whose measurements are agreed and whose documentation is complete.

Plan for it in the price

Payment cycles on public contracts are long, and delays are common enough to be a planning assumption rather than an exception. That financing cost belongs in the bid price. See how to price a government tender.

It also belongs in your bid capacity: a firm whose receivables are stretched has less capacity to bid, regardless of its order book.

The related recoveries

Two other pools of your money sit with buyers, on longer timescales and with even less follow-up: retention money and unrefunded EMD. If you are building a follow-up register for one, build it for all three.

Nothing here is legal advice; a specific dispute turns on its own contract. See the disclaimer.

Avsar keeps the position on bills, retention and deposits in one register. See the treasury module.