108. India Payments and Finance Stack

In India, payments are easy to start and surprisingly hard to operate well. UPI, cards, netbanking, payment links, wallets, invoices, subscriptions, international payments, refunds, settlements, GST, reconciliation, and collections all touch the founder’s cash flow.

The mistake is thinking “we integrated a payment gateway” means finance is handled. It does not. Money has to be requested, received, matched, taxed, reported, refunded, collected, and understood.

This page is a founder operating guide, not tax, accounting, legal, or payments-regulation advice. Verify current requirements with your CA, banker, payment provider, and counsel where relevant.

The Payment Stack

Choose payment methods based on customer behavior, ticket size, recurrence, trust, and reconciliation needs.

Method	Useful when	Watch for
UPI	Low-friction domestic payments, consumer or SMB use, instant collection.	Reconciliation, refunds, payer identity, limits, and operational matching.
Payment links	Early B2B, services, pilots, invoices, founder-led sales.	Manual follow-up and matching payments to invoices.
Cards	SaaS, subscriptions, international-style checkout, higher-trust digital users.	Failures, chargebacks, card coverage, recurring mandate rules.
Netbanking	Some business payments and older buyer workflows.	UX friction and confirmation delays.
Wallets	Certain consumer contexts.	Wallet-specific economics and customer preference.
Bank transfer	Enterprise, larger B2B, export, procurement-led payments.	Delays, remittance advice, matching, and follow-up.
International payments	Export SaaS, services, cross-border customers.	Tax, foreign exchange, invoices, documentation, bank process, compliance.

Start simple. Add complexity only when customer behavior demands it.

Collections Are Part Of Sales

Many founders celebrate a signed deal and forget that cash has not arrived. In India, collection can be a real operating motion, especially for B2B.

Design collections before the first invoice:

Who receives the invoice?
What details must be on the invoice?
Is there a PO process?
Who confirms service delivery?
What are the payment terms?
Who releases payment?
Who follows up?
What happens after 7, 15, 30, 45, or 60 days?
When do you pause service for non-payment?

Founder-led sales should include payment conversation early. If the customer says yes to the product but avoids payment terms, the deal is not fully understood.

Reconciliation

Reconciliation is matching what you expected to receive with what actually arrived.

Early founders can do this manually, but the process must exist:

Invoice number.
Customer name.
Amount billed.
GST and tax details where applicable.
Payment method.
Settlement date.
Gateway fee or bank charge.
Refund or dispute.
Outstanding balance.
Owner for follow-up.

Without reconciliation, revenue reporting becomes unreliable. You may think growth is strong while cash is stuck, refunds are rising, or invoices are unpaid.

Payment Failure And Exception Handling

The finance stack should include a way to handle exceptions, not only successful payments. Exceptions are where trust and cash leak quietly.

Exception	What to check	Founder action
Customer says paid, but cash not visible	UTR, gateway status, settlement date, bank account, invoice number.	Do not mark paid until reconciliation is complete.
Gateway shows success, but settlement is delayed	Settlement report, holiday, risk hold, provider ticket.	Track separately from unpaid invoices so cash forecast is honest.
Duplicate payment	Customer ledger, invoice mapping, refund/credit note process.	Decide refund or credit quickly and record it cleanly.
Failed subscription payment	Failure reason, retry rules, customer notification, grace period.	Trigger renewal workflow before service disruption surprises the customer.
Refund requested	Eligibility, approval owner, credit note, product or sales reason.	Treat as trust feedback, not only a transaction.
Chargeback or dispute	Evidence, service delivery, communication trail, provider process.	Preserve documentation and review sales/support promises.
Wrong GST or billing details	Customer master data, invoice correction, PO requirements.	Fix the billing data before the next invoice cycle.

Make one person accountable for exceptions each week. In a small startup that person may be the founder. The important thing is that exceptions do not live only inside email, WhatsApp, or gateway dashboards.

Finance Operations

A basic finance operating system should answer five questions every month:

How much cash do we have?
How much revenue did we earn?
How much cash did we collect?
What do customers owe us?
How many months of runway remain?

Build the stack:

