Multi-Vendor Billing Software in India 2026: Automating Commissions, Payouts, TCS, and GST for a Marketplace

If you run a marketplace, an aggregator, or any business that collects money from customers and then pays out many vendors, your billing is almost certainly held together by a spreadsheet, a few WhatsApp messages, and one person who actually understands how the commissions work. It survives right up until it doesn't. The month a vendor disputes a payout, or GST filing lands, or that one person goes on leave, the whole thing wobbles.

Normal billing software bills one customer for one company. Multi-vendor billing is a different animal: a single customer payment has to be split across several sellers, each with their own commission rate, their own GST number, and their own payout schedule. Off-the-shelf invoicing tools are not built for this, which is why most marketplaces end up building it custom. This is the founder-honest guide to what that software has to do, what it costs in India in 2026, and when you should build versus stitch together what already exists.

We build these systems in Noida, usually on Laravel with a Postgres database, and they often sit right next to a MultiVendor CRM so vendor onboarding, orders, commissions, and payouts all live in one system. Here is how the billing side actually works.

Why marketplace billing is harder than normal billing

Single-seller billing is a straight line: customer pays, you raise one invoice, money lands in one account. A marketplace breaks every part of that line. One payment becomes many payouts. One transaction involves two GST identities. And you, the operator, are legally on the hook for tax you collect on someone else's behalf. The parts that simply do not exist in normal billing:

• One customer payment, many payees. A single ₹2,000 order might pay three different vendors plus your platform fee.
• Per-vendor commission that keeps changing. Flat percentage, per-category, volume tiers, and the special rate you negotiated with your biggest seller last quarter.
• Two GST identities per sale. The vendor's GSTIN on the customer invoice, and your GSTIN on the commission invoice you raise to the vendor.
• TCS you must collect for the government. As an e-commerce operator you withhold tax at source on the vendor's net sales, deposit it, and report it monthly.
• Payout timing and holds. You hold funds, release on a schedule, often keep a return or dispute window before money actually moves.
• Refunds and chargebacks that claw back from the right vendor. A return three weeks later has to reverse the correct vendor's payout, commission, and tax.
• Reconciliation. The gateway settlement, the order total, and the vendor payout are three different numbers, and someone has to match them every month.

What multi-vendor billing software actually has to do

1. Split payments at checkout

The customer pays once. The platform splits that payment into each vendor's linked account and keeps your commission, automatically. In India this runs on Razorpay Route or Cashfree Easy Split, which let you route parts of a single payment to multiple connected accounts. Getting the Razorpay integration right is the foundation; everything downstream depends on the split being recorded correctly at the moment of payment.

2. A commission engine

This is the piece that lives in a spreadsheet today and should not. A real engine handles flat percentages, per-category rates, per-vendor negotiated rates, and volume tiers, plus the awkward edges: who funds a promotional discount, who pays the shipping, and what happens to commission when a coupon is applied. If a human has to look up a rate to calculate a payout, the system is not finished.

3. GST invoices, in both directions

Every sale produces at least two tax documents. There is the customer tax invoice, which carries the vendor's GSTIN, and there is the commission or platform-fee invoice that you raise to the vendor with your GSTIN. On top of that, vendors expect a clean settlement statement showing gross sales, commission, TCS, and net payout. Proper GST invoicing with sequential numbering, correct IGST or CGST and SGST splits, and PDF plus WhatsApp delivery is table stakes, not a nice-to-have.

4. TCS under Section 52

This is the one founders forget until a notice arrives. As an e-commerce operator that collects payment on behalf of sellers, you are required to collect Tax at Source (around 1% of the net value of taxable supplies, under Section 52 of the CGST Act), deposit it, and file GSTR-8 every month. The vendor then claims that amount as credit. Rates and thresholds do change, so confirm the current numbers with your CA, but the software has to compute it per vendor, withhold it from the payout, and produce the GSTR-8 data without anyone re-keying numbers.

