Selling to Government: Purchase Order, Delivery and Payment Evidence

Government orders feel like the safest sale a small business can win — a real buyer, a published rate, no negotiation on price — right up until payment stalls on a technicality nobody flagged at dispatch: the wrong consignee, a missing inspection certificate, an acceptance record that was never generated. This file exists to catch those technicalities before they cost you the payment cycle.

What the business should understand

• The order itself is a stack of documents, not one page: the General Terms and Conditions (GTC) apply to every GeM order by default, Special Terms and Conditions (STC) are category-specific, and Additional Terms and Conditions (ATC) are buyer-specific for that one order — a clause you assumed was standard may have been overridden by the ATC for this particular buyer.
• Liquidated damages for late delivery are usually deducted automatically from the payment due, not billed separately — so a delivery that looks “paid in full eventually” can still have quietly lost margin to an LD deduction that was never explained line-by-line.
• The consignee named in the order, not the buyer’s head office or procurement contact, is who must actually receive and inspect the goods — delivering to the right department at the wrong physical consignee address is treated the same as non-delivery for acceptance purposes.
• Payment timelines run from the CRAC (Consignee Receipt and Acceptance Certificate) or equivalent acceptance date, not the invoice date or the dispatch date — chasing payment by counting days from the invoice alone will consistently understate how much time the department still legitimately has.
• MSMEs registered under Udyam retain their MSMED Act delayed-payment rights on a GeM order exactly as on any other sale — GeM’s own portal timelines and the statutory delayed-payment remedy run in parallel, and using one does not waive the other.

For the connected rule, example or next step, see Tax Payment Challan Mistake: Year, Minor Head and Correction Evidence.

The five-point review

Practical example

How to apply the framework

Start from the live legal and commercial record

Verify the legal entity, current Udyam status, customer or lender identity, contract, sanction, purchase order, invoice and portal record. A spreadsheet or certificate stored at incorporation does not prove that the enterprise, category, activity, buyer, facility or claim remains current. Match names, PAN, GSTIN, bank details, dates and authorised users before money moves.

Reconcile the operating evidence

Connect purchase order, delivery or service completion, acceptance, invoice, credit note, customer ledger, GST reporting and bank receipt. For a bank facility, connect the sanction to eligible inventory, receivables, creditors, insurance and monthly submissions. Differences should be explained through a written bridge rather than hidden in a round number.

Quantify cash before choosing the remedy

Show when cash leaves and when it is realistically expected to return. Include payroll, GST, TDS, debt service, critical suppliers and minimum operating cash. Compare a base case with customer delay, lower sales, margin compression or loss of drawing power. A profitable order can still be dangerous when tax, inventory and financing are funded months before collection.

Use the current portal, scheme and contract

New delayed-payment applications should follow the current MSME ODR workflow while Samadhaan remains relevant for monitoring, reference and legacy matters. Government credit guarantees, MUDRA categories, GeM orders, e-invoice rules and bank facilities do not create automatic approval or payment. The actual sanction, electronic contract, guarantee instrument or insurance policy wording controls the commercial exposure.

Close the loop with proof

Assign one owner, one deadline and one measurable result. Verify buyer acceptance, financier settlement, lender statement, portal conversion, signed restructuring, tax filing or actual bank credit. An application number, email promise, provisional bid, stock statement or unsigned settlement should not be reported as completed.

Implementation checkpoint

Before marking the issue closed, reconcile the final accounting entry, bank movement, GST or tax record, lender or customer ledger and supporting acknowledgement. Record the reference number, date, residual amount, next review date and unresolved exception. Preserve the actual policy wording or instrument terms wherever insurance, guarantee or contingent cover is involved.

Action checklist

• Verify portal users and roles.
• Read the full electronic contract.
• Validate catalogue and bid evidence.
• Control dispatch and consignee proof.
• Secure inspection and acceptance.
• Reconcile invoice, deduction and payment.

Evidence to keep

• Seller profile and user authorisation
• Bid and electronic order
• Delivery and inspection records
• CRAC or acceptance evidence
• Invoice, deduction and payment trail

Warning signs

Finin2min takeaway