FINANCE & WORKING CAPITAL

Accounts Receivable Management for Indian MSMEs: An Invoice-to-Cash Playbook

A practical system for turning completed work and issued invoices into collected cash: customer credit checks, invoice evidence, ageing, follow-ups, dispute resolution and carefully scoped MSME payment remedies.

Accounts receivable management is the operating system that helps a business convert completed work and issued invoices into money actually received. For an Indian MSME, the practical sequence is simple: agree the buyer and payment terms before work starts, submit a complete invoice pack, confirm acceptance, track each invoice by due date and dispute status, follow up through a named owner, and reconcile every receipt against the right invoice. Eligible micro and small suppliers may also have specific remedies under the MSMED Act, while TReDS can provide a separate invoice-financing route when its participation and acceptance conditions are met. This guide is an operational playbook—not a promise of collection, legal advice or a lending offer.

1. What accounts receivable management actually means

Accounts receivable (AR) is money customers owe for goods supplied or services already delivered on credit. Managing AR is more than sending reminders after an invoice becomes overdue. It begins when the business accepts an order and continues through delivery, customer acceptance, invoicing, approval, collection, bank reconciliation and closure of the balance.

A business can report a sale and still have no cash available to pay salaries, suppliers or tax obligations. Revenue recognition, invoice issue, customer approval and bank receipt are different events. A useful AR process records each event separately so a team can see whether the delay is caused by a missing purchase order, incomplete delivery evidence, a genuine dispute, an internal approval queue or a customer who has simply not paid.

  • Revenue answers what the business has earned under its accounting policy.
  • An invoice records a demand for payment under the agreed commercial and tax process.
  • A receivable is the amount still owed by the customer.
  • A collection is cash received and correctly matched to the invoice.
  • A dispute is an unresolved reason why the customer has withheld or questioned payment; it should have its own owner and action date.

2. Map the invoice-to-cash process before buying software

A small business can begin with an invoice register and a shared follow-up routine. Software is useful only after the business has decided who owns each stage, which evidence proves completion and what should happen when a step is late. If the sales person, delivery team and accounts person each keep a different status, the owner cannot see the real position.

Assign one accountable owner to each stage. In a small team, one person may hold more than one role, but the responsibility still needs to be explicit. Keep commercial approvals separate from the person who changes bank details or marks a receipt as reconciled.

StageAccountable ownerEvidence to retainNext control
Order and credit approvalSales owner / founderAccepted quotation, PO or signed scope; approved payment termsConfirm buyer entity and credit exposure
Delivery or milestoneOperations / project ownerDelivery proof, completion note, timesheet or acceptance record as applicableResolve missing evidence before billing
Invoice submissionAccounts / billing ownerInvoice copy, portal acknowledgement and supporting documentsRecord submission and due dates
Buyer approvalAccount owner with buyer AP contactAcceptance, query, rejection reason or portal statusAssign every query to a named person
Collection and reconciliationAccounts / finance ownerPayment advice, bank credit and invoice allocationClose only after matching the receipt

3. Set payment terms and customer limits before work begins

The cheapest collection problem to solve is the one prevented before the order is accepted. For every credit customer, record the legal buying entity, billing address, GSTIN where relevant, purchase-order requirement, authorised commercial contact, accounts-payable contact, invoice submission method, payment term and dispute route. A large organisation may require a vendor code or portal submission; discovering that after delivery can delay approval even when the work is complete.

Set a credit limit based on the amount the business can safely carry, the customer's payment history, the size of work in progress and the concentration risk if that customer pays late. There is no universal credit-limit formula for every MSME. Treat the limit as an internal approval control, not a statement about the customer's legal creditworthiness.

For new customers or uncertain projects, consider an advance, a mobilisation payment or milestone billing. For recurring work, agree the billing cycle and what counts as an accepted milestone. Any interest, suspension, retention or termination wording should be reviewed for the contract and applicable law before it is used.

  • Identify the exact legal entity that will pay—not only the brand or trading name.
  • Confirm whether a purchase order, work order, vendor code or portal upload is required.
  • Write down the payment period and the event from which it is calculated.
  • Agree who can certify delivery or approve a milestone.
  • Set an internal exposure cap and an approval route for exceptions.
  • Review the terms before extending more credit to a customer with overdue balances.