5. Scheduled payouts

Money moves to vendors on a schedule (T+2, weekly, or whatever you commit to), usually through RazorpayX or direct bank transfers. The software handles hold-and-release for return windows, minimum payout thresholds so you are not transferring ₹40, and an on-hold state for vendors under dispute. Every payout links back to the exact orders it covers.

6. Refunds, returns, and chargebacks

A refund is not just money back to the customer. It has to reverse the right vendor's share, adjust the commission you already counted, and reverse the TCS. If the vendor was already paid out, the amount is clawed back from their next settlement. Getting this wrong is how marketplaces quietly lose money for months before anyone notices.

7. Reconciliation

The dashboard that lets your finance person close the month in an afternoon instead of a week. It matches the gateway settlement to orders, orders to payouts, and payouts to invoices, then flags anything that does not line up. Without it, you are trusting that three systems agree, and they rarely do on their own.

The GST and TCS rules you cannot ignore

Two things trip up almost every new marketplace. First, invoice responsibility: in most models the vendor is the supplier to the customer, so the customer tax invoice carries the vendor's GSTIN, while you separately invoice the vendor for your commission. Getting this backwards creates a GST mess that is painful to unwind. Second, TCS: you collect it, you deposit it, you file GSTR-8 monthly, and the vendor reconciles it against their own returns. Build the billing system so this data falls out automatically at month end. The exact rate and any threshold should be confirmed with your accountant, because GST rules shift, but the architecture stays the same.

Real INR pricing for multi-vendor billing software in 2026

Tier 1: Billing and payouts module (₹60K-1.2L, 4-7 weeks)

What you get: split payments via Razorpay Route, a flat or per-category commission rate, customer GST invoices, vendor settlement statements, basic scheduled payouts, and a simple admin dashboard. Stack is usually Laravel with Postgres. Good for: a marketplace with up to roughly 25 vendors, straightforward commission rules, and moderate volume that just needs to stop running payouts by hand.

Tier 2: Full marketplace billing (₹1.2L-2.5L, 8-14 weeks)

Everything in Tier 1, plus a real commission engine (per-vendor rates, tiers, promotions), TCS computation with GSTR-8 export, automated payouts with hold and release windows, refund and chargeback clawbacks, a reconciliation dashboard, and a vendor portal where sellers download their own statements and invoices. Good for: an active marketplace with dozens to a few hundred vendors where finance is spending real time every month on settlements.

Tier 3: Enterprise and multi-entity (₹2.5L-5L+, 14-24 weeks)

Everything in Tier 2, plus multi-entity or multi-GSTIN support, multi-currency for cross-border sellers, two-way sync with Tally or Zoho Books or your ERP, bank-statement-level reconciliation, a formal dispute workflow, finance-team roles with audit logs, and an API vendors can pull their own data from. Good for: established marketplaces and aggregators with hundreds of vendors and a finance team that needs auditable books.

Monthly maintenance retainer

₹20-40K/month covers hosting, security patches, gateway and API token rotation, small feature additions, bug fixes, and a monthly reconciliation and performance check. Billing software is not a build-once-and-forget system: gateways change APIs, GST rules shift, and you will want new commission rules as the business grows. Budget for the retainer from day one.

Build it custom, or use what already exists?

Be honest about your scale before you spend. Razorpay Route plus a careful spreadsheet genuinely works when you are small. Subscription-billing tools like Chargebee or Zoho Billing are excellent, but they bill your customers for your own products; they are not marketplace settlement engines and will fight you the moment you need per-vendor commissions and TCS. Here is the rough line:

• Custom wins when: your commission logic is more than one flat rate, you are liable for TCS and GSTR-8, you want a vendor portal, refunds have to claw back across vendors, or reconciliation is eating days every month.
• Stay manual when: you have under roughly 20 vendors, a single flat commission, low volume, and no TCS exposure yet. Use Razorpay Route plus a tight spreadsheet and revisit once payouts start hurting.

