You're running three invoicing platforms: Xero for GL reconciliation, Wave for contractor payables, and Chargebee for recurring SaaS revenue. Each one works well at its job. Your CFO suggests consolidating into one—Odoo, Zoho Books, or a mid-market ERP. It sounds rational. One login. One vendor. One contract renewal cycle. It's also wrong. The math says you should keep them separate. Consolidation isn't cheap. It's a layered cost: migration friction (data loss, process rewrites), customization tax (forcing your invoicing logic into someone else's mold), switching risk (you're now trapped with a platform that doesn't fit), and retraining drag. A finance team moving three platforms into one often spends ₹35–45 lakh on the migration alone—and then hits the operational tax year one. A sync layer—Make, n8n, or Zapier—costs ₹2.4–3.6 lakh annually and keeps you flexible. You run best-of-breed tools and control the integration rules yourself. When one platform breaks or raises prices, you leave without rewriting your GL or contract-to-cash workflows. Why consolidation hides its real cost Finance leaders see one invoice platform and think: simpler, cheaper, faster. Vendors will tell you that too. They won't mention what breaks in the move. Data migration is never clean. A ₹35L invoice in Wave doesn't map to Odoo's line-item structure without manual touch. Recurring billing logic in Chargebee doesn't translate to Wave's flat-fee model. You're paying for API development, data auditing, and reconciliation drift. Most teams budget 8–12 weeks of finance + tech time. That's ₹15–25 lakh right there. Process collapse. Xero's GL reconciliation workflow is different from Zoho Books'. Your AP team's approval rules don't move over. Your tax-ID validation logic (critical for Malaysia and Singapore) gets replaced with the platform's native logic, which may not match your regional compliance rules. You're not just changing tools; you're rewriting finance operations. Budget another ₹8–12 lakh for process redesign. Customization lock-in. One platform can't do three jobs equally well. Xero's GL is strong but invoicing is average. Chargebee is built for recurring revenue but will choke on contractor payables. So you customize. You build custom fields, approval workflows, tax rules. By year two, your Odoo instance is so customized that switching costs exceed the original migration bill by 3x. You're now stuck—not because the platform is good, but because leaving would cost ₹80+ lakh in rewrites. Switching risk crystallizes. Once your GL, AP, AR, and billing logic all live in one platform, you can't leave without rebuilding the whole finance stack. Vendors know this. Odoo starts with a ₹35K bill. Year two it's ₹47K (see: Orin's accounting module for built-in alternatives). You're trapped. The consolidation you bought for safety now cost you flexibility and pricing power. The math: Consolidation vs. sync-layer economics Let's model a real case: a ₹50 crore ARR company with invoicing spread across Xero (GL), Wave (contractor payables), and Chargebee (SaaS recurring billing). Consolidation path (Odoo): Migration and data cleanup: ₹25 lakh Process redesign: ₹10 lakh Year-one Odoo fees + customization: ₹15 lakh Year-two Odoo fees + continued customization: ₹20 lakh Year-three and beyond: ₹20–25 lakh/year Three-year total: ₹90 lakh Best-of-breed + sync-layer path: Initial Make/n8n setup: ₹3 lakh (one-time) Year-one Make costs + vendor SaaS: ₹24 lakh Year-two: ₹24 lakh Year-three: ₹24 lakh Three-year total: ₹75 lakh Plus: Zero switching cost if you need to change invoicing platforms The best-of-breed approach costs ₹15 lakh less over three years. More important: on day 91 of year four, if Odoo raises prices or a competitor launches a better GL platform, you're locked in. With a sync layer, you're not. You can move Chargebee to Recurly, swap Wave for Bill.com, or shift to Orin's combined billing + GL module without rewriting everything. When consolidation actually wins (and it's rare) Consolidation makes sense in two scenarios: You have fewer than 8 people in finance. If you're a ₹5–10 crore company with one finance person and no dedicated integration engineer, maintaining a sync layer is overhead. A consolidated platform handles the handoff for you. You'll pay more per dollar of revenue, but you'll save operational anxiety. Your invoicing logic is dead simple. No regional tax rules, no multi-currency rounding, no recurring-plus-one-off hybrid billing, no contractor payables. Just: create invoice, send, collect payment, post to GL. If that's you, Zoho Books or FreshBooks alone might work. But if you're reading this, that's not you. For everyone else—especially growth-stage companies with regional complexity (Malaysia, Singapore, Indonesia tax compliance; multi-currency invoicing; mixed billing models)—the sync layer wins on both cost and flexibility. Building the sync layer that replaces consolidation A working best-of-breed stack needs three a