4. Build an invoice pack that the buyer can approve

An invoice can be accurate and still be delayed because the buyer cannot match it to the order or prove that the work was accepted. Create a standard invoice pack for each customer. Depending on the transaction, that pack may include the invoice, purchase order, delivery challan, e-way bill, signed proof of delivery, service completion note, timesheet, milestone certificate, approved change request or portal acknowledgement.

The invoice itself must follow the GST and other tax requirements that apply to the supplier and transaction. Do not copy another business's invoice format as proof of compliance. Confirm the required particulars, tax treatment, e-invoice applicability and reporting process with the business's tax professional or the official GST system.

Send the pack through the channel the buyer has agreed to use. Save the sent copy, timestamp, recipient and acknowledgement. If a portal rejects the invoice, capture the rejection reason and resubmission date rather than leaving the status as a vague 'sent'.

  • Match the buyer's legal name, GSTIN and billing details to the purchase record where applicable.
  • Check invoice number, date, description, quantity, rate, tax and payment details against the transaction.
  • Attach the PO or work order reference when the buyer requires it.
  • Attach delivery or milestone evidence that is relevant to the contract.
  • Record the portal or email submission acknowledgement.
  • Keep credit notes, debit notes and revised documents linked to the original invoice instead of overwriting history.

5. Maintain one receivables register with the fields that drive action

The AR register should answer five questions quickly: who owes the money, how much is open, when payment is due, why it has not arrived and who will act next. Use one row per invoice or credit note, not one row per customer with several unrelated balances hidden in a comment.

A spreadsheet is enough for a small team if it has controlled access, a clear owner and a regular backup. Protect formula columns, use consistent date formats and avoid storing unnecessary personal information. Do not share the full debtor ledger with staff or external partners who do not need it.

FieldWhy it matters
Customer legal name and account IDIdentifies the debtor consistently across orders, invoices and receipts
Invoice number, invoice date and amountConnects the source document to the open balance
PO / work order and delivery referenceHelps the buyer match the claim to the approved transaction
Submission date and acknowledgementShows when the buyer actually received the invoice pack
Contractual due date and basisPrevents teams from calculating due dates from memory
Outstanding amount and credit notesShows the amount still to be collected after adjustments
Ageing days and dispute codeSeparates overdue time from the reason for non-payment
Buyer AP contact and account ownerMakes follow-up accountable
Last contact, promise-to-pay date and next actionTurns a reminder into a dated commitment
Bank receipt reference and allocation statusPrevents a payment being counted twice or matched to the wrong invoice

6. Use ageing buckets to prioritise—not to make legal conclusions

An ageing report groups unpaid invoices by how long they have remained outstanding. Choose buckets that help the team act, such as not yet due, 1–30 days overdue, 31–60 days overdue, 61–90 days overdue and more than 90 days overdue. These are management categories only; they are not statutory payment deadlines and do not replace the contract or the specific rules that may apply to a qualifying micro or small supplier.

Sort the report by amount, days overdue, customer concentration and whether the invoice is disputed. A small invoice with a missing portal reference may need a quick correction. A large undisputed invoice from a strategic customer may need senior escalation. A disputed invoice needs an evidence owner, not repeated generic reminders.

Internal ageing viewSuggested management actionDo not do this
Not yet dueConfirm invoice receipt and buyer approval path; send a courteous pre-due reminder if appropriateWait until the due date to discover a missing PO
1–30 days overdueAsk for payment status and a specific expected date; identify any AP blockerSend repeated messages without checking the reason
31–60 days overdueEscalate to the account owner and buyer's commercial sponsor; agree a written action planAllow the account to keep growing without an exposure review
61–90 days overdueSenior review of supply, credit exposure, dispute evidence and professional recovery optionsThreaten action that the business is not authorised or prepared to take
More than 90 days overdueReview recoverability, legal advice, accounting treatment and customer relationship riskAssume a reminder alone will resolve the balance

7. Use a consistent, respectful follow-up cadence

A follow-up schedule is a recommended operating routine, not a statutory timetable. Adjust it to the contract, buyer's payment cycle, value of the invoice and relationship. The purpose is to make every open invoice visible and to secure a clear next step—not to overwhelm a customer with daily messages.

