The workpapers are nearly ready. Then another version of the trial balance arrives.
In my in-house roles, an updated trial balance meant revisiting supporting schedules, updating calculations, checking links, and tying everything out again, all against the same close deadline.
Across nearly twenty years in CPA-firm and in-house tax roles, I've seen how much care teams put into getting the provision right. The issue I'm describing isn't a lack of expertise or effort. It's the repeated work of keeping schedules aligned while the underlying numbers change.
Excel isn't the problem by itself
Excel remains useful for provision work. It gives teams flexibility, visibility into calculations, and a familiar place to document and review their work. It also has a role alongside dedicated provision software for data preparation, supporting calculations, and reconciliations.
The difficulty comes when recurring steps depend on copying balances, reconnecting formulas, or remembering how a workbook was assembled. The distinction isn't Excel versus software. It's a workflow designed to handle updates versus one that requires repeated manual intervention.
ASC 740 also involves genuine technical complexity. Automation does not remove that. The opportunity is to reduce repetitive preparation so the team has more time for the questions that need its judgment.
Then the trial balance changes again
A late journal entry, an account reclassification, or an updated entity submission can affect work that has already been prepared or reviewed. The tax team needs to understand what changed, where it flows, and which conclusions or review steps need another look.
In a heavily manual workflow, refreshing the numbers is only the first step. The team then checks affected book-to-tax schedules, confirms that mappings still apply, updates workpapers, and reruns the tie-outs. When balances have been copied into several places, each affected schedule needs attention.
The challenge isn't only calculating the provision. It's keeping the workpapers aligned as the underlying numbers change.
Not every updated trial balance requires a rebuild. If the accounts and approved mappings are unchanged, a controlled refresh may be enough. New accounts, changed classifications, or a different tax treatment still need someone to evaluate them before relying on the updated results.
Every additional round of preparation against the same deadline leaves less time for technical analysis and review. For a CPA firm managing several client provisions, that pressure extends across different workbooks and reporting timetables. Rechecking the same schedules late in the close is tiring; reducing avoidable rework matters to the people doing it, not just the timetable.
What a more repeatable process looks like
Start with one recurring step that takes too much effort each time the numbers change. A complete system replacement isn't a prerequisite for improving that step.
- Reusable approved mappings. Keep account and entity mappings consistent where appropriate, with a clear review step for new accounts or changes in treatment.
- A controlled way to refresh inputs. Identify the period and version of the trial balance being used, check completeness, and carry updated balances through the applicable calculations.
- Visible changes and exceptions. Make it clear which inputs changed and which items need attention, rather than assuming a successful rerun means every issue is resolved.
- Traceable workpapers and tie-outs. Connect supporting inputs to calculations and outputs so reviewers can follow the work and investigate differences.
These are workflow goals, not a promise that every update becomes automatic. A refreshed calculation still needs appropriate review. Technical positions, judgments, and sign-off remain with the team and its advisors.
Whether an improvement uses AI or conventional automation, understanding the task, the inputs, and the controls comes first. I explore that distinction further in where AI helps with the tax provision, and where it doesn't.
Start with the work your team would most like to change
This experience is part of what led me to build Polaris Tax Intelligence. Polaris is designed to help teams carry controlled inputs and approved mappings into formula-linked Excel workpapers with validation and tie-out checks.
I'm speaking with in-house tax teams about the preparation work they want to improve and the parts of their existing process they want to keep. That starts with a specific task, such as carrying prior-period work forward or absorbing an updated trial balance without repeating so much manual preparation.
The aim isn't to automate every part of the provision. It's to make the repeatable work easier to manage, while keeping technical judgment and review where they belong.