Area	Founder standard
CA and bookkeeping	Monthly close, not annual cleanup.
Accounting tool	Customer, invoice, payment, expense, and tax data entered consistently.
Payroll	Salaries, reimbursements, contractor payments, and deductions handled on time.
Expense management	Founder and team expenses documented with approvals and receipts.
MIS	Monthly view of revenue, collections, burn, runway, receivables, payables, and taxes.
Investor reports	Same numbers each month, with definitions that do not keep changing.
Tax planning	No surprises because someone reviewed liabilities before cash was spent.

If your CA only appears near filing season, you do not have finance operations. You have annual cleanup.

Monthly Finance Close

A monthly close sounds corporate, but even a five-person startup needs a lightweight version. It prevents founders from making decisions with half-known numbers.

By the fifth working day of each month, create a simple monthly close note:

Section	What to include
Opening cash	Bank balance at the start of the month.
Cash collected	Customer cash received, separated from invoices raised.
Revenue booked	Revenue earned according to your accounting treatment.
Gross margin	Revenue minus direct delivery, support, infra, marketplace, mentor, logistics, or service costs.
Net burn	Cash outflow minus cash collected.
Receivables	0-30, 31-60, 61-90, and 90+ day buckets.
Payables	Vendor, salary, tax, reimbursement, and statutory obligations due soon.
Tax and compliance reserve	Money that is not freely spendable because obligations are coming.
Runway	Current and conservative runway.
Finance risks	Anything that could surprise the company this month.

The monthly close should be boring. If it creates drama every month, the operating system is weak or the founder is seeing reality too late.

Credit Risk And Bad Debt

Credit is hidden financing. When a customer gets 60-day terms, you are funding them for 60 days. That may be acceptable, but it should be intentional.

Watch for:

Customers asking for long terms before trust is established.
Repeated invoice corrections as a delay tactic.
No clear payment owner.
Procurement saying yes but finance not responding.
Large customer concentration with slow payment.
Founder fear of asking for money.

Create rules:

New customers start with upfront payment or shorter terms where possible.
Enterprise terms require named payment owner and PO clarity.
Renewal or expansion is blocked if old invoices are unpaid.
Bad debt is reviewed monthly.

Collections is not rude. It is part of respecting the business.

Payment Architecture By Business Model

Different startup models need different payment design. Copying another company’s checkout can create operational pain.

Business model	Payment design priority	Finance risk
B2B SaaS	Invoices, subscription renewals, annual plans, GST details, receivables ageing.	Signed customers who do not pay on time.
Consumer app	Low-friction checkout, UPI/cards, refunds, failed payments, cancellation flow.	High usage with weak monetization or refund leakage.
Marketplace	Escrow-like flows where applicable, commissions, seller payouts, refunds, disputes, reconciliation.	Money movement complexity and trust disputes.
Services-to-product	Advance payments, milestones, scope control, credit notes, retainer conversion.	Custom work hiding poor product economics.
Export SaaS/services	International invoices, foreign exchange, bank documentation, tax treatment, contracts.	Collection delays and documentation gaps.
Fintech or lending-adjacent	Regulatory review, partner agreements, customer consent, audit trail, grievance handling.	Compliance and reputation risk.

The founder should design the payment stack from the customer’s buying behavior backward. A student, a shop owner, a CFO, a procurement team, and a US SaaS buyer do not pay the same way.

Subscriptions, Mandates, And Renewals

Recurring revenue is powerful only if renewal and collection are operationally real.

For subscription businesses, define:

Is the plan monthly, quarterly, annual, or usage-based?
What payment method supports the customer’s actual behavior?
What happens when payment fails?
How many reminders go out before service changes?
Who owns renewal conversations?
What usage or value proof is sent before renewal?
How are upgrades, downgrades, cancellations, refunds, and credits handled?

Many founders say “MRR” before the renewal motion is mature. True recurring revenue means customers keep paying because value is delivered, reminders are clear, failures are handled, and finance can reconcile the cash.

Payment Provider Selection Checklist

Do not choose a provider only because integration looks easy. Choose based on the operating reality of your business model.

Question	Why it matters
Does it support the payment methods your customers actually prefer?	Checkout convenience differs across consumer, SMB, enterprise, and global buyers.
Are settlements predictable and easy to reconcile?	Cash planning depends on knowing when money reaches the bank.
Are fees clear by method, ticket size, refund, dispute, and currency?	Hidden fees distort gross margin.
How good are reports and exports?	Finance should not manually decode every transaction.
How are refunds, chargebacks, and failed mandates handled?	Edge cases become common at scale.
Does it support invoices, GST details, subscriptions, payment links, or marketplace flows if needed?	The provider should match the business model, not just the first checkout.
Is support reachable when money is stuck?	Payment issues become customer trust issues.
Can the stack be changed later without breaking operations?	Early choices should not trap the company.

