Who knows what when building a tax strategy and plan

The tax team knows the rules and the positions already taken. Finance knows the numbers and the forecast. The business knows what it is about to do. Master data owners know how entities and codes are really set up. Trouble starts when the plan rests on one view.

What the tax team holds

Tax specialists carry the history. They know which positions were argued with an authority and which were conceded. They remember why a structure exists, even when nobody else does. They also know which jurisdictions are tightening their approach and where a ruling or treaty is about to shift.

What they often lack is a live picture of the business. Their forecast of taxable profit usually arrives secondhand, already shaped by someone else's assumptions.

What finance and planning hold

Controllers and planning analysts own the forecast. They know which business units are expected to grow, where margins are thin, and how intercompany charges are booked month to month. They rarely know the tax reasoning behind a transfer pricing policy. So when they adjust a recharge to tidy up a cost centre, they may quietly move profit into the wrong country.

What the business knows first

Operating leaders hear about change before anyone in finance. A new sales office, a hire who will work from another country, a supplier switch, an acquisition still under wraps. Each can create a taxable presence or alter how profit should be split.

These people do not think of their decisions as tax events. They tell the tax team late, or never.

What treasury and legal see

Treasury knows where cash physically sits and how it moves. It sees intercompany loans, dividends and cash pooling, all of which carry withholding and interest deduction consequences. Legal holds the entity register: incorporations, mergers, dormant companies awaiting closure, directors and registered addresses.

Both groups make changes on their own timetable. A loan drawn to cover a short-term need can undo a carefully planned financing structure, and a dissolved entity can strand losses the plan was counting on.

Where master data hides the truth

The people who maintain tax codes, entity records and vendor and customer tax settings in the ledger know something nobody else does. They know how the system actually treats a transaction. A strategy may assume goods ship from one entity while the ledger books the sale through another. Determination rules may be years out of date. Nobody notices until a return is prepared or an auditor asks.

This role is usually junior and seldom invited to planning meetings. That is a mistake.

Where the gaps bite

The most common failure is a consolidated tax plan built on a forecast that ignores known business changes. The effective rate looks stable on paper, then moves sharply once the year closes.

Another is drift between the documented structure and actual behaviour. Transfer pricing policy says one thing while the ledger, the contracts and the people do another. Authorities look at substance, so the gap becomes exposure.

A quieter problem sits between national and local work. Federal or national planning is often owned centrally, while state, provincial and municipal obligations are handled by a separate team or an outside adviser. Each optimises its own piece. Neither sees how a change in one shifts the other.

Finally, outside advisers frequently hold the best knowledge of a specific jurisdiction. When that knowledge lives only in their files, the internal team cannot challenge or maintain it.

Questions to ask the people who run it

Ask the tax team which forecast they used for the last plan, who supplied it, and when it was frozen. Then ask what has changed in the business since.

Ask planning analysts whether they have ever changed an intercompany recharge, and who approved it.

Ask operating leaders where staff actually work, not where their contracts say they work.

Ask treasury which intercompany balances exist that the tax team has not reviewed.

Ask legal which entities are being opened, merged or wound down this year.

Ask whoever maintains tax master data how a new entity or product gets its tax settings, and what happens when nobody requests a change.

Ask everyone the same final question: when did a tax surprise last come from something you knew and nobody asked about?

The answers rarely match the process document. That mismatch is the real map.

Changing the process without widening the gaps

The fix is seldom a new report. It is a trigger. Business events that carry tax consequences, such as entity changes, cross-border hires, new financing and shifts in where goods ship from, need a route to the tax team before they happen.

Give master data a named owner with authority to refuse a setup that contradicts the strategy. Bring that owner into planning reviews.

Agree one forecast that tax and finance both sign, with a defined point where it is refreshed. Record the reasoning behind each structure inside the organisation, so it survives when an adviser or a long-serving specialist leaves.

When redesigning roles, check that each piece of knowledge has a path to the person who needs it. A clean handoff between teams matters more than a perfect document in any single one.

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.