Back to thinking
India 4 Jun 2026

The Indian Fiscal Year Problem: Why Generic SaaS Doesn't Work for Indian Businesses (And What to Do About It)

Indian businesses run April to March fiscal year. Most generic SaaS hardcodes January year-start. Most generic SaaS also defaults to comma-thousand currency formatting (₹100,000) instead of lakh formatting (₹1,00,000). And most generic SaaS treats multi-entity invoicing as an enterprise upsell. These three gaps cost Indian operators measurable time and confidence every month. Here's exactly what breaks, what we tried, and the workarounds that work.

**Indian businesses run April to March fiscal year. Most generic SaaS hardcodes January year-start. Most generic SaaS defaults to comma-thousand currency formatting (₹100,000) instead of lakh formatting (₹1,00,000). And most generic SaaS treats multi-entity invoicing as an enterprise upsell. These three gaps cost Indian operators measurable time, money, and confidence every month, and the global product roadmap of US-first SaaS isn't fixing them.**

We hit all three building NOW Media. After two years of workarounds across HubSpot, Pipedrive, Zoho, and Notion, we built our own operations command center. The Indian-FY + multi-currency + multi-entity decisions baked in from day one are the reason it works for our business. This is the full breakdown of what breaks in generic SaaS, what we tried, what worked, and what to do if you're operating Indian-context and stuck with US-first tools.

If you're a CFO, ops lead, or founder running an Indian-incorporated business and your team spends measurable time reconciling tool outputs against your actual financial calendar, this is for you.

— — —

The three gaps, ranked by daily cost

Gap 1: Fiscal calendar

The problem: India's fiscal year runs April 1 to March 31. Most SaaS hardcodes January 1 to December 31 reporting. Even SaaS that lets you "set a custom fiscal year" typically applies it to *display* only, quarter calculations, pipeline reports, and year-over-year comparisons still run on calendar-year math underneath.

**What breaks in practice**:

  • Pipeline reports that show "Q1 performance" mean Jan-Feb-Mar (US Q1) when your Q1 is Apr-May-Jun.
  • Revenue dashboards showing "vs same period last year" compare January through October to January through October instead of fiscal year to date.
  • Year-end close reporting in tools like HubSpot fires in December instead of March.
  • Audit prep happens twice, once for the SaaS's calendar-year close, once for your actual fiscal-year close.
  • Team performance reviews that auto-roll up "annual" metrics use the wrong twelve months.

Real cost we measured: at NOW Media before the command center, our ops team spent roughly 8 hours per quarter reconciling HubSpot's calendar-year pipeline reports against our actual April-start fiscal targets. That's 32 hours a year of pure reconciliation work, finding the right cells in HubSpot, manually shifting the date ranges, exporting to spreadsheets, rebuilding the math.

The deeper problem: even when we got the reconciled numbers, the team didn't trust the dashboard. Anything that needed FY-correct math went to a side spreadsheet. The CRM became a glorified contact database, not the operating system it was supposed to be.

Gap 2: Currency formatting

The problem: Indian English convention writes large numbers with the lakh-comma. ₹1,00,000 is one lakh. ₹1,00,00,000 is one crore. Most US-first SaaS displays ₹100000 or ₹100,000, using either no commas or the thousand-comma convention.

**What breaks in practice**:

  • Quote PDFs sent to Indian clients display amounts in a format that looks wrong to every Indian reader. Clients have flagged it to us specifically.
  • Internal review of large pipeline figures requires mental conversion every time, is ₹50000000 fifty lakh or five crore? You have to count the zeros to be sure.
  • Invoices imported into Zoho or Tally end up with format mismatches that take manual cleanup.
  • Slack notifications about deal sizes ("New deal: ₹1500000") require translation to the lakh-crore reference frame humans actually think in.

Real cost: at scale, currency formatting is a small per-instance cost (~30 seconds of mental conversion) that compounds. Across 100 financial documents per month per ops person, that's 50 minutes of pure conversion friction. More importantly, it's a confidence drag, every document looks slightly off to the Indian reader, which subtly undermines the tool's perceived authority.

The deeper problem: it signals the tool wasn't built for you. Once that perception sets in, the team treats the tool as foreign infrastructure rather than core operating software.

Gap 3: Multi-entity by default