For the first version, the best provider is often the one that lets you collect, reconcile, refund, and explain payments cleanly. Fancy features matter less than operational clarity.

Refunds, Disputes, And Trust

Refunds are not only a finance line item. They are a trust signal.

Define refund rules before volume grows:

When is a refund allowed?
Who can approve it?
How long will it take?
How is it recorded in accounting?
Does it require a credit note?
What pattern indicates product, sales, support, or expectation mismatch?

For consumer products, a confusing refund experience can damage brand trust quickly. For B2B, unresolved disputes can delay future payments and references. Treat refunds as product feedback, not only cash leakage.

Cross-Border Money

Many Indian startups sell to international customers from day one. That can be a major advantage, but the finance stack must be clean.

Founders selling globally should clarify:

What entity is contracting with the customer?
What currency is quoted?
How will invoices be raised?
What bank or payment provider receives funds?
What documents does the bank need?
How are exchange rates, fees, and settlement dates recorded?
What tax treatment applies?
Are there export documentation or reporting requirements?
Does the customer need security, privacy, or vendor onboarding paperwork?

Do not wait until the first large foreign payment is stuck with the bank to learn the documentation path.

Weekly Cash Ritual

Use a simple weekly cash review until the company has a mature finance team.

Every Friday, review:

Question	Why it matters
What cash is in the bank today?	Prevents runway fantasy.
What invoices were raised this week?	Keeps revenue and billing current.
What cash was collected?	Separates booked revenue from real cash.
Which receivables are overdue?	Forces follow-up before the issue ages.
What payments are due next week?	Prevents surprise outflows.
What refunds, credits, or disputes happened?	Reveals product or expectation problems.
Has runway changed?	Connects operating decisions to survival.

This ritual should take less than thirty minutes in a small company. If it takes longer, the stack is too messy.

GST Invoices And Documentation

GST, invoicing, e-invoicing applicability, export documentation, TDS, and other tax details depend on your business, registration, customer type, and current rules. Do not guess.

Founder checklist:

Does this customer need a GST invoice?
What GSTIN, address, place of supply, HSN/SAC, and tax treatment apply?
Does the customer deduct TDS?
Does the invoice need a PO number?
Are exports documented correctly?
Are credit notes, refunds, and cancellations recorded?
Does e-invoicing apply to the business based on current rules?

Use your CA and current official portals. The operational point is simple: invoices should help you collect money and survive audit, not create confusion.

Investor-Ready Finance

Investors do not only want numbers. They want confidence that the founder understands the business.

Track:

Revenue booked.
Cash collected.
Gross margin.
Burn.
Runway.
Receivables ageing.
Payables.
Customer concentration.
Refunds and chargebacks.
Tax liabilities.
Monthly recurring revenue if applicable.

The earlier you build this habit, the easier fundraising, board reporting, and strategic decisions become.

Official Links To Verify

Collections Operating System

Collections should not depend on founder memory. Build a simple operating system from the first invoice.

Step	Owner	What must be true
Before sale	Sales/founder	Buyer, billing entity, GST details, payment terms, purchase process, approval owner are known
At proposal	Sales/founder	Price, taxes, scope, start date, payment milestone, late-payment consequence are explicit
At invoice	Finance owner	Invoice is correct, sent to the right person, and logged in receivables tracker
Before due date	Account owner	Customer receives reminder and confirms payment path
On due date	Finance/account owner	Payment status is checked, not assumed
7 days overdue	Founder or senior owner if important	Escalation happens politely but firmly
30 days overdue	Founder/finance	Credit risk decision: pause service, negotiate plan, escalate, or write provision
After payment	Finance	Receipt, reconciliation, tax records, and customer status are updated

Track receivables ageing every week:

0-15 days.
16-30 days.
31-60 days.
60+ days.

Do not treat every overdue invoice equally. Segment by customer quality, relationship, reason, amount, and repeat risk. Some customers need better payment process. Some need founder escalation. Some should not be sold to again.

Cash Conversion Map

Map every step from interest to usable cash. This reveals where the company actually leaks money.