Use email for a durable record, a call to understand a blocker and an agreed business messaging channel for a short coordination note. Record the person contacted, the status they gave, any documents requested and the date they committed to. A promise such as 'next week' should be converted into an actual date and a reminder for the account owner.

TimingSuggested actionRecord to update
After invoice submissionConfirm receipt and ask whether the buyer needs any missing documentAcknowledgement and buyer AP contact
Before due dateSend a courteous statement showing invoice number, amount and due dateReminder date and any query raised
On due dateCheck whether payment is scheduled and whether the buyer needs a referencePayment status or reason for hold
1–7 days overdueContact AP, confirm the blocker and request a specific payment dateReason code and promise-to-pay date
8–15 days overdueEscalate internally and involve the commercial contact if AP cannot resolve itEscalation owner and next review date
Beyond 15 days overdueReview exposure, future work, dispute evidence and whether professional advice is neededManagement decision and documented action

8. Separate invoice disputes from collection follow-ups

A disputed invoice should not be treated as an ordinary unpaid invoice. Record the exact issue, who raised it, when it was raised, what evidence is needed and who will resolve it. Common operational reason codes include missing purchase order, quantity mismatch, delivery proof missing, quality query, rate mismatch, incomplete milestone, tax-detail correction, duplicate invoice or buyer portal rejection.

Keep the undisputed and disputed portions visible separately where the contract and accounting records allow. Do not issue a credit note simply to make an ageing report look clean; confirm that a genuine commercial or tax adjustment is required and obtain the appropriate review. If the customer has a valid query, resolve it promptly. If the query is unsupported, respond with the contract and delivery evidence rather than escalating the tone.

A useful dispute log includes invoice ID, disputed amount, reason, date raised, buyer contact, evidence requested, internal owner, response sent, resolution, revised due-date treatment if agreed and final closure reference.

  • Acknowledge the query and repeat it in precise, neutral language.
  • Ask for the clause, PO line or delivery reference the buyer is relying on.
  • Assign one internal owner and a response date.
  • Send the missing evidence or a reasoned explanation.
  • Record any agreed adjustment or revised payment commitment in writing.
  • Keep collection of the undisputed balance moving where commercially and legally appropriate.

9. Measure collection performance with a small dashboard

A useful AR dashboard is small enough to review every week. Start with total open receivables, overdue receivables, disputed amount, top customer exposures, invoices due in the next 14 days, cash collected during the period and invoices with no next action. Add more metrics only when someone uses them to make a decision.

Days Sales Outstanding (DSO) is a common directional measure of how long credit sales take to convert into cash. A simple period-based formula is: average trade receivables divided by net credit sales for the same period, multiplied by the number of days in that period. Use a consistent basis for the receivable and sales figures, understand whether GST is included, and have the accountant confirm the calculation for the business's reporting policy. DSO can be distorted by seasonality, large one-off invoices, cash sales and the choice of average balance.

For example, if a hypothetical business has average trade receivables of ₹6 lakh and net credit sales of ₹15 lakh over a 30-day period, the simple DSO calculation is 12 days. That is an illustration of the formula, not an industry benchmark or a target every business should adopt.

  • Total open AR and total overdue AR.
  • Overdue AR by ageing bucket and by customer.
  • Disputed invoices and the value awaiting customer or internal action.
  • Invoices due in the next 7 and 14 days.
  • Collections received and correctly allocated this week.
  • Invoices without a named owner, last-contact date or next action.
  • DSO trend calculated consistently and interpreted with seasonality in mind.

10. Control customer exposure before it becomes a cash crisis

A customer can be reliable on a small order and still create a dangerous concentration when the business allows several large jobs to remain unpaid. Review the customer's total exposure, not only the oldest invoice. Include open invoices, approved work in progress, goods dispatched but not yet invoiced and any contractual retention that is likely to remain unpaid.

Set an approval trigger for new work when the customer is above the agreed credit limit or has an unresolved dispute. The response may be an advance, a smaller milestone, a revised schedule, a senior approval or a pause allowed by the contract. Do not automatically stop supply or cancel work without checking the contract, service obligations, safety implications and legal advice where needed.

