How an India-US SaaS company closed a 14-month books gap and stopped missing FEMA filings
A founder-led SaaS company had an India parent and a US subsidiary, two separate bookkeepers who never spoke to each other, and a missed RBI overseas-investment filing that surfaced only when a bank flagged an inbound remittance. We closed a 14-month reconciliation gap and put one team across both entities' calendars in six weeks.
The challenge
The company had incorporated a Delaware C-corp to bill US customers in dollars, while the original India entity kept the engineering team and Indian customer contracts. Each side had its own bookkeeper — an India CA firm for the parent, a US bookkeeping service for the subsidiary — and neither had visibility into the other's filings.
The gap surfaced when the founder tried to move retained earnings from the US subsidiary back to India and the bank asked for the RBI Form FC and Annual Performance Report that documented the original investment. Neither had been filed. The US side, meanwhile, had never filed Form 5472 for the intercompany management fee the India entity was charging the subsidiary — a $25,000 minimum penalty per year missed.
Books on both sides hadn't been reconciled against each other in 14 months. The India entity's ledger showed one number for the intercompany fee; the US entity's ledger showed a different number, because of a currency-conversion timing mismatch nobody had caught.
Our approach
We paired a CA on the India side with a CPA-partnered US bookkeeper under one engagement, working from one shared reconciliation model rather than two separate ledgers reporting different numbers.
First pass: rebuild the intercompany transaction history month-by-month, applying a consistent conversion-rate policy (RBI reference rate on the transaction date) so both entities' books tie out to the same intercompany balance.
Filed the retrospective RBI Form FC and the missing Annual Performance Reports for each year the subsidiary had existed, working with the Authorised Dealer bank to document the delay and avoid it recurring on the retained-earnings transfer already in motion.
Filed the outstanding Form 5472 + pro-forma 1120 for the US entity, along with a reasonable-cause statement — the IRS does not automatically penalize when correction happens before an audit notice, but only if the filing gap is closed properly and promptly.
Built one shared compliance calendar covering both jurisdictions — RBI APR due dates, US Form 1120/5472/BOI due dates, and India ITR/GST due dates — with the founder cc'd on every filing confirmation from both teams, not routed through them.
The results
Both entities' books reconciled to the same intercompany balance within 6 weeks, with a documented, repeatable month-end close process going forward.
The retained-earnings transfer the founder originally wanted completed inside 3 weeks of the retrospective RBI filings clearing, instead of stalling indefinitely at the bank.
Filed the missing Form 5472 proactively, before any IRS notice — avoiding what would have been a minimum $25,000 penalty per missed year had it surfaced in an audit instead.
The founder now gets one monthly close from one team, instead of reconciling two bookkeepers' numbers against each other himself.
Takeaways
- Two entities need one compliance calendar tracked by people who talk to each other — not two bookkeepers each covering their own half and assuming the other side is handled.
- Banks enforce RBI filings at the least convenient moment: when you actually try to move money. Retrospective filing is possible but slower than filing on time would have been.
- Fixing a US filing gap before an IRS notice arrives is a different, much cheaper conversation than fixing it after one does.
Thinking about a similar project? Let's talk specifics.
Book a free 45-minute call. Bring your current numbers; we'll bring an honest opinion on what would actually move them.
Book ConsultationHow an India-US SaaS company closed a 14-month books gap and stopped missing FEMA filings — FAQ
Questions we usually get about projects like this one.
The outcome above is specific to this client's baseline, market, and constraints — we don't promise identical numbers. What we can replicate is the method: the same diagnostic, the same attribution discipline, and the same hand-coded delivery approach used on this finance engagement. During the discovery call we will map your starting point against this case and tell you what parts of the playbook realistically transfer and which would need to be adjusted.
For finance engagements we default to a lean, well-supported stack: React + Vite for custom frontends, Node.js or serverless functions on Vercel for any backend, Shopify / WooCommerce where commerce is in scope, GA4 + PostHog + server-side tagging for analytics, Meta Ads / Google Ads / LinkedIn Ads for paid, n8n or native Zapier for workflow automation, and Tally / Zoho Books for accounting integrations. We pick the simplest tool that clears the bar — we don't sell stack complexity.
This specific engagement ran for the period referenced above. Typical finance projects of comparable scope take between 4 and 12 weeks from kickoff to launch, with a further 4 weeks of post-launch iteration. Fixed-scope work is priced upfront; open-scope work is run on a monthly retainer with weekly written updates so there are no invoice surprises.
Pricing depends on scope, integrations, and whether we are starting from scratch or improving an existing setup. We publish transparent price bands per dimension on our pricing page — engagements comparable to this case study typically sit in the mid-tier band for Finance. You can see exact ranges at /pricing, and we confirm a fixed fee (or retainer range) before any work begins.
You do. All code is delivered into your GitHub / GitLab organisation. Ad accounts, analytics properties, domains, and hosting sit in your name — not ours — from day one. On handoff we transfer admin access, document every integration, and record a 30-minute video walkthrough of the stack so your next hire or incoming agency can pick it up without us being a single point of failure.
More case studies
How a Bangalore D2C skincare brand cut bounce rate 41% with a hand-coded rebuild
A skincare brand was losing mobile shoppers at the homepage because their Shopify theme was shipping 2.1 MB of JavaScript. We rebuilt the storefront on a custom stack, kept the Shopify backend, and cut time-to-interactive from 5.4 seconds to 1.9 seconds.
Read case studyFrom ₹1.2 L CAC to ₹38K CAC: scaling a B2B SaaS on LinkedIn Ads
A founder-led SaaS was paying ₹1.2L to acquire each paying customer on LinkedIn Ads. We rebuilt their funnel, targeting, and creative, and brought CAC down to ₹38K inside one quarter — with more customers than before, not fewer.
Read case studyA Delhi fintech replaced 14 spreadsheets with one warehouse and three dashboards
A founder was spending 6 hours every Monday rebuilding the same weekly business review from spreadsheets pulled out of five different systems. We set up a BigQuery warehouse, dbt models, and three dashboards. He got his Mondays back.
Read case studyLet's talk about your business.
Tell us what you're working on and where you want to go. We'll put together a plan. No obligation, no sales pitch.
- Free 30-minute call
- A plan built around your goals
- No obligation, no pressure
- Your own account manager