Step	Question	Common leak
Verbal yes	Who said yes, and do they control money?	User likes product but budget owner is absent.
Commercial agreement	Are price, scope, taxes, terms, and start date clear?	Side promises and vague payment terms.
Billing setup	Do we have legal name, GSTIN if applicable, address, PO process, and billing contact?	Invoice rejected or delayed for missing details.
Invoice raised	Was it sent to the correct person and recorded?	Invoice exists but nobody follows up.
Payment approval	Who approves payment on customer side?	Buyer says yes but finance is unaware.
Cash received	Has money actually reached the bank or settlement account?	Gateway success confused with bank cash.
Reconciliation	Is payment matched to invoice, fees, refunds, credits, and tax records?	Revenue and cash reports drift apart.
Usable cash	What portion is truly available after tax, refunds, fees, and obligations?	Founder spends money needed for obligations.

For B2B India, the cash conversion map is part of sales. A deal is not mature until the payment path is known.

Finance Control Tower

Create one finance control tower document or dashboard. It should be boring enough to maintain weekly and strong enough to prevent fantasy.

Include:

Bank balance today.
Expected collections by customer.
Receivables ageing.
Payables due in the next 30 days.
Payroll and statutory obligations.
Tax reserve or obligations to verify.
Refunds, credits, disputes, and chargebacks.
Monthly burn and conservative runway.
Customer concentration.
Large payment risks.

The founder should review this even if a CA or finance person owns execution. Finance delegation without founder visibility creates late surprises.

Payment Data Hygiene

Payment operations become messy when customer, invoice, and payment data do not match.

Maintain clean master data:

Data	Why it matters
Legal customer name	Contracting, invoicing, GST, collections, diligence.
Billing contact	Avoids invoices getting lost with the user.
Payment owner	Identifies who releases money.
GSTIN and address where applicable	Reduces invoice rejection and correction cycles.
Purchase order or approval process	Prevents procurement delays.
Payment terms	Makes follow-up objective, not personal.
Invoice number and amount	Enables reconciliation.
UTR/gateway/settlement reference	Proves payment status.
Refund or credit note record	Keeps books and customer trust clean.

Do not let this data live only in founder WhatsApp chats. Put it in the CRM, accounting system, or finance tracker.

Pricing And Payment Terms Discipline

Pricing is not only a growth question. It affects collections, support, cash flow, and customer expectations.

Set guardrails:

Minimum upfront amount or pilot fee where possible.
Standard payment terms by customer type.
Discount approval rules.
Renewal and expansion payment rules.
Refund and cancellation policy.
Service pause rule for non-payment.
Implementation or onboarding fee rules if effort is high.
Annual versus monthly plan logic.

The goal is not rigidity. The goal is to prevent every deal from becoming custom finance. Custom payment terms are sometimes strategic, but they should be visible and approved.

Runway Reality Review

Runway should be calculated from cash and likely collections, not optimistic invoices.

Review three runway views:

View	Meaning
Current runway	Based on current cash and current burn.
Conservative runway	Assumes delayed collections and essential spend only.
Plan runway	Assumes hiring, growth spend, expected collections, and fundraising plan.

If these numbers differ dramatically, discuss why. A founder who only looks at plan runway may make decisions the bank balance cannot support.

Payment Method Fit

India gives founders many payment options. The right choice depends on buyer behavior, ticket size, trust, reconciliation, refunds, and compliance.

Use payment methods deliberately:

Method	Works well for	Watch out for
UPI collect or QR	Small-ticket, mobile-first, fast payment, repeat consumer or SMB behavior.	Reconciliation, limits, failed payments, user confusion between intent and completion.
Payment links	Quick B2B/SMB collection without full checkout.	Link expiry, who receives it, invoice match, partial payments.
Cards	Consumer subscriptions, international customers, higher convenience.	Fees, chargebacks, card failure, mandate rules, refund handling.
Netbanking	Enterprise or older buyer behavior, larger payments.	Bank-specific friction, slower user experience, reconciliation.
Bank transfer/NEFT/RTGS/IMPS	B2B invoices, enterprise procurement, high-value payments.	Manual follow-up, UTR tracking, customer finance process.
Wallets or PPIs	Consumer convenience in some segments.	Acceptance, regulatory/provider limits, settlement and refund rules.
International payment rails	Export/SaaS/services revenue.	FEMA, invoices, purpose codes, fees, settlement timing, tax documentation.