For project businesses, invoice at contractually agreed milestones rather than waiting until all work is complete if the commercial arrangement supports staged billing. For recurring services, agree the billing cycle and evidence of service delivery before the first month begins.

  • Review exposure by customer and related buying entity.
  • Set a named approver for credit-limit exceptions.
  • Do not count a purchase order as cash or as a confirmed collection.
  • Separate signed work from proposals and verbal opportunities.
  • Review customer concentration before accepting a large low-margin order.
  • Document any change to payment terms before the additional work is performed.

11. Know when the MSMED Act delayed-payment provisions may apply

Sections 15–24 of the Micro, Small and Medium Enterprises Development Act, 2006 contain delayed-payment provisions for qualifying micro and small enterprise suppliers. The Act's definition of 'supplier' is not simply every business that describes itself as an MSME: section 2(n) refers to a micro or small enterprise that has filed the required memorandum, subject to the additional categories specified in the Act. The Ministry's MSME Samadhaan information page says a micro or small enterprise with valid Udyam Registration can apply through the portal. Medium enterprises should not assume that the section 15–24 delayed-payment route applies to them in the same way.

Section 15 says that where there is a written agreement, the agreed payment period cannot exceed 45 days from the day of acceptance or deemed acceptance. If there is no written agreement, the Act refers to payment before the 'appointed day'; section 2(b) defines that day by reference to the expiry of 15 days from acceptance or deemed acceptance. The 45-day cap is therefore not a universal grace period that starts automatically from the invoice date.

The Act also defines acceptance and deemed acceptance. The actual delivery of goods or rendering of services is relevant; if the buyer makes a written objection within 15 days, the date on which the supplier removes that objection becomes relevant. If no written objection is made within 15 days, the Act's deemed-acceptance definition refers to the actual delivery or service date. A contract, delivery record and correspondence may therefore matter when calculating the statutory timeline.

Section 16 provides for compound interest with monthly rests at three times the bank rate notified by the Reserve Bank, from the appointed day or the day immediately following the agreed date, as applicable. Do not calculate or demand a statutory amount from a generic online calculator without checking supplier eligibility, the acceptance date, the agreement, the applicable bank rate and the legal facts of the transaction.

  • Confirm that the supplier falls within the statutory micro or small enterprise definition for the relevant claim.
  • Keep the Udyam certificate and the registration details that relate to the supply.
  • Retain the written contract, PO, invoice, delivery or service evidence and acceptance correspondence.
  • Identify whether the payment term is written and calculate the relevant date from acceptance or deemed acceptance—not by assuming invoice date alone.
  • Have a qualified professional review the facts and interest calculation before making a legal demand.

12. Understand the MSME Samadhaan and MSEFC route

The Ministry of MSME describes Samadhaan as a portal through which eligible micro and small enterprises with valid Udyam Registration can file information about delayed payments. The application is routed to the relevant Micro and Small Enterprises Facilitation Council (MSEFC). The Council—not a private consultant and not the portal interface—examines the matter and exercises the powers provided by the Act. The Ministry information page used for this guide shows a last-updated date of 3 July 2026, before the 2026 amendment's staged commencement. Treat its Udyam note as published portal guidance and confirm the current registration mechanism and filing instructions on the live Ministry/Samadhaan portal before filing, because amended section 8 provides for a free and voluntary national digital registration platform.

Section 18(5) states that every reference shall be decided within 90 days, but that statutory wording should not be presented as a guarantee that an individual matter will finish within that time in practice. Important commencement update as at 15 November 2026: the Micro, Small and Medium Enterprises Development (Amendment) Act, 2026 (Act No. 16 of 2026) was assented to on 13 August 2026 and allows different provisions to commence on different dates. The commencement notification S.O. 5575(E), dated 12 October 2026, appointed 15 October 2026 for amendment Act sections 2–7, 11 and 13–17, and 15 December 2026 for amendment Act section 12. It did not include amendment Act sections 8–10, which contain the changes to principal section 18, new section 18A and substituted section 19. Based on that commencement notification, do not treat the proposed revised mediation/arbitration timelines, land-revenue recovery mechanism or revised pre-deposit rules as operative unless a later Gazette notification has commenced them. Check the latest Official Gazette before relying on a changed dispute procedure.

