Managing Receivables When Your Customers Are Government or PSUs

 If your biggest customers are government departments or PSUs, you already know this truth: sales are guaranteed, but cash is not.

On paper, things look better than before. Delayed payments to Indian businesses have come down to ~₹7.34 lakh crore as of March 2024, lower than previous years. But for MSMEs and mid-sized suppliers, that number hides the real pain, months of capital locked inside “approved but unpaid” invoices, while payroll, GST, and vendors wait every 30 days.

This is where most companies go wrong. They treat government receivables as a patience problem instead of a process problem.

At the same time, something important has changed in the last three years. TReDS financing volumes doubled in FY24, with over ₹1.46 lakh crore worth of invoices financed. That tells us one thing clearly: managing receivables from government and PSUs is no longer about “waiting it out.” It’s about structuring contracts correctly, tracking approvals aggressively, and using financing as a planned cash-flow tool, not a last resort.

This is a step-by-step, operational guide on how Indian companies actually manage receivables when their customers are government bodies or PSUs, without damaging relationships, without legal overreach, and without letting unpaid invoices choke working capital.

How Government & PSU Payment Cycles Actually Work in India

Before you can manage government receivables, you need to understand where your invoice actually travels after delivery, because delays rarely happen at “payment stage.” They happen much earlier, inside approval and routing layers that most vendors don’t actively track.

Once goods or services are delivered, a government or PSU invoice typically moves through five internal checkpoints:

1. Delivery & Acceptance: Goods/services are delivered to the consignee or user department.
2. CRAC / SDAC Generation (Acceptance Certificate)
   • For goods: CRAC (Consignee Receipt & Acceptance Certificate)
   • For services: SDAC (Service Delivery & Acceptance Certificate)

This confirms that delivery meets contract terms.

1. Departmental Finance Verification: Internal finance checks invoice accuracy, GST compliance, PO linkage, and budget head.
2. DDO / PAO Routing
   • DDO (Drawing & Disbursing Officer) initiates payment
   • PAO (Pay & Accounts Office) authorizes and releases funds
3. Treasury / Bank Release: Final disbursement through government treasury systems or PSU banking channels.

Key reality: Your invoice is “approved” long before it is “paid.” The longest delays happen between acceptance (CRAC/SDAC) and finance/PAO clearance, not at the bank.

GeM as the Canonical

The Government e-Marketplace (GeM) is often cited as proof that government payments are now fast—and technically, that’s true.

According to GeM SOPs and manuals:

• CRAC is auto-generated once delivery is confirmed (or after a defined timeline if no objection is raised).
• Payment is expected within 10–15 working days after CRAC generation.

However, in practice, many vendors experience:

• 30–45 day payment cycles, even after CRAC is visible on the portal.

Why?

Because CRAC alone does not trigger payment. It only unlocks the next layers:

• Departmental finance verification
• Budget availability confirmation
• PAO routing and scheduling

A single missing document, incorrect GST breakup, mismatch between PO and invoice, or delayed consignee confirmation can quietly stall the file without any automated alert to the vendor.

This is why vendors often say:

“The CRAC is done, but payment hasn’t moved.”

They’re right. But incomplete.

How to Manage Receivables When Your Customers Are Government or PSUs

When your customers are government bodies or PSUs, receivables are driven by process, not payment terms. Approval cycles, documentation checks, and administrative delays stretch cash inflows beyond control. Managing receivables here means designing systems that absorb delays without breaking working capital.

Step 1: Set Up the Contract to Protect Your Receivables

Government receivable delays usually begin at the contract stage, not during payment follow-ups.

Your contract or PO must clearly define how acceptance happens, because payment does not move without CRAC (for goods) or SDAC (for services). Specify who issues the acceptance, how soon after delivery, and what counts as deemed acceptance if no objections are raised. On non-GeM PSU contracts, this is often manual, and ambiguity here directly causes payment stalls.

Avoid vague clauses like “30 days from invoice.” Instead, define payment timelines from CRAC/SDAC issuance, since that is the real trigger in government systems.

Also identify who actually pays, department, PSU finance, or PAO and whether treasury routing applies. Escalations only work when directed correctly.

Where possible, include delay-protection clauses (statutory references, escalation rights, or supply suspension thresholds). You may not enforce them often, but their presence changes internal priority.

Step 2: Prepare a Government-Ready Invoicing Process

In government and PSU contracts, payment speed is decided by invoice accuracy. Even on GeM, where CRAC can be auto-generated, invoice–PO mismatches are the most common reason payments slip from the expected 10–15 days to 30–45 days.

A “government-ready” invoice is not a standard commercial invoice. It must survive system validation, finance scrutiny, and PAO checks without manual intervention.

Use this checklist before submission:

• Correct PO / Work Order reference (exact match to system entry)
• Unique invoice serial number (as per GST rules)
• HSN/SAC codes aligned with PO line items
• GSTIN of buyer & seller (correct registration type)
• Clear tax breakup (CGST/SGST/IGST as applicable)
• CRAC / SDAC reference (or delivery confirmation linkage)
• Delivery challan / service completion proof
• Digitally signed invoice PDF
• TDS deduction fields (where applicable)
• Correct bank details matching vendor master
• Department contact person / consignee details
• Any mandated annexures or compliance declarations

Step 3: Track Each Invoice Through the Government Approval Chain

Once an invoice is submitted, waiting without tracking is the fastest way to lose control. Government payments don’t fail, they stall inside approval queues unless actively monitored.

At minimum, your tracker should capture:

