The tax provision needs a governed correction while the evidence still leaves rare intercompany records in dispute.
An on-time filing protects close commitments, while a premature mapping change can alter posted tax treatment.
Who you’d be doing this for
“I’ve got reviewers asking why one entity moved overnight, and I can’t send them another spreadsheet.”
Chebet Girma · Tax Provision Manager
Reviews intercompany tax balances and signs off on the provision built from the curated Finance dataset.
What is at stake
Intercompany balances are shifting between entities despite matching source totals. You must weigh filing speed against a production correction that may change tax treatment.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- filing speed vs. tax-treatment certainty
- automated comparison vs. independent verification
- source stability vs. curated-data correctness
- production correction vs. close continuity
Why Databricks
Lakeflow, Unity Catalog, and the Finance data lake sit directly beneath the tax deliverable that must withstand close and audit review.
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.