Selling to Government: Purchase Order, Delivery and Payment Evidence

A government-order evidence file covering the electronic contract, delivery, inspection, acceptance, CRAC, invoice, deductions and payment follow-up. The objective is to convert a financing, collection or compliance issue into a cash impact, evidence file, accountable owner and dated next action.

What the business should understand

• A GeM purchase order is an electronic contract that incorporates the order and applicable general, special and additional terms.
• Seller acceptance, delivery period, consignee, inspection, warranty, liquidated damages and invoice requirements should be reviewed before dispatch.
• Delivery is not complete merely because goods leave the warehouse; consignee receipt, inspection and acceptance evidence matter.
• CRAC or the applicable acceptance record is central to payment processing under GeM orders.
• MSME delayed-payment rights, contractual remedies and GeM processes should be coordinated rather than treated as unrelated portals.

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