The problem: Indian businesses commonly operate multiple legal entities, services revenue under one Pvt Ltd, product revenue under another, IP holdings under a third, sometimes a foreign entity for international clients. Generic CRMs assume one company per account. Workarounds exist (duplicate pipelines, tag-based segregation, custom properties) but they're patches.

**What breaks in practice**:

  • Invoices generated from the CRM use the same entity for every client, manual override required per invoice when billing under the alternate entity.
  • P&L rollups by entity require exporting to a separate spreadsheet and tagging by hand.
  • Client records get duplicated when the same client gets billed under different entities for different projects (services under entity A, product under entity B).
  • Auditor reporting per entity becomes a one-off manual reconciliation rather than a dashboard view.
  • Pipeline reports don't distinguish "won under entity A" from "won under entity B", affecting how revenue forecasting maps to legal cash flow.

Real cost: at our scale (two entities, ~150 active clients), manual entity assignment on invoices added ~3 hours per month of ops work. More significant: tax season reconciliation per entity added ~12 hours in March every year.

The deeper problem: this isn't a workflow nuisance, it's a compliance risk. Wrong-entity invoicing creates downstream cleanup with implications for GST input credit, transfer pricing documentation between entities, and Companies Act compliance.

— — —

What we tried (and why each failed)

We didn't jump straight to building. We tried four serious workarounds first.

Workaround 1: Custom HubSpot properties + custom reports

We built custom date properties on HubSpot deals (dealclosefyquarter, dealclosefyyear) populated by HubSpot Workflows from the standard close_date. Custom reports filtered on these properties to give us FY-aligned pipeline.

Why it failed: HubSpot Workflows fire on property changes, which means historical deals (closed before we added the workflow) had no FY properties. Backfilling required a one-time export, manual computation, and re-import. Going forward, every new deal had a 60-second delay between close_date being set and the FY properties being populated, which broke real-time dashboard reporting. The math worked; the operational reliability didn't.

Workaround 2: Pipedrive + Zoho Books with Zapier sync

Pipedrive for pipeline (calendar-year display, but we ignored its native reports), Zoho Books for invoicing (Indian-FY native, multi-currency native, GST native). Zapier zaps to sync deals → Zoho clients and won deals → Zoho draft invoices.

Why it failed: cross-tool sync is fragile. Pipedrive's API rate-limited unexpectedly during a busy week. Zoho changed an invoice-creation field name and our zap broke silently. We missed three invoice deadlines before noticing. The cleanup took two weeks. The Zapier-glue approach gives you the surface of one system and the failure mode of N + glue.

Workaround 3: Notion-as-CRM with Indian-FY rollup database

Notion is infinitely customizable. We built a database for deals with Indian-FY columns computed by formula. Rollup database for revenue by FY quarter. Linked to an invoicing database.

Why it failed: Notion is great for documents and bad for transactional data. The deal database hit Notion's view performance limits at ~600 records. Sorting + filtering became slow. The team stopped using filters and reverted to manual scrolling. Worst case for any tool: built correctly, used incorrectly.

Workaround 4: Salesforce Essentials + custom Apex

