The cutover preserves one billing model or another, but quarter close cannot wait for both.
Revenue Operations needs Salesforce history carried forward, while Accounting needs recognized values to remain unchanged in NetSuite.
Who you’d be doing this for
“I have account owners asking why an amendment vanished from their forecast, and close is tomorrow.”
Maria Gheorghiu · Revenue Operations Manager
Uses the billing and contract dataset to maintain account reporting and forecast changes.
What is at stake
Amendments and credits match by count but not by recognized value across BigQuery and NetSuite. You must weigh a clean Salesforce history against an irreversible close-time mapping decision.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- ledger integrity vs. contract-history continuity
- quarter-close timing vs. exhaustive validation
- record completeness vs. recognized-value accuracy
- automation speed vs. independently verified evidence
Why Fivetran
Salesforce, NetSuite, BigQuery, Celigo, and Fivetran carry the business data that supports billing and forecasting.
Written with these in mind
Not your kind of problem? 43 more at Fivetran, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.