The founder question is not “which gateway is cheapest?” It is “which method creates paid, reconciled, trusted, repeatable revenue for this customer?”

Settlement And Refund Reality

A payment success screen is not the same as usable company cash. Payment operations have at least five states:

Customer attempted payment.
Payment was authorized or shown as successful.
Payment was captured by the provider.
Settlement reached the company bank account.
Payment was matched to the right customer, invoice, fee, tax treatment, and refund risk.

Track settlement separately from sales. A founder should know:

Settlement cycle by payment method and provider.
Fees and taxes deducted before settlement.
Failed, pending, reversed, refunded, and chargeback states.
Who handles customer complaints when money is debited but service is not activated.
How refunds are approved, recorded, and communicated.
What happens if a payment provider pauses settlements or requests documents.
How reconciliation works when one settlement contains many customer payments.

Refunds deserve their own policy:

Question	Policy needed
When is refund allowed?	Trial, cancellation, failed delivery, duplicate payment, goodwill, legal obligation.
Who approves refund?	Support, finance, founder, automated rule.
How fast is refund processed?	Customer expectation and provider reality.
How is refund recorded?	Credit note, accounting entry, customer record, tax implication.
What is abuse?	Repeated refund behavior, chargeback misuse, policy gaming.

Trust in India can be won or lost during payment failure. A clear refund and support path is not back-office work; it is part of the product.

Enterprise Collections Playbook

For B2B India, collections must start before the invoice is raised.

Before signing:

Identify user, buyer, finance contact, procurement contact, and payment approver.
Ask whether a purchase order is required.
Confirm billing entity name, GSTIN if applicable, address, tax treatment, and invoice format.
Define payment milestone, due date, late-payment escalation, and service-pause rule.
Confirm whether TDS or other deductions may happen.
Decide whether work begins before advance payment.

During delivery:

Send progress evidence tied to payment milestones.
Keep the business sponsor aware of upcoming invoice dates.
Store acceptance, delivery notes, usage reports, or sign-offs if required.
Avoid expanding scope without commercial approval.

After invoicing:

Send invoice to both sponsor and finance contact.
Confirm receipt within 48 hours.
Ask for payment date before due date.
Track promises, not only invoice age.
Escalate respectfully when the due date passes.
Separate genuine process delays from credit risk.

Use this escalation ladder:

Stage	Action
7 days before due	Friendly reminder with invoice, PO, amount, due date, bank details.
Due date	Confirm payment status and expected release date.
7 days overdue	Ask sponsor to help unblock finance/procurement.
15-30 days overdue	Founder escalation for meaningful amounts; clarify service continuation.
30+ days overdue	Credit decision: pause, payment plan, legal notice, write provision, or stop selling to similar customers.

A founder who hates collections should still design collections. Otherwise the company may confuse booked revenue with survival.

Finance Metrics For Indian Startups

Track metrics that match the reality of the business, not only investor templates.

Metric	Why it matters
Invoice-to-cash days	Shows whether revenue converts into money.
Receivables ageing	Reveals collection risk before it becomes a crisis.
Gross margin after payment fees and support	Shows whether the business model survives real operations.
Refund and chargeback rate	Measures trust, product fit, and payment quality.
Customer concentration	Large unpaid invoices from one customer can distort confidence.
Tax reserve	Prevents spending money that belongs to statutory obligations.
Founder salary gap	Shows hidden personal pressure on the company.
Conservative runway	Protects decisions from optimistic collections.
Revenue quality by channel	Some channels create signups, others create cash.
Support cost per paid customer	Reveals whether low-price customers are actually profitable.

For early companies, a simple weekly dashboard is enough. It should answer:

How much cash is in the bank?
What cash is expected in the next 30 days?
What cash is at risk?
What must be paid regardless of sales optimism?
Which customers or channels are improving cash quality?

Provider And Tool Selection

Do not choose payment, accounting, payroll, or expense tools only from founder familiarity. Choose based on operating fit.

Evaluate:

Supported payment methods for your customer segment.
Settlement cycle and reconciliation exports.
Refund, dispute, and chargeback workflows.
GST invoice and accounting integration needs.
Subscription or recurring payment support where relevant.
International payment support if selling globally.
Reliability and support responsiveness.
Compliance posture and documentation.
Ability to export clean data if you migrate.
Pricing after volume grows, not only the first-month discount.

