Where tax strategy and planning breaks down

Tax planning usually breaks where it depends on people outside the tax team. Forecasts arrive late or in the wrong shape. Operating changes go unreported. Local advisors work from different facts. Master data drifts from the plan. Each failure leaves traces in overrides, late adjustments and surprises at close.

Forecasts that arrive late or in the wrong shape

The tax plan rests on a profit forecast that someone else owns. Planning teams build it by business unit or product line. Tax needs it by legal entity and by jurisdiction. Somebody has to translate one view into the other, and that translation is rarely written down.

When the forecast lands late, tax compresses its own work. Rate modelling gets done on last cycle's numbers and is patched afterward. When the forecast changes after tax has finished, nobody reliably tells the tax team.

How to spot it: the effective rate in the plan moves sharply between drafts without any change in tax law. Tax staff keep their own mapping file from business units to entities. Questions about which forecast version was used get answered with "probably the latest one."

Operating changes that never reach tax

Strategy at the foreign, national, state and local levels assumes the business looks a certain way. Then sales hires staff in a new region. A warehouse opens. A product starts shipping from a different entity. Procurement signs a contract that changes where value is created.

None of these decisions feel like tax decisions to the people making them. So they skip the tax review. The result is filing obligations nobody planned for, transfer pricing that no longer fits the facts, and planning structures that quietly stop working.

How to spot it: registrations get discovered during an audit or a notice. Intercompany agreements describe functions that the entities no longer perform. The tax team learns about expansions from press releases or internal newsletters.

Local plans that do not add up centrally

Consolidating the total tax plan means combining work from regional teams and outside advisors. Each uses its own assumptions about exchange rates, timing of deductions and which entity books which income. The central team spends its effort reconciling inputs when it should be optimizing the whole.

Exceptions make this worse. A one-off restructuring, a large disposal or a dispute settlement gets modelled locally in a way the central model cannot absorb. Someone overrides the consolidated figure by hand.

How to spot it: the consolidated plan carries a manual adjustment line with a vague label. Local and central figures for the same entity disagree. Nobody can say which version a board paper used.

Master data that drifts from the plan

Tax master data covers legal entities, registration numbers, jurisdiction codes, tax codes in the finance system and the mapping between them. Strategy decisions should flow into this data. Often they do not.

A new entity gets created in the ledger without its tax attributes. An entity is dissolved but its codes stay open. A rate change is agreed in planning but never loaded. Transactions then post with the wrong treatment, and the error surfaces only when returns or provisions are prepared.

How to spot it: the tax team corrects postings during close. Requests to set up or change tax codes sit in a general IT queue with no tax owner. Several spreadsheets claim to be the true entity list.

Workarounds that become the process

Most tax planning teams run on a model that one person built and only that person fully understands. It works, so it survives. Links break when the chart of accounts changes. Formulas get overwritten. Review consists of the builder checking their own work.

Another common workaround is approval by email. Planning positions get agreed in a thread, never recorded centrally, and later disputed. When an auditor or a new leader asks why a position was taken, the evidence is scattered.

How to spot it: holidays and resignations cause visible delays. Documentation describes a system workflow that staff admit they bypass. Supporting memos for major positions are written after the fact.

Questions to ask the people who run it

What staff actually do often differs from the documented procedure. These questions tend to surface the gap:

• Which forecast do you use, who sends it, and how do you know it is final?
• How do you hear about a new hire, site or contract in a new location?
• When a local advisor's numbers disagree with yours, what do you do with the difference?
• Who can create or change a tax code or entity in the system, and does tax approve it?
• Which spreadsheet would hurt most if it disappeared tomorrow?
• What adjustment do you make by hand every cycle, and why has it never been fixed?
• Where is the record of why the current planning positions were chosen?
• What did the last audit or notice teach you that the process still does not reflect?

Listen for hesitation and for answers that start with "normally." Those point to the steps that depend on memory and goodwill instead of a defined handoff.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.