• Invoice number
• PO / Work Order reference
• Submission date & portal used (GeM / departmental)
• PRC / CRAC / SDAC reference number
• Current stage (consignee, finance, PAO/DDO, treasury)
• Last movement date
• Next escalation date
• Internal owner responsible

This ensures accountability on your side before you demand it from the buyer.

Step 4: Follow Up Without Damaging Government Relationships

Government follow-ups fail when vendors escalate emotionally or skip levels. The goal is to move the file forward, not to corner the officer.

Correct Order of Escalation:

1. Technical / Consignee Officer – acceptance or CRAC delay
2. Buyer Admin (GeM) / Department Nodal Officer – workflow blockage
3. Finance / PAO / DDO – payment authorization delay
4. MSME Samadhaan / MSEFC (only if MSME & statutory limits crossed)

Escalate sequentially, with documented gaps of 7–10 working days.

An example of a Formal Payment Reminder (Finance / PAO – MSME)

Subject: Payment Pending Beyond Statutory Timeline – Invoice [No.]
Dear Sir/Madam,
Payment for Invoice [No.], CRAC ref [No.], dated [date], remains outstanding for [X] days.
As an MSME supplier, this falls under the MSME Act payment provisions.
We request status confirmation or expected release date.
Regards,
[Name]

If payment crosses statutory limits and process follow-ups fail, MSME Samadhaan provides a structured escalation route. Councils are mandated to resolve cases within 90 days, but documentation quality decides speed.

Step 5: Use Legal Protection When Payments Cross Statutory Limits

Legal escalation should be strategic. Used correctly, it accelerates payment; used prematurely, it freezes relationships.

Under the MSMED Act:

• Buyers must pay within 45 days of acceptance (CRAC/SDAC)
• Delays attract interest at 3× the RBI bank rate
• Disputes fall under MSEFC jurisdiction, filed via the MSME Samadhaan portal

Councils are mandated to resolve cases within 90 days, though timelines depend on documentation quality.

Section 43B(h) disallows buyers from claiming expense deductions if MSME payments are delayed beyond statutory limits. This has made finance teams far more responsive once formal notice is issued.

Step 6: Bridge Cash Flow Gaps Using Receivable Financing

When government payments stretch beyond plan, the question you should ask is whether waiting is costing you more than financing. 

Evaluate Your Financing Options:

• TReDS platforms (M1xchange, RXIL, InvoiceMart)
• Invoice discounting (bank/NBFC-backed)
• Bank OD / CC limits
• Supply-chain finance (buyer-led, limited availability)

TReDS has become mainstream, over ₹1.46 lakh crore financed in FY24, with volumes doubling year-on-year, backed by SIDBI and PSU participation. Availability is no longer the constraint.

If financing cost < opportunity cost of funds + penalty risk, finance the invoice.

For repeat government work, build expected financing cost into bid pricing instead of absorbing it later.

Step 7: Build Internal Controls for Government Receivables

Government receivables fail when they’re treated like regular trade AR. They need separate controls, separate reviews, and separate accountability.

Set Up the Right Controls. At a minimum:

• Create a separate AR bucket for Government & PSU customers
• Track DSO separately (Govt vs private customers)
• Assign invoice-level ownership (one person accountable per file)
• Enforce internal SLAs for CRAC, escalation, and financing decisions
• Maintain a document retention pack (PO, CRAC/SDAC, invoices, emails) for each invoice

This structure aligns with how MSME Samadhaan and councils assess cases; missing records weaken recoverability.

Step 8: Pause Supply When Receivables Become Unsafe

Continuing supply in the face of mounting unpaid dues is not professionalism—it is unpriced credit risk. Government vendors often fail not because payments stop, but because they don’t stop supply in time.

Adopt a written policy to pause new deliveries when all three conditions are met:

• >30% of total contract value remains unpaid
• Oldest invoice exceeds 120 days
• CRAC / SDAC or acceptance certification is pending or disputed

Any exception must be approved at CEO/CFO level, with documented risk justification.

How to Communicate:

Use factual, non-confrontational language, never threats.

Suspend Delivery Email (Example)

Subject: Temporary Suspension of Further Deliveries – PO [No.]
Dear [Authority],
As of today, payments against Invoice(s) [Nos.] totaling ₹[amount] remain outstanding beyond agreed timelines, with acceptance pending for [reference].
Until dues are regularised or certification is completed, we are pausing further deliveries under the PO to manage contractual and audit compliance.
We remain ready to resume immediately upon resolution.
Regards,
[Name]

Recent state-level contractor disputes and public warnings over unpaid government dues show a clear pattern: supply pauses trigger resolution when follow-ups fail. Governments respond faster to operational risk than reminders.

Conclusion

If government and PSU customers are part of your revenue mix, receivables cannot be “managed later.” They must be designed, tracked, financed, and enforced from day one.

This article showed one thing clearly:

• Delays are predictable
• The approval chain is knowable
• Cash-flow risk is manageable, if treated as a system, not a follow-up task

Most companies don’t fail because payments stop. They fail because:

• Contracts aren’t structured for acceptance,
• Invoices aren’t government-ready,
• Approvals aren’t tracked,
• Escalation comes too late,
• And cash gaps are left unmanaged.

At CFOSME, we work as CFO partners for MSMEs dealing with exactly this problem, government-heavy receivables, long cycles, and cash pressure. We help clients build these controls into operations, not chase payments reactively.

If government receivables are straining your working capital, a short consultation can help you see where the leak actually is and how to fix it.

Talk to a CFOSME expert. Before receivables start deciding your business for you.