Most marketplaces cross the line into custom somewhere between 20 and 50 active vendors, or the first time a GST notice makes the TCS question real.

How we build it

Billing software is money software, so the engineering bar is higher than a normal web app. We build the core on Laravel (or Node.js when the rest of the stack is JavaScript) with a few non-negotiables: money is stored as integers in paise, never floats, so rounding never silently loses rupees; every payment, payout, and refund is idempotent so a retried webhook cannot double-pay a vendor; and there is a ledger so every rupee is traceable from customer payment to vendor payout to invoice. Payouts run as scheduled background jobs, the vendor portal is a React or Next.js front end, and reconciliation is a first-class screen, not an afterthought. It pairs naturally with the same custom-build approach we use for CRMs.

Common questions about multi-vendor billing software

How much does it cost to build multi-vendor billing software in India?

A Tier 1 billing and payouts module starts around ₹60K-1.2L. A full marketplace billing system with a commission engine, TCS handling, refunds, and a vendor portal runs ₹1.2L-2.5L. Enterprise and multi-entity builds start at ₹2.5L. Plan for ₹20-40K/month maintenance on top. The final number depends on how complex your commission rules are and how many integrations (accounting, ERP, logistics) you need.

How long does it take?

Tier 1: 4-7 weeks. Tier 2: 8-14 weeks. Tier 3: 14-24 weeks. We work in weekly sprints with a demo each week, and we always build the split-payment and payout core first so you can run real money through it early and trust it before the rest is finished.

Can I just use Razorpay Route and skip custom software?

At small scale, yes. Razorpay Route handles the split at payment time, and a careful spreadsheet can cover the commission math and payouts for a handful of vendors. What Route does not do is your commission engine, GST invoicing both ways, TCS and GSTR-8, refund clawbacks, a vendor portal, or reconciliation. Custom software is the layer that wraps Route once those become real work.

How do you handle GST TCS and GSTR-8?

The software computes TCS per vendor on net taxable sales, withholds it from each payout, and produces the data you need to file GSTR-8 every month, so nobody re-keys numbers into a portal. We build the logic but always recommend your CA confirms the current rate and thresholds, since GST rules change and your accountant signs the return.

What happens on refunds and vendor disputes?

A refund reverses the correct vendor's share, the commission you counted, and the TCS. If the vendor has already been paid, the amount is clawed back from their next settlement. Disputed orders can be put on hold so the money does not move until it is resolved. Every adjustment is logged, so a vendor questioning their payout can be answered in minutes with a clear trail.

Can it integrate with Tally or Zoho Books?

Yes. Tally connects through its gateway and TDL scripts, and Zoho Books has a clean REST API. We sync customers, invoices, payouts, and TCS so your books stay current without manual entry. This is usually part of a Tier 2 or Tier 3 build; budget ₹15-30K extra per accounting integration.

How do you make sure the money math is actually correct?

Three habits. Money is stored as integers in paise so floating-point rounding can never lose rupees. Every payment, payout, and refund is idempotent, so a webhook fired twice cannot pay a vendor twice. And a ledger plus a reconciliation screen means every rupee is traceable end to end, with mismatches flagged automatically. We also write tests around the commission and TCS calculations specifically, because that is where money bugs hide.

Honest summary

Multi-vendor billing is the unglamorous system that decides whether your marketplace is trusted by its vendors. Sellers forgive a clunky dashboard; they do not forgive a payout that is late, wrong, or unexplained. Spreadsheets get you to your first 20 or so vendors, and Razorpay Route handles the split at checkout, but the commission engine, GST invoices both ways, TCS and GSTR-8, refunds, payouts, and reconciliation are where custom software earns its cost.

If your finance team is losing days every month to settlements, or a TCS question is keeping you up, it is worth scoping a build. The cost calculator gives a rough starting estimate, or send us a WhatsApp message with your vendor count, commission model, and current setup, and we will reply within 24 hours with a written scope and an INR range.