Prepare a clean evidence file before considering a reference: Udyam details, buyer identity, contract or work order, invoice list, delivery or service acceptance evidence, ledger statement, payment history, written objections, follow-up record and calculation notes. Check the current portal instructions and the jurisdiction and procedure of the relevant MSEFC. The Ministry's FAQ also explains that the Samadhaan portal facilitates online filing and that the concerned Council takes action on the application.

  • Start with the official [MSME Samadhaan information page](https://ramp.msme.gov.in/ramp/RAMP-initiative/msme-samadhaan/msme-samadhaan).
  • Use the official portal link published by the Ministry and check the current filing process.
  • Confirm that the supplier and transaction meet the statutory conditions before filing.
  • Keep every invoice and delivery record consistent with the buyer ledger.
  • Seek legal advice on limitation, jurisdiction, interest and the correct claimant before proceeding.
  • Do not describe portal submission as an assured recovery or a government grant.

13. Consider TReDS as a separate receivables-financing option

The Trade Receivables Discounting System (TReDS) is different from a delayed-payment complaint. Under RBI's TReDS framework, the platform brings sellers, buyers and multiple financiers together so an eligible trade receivable can be uploaded, accepted, bid on and discounted. If a financier funds the accepted factoring unit, the seller receives funds at the agreed discounted amount and the buyer pays the financier on the due date.

The RBI's Trade Receivables Discounting System Directions, 2026 were issued on 23 June 2026 and took effect immediately. They describe TReDS as a technology platform for facilitating factoring of trade receivables through multiple financiers. The Directions state that accepted factoring units carry the specified enforceability and that discounted factoring units are without recourse to the seller. The actual transaction still depends on participation, genuine underlying trade, buyer acceptance, platform rules, financier bids and the cost of discounting. The MSMED Amendment Act, 2026 also inserted section 15A into the principal Act; that amendment provision was among the provisions appointed to commence on 15 October 2026 by S.O. 5575(E). Section 15A requires every Central Public Sector Enterprise to route settlement of invoices for procurement from MSMEs through an RBI-authorised TReDS platform, in the prescribed form and manner. The Central Government may notify other bodies or entities, and State Governments may notify State Public Sector Enterprises or other entities. This is not a blanket statutory requirement on every private buyer.

The 2026 amendment also inserted section 22A, which was included in the provisions commenced from 15 October 2026. It requires Central Public Sector Enterprises and other notified entities, and State Public Sector Enterprises or other entities notified by State Governments, to disclose details of MSME invoices routed and settled through TReDS in the prescribed form and manner. The amendment Act's section 12, concerning the composition of Facilitation Councils, is appointed for 15 December 2026. Check the applicable rules and notifications for the buyer and reporting format; do not assume every private buyer is covered.

TReDS is not a free collection service, not a Samadhaan filing and not a guarantee that a buyer will accept an invoice or that a financier will bid. Before using a platform, review its current onboarding requirements, buyer coverage, fees, discount rate, settlement process and treatment of any existing charge or working-capital arrangement. Use an RBI-authorised platform and verify the current directions.

  • Check whether the business and the buyer can participate on the platform.
  • Confirm that the invoice represents a genuine completed supply and can be accepted by the buyer.
  • Compare the financier's discount cost with the value of receiving cash earlier.
  • Check whether the receivable is already financed, assigned or charged to a lender.
  • Read the platform and financier terms before accepting a bid.
  • Do not record a proposed TReDS transaction as cash until settlement is actually received.

14. A practical 30-day rollout for a small business

A small business can establish the basic AR control system in a month without buying an enterprise collections platform. The sequence below is a recommended implementation plan. It does not guarantee a particular reduction in overdue balances; the result depends on customer behaviour, contract quality, delivery evidence and the team's ability to resolve disputes.

  • Days 1–3 — Collect the open invoice list, bank receipts, credit notes, customer contracts and delivery records. Reconcile the opening balance to the accounting records.
  • Days 4–7 — Create one invoice register with customer, amount, due date, submission proof, ageing, dispute reason, owner and next action.
  • Days 8–10 — Identify the top customer exposures and invoices missing a PO, acceptance or portal acknowledgement.
  • Days 11–15 — Agree the follow-up cadence, email templates, escalation owner and promise-to-pay recording method.
  • Days 16–20 — Resolve the highest-value documentation and dispute blockers; send customer statements and confirm payment allocations.
  • Days 21–25 — Review credit limits, milestone billing, advance requirements and approval rules for new work.
  • Days 26–30 — Review overdue AR, DSO, dispute ageing and cash collected; document the next month's changes and check whether professional advice or a financing route is appropriate.

15. An example of how the register changes the next action

Consider a hypothetical service company with three open invoices. Invoice A is ₹1,18,000 and is eight days overdue because the buyer's portal says the PO number is missing. Invoice B is ₹2,36,000 and falls due in five days; the delivery certificate is already accepted. Invoice C is ₹59,000 and is 42 days overdue with no recorded dispute or payment commitment.

A single 'total overdue' number would hide the work required. Invoice A needs a corrected portal submission and proof of resubmission. Invoice B needs a pre-due confirmation and no escalation yet. Invoice C needs an account-owner call, a written payment date and senior review of the customer's exposure. The register turns the same outstanding balance into three different actions.

The amounts and ageing in this example are invented solely to demonstrate the workflow. They are not a customer case study, recovery result or market benchmark.

Illustrative invoicePositionReason / evidenceNext action
A — ₹1,18,0008 days overdueBuyer portal requires PO referenceCorrect the reference, resubmit and retain acknowledgement
B — ₹2,36,000Due in 5 daysDelivery certificate acceptedSend statement and confirm payment-run date
C — ₹59,00042 days overdueNo dispute or payment date recordedEscalate to account owner and obtain written commitment

16. FAQs about accounts receivable and delayed MSME payments

What is the difference between accounts receivable and cash flow? Accounts receivable is money customers owe. Cash flow records money actually entering and leaving the business. An invoice can increase receivables without increasing the bank balance.

How often should a small business review receivables? A weekly review is a practical starting point for most small B2B teams, with more frequent checks for high-value or time-sensitive balances. The cadence should match transaction volume and risk.

Does the MSMED Act's 45-day limit start from the invoice date? Section 15 refers to acceptance or deemed acceptance of goods or services. Where a written agreement exists, the agreed period cannot exceed 45 days from that point. Where there is no written agreement, the appointed-day definition in section 2(b) applies. Do not assume that every invoice receives 45 days from its date.

Can a medium enterprise use MSME Samadhaan for the delayed-payment provisions in sections 15–24? The Act's definition of supplier for this chapter refers to a micro or small enterprise that has filed the required memorandum, and the Ministry's Samadhaan page describes eligibility for micro and small enterprises with valid Udyam Registration. A medium enterprise should not assume the same statutory route applies.

Does filing on Samadhaan guarantee payment? No. The portal facilitates filing and routes the matter to the relevant MSEFC. The Council examines the case under the Act. Eligibility, evidence, procedure and the outcome are not guaranteed by submitting a form.

Is TReDS the same as MSME Samadhaan? No. TReDS facilitates financing or discounting of accepted trade receivables through financiers. Samadhaan is a delayed-payment filing route for eligible micro and small enterprises under the MSMED Act.

Should a business stop supplying a customer with overdue invoices? Not automatically. Review the contract, the customer's dispute, operational dependencies and legal obligations. A credit hold or pause should follow an authorised, documented decision and professional advice where needed.

Does an AR spreadsheet replace accounting software or a chartered accountant? No. A tracker supports follow-up and management visibility. Accounting records, GST treatment, bad-debt provisions, tax positions and statutory claims should be reviewed through the appropriate accounting and professional process.

Key takeaway

Receivables improve when every invoice has a complete evidence pack, a recorded due date, a named owner, a reason code and a next action. Use ageing and DSO as management tools, not as substitutes for customer-level judgement. For qualifying micro and small suppliers, check the exact MSMED Act conditions and MSEFC process; consider TReDS separately when an accepted receivable and financier bid make the economics sensible. A spreadsheet and a weekly review are enough to begin.

← Back to all guidesExplore related support ↗
Diwali Business Growth • Wishing you prosperity and new beginnings
Chat on WhatsApp