Briefly evaluated. Indian-FY reporting in Salesforce requires Apex code (Salesforce's programming language) or expensive third-party AppExchange tools. Multi-entity invoicing requires Salesforce's Revenue Cloud (₹50K+/user/month). Multi-currency at Essentials tier is limited.

**Why we didn't pursue**: the customization cost approached the cost of building our own from scratch, without the productization upside. Salesforce + Indian-context customization is a path that works for ₹500Cr+ companies with dedicated Salesforce admins. Not for a 30-person creative studio.

— — —

What works (the workarounds that survive)

If you're not ready to build, these are the workaround stacks that genuinely work for Indian-context businesses without compounding fragility.

Stack A: Zoho One (₹4,500/user/month)

Zoho is the only major SaaS suite built India-first. Zoho CRM, Zoho Books, Zoho Invoice, Zoho Projects, Zoho Analytics, all natively understand Indian fiscal year, lakh-crore currency formatting, GST, and multi-entity setups. The UX is dated and the integrations outside the Zoho ecosystem are clunky, but the India-first defaults solve all three gaps.

Best fit: companies with 5 to 50 employees, mostly Indian clients, willing to standardize on a single vendor.

**Limitations**: Zoho CRM's pipeline UX is meaningfully worse than HubSpot/Pipedrive. The team you ask to use it daily will push back. Plan for change management.

Stack B: HubSpot + Tally + manual reconciliation

HubSpot for sales pipeline (accept calendar-year reporting and build mental translation), Tally for accounting (Indian-FY native, GST native, multi-entity strong), manual quarterly reconciliation between the two. Use Tally for the system of record on revenue and HubSpot purely for pipeline management.

Best fit: companies that already have Tally for accounting (most Indian businesses do) and want HubSpot's pipeline UX without rebuilding the accounting layer.

**Limitations**: the dashboards you actually look at daily are in HubSpot, which means you'll mentally translate FY math every morning. Acceptable cost for some teams.

Stack C: Pipedrive + Zoho Books (carefully)

Pipedrive for pipeline (calendar-year display tolerated), Zoho Books for invoicing and Indian-FY accounting. Avoid Zapier glue, use Pipedrive's native Zoho integration and accept the lag between deal close and invoice creation. Manual entity assignment on each invoice.

Best fit: small teams where the ops person can do manual entity tagging without it becoming a bottleneck.

**Limitations**: stops scaling around 100 active client engagements.

Stack D: Build your own

What we eventually did. Worth it only if (a) you have engineering capacity, (b) your operational gaps are structural enough that workarounds keep breaking, and (c) you can amortize the build cost (either across multiple business units or by productizing).

We covered the build cost vs rent cost math in detail in Why we built our own command center.

— — —

What an Indian-FY native system looks like

If you do build, or evaluate a tool that claims India-first, these are the specifics to check for.

Fiscal year reporting

  • Year selector defaults to current FY (April to March), not calendar year.
  • Quarter labels read Q1 (Apr to Jun), Q2 (Jul to Sep), Q3 (Oct to Dec), Q4 (Jan to Mar).
  • "Vs same period last year" comparisons align fiscal periods, not calendar periods.
  • Smart pro-rating on FY targets: if you set ₹4Cr annual on May 15, the system pro-rates May, Q1, and YTD targets to account for elapsed days.
  • Quarter close reports auto-generate on the 1st of April/July/October/January.
  • Year-end close auto-generates on April 1 with the prior FY summary.

Currency formatting

  • INR amounts display with lakh-comma: ₹1,00,000 not ₹100,000.
  • Large amounts use crore-comma: ₹1,00,00,000 not ₹10,000,000.
  • Toggle option in user settings for traditional accountants who prefer the thousand-comma convention (some firms do).
  • Multi-currency displays without forced conversion, show ₹2,50,000 + $3,000 separately, not ₹4,98,000 with embedded forex.
  • PDF exports respect the user's locale formatting.

Multi-entity setup

  • Each invoice is generated under a specific legal entity (selected at invoice creation, defaults to deal-tagged entity).
  • Client records can have multiple entity relationships, "Client X has services with Entity A and product subscription with Entity B."
  • P&L rollups can be filtered by entity.
  • Tax compliance per entity (GST returns, TDS) is generated per entity.
  • Inter-entity invoicing supported (Entity A bills Entity B for shared services, common in holding-company structures).

Indian payment methods

  • UPI integration (the bare minimum in 2026).
  • IMPS / NEFT / RTGS payment reconciliation (matching bank deposits to invoices).
  • Cheque tracking (still very common for large B2B payments in India).
  • TDS handling on incoming payments (auto-deduct TDS at the right percentage based on PAN/section).

— — —

What to do this week

If you're stuck with a generic-SaaS stack and the gaps above sound familiar, the cheapest immediate fixes:

  1. **Don't try to fix fiscal year reporting in your existing CRM.** Accept it for pipeline, do real revenue reporting in your accounting tool. Most Indian businesses already do this, formalize it as the policy.
  2. **Add a "lakh-crore" Slack bot or browser extension** for instant currency translation. The Slack /lakh command takes a number and replies with the Indian-format version. We had one for a year before the command center launched. Reduced friction noticeably.
  3. **If you operate multi-entity**, build a one-page entity-assignment cheat sheet for the ops team: "Service X for Client Y is billed under Entity A. Service Z for Client Y is billed under Entity B." Put it in Notion. Reference it every time an invoice goes out. Cheap, reliable.
  4. **For pipeline reporting that needs to be FY-correct**, build a Google Sheet that imports your CRM data via Zapier or native integration and re-pivots on Indian-FY periods. Refresh quarterly. Acceptable as a stop-gap.
  5. **If you're 12+ months from a possible custom build**, evaluate Zoho One for the simplification gain. India-first defaults solve all three gaps. The UX cost is real but quantifiable.

— — —

What we're doing at NOW Media

Our operations command center handles all three gaps natively, built that way from day one. The product is currently used internally to run NOW Media's entire creative practice. It is being productized for external availability. Custom builds for clients are available today under the AI Automation service at ₹15L to ₹30L (8 to 16 weeks), built specifically for your business workflow rather than retrofitted from a generic SaaS.

If you want the build-cost-vs-rent-cost math for your specific situation, start your scope, happy to do the analysis.

— — —

FAQ

Does Zoho fully solve the Indian fiscal year problem?

For most use cases, yes. Zoho's products are India-first by default, Indian FY is the default in Zoho Books and Zoho Analytics, lakh-crore formatting is native, multi-entity is supported in higher tiers. The trade-off is Zoho's UX is dated compared to HubSpot or Pipedrive, and the cross-product integrations within Zoho One are clunkier than equivalent integrations within Microsoft 365 or Google Workspace. For Indian-context simplification, it's the most pragmatic single-vendor choice.

Can I make HubSpot work for Indian fiscal year?

With effort, yes, but the effort doesn't end. HubSpot Workflows can populate custom FY properties on deals. Custom reports can filter on them. The math works. What doesn't work is the operational reliability: historical deals require backfilling, new deals have lag between close and FY property assignment, and any HubSpot UI update can break the workaround. We ran this for 6 months before giving up. Workable for teams that have dedicated HubSpot admin time. Not workable for teams that want to set it and forget it.

Why doesn't generic SaaS just add Indian FY support?

Two reasons. First, the global product roadmap goes to the biggest market first, US-first SaaS prioritizes US customer requests, then EU, then Asia-Pacific (where India is one of many markets). Second, "Indian fiscal year" sounds like a localization checkbox but is actually a deep change, it affects pipeline math, quarter rollups, year-over-year comparisons, audit reporting, and dozens of derivative reports. Half-implementing it (display-only, with calendar-year math underneath) creates user confusion worse than not implementing it. So SaaS teams either commit fully or skip.

Is lakh-crore formatting a real productivity cost?

Yes, but small per instance. ~30 seconds of mental conversion per financial document for users who think natively in lakhs. Across an ops person reviewing 100 financial documents per month, that's roughly 50 minutes of pure conversion friction. The bigger cost is psychological, every document looks slightly off to the Indian reader, which subtly undermines the tool's perceived authority and adoption.

What about Tally?

Tally is the most widely-used accounting software in India and natively handles FY, GST, multi-entity, lakh-crore, everything. Limitations: dated UX (DOS-era keyboard shortcuts are still primary), weak collaboration features (it's primarily single-user-at-a-time), and no built-in CRM or project management. If you already use Tally for accounting (most Indian businesses do), pair it with a separate sales pipeline tool. Don't try to make Tally the system of record for sales.

What's the right stack for a 10-person creative studio in Bangalore?

For most teams in this size: Zoho One (CRM + Books + Projects + Analytics for ₹4,500/user/month covers everything) OR Pipedrive + Zoho Books + manual entity assignment + Slack reminders. The "build your own" path only makes sense if you have a 12-month-plus operational tenure that justifies the engineering investment plus a productization upside.

How does multi-currency interact with Indian fiscal year for revenue reporting?

Carefully. If you bill in INR, USD, and AED, you need to decide whether to report revenue at booking-rate forex or settlement-rate forex. Most teams choose booking-rate for management reporting and settlement-rate for statutory accounting, meaning your management dashboards diverge from your audited financials by ~3-5% depending on currency movement. Document the convention explicitly and apply it consistently. Generic SaaS rarely handles this well, either it forces conversion to base currency at unclear rates, or it doesn't convert at all and you can't sum across currencies cleanly.

— — —

*NOW Media is a Bangalore creative studio founded in 2019 by Nithin Koshy and Divya Maben, a brand of Bleep Design Private Limited. Our operations command center handles Indian FY, multi-currency, and multi-entity natively, currently used internally, coming soon to market. Start your scope or view the AI Automation service.*

Internal links