The best tool is the one your team can operate correctly every week. A fancy finance stack with poor discipline is worse than a simple stack with clean records.

Cash Collection Command Center

In India, a sale is not finished when the customer says yes. For many B2B startups, the real work continues through PO, invoice, GST details, vendor onboarding, internal approval, payment follow-up, reconciliation, and support. Treat collections as part of the revenue system, not as an awkward finance chore.

Create a cash collection command center:

Field	Why it matters
Customer and entity name	Avoids invoice mismatch and payment delay.
Buyer and finance contact	Separates product champion from payment owner.
Contract/PO status	Shows whether the customer can legally/process-wise pay.
Invoice date and due date	Makes ageing visible.
Payment terms	Prevents founder memory from replacing records.
GST/invoice details	Reduces rework and customer finance objections.
Amount due and amount collected	Separates booked revenue from cash.
Blocker	PO, approval, finance queue, dispute, onboarding issue, cash issue.
Next follow-up	Owner, date, channel, and message.
Escalation path	Who can unblock if routine follow-up fails.

Run a weekly 20-minute review:

Which invoices are overdue?
Which customers need finance-contact follow-up?
Which payment delays are caused by our own documentation mistakes?
Which deals were closed with weak payment terms?
Which segment or channel creates low-quality cash?

This is not only about cash discipline. It teaches pricing, customer quality, sales process, onboarding, and trust. A customer who loves the product but repeatedly delays payment may still be a poor fit for your current business model.

Receivables Aging Ladder

Receivables age differently in India depending on customer type, invoice quality, internal approval, buyer power, finance process, and relationship. Do not treat all unpaid invoices the same. Classify them so the founder knows what action is needed.

Age/status	What it may mean	Founder action
Not yet due	Normal payment cycle	Confirm invoice received and no documentation gap exists.
1-7 days overdue	Process delay or missing reminder	Send polite finance follow-up with invoice, PO, and payment link/details.
8-15 days overdue	Internal approval or buyer/finance disconnect	Ask buyer to introduce finance owner or confirm payment date.
16-30 days overdue	Weak payment process, dispute, cash issue, or low urgency	Escalate respectfully; identify blocker and pause expansion promises.
31-60 days overdue	Credit risk or relationship risk	Founder review; decide service limits, payment plan, or senior escalation.
60+ days overdue	Potential bad debt or serious mismatch	Stop treating as normal revenue; seek advisor input and update cash forecast.

Track the reason, not only the age:

Reason	System fix
Wrong invoice details	Improve onboarding, GST detail capture, and finance-contact fields.
PO not issued	Do not start work without commercial process clarity for similar customers.
Buyer disappeared	Multi-thread earlier; separate champion from payment owner.
Product dispute	Fix delivery, success criteria, or support promise before chasing harder.
Customer cash issue	Tighten credit policy and payment terms for that segment.
Founder discomfort	Create scripts and cadence so follow-up is professional, not emotional.

The founder should review aged receivables weekly until collections become predictable. The goal is not to become aggressive. The goal is to make cash reality visible early enough to protect payroll, runway, and customer quality.

Add a rule to sales:

A deal is not healthy until the buying process, invoice details, payment owner, payment term, and collection path are known.

This rule changes behavior. Sales calls start asking better commercial questions. Onboarding captures finance details earlier. Product teams understand which customers create support without cash. Founders stop confusing booked revenue with usable money.

Revenue, Invoice, Cash, And Runway View

Indian founders should separate four ideas that often get mixed in casual conversation:

View	What it means	Founder danger
Signed revenue	Customer agreed commercially.	May still need PO, invoice, onboarding, or approval.
Invoiced revenue	Invoice has been raised.	Cash may not arrive on time.
Collected cash	Money reached the bank.	May include taxes, refunds, disputes, or obligations.
Usable runway cash	Cash available for payroll and operations after obligations.	Founders may overestimate runway if receivables are high.

Do not run the company only on sales excitement. Run it on cash reality.

Create a weekly view:

Metric	Question
New contracts signed	What did customers commit to?
Invoices raised	What has actually been billed?
Cash collected	What arrived in the bank?
Receivables ageing	What is overdue and why?
Refunds/credits/disputes	What revenue may reverse?
Tax and statutory obligations	What cash is not really free?
Payroll and vendor commitments	What must be paid soon?
Updated runway	How many months remain under realistic collection assumptions?

