Practical FY 2026-27 challenges and solutions for B2B and B2C Indian businesses across GST, DPDP, consumer protection and working capital.
No Coupler.io data-pipeline skills are relevant to this blog-writing task. Proceeding directly with the content.
B2B and B2C Challenges & Solutions
Selling B2B and B2C in India share a P&L but almost nothing else. In FY 2026-27, e-invoicing under Rule 48(4) of the CGST Rules now covers most B2B suppliers, section 43B(h) of the Income-tax Act is disallowing deductions for late MSME payments, the Digital Personal Data Protection (DPDP) Act 2023 is reshaping consumer-data flows, and ONDC is forcing brands to rethink channel economics. This guide maps the live pressure points for each model and gives you the specific steps, section numbers and rupee-level examples you need to act on today.
The B2B Operating Reality in FY 2026-27
Long Sales Cycles and Working-Capital Drain
A typical mid-market B2B sale moves through an RFQ, vendor registration, commercial negotiation, legal review, purchase order and then invoice-to-payment on net-60 or net-90 terms. By the time cash arrives, the seller has already borrowed to fund inventory and labour. Days Sales Outstanding (DSO) of 75-90 days means a company with Rs. 10 crore in monthly revenue is carrying Rs. 25-30 crore of receivables at any moment. At a 14% cost of capital, that is Rs. 3.5-4.2 crore of invisible interest expense per year โ enough to erase the profit on a material slice of the business.
GST E-Invoicing: What Is Mandatory Now
E-invoicing under Rule 48(4) of the CGST Rules, 2017 is mandatory for every registered supplier whose aggregate turnover in any preceding financial year from FY 2017-18 exceeds Rs. 5 crore. From that threshold, every B2B invoice, debit note and credit note must be registered with the Invoice Registration Portal (IRP) and stamped with an Invoice Reference Number (IRN) before it reaches the buyer.
The IRN workflow in five steps:
- Your ERP or accounting software (Tally Prime, SAP, Zoho Books, etc.) generates the invoice as a JSON document in the prescribed GSTN schema.
- The JSON is pushed to the IRP โ either directly or via a GST Suvidha Provider (GSP).
- The IRP validates both GSTINs, checks for duplicate IRNs and returns a signed IRN and QR code within seconds.
- The signed invoice with embedded QR code is issued to the buyer; this is the only legally valid B2B invoice.
- GSTR-1 auto-populates from IRP data โ no manual re-entry needed.
Miss step 2, and the invoice is legally invalid. The buyer cannot claim Input Tax Credit (ITC), and GSTN's reconciliation engine will flag your account for generating "non-IRP" invoices. Scrutiny notices follow.
ITC Dependence on Supplier Filing Discipline
Your ITC is only as good as your vendors' GSTR-1 punctuality. Under section 16(2)(aa) of the CGST Act 2017, ITC is available to the extent the supply is reflected in your auto-generated GSTR-2B. If a vendor files GSTR-1 even one day late, the corresponding credit drops off your GSTR-2B for that month.
On a monthly GST purchase pool of Rs. 1 crore at 18%, a single month's GSTR-1 delay by a major vendor defers Rs. 18 lakh of ITC. At a 14% cost of capital that deferral costs roughly Rs. 21,000 per month in cash drag โ insignificant per invoice, substantial across a large vendor base.
Section 43B(h): The MSME Payment Trap
Section 43B(h) of the Income-tax Act 1961, operative from AY 2024-25 onwards, disallows any deduction for sums payable to a Micro or Small Enterprise (as defined under the MSMED Act 2006) unless actually paid within the time prescribed under section 15 of that Act:
- No written agreement: payment must be made within 15 days of delivery or acceptance of goods/services.
- Written agreement: payment must be made within the agreed period, which cannot exceed 45 days.
There is no grace period and no partial-disallowance rule โ the entire outstanding amount is disallowed in the year the expense is booked and becomes deductible only in the year actual payment is made.
TDS under Section 194Q and TCS under Section 206C(1H)
If your business turnover exceeded Rs. 10 crore in the preceding financial year, you must deduct TDS at 0.1% under section 194Q on purchases of goods from a resident seller where the aggregate consideration in a financial year exceeds Rs. 50 lakh. The mirror obligation on sellers โ TCS at 0.1% under section 206C(1H) โ is superseded wherever the buyer deducts first under 194Q.
Late or non-deduction attracts interest at 1% per month under section 201(1A) plus a penalty equal to the TDS amount under section 271C. For a Rs. 2 crore annual purchase from one vendor, the TDS at stake is just Rs. 15,000 โ but prosecution risk under section 276B is real and non-compoundable without department consent.
Worked Example: The True Cost of a 170-Day MSME Payment Delay
> Facts: MSME vendor raises an invoice for Rs. 5 lakh on 1 April 2026. The buyer has a written credit agreement. Statutory maximum: 45 days. Due date: 16 May 2026. > > Actual payment date: 2 November 2026 โ 170 days past the due date. > > MSMED Act interest (section 16): Compound interest at 3ร the RBI bank rate. With the bank rate at 6.5%, the penal rate = 19.5% p.a. > > Interest = Rs. 5,00,000 ร 19.5% ร (170 รท 365) = Rs. 45,445 > > Income-tax disallowance (section 43B(h)): Rs. 5 lakh disallowed in FY 2026-27. At a 25% corporate tax rate, this accelerates a Rs. 1,25,000 tax payment by one year. Opportunity cost at 10%: Rs. 12,500. > > MSME Samadhaan risk: If the vendor files on the government portal (samadhaan.msme.gov.in), the buyer receives a government notice and must respond within 30 days. Non-response escalates to the Micro and Small Enterprises Facilitation Council (MSEFC). > > Avoidable cost per invoice: Rs. 45,445 interest + Rs. 12,500 tax acceleration = Rs. 57,945 โ on a single Rs. 5 lakh invoice.
Scale this across a procurement function with 50 active MSME vendors and the aggregate exposure is material.
B2B Solutions: Steps You Can Implement This Quarter
Step 1 โ Vendor onboarding hygiene. Before opening any credit line, collect and validate: GSTIN (verify at gstin.gov.in), PAN, Udyam Registration Number (free lookup at udyamregistration.gov.in) to confirm MSME tier, and a bureau report (CIBIL or CRIF). Tag MSME vendors in your ERP so that 43B(h) payment timers start automatically from invoice acceptance.
Step 2 โ E-invoice workflow with a hard block. Integrate your ERP with an IRP-connected API (direct GSTN API or via a GSP). Configure a workflow rule that prevents invoice posting unless a valid IRN has been returned. This single control eliminates the risk of issuing non-IRP invoices and removes manual GSTR-1 data entry entirely.
Step 3 โ Monthly GSTR-2B reconciliation before vendor payment. Run a purchase-register-versus-GSTR-2B match every month, ideally before the GSTR-3B filing date. Vendors with persistent GSTR-1 mismatches receive a "hold" flag โ no new POs or payments are released until the mismatch is explained or corrected.
Step 4 โ DSO ageing dashboard. Build a receivables dashboard with buckets: current, 1-30, 31-60, 61-90 and 90+ days. Auto-trigger reminder emails at day 30 and day 60. Escalate to account manager and legal at day 75. DSO above 60 days on any single customer above 5% of revenue should trigger a credit-limit review.
Step 5 โ TReDS for MSME receivables. If you are an MSME supplier with invoices accepted by a large corporate buyer, register on one of the three RBI-licensed TReDS platforms: RXIL, M1xchange or Invoicemart. Accepted invoices can typically be discounted at 8-11% p.a., converting a 90-day receivable to same-week cash and eliminating the DSO problem at source.
The B2C Operating Reality in FY 2026-27
DPDP Act 2023: Consent Is Now a Compliance Obligation
The Digital Personal Data Protection Act 2023 governs how you collect, store, process and share the personal data of your customers โ termed "Data Principals" under the Act. The law is in force; specific timelines under the DPDP Rules are operative as notified. Key obligations apply now:
- Explicit, purpose-specific consent. Pre-ticked checkboxes and bundled "I accept terms and conditions" clauses do not qualify. Each data category and purpose needs a separate, affirmative consent.
- Data minimisation. Collect only what is necessary for the stated purpose. Collecting email, phone and date of birth just to process an order is disproportionate unless each field is genuinely needed.
- Retention and deletion. When the stated purpose is fulfilled, personal data must be deleted. You need an auto-deletion workflow, not just a policy statement.
- Breach notification. Notify the Data Protection Board and affected Data Principals as soon as reasonably practicable after becoming aware of a personal data breach, within timelines as notified.
Penalties under Schedule I of the DPDP Act:
- Failure to implement adequate security safeguards: up to Rs. 250 crore per instance.
- Failure to notify a personal data breach: up to Rs. 200 crore per instance.
- Violation of obligations relating to children's data: up to Rs. 200 crore per instance.
These are not aggregate annual caps โ they apply per instance. A single breach event can trigger multiple penalty heads simultaneously.
Consumer Protection (E-Commerce) Rules: The Basics That Most Sellers Still Miss
The Consumer Protection (E-Commerce) Rules 2020, read with the Consumer Protection Act 2019, apply to every entity that sells goods or services online, whether on your own platform or a third-party marketplace. Non-negotiable requirements:
- Total price visibility. Display the inclusive total price โ including all taxes, platform fees and delivery charges โ before checkout. Revealing a Rs. 200 "handling fee" only at the payment screen is a violation.
- Seller identification. Every product listing must display the seller's legal name, registered address and customer-service contact.
- Grievance officer. Appoint a named grievance officer and publish their name and contact on every product-listing page and in the website footer. They must acknowledge complaints within 48 hours and resolve them within one month from the date of receipt.
- Refund timelines. Your published refund policy must appear on the product listing page itself, not buried in a footer link. The timeline must be reasonable โ a 30-day refund window on a digital product will attract consumer forum complaints.
The Central Consumer Protection Authority (CCPA) can impose a penalty of up to Rs. 10 lakh for a first misleading advertisement offence and Rs. 50 lakh for each repeat. Influencers and brand endorsers face personal liability if their disclosure statements are missing or misleading.
GST Section 9(5): When the Platform Pays the Tax, Not the Supplier
Under section 9(5) of the CGST Act 2017, for specified categories of supplies made through electronic commerce operators (ECOs), the ECO is the deemed supplier for GST purposes and pays the tax โ not the underlying vendor. The categories as notified include restaurant services, housekeeping services, and passenger transport.
Practically: When a customer orders food through Swiggy or Zomato, the ECO pays 5% GST on the order value. The restaurant does not charge or pay GST on that order. If you operate a food-delivery marketplace, you are the taxpayer on every restaurant order, whether or not you have charged, collected or remitted the GST. Misclassifying this as the restaurant's liability creates a large retrospective exposure on assessment.
Channel Fragmentation and ONDC Compliance
ONDC (Open Network for Digital Commerce), operated under DPIIT, is a decentralised network that separates buyer apps, seller apps and logistics providers. As ONDC adoption widens in FY 2026-27, your product master data โ SKU name, HSN code, MRP, GST rate, return policy โ flows through your seller app to buyer apps the moment you publish. An error in your product master propagates to every connected buyer app instantly, creating inconsistent pricing and classification across channels that GSTN and CCPA can both act on.
Worked Example: The Channel P&L Reality for a B2C Brand
> A consumer electronics brand sells a Rs. 3,000 Bluetooth speaker across three channels (all figures per unit, before GST).
| Channel | Gross Price | Commission / Fee | Returns (5%) | Advertising | Shipping | Net Revenue |
|---|---|---|---|---|---|---|
| D2C Website | Rs. 3,000 | Rs. 0 | Rs. 150 | Rs. 180 | Rs. 120 | Rs. 2,550 |
| Marketplace | Rs. 3,000 | Rs. 450 (15%) | Rs. 150 | Rs. 300 | Rs. 60 (FBA) | Rs. 2,040 |
| ONDC Seller App | Rs. 3,000 | Rs. 150 (5%) | Rs. 120 | Rs. 90 | Rs. 150 | Rs. 2,490 |
> The aggregate blended net revenue of ~Rs. 2,360 looks acceptable. But the marketplace channel at Rs. 2,040 per unit is 20% below D2C. If 60% of volume flows through the marketplace, the blended realisation is materially worse than what an aggregate P&L shows. > > GST implication: GST at 18% applies. Tax-exclusive base on Rs. 3,000 MRP = Rs. 2,542.37; IGST = Rs. 457.63. Marketplace deducts TCS at 1% under section 52 = Rs. 25.42 per order. You must claim this TCS credit in your GSTR-3 when filing. Miss this reconciliation and you double-pay.
B2C Solutions: Practical Steps
Step 1 โ Single PIM hub for all channels. Maintain one master product database carrying: legal product name, MRP, HSN code, applicable GST rate, return policy, country of origin and regulatory certifications. Push updates to all channels โ website, marketplace, ONDC seller app โ from this single source. Any HSN or price change flows everywhere simultaneously.
Step 2 โ Rebuild consent architecture from first principles. On your website and app: (a) separate checkboxes for each data purpose โ order processing, marketing communications, analytics, third-party sharing; (b) retain consent logs with timestamp, IP address and the exact purpose text shown; (c) provide a "manage preferences" centre where customers can withdraw individual consents; (d) configure auto-deletion workflows when a customer deletes their account or retention periods expire. This is infrastructure, not a one-time audit task.
Step 3 โ Grievance officer setup with ticketing SLAs. Appoint a named, real individual as grievance officer โ not a shared inbox with a generic job title. Publish their name and email address on every product-listing page. Set up a ticketing system that auto-acknowledges within 48 hours and escalates unresolved tickets at Day 25 so they close within the one-month window. Unresolved complaints are the raw material for consumer forum cases.
Step 4 โ Weekly marketplace settlement reconciliation. Every week, reconcile: (a) marketplace settlement statement against your sales register; (b) TCS amounts deducted by the marketplace against your GSTR-2B auto-credit; (c) commission rates applied against your signed rate card. A 1% commission rate error on Rs. 50 lakh monthly GMV is Rs. 50,000 per month โ Rs. 6 lakh per year โ that compounds silently.
Step 5 โ ONDC catalogue audit. Check your ONDC seller-app compliance dashboard weekly. ONDC's catalogue validation rejects listings with mismatched HSN codes, missing MRP fields or non-standard category tags. De-ranked listings reduce discoverability on buyer apps without any visible notification to the seller.
Common Mistakes and Pitfalls to Avoid
B2B pitfalls:
- Treating all vendors as non-MSME by default. The obligation to check MSME status sits with the buyer, not the vendor. Udyam Registration lookup is free; not checking is not a defence under section 43B(h).
- Generating e-invoices after issuing the physical document. The IRP must be hit before the invoice is issued. Retroactive IRN generation is non-compliant and voids the credit chain.
- Running 194Q and 206C in parallel on the same transaction. Both cannot apply simultaneously to the same supply. Where the buyer deducts under 194Q, the seller's 206C(1H) obligation is extinguished. Over-withholding creates vendor disputes and refund claims.
- Relying on oral or email credit terms with MSME vendors. Without a written agreement capped at 45 days, the default 15-day rule applies โ operationally impossible for most procurement cycles.
B2C pitfalls:
- Bundled consent clauses. A single "I agree to terms and conditions" that embeds marketing consent is non-compliant under the DPDP Act. Regulators will look for granular, purpose-specific consent at the point of collection.
- Ignoring TCS from marketplaces. If your aggregate annual sales across all marketplaces exceed Rs. 20 lakh (or Rs. 10 lakh in special category states) and you are not GST-registered, you are exposed. Once registered, claim marketplace TCS in your GSTR-3 every quarter โ failure to reconcile means you pay tax twice.
- Publishing return policies that exceed customer expectations. A 30-day refund timeline on a digital product routinely triggers consumer forum complaints. Seven days is the market-aligned benchmark.
- Assuming ONDC is a commission-free channel. Seller apps on ONDC charge their own network and service fees. Build a separate ONDC channel P&L before scaling inventory commitments.
Shared Compliance Infrastructure: What Both Models Require
Despite the surface differences, B2B and B2C share a compliance backbone:
| Requirement | B2B | B2C |
|---|---|---|
| Monthly GST reconciliation (GSTR-1 / GSTR-3B / books) | โ | โ |
| DPDP-grade personal data governance | Vendor and customer master | Consumer transactional data |
| Audit trail under Companies (Accounts) Rules 2014 | ERP + document retention | Order management + ERP |
| Accurate master data | GSTIN, MSME status, PAN | HSN code, MRP, consent flags |
| Income-tax withholding | 194Q, 194C, 195 | 194-O (marketplace operators) |
Both models also face AI-driven enforcement that is already running. The GSTN analytics engine flags suppliers whose GSTR-1 filing patterns โ invoice count spikes, buyer concentration, HSN classification shifts โ deviate from peer norms. The CCPA monitors e-commerce platforms for misleading pricing and unsubstantiated claims. The Data Protection Board, once fully operational, will use automated surveillance to identify high-volume personal-data processors who lack published privacy notices.
Reactive compliance โ responding to a government notice after it arrives โ costs between five and ten times more than proactive compliance, once professional fees, penalties, management distraction and reputational damage are totalled. Publishing your privacy notice, training procurement on MSME payment timelines, reconciling marketplace settlements weekly and running GSTR-2B checks monthly are the four habits that keep you out of that reactive cost curve.
Working Capital as a Strategic Variable
Working capital is the single most consequential operational variable for both B2B and B2C operators in FY 2026-27, and it has financing-side solutions that many businesses have not yet used.
For B2B sellers:
- TReDS discounting converts accepted invoices to cash in 2-3 working days at 8-11% p.a. โ consistently cheaper than an overdraft.
- Supply-chain finance (reverse factoring) allows the buyer to offer early payment to vendors at the buyer's lower credit rating. The buyer extends its own DPO while vendors get paid in 5-10 days.
- Bank OD against receivables is widely available but typically priced at 13-16%; use as a bridge for large lumpy collections rather than as steady-state financing.
For B2C operators:
- Negotiate T+7 settlement cycles with marketplace partners โ most platforms will grant this above a minimum volume threshold.
- Model your cash cycle for ONDC separately: logistics settlement and product-sale settlement clear on different timescales; confusing them will cause cash-flow forecast errors.
- Use fintech-enabled receivables advances against expected marketplace settlements for working capital peaks around large sale events (Diwali, End-of-Season).
Key Takeaways
- E-invoicing has no threshold exception below Rs. 5 crore โ if your turnover exceeds it, every B2B invoice needs an IRN before dispatch. Automate IRP submission from your ERP; manual workflows create gaps that GSTN will find.
- Section 43B(h) is live and biting. Any amount payable to an MSME vendor beyond 15 days (no agreement) or 45 days (written agreement) is disallowed in the year of booking. Tag MSME vendors in your ERP and set automatic payment-deadline alerts.
- DPDP consent is an architecture problem, not a policy problem. You cannot retrofit compliant consent onto an existing system with a checkbox. Rebuild consent collection from first principles โ purpose, granularity, withdrawal mechanism, deletion workflow.
- Run a channel P&L, not just an aggregate P&L. If you do not know your true net revenue per channel after commissions, returns, shipping and advertising, you cannot make rational decisions about pricing, channel mix or D2C investment.
- GSTR-2B reconciliation is a cash-flow tool as much as a compliance tool. Vendors who persistently mis-file cost you ITC that is real working capital. Identify them monthly and use that leverage to enforce filing discipline before releasing payment.
- Section 9(5) places GST liability on the ECO, not the vendor. If you operate a marketplace in restaurant, housekeeping or cab categories, you are the statutory taxpayer on every transaction. There is no contractual way to transfer this liability downstream.
- Proactive compliance is the cheaper path. The GSTN, CCPA and Data Protection Board all run enforcement analytics now. A published privacy notice, a named grievance officer and a weekly settlement reconciliation cost a fraction of the penalty exposure they eliminate.




![Read article: Cyber Crime FIR in India: How to File Complaint for Online Fraud, Banking Fraud & Digital Harassment [2025 Guide]](/_next/image?url=%2Fapi%2Fmedia%2Ffile%2FCyber-Crime-Complaint.png&w=3840&q=75)
