The tax forecast needs wider input coverage without turning disputed assumptions into governed facts.
Tax needs a usable quarterly view of cash exposure, while FP&A needs every included input to reconcile to an approved definition.
Who you’d be doing this for
“I spent half the review explaining where each number came from instead of discussing the forecast.”
Chrysanthi Fernandez · Tax Forecasting Manager
Owns the quarterly cash-tax forecast assembled from Finance source extracts.
What is at stake
Tax analysts are rebuilding NetSuite, Stripe, and Salesforce inputs while FP&A disputes the timing behind the forecast. You must weigh broad forecasting coverage against definitions that can survive reconciliation.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- forecast coverage vs. reconciled definitions
- tax judgment vs. reusable Finance data
- self-service access vs. row-level security
- quarterly readiness vs. durable lineage
Why Databricks
Lakeflow Declarative Pipelines and Unity Catalog place Finance and Tax data products on the same governed foundation used for close reporting.
Written with these in mind
Not your kind of problem? 107 more at Databricks, 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.