Built for Bangalore SaaS, startups, e-commerce, and CA firms — across Koramangala, Indiranagar, HSR Layout, Whitefield, and Electronic City. Karnataka GST (state code 29), recurring billing, export of services (LUT), TCS for marketplaces, ESOP accounting. Free plan available.
From SaaS recurring billing to e-commerce TCS — every Bangalore business covered.
State code 29 is applied automatically to every Bangalore GSTIN. Intra-state (CGST + SGST) and inter-state (IGST) classification handled by place-of-supply rules.
Subscriptions with monthly, quarterly, or annual cycles. Pro-rata billing for mid-cycle upgrades. Stripe / Razorpay integration. ARR / MRR reporting alongside GST-compliant Indian invoicing.
Software exports from Bangalore as zero-rated supplies. LUT-aware invoice generation, GSTR-1 export table routing, and foreign-currency receipt reconciliation built-in.
Marketplace payouts (Amazon, Flipkart, Meesho) reconciled net of TCS under Section 52. GSTR-8 reconciliation. TCS credit auto-claimed in your electronic cash ledger.
Grant-date fair-value computation, vesting tracking, expense recognition over the vesting period, and exercise-event share capital entries. Built for Bangalore startups with active ESOP pools.
Ask "What is our cash runway?" or "How much MRR did we add last month?" Bangalore founders short on accounting time get instant answers without building reports.
Built for how Bangalore companies actually run.
Bangalore startups operate distributed teams from day one. Cloud accounting from any laptop — not "the machine in the office with Tally on it" — is non-negotiable.
SaaS and IT services are service businesses. SAC codes, B2B service GST, export-of-services with LUT, and recurring billing are first-class — not tacked on for "Indian compliance".
Section 52 TCS reconciliation across marketplaces is painful in Tally and Zoho. ReadyBooks.ai pulls GSTR-8 from each marketplace, matches it line-by-line, and reconciles the TCS credit automatically.
Startups fundraising need clean books fast. ARR / MRR cohort reports, runway projections, and an AI assistant that answers due-diligence questions in plain language — useful when an investor email arrives at 2am.
Bangalore is India's densest concentration of SaaS, IT services, and consumer-internet companies. The accounting needs of these businesses differ from a Mumbai wholesale trader or a Surat manufacturer — recurring revenue accounting, multi-currency invoicing, export of services with LUT, ESOP grants, TCS on marketplace sales, and the cash-flow sensitivity of an early-stage company that has not raised its next round.
ReadyBooks.ai covers all of these out of the box. SaaS recurring billing produces revenue schedules under AS-9 / Ind AS 115. Multi-currency invoices in INR, USD, GBP, and EUR are accepted by the GSTR-1 schema. Export-of-services flow with LUT is a checkbox, not a settings nightmare. ESOP accounting under Ind AS 102 is templated. Startup founders get this without paying for an enterprise tier.
A subscription business in Bangalore typically bills monthly, quarterly, or annually. Each billing cycle generates an invoice; each invoice flows into GSTR-1 in the period it was issued (not the period it was paid). ReadyBooks.ai handles the timing — the invoice issue-date determines GSTR-1 inclusion, the receipt-date determines bank reconciliation, and revenue recognition (under AS-9 for non-Ind-AS companies or Ind AS 115 for Ind AS companies) follows the service period regardless of invoice date.
Mid-cycle plan changes — upgrading a customer from Lite to Pro on day 12 of a monthly cycle — produce pro-rata adjustments. ReadyBooks.ai computes the proration credit on the old plan and the proration charge on the new plan, generates the corresponding credit note + invoice, routes both to GSTR-1, and updates the customer ledger correctly. Common operations that mainstream Indian accounting tools either do not support or require manual intervention for.
For B2B customers in India, the SAC code for software subscriptions is typically 998314 (online information / software). For B2C customers, the same SAC applies. For business customers in another state (intra-India), the GST is IGST. For consumers in another country, the supply is zero-rated under LUT or eligible for IGST refund.
Most software exports from Bangalore are zero-rated supplies under Section 16(1) of the IGST Act. The exporter has two options: pay IGST upfront and claim a refund later, or file a Letter of Undertaking (LUT) to ship without IGST payment. The vast majority pick the LUT route because the refund cycle is slow.
LUT is filed annually via GST RFD-11 on the GST portal. Once filed, every export invoice for that financial year must reference the LUT. ReadyBooks.ai stores your LUT details, prints the LUT reference on every export invoice, routes the invoice to the GSTR-1 "exports without payment of tax" table, and includes the FOB value, country of destination, port of export, and shipping bill details (where available).
Foreign-currency receipts against export invoices are reconciled via the FIRC (Foreign Inward Remittance Certificate) issued by your AD bank. ReadyBooks.ai matches the FIRC value against the original invoice value at the bank reconciliation step, applies the FX gain or loss to the books, and produces the FIRC-wise export realisation report that some authorised dealer banks require.
Bangalore is also home to a significant chunk of India's D2C and e-commerce sellers. Sales through Amazon, Flipkart, Meesho, and similar marketplaces attract TCS (Tax Collected at Source) at 1% under Section 52 of the CGST Act. The marketplace collects the TCS, deposits it with the GST department under the seller's GSTIN, and files GSTR-8.
For the seller, the workflow is: invoice generated to the buyer (with full GST), marketplace collects payment net of TCS + marketplace commission, marketplace remits to the seller, and the TCS credit shows up in the seller's electronic cash ledger (visible in GSTR-2X). ReadyBooks.ai automates this reconciliation: marketplace settlement reports (Amazon, Flipkart, Meesho all have downloadable settlement files) are imported, payouts are matched to invoices, TCS is reconciled against the marketplace's GSTR-8, and the cash ledger credit is reflected in the GSTR-3B liability set-off.
Common failure mode in Tally / Zoho workflow: TCS amount sitting in a "marketplace deductions" suspense account because the seller never reconciled it against GSTR-8. ReadyBooks.ai forces reconciliation, so TCS credit is claimed correctly and the seller does not pay GST twice (once net of TCS, once forgotten as a credit).
LUT details stored once, applied to every export invoice automatically. FIRC matching at bank reconciliation. Monthly export realisation report ready for the AD bank without spreadsheets.
All three settlement reports imported into a single TCS reconciliation dashboard. TCS credits matched against GSTR-8 from each marketplace. The "where is my GST refund" question stops.
Multi-client dashboard with per-client GST configuration. SaaS clients get LUT + export-of-services flow; D2C clients get TCS + GSTR-8 reconciliation. One platform, two distinct workflows handled correctly.