Two clouds become four.
Then five.
Then your CFO asks for one number.
SaaS-acquires-SaaS integration brings 2–5 cloud bills, three chart-of-accounts conventions, and a 90-day clock on Day-1 close. Tovin.io is the multi-vendor cloud ledger built for the acquirer's finance lead — not the Fortune 500 FinOps program.
Post-merger cloud integration is the workflow of consolidating two or more SaaS companies' cloud bills (AWS, GCP, DigitalOcean, Snowflake) into a single ledger, allocating spend to the post-acquisition cost-center structure, and reporting integration variance against the deal model. With read-only credentials to both estates, a SaaS finance team typically has consolidated reporting live in two weeks and a clean integration variance report inside 90 days.
The Day-1 problem
What every SaaS-acquires-SaaS deal looks like for cloud cost.
Two clouds, then four, then five
Acquirer on AWS. Acquired on GCP plus a DigitalOcean sandbox. Often a Snowflake account on each side. Finance inherits 3–5 separate invoices arriving on different days, with different SKUs, and no consolidated view.
No shared chart of accounts
Each company allocated cloud differently — by team, by product, by legal entity, or not at all. The deal model assumed synergies; the deal model didn't define how to measure them.
Purchase-accounting timeline pressure
Day-1 close, opening balance sheet, and the 90-day integration plan all need a single consolidated cloud cost number. Engineering is heads-down on technical integration. Finance can't wait three quarters for FinOps to build out.
Retained-employee uncertainty
The acquired company's cloud admins may or may not be staying. Read-only credentials carry zero risk if they leave; full access roles do.
The 90-day plan
Week-by-week. Owned by finance, scoped to the controller's calendar, not a six-month FinOps rollout.
- Week 1
Inventory both cloud estates
Connect AWS, GCP, DigitalOcean (and Snowflake, Datadog, etc.) accounts from both legal entities with read-only credentials. No engineering implementation; finance owns the run.
- Weeks 2–3
Map to post-acquisition cost centers
Define the post-acquisition product / cost-center structure. Apply tag-, account-, and rule-based allocation so every line item from both estates lands in the new chart of accounts — without touching the production resources.
- Weeks 4–6
Run the first joint month-end close
Reconcile the consolidated cloud bill against the GL. Variance vs purchase-accounting assumptions surfaces in the same view the operating finance team uses for ongoing close.
- Weeks 7–12
Produce the integration variance report
Quarterly board update: integration synergies realized vs deal model. Cloud-cost contribution to the synergy plan, decomposed into price, volume, and mix — the same pattern that drives ongoing variance reviews.
Tovin.io's role in the integration
- Read-only credentials to both estates, KMS-encrypted at rest. Zero blast radius — credentials cannot modify resources, change billing, or read customer data. Retained-employee turnover is a credential rotation, not an integration risk.
- Allocation rules adapt to the new cost-center structure. Tag, account, and regex-based mapping applied across both estates. No production change required. Wrong allocation? Re-run the mapping; history rebuilds.
- Separate ledgers per legal entity, one consolidated parent. Supports the carve-out + portfolio-company pattern where the legal entity collapse trails the operational integration. Folds back into the consolidated view automatically when the legal merger lands.
- Integration variance vs deal model. The same variance-decomposition tooling the operating finance team uses for monthly close — applied to the synergy plan. Price / volume / mix decomposition in the management memo, not just a rolled-up delta.
- CSV out, GL-friendly. Cost-center allocation flows into your accounting system via the same CSV path the ongoing close uses. Purchase-accounting entries stay where they belong — in your ERP. Tovin.io is the source for the cloud line, not the journal.
Walkthrough: SaaS acquires SaaS
Composite, not a real customer — built from typical patterns across SaaS acquisitions in the $5M–$50M deal-size band.
Acquirer — a $20M ARR vertical SaaS company on AWS. ~$45K/month cloud spend, allocated to two product lines and an internal-tools cost center.
Acquired — a $4M ARR tuck-in. GCP for production, DigitalOcean for the analytics sandbox the engineering team built last summer. ~$11K/month combined. Allocation: none — both clouds appear as a single "Cloud costs" line in the seller's ledger.
Week 1. Finance lead at the acquirer provisions read-only credentials to both GCP and DigitalOcean (the acquired entity's CTO does the actual provisioning; the finance lead reviews the credential audit log). Connected, backfilled 90 days, consolidated view live by Friday.
Weeks 2–3. Post-acquisition cost-center structure: three product lines (acquirer's two + the tuck-in's product as the new third line), one Customer Support pool, one R&D pool. Mapping rules: GCP project labels → product lines; DigitalOcean droplet name prefixes → R&D pool; AWS tags inherit existing rules. Sample QA: two months of historic allocation, spot-checked against the seller's general ledger.
Weeks 4–6. First joint month-end close. Total cloud spend: $56K. Cost-center breakdown: Product Line A $24K, Product Line B $17K, Product Line C (new) $9K, Customer Support $3K, R&D $3K. Variance vs deal model: $2K favorable on the new product line. Memo writes itself.
Weeks 7–12. Integration variance report. Synergy plan called for $4K/month of consolidation by month 3 (DigitalOcean sandbox onto the existing AWS data plane). Actual: $3.2K. Decomposition: $1K from droplet shutdown (planned), $0.8K from S3 storage class change (unplanned tailwind), -$0.4K from cross-cloud egress during the migration (planned headwind, transient). Board update writes itself; CFO leaves the integration steering committee.
Frequently asked
How long does post-merger cloud integration take with Tovin.io?
Most SaaS-acquires-SaaS integrations have a consolidated view live inside two weeks of credential access. The first joint month-end close lands in week 4–6. The full 90-day integration variance report — synergies realized vs deal model, decomposed into price/volume/mix — produces at the end of week 12. The bottleneck is rarely the tooling; it's deciding on the post-acquisition cost-center structure.
Do we need IT or engineering to set this up?
Provisioning read-only credentials to both cloud estates is a 10-minute task for someone with admin access (often the existing cloud admin at each legal entity). After that, mapping, allocation, and reporting are finance-owned. The credentials carry zero blast radius — they cannot modify resources, change billing, or read customer data.
What about retained employees from the acquired company?
Read-only credentials are scoped to billing data only. If a retained cloud admin leaves three months in, rotating the credential is a one-line change in Tovin.io and the audit trail is intact. The integration plan does not depend on retaining specific cloud admins — only on someone with read access to billing.
How does this interact with purchase accounting?
Tovin.io reports cloud cost in real time; it does not produce purchase-accounting entries. What it does give the controller is a clean, defensible allocation of cloud spend across the new cost-center structure, which feeds the opening balance sheet, the synergy realization tracker, and the management variance memo. Most acquisitions reconcile the cloud line in purchase accounting via Tovin.io's CSV export.
What if we keep separate legal entities for a while?
Common in private-equity portfolio-company structures and in carve-outs where the legal merger trails the operational one. Tovin.io supports separate ledger views per legal entity, with a consolidated parent view for the deal team. When the legal entity collapse happens, the per-entity views fold into the parent without a re-mapping pass.
Does this cover non-cloud SaaS spend too — Snowflake, Datadog, etc.?
AWS, GCP, and DigitalOcean are first-class today. Snowflake usage-based invoices ingest via the same CSV import path that powers the monthly close. Datadog, CDNs, and other usage-based SaaS line items can be added as 'other vendor' rows in the ledger and allocated to cost centers alongside the cloud spend.
Is this just for large enterprise M&A?
No — that's the opposite of the wedge. Apptio, Finout, and Vantage target Fortune 500 M&A integration with enterprise pricing and procurement cycles measured in quarters. Tovin.io is built for the controller, fractional CFO, or finance lead at the 10–500 person SaaS acquirer (or the private-equity portfolio company doing a tuck-in) who needs the cloud integration view next month, not next year.
Start the integration ledger
Connect AWS, GCP, and DigitalOcean from both legal entities. Read-only credentials, KMS-encrypted at rest. The consolidated view is live before your next standup.
Start free