For tax, accounting, and revenue recognition, use your CA or finance advisor. The founder’s job is to keep the operating distinction clear: a signed deal is not the same as money available for salaries.

Cash reality rule

Use this sentence in weekly reviews:

Our reported traction is ______, but our cash reality is ______ because ______.

Examples:

“Our reported traction is Rs 18 lakh in signed annual contracts, but our cash reality is Rs 4 lakh collected because three enterprise invoices are still waiting for PO approval.”
“Our reported traction is 300 paid users, but our cash reality is weaker because refunds and support load are rising in one channel.”

This protects the founder from confusing momentum with financial safety.

UPI, Invoice, And Bank Reconciliation Workflow

India payment flow can look simple at the user level and messy at the finance level. UPI, payment links, cards, bank transfers, invoices, GST, refunds, platform fees, chargebacks, and settlement delays can all create gaps between product revenue and bank cash.

Create a reconciliation workflow:

Step	Check
Order or contract created	Customer, amount, tax, product/package, payment terms.
Invoice raised	GST details, invoice number, due date, buyer entity, PO if required.
Payment initiated	UPI/card/link/NEFT/RTGS/international method and reference.
Settlement received	Bank amount, provider fee, TDS/withholding if any, date received.
Accounting entry made	Revenue, GST, fees, refunds, receivable, bad debt where applicable.
Customer access updated	Activation, renewal, downgrade, suspension, or support status.
Exception resolved	Failed payment, partial payment, duplicate, refund, disputed amount, wrong entity.

Reconciliation owner rule

Use this rule:

Every rupee should have a path from customer promise to invoice to payment reference to bank receipt to accounting entry to customer access.

This is not bureaucracy. It protects runway, investor reporting, GST records, customer trust, and founder sleep. A startup can survive slow collections if it sees them early. It gets hurt when everyone believes revenue exists but cash and records disagree.

Payment Terms Design

Payment terms are part of product-market fit in India. They influence conversion, cash flow, customer quality, and support load.

Design terms by customer type:

Customer type	Common risk	Term design question
Consumer	Refunds, failed payments, support disputes	Is payment simple, reversible where needed, and clearly explained?
SMB owner	Price sensitivity, manual payment, follow-up	Can we reduce friction without extending risky credit?
Enterprise	PO, vendor onboarding, long cycles	Do we know finance owner, process, due date, and escalation path?
Marketplace participant	Settlement trust, disputes, reconciliation	Are ledger, refund, fee, and payout rules visible?
International customer	Currency, tax, documentation, bank/payment rails	Can finance and customer both reconcile cleanly?

Term discipline checklist

Before starting work, know:

Who approves the purchase.
Who receives the invoice.
Who releases payment.
What documents are needed.
What payment method will be used.
What date payment is expected.
What happens if payment is delayed.
Whether support/service continues during non-payment.

This is not about being rigid. It is about being clear. Clarity prevents awkward founder follow-up later.

Payment Exception Register

In India, payment exceptions are normal: delayed POs, partial payments, TDS confusion, GST detail mistakes, duplicate transfers, wrong legal entity, payment link failures, refund disputes, bank settlement delays, and enterprise finance follow-ups. The danger is not the exception. The danger is losing track of it.

Maintain a payment exception register:

Exception	Customer	Amount	Owner	Root cause	Next action	Due date	Status
PO delayed				Procurement not complete
Partial payment				TDS/GST/approval issue
Refund requested				Product/support expectation mismatch
Payment received, not reconciled				Missing reference or wrong entity

Classify exceptions:

Type	Founder response
Process issue	Improve invoice, PO, documentation, or reminder workflow.
Customer quality issue	Revisit qualification and payment terms.
Product/support issue	Fix expectation, onboarding, or refund policy.
Finance/accounting issue	Involve CA/finance owner and document treatment.
Trust issue	Communicate clearly and assign one owner.

Review the register weekly until the exception is closed. Every exception should either become cash, a written credit/refund, a bad-debt decision, or a process improvement.

Reader Action

Create a collections and finance dashboard with five rows: invoices raised, cash collected, receivables ageing, refunds/credits, and runway. Review it every Friday for one month. You will learn more from this than from a fancy financial model.