Who knows what in tax processing, and where the gaps cause trouble

Tax work runs on knowledge that no single role holds. Planners know the intent behind a structure, preparers know what the forms demand, accountants know how entries were booked, and operations knows what actually happened. Trouble starts wherever one group acts on an assumption another group could have corrected.

The planner holds the reasoning

Whoever sets tax strategy knows why an entity exists, why a transaction was routed a certain way, and which positions are firm and which are arguable. That reasoning usually lives in memos, advisers' letters and the planner's head.

The people downstream see only the result. A preparer finds an intercompany charge and books it as routine. A controller sees a new entity and treats it like the others. Nobody told them that the arrangement only holds if certain conditions stay true, such as where decisions are made or how services are priced. When those conditions drift, the planner is often the last to hear.

Preparers know the rules but not the story

Return preparers understand forms, elections, thresholds and filing mechanics better than anyone. What they lack is context. They work from trial balances and supporting schedules, so they inherit whatever the ledger says, including miscoded expenses and reclassifications made for management reporting.

A preparer who asks the right question can catch a problem early. One who is pressed for time rolls forward last cycle's workpapers and hopes the business has not changed. It usually has.

Foreign filings sit far from head office

Local finance staff and outside advisers in each country know the domestic rules, the habits of the local authority and which deductions get challenged in practice. Head office knows the group picture: transfer pricing policy, consolidated positions and what was promised to auditors.

These views rarely meet until something breaks. A local team files on a basis that contradicts the group's documentation. Or head office changes a policy and the local return goes out unchanged because no one sent word. Withholding on cross-border payments is a common casualty, since accounts payable makes the payment and assumes someone else checked the treaty position.

Deferred tax depends on facts nobody sends

The people calculating deferred tax need to know about asset lives, impairments, provisions, share schemes, losses and planned restructurings. Most of those facts belong to other teams. Fixed asset accounting knows the book basis. Treasury knows about hedges. Legal knows about entity mergers that will wipe out carried forward losses.

When those facts arrive late or not at all, the tax provision is wrong, and the error surfaces at audit or after a return is filed and the true-up does not reconcile.

The ledger team owns the numbers but not their meaning

General ledger accountants record tax entries, accruals and payments. They know exactly what was booked and when. They often do not know whether a balance reflects an uncertain position, a payment on account or a refund that will never come. Tax accounts become parking lots, and reconciling them turns into archaeology.

Compliance monitoring sees dates without context

Those who track filing obligations know the calendar. They may not know that an entity has started selling into a new jurisdiction, hired staff abroad or crossed a registration threshold. Sales, payroll and procurement hold those facts and seldom think of them as tax events. New obligations go unnoticed until a notice arrives.

Inquiries expose every gap at once

When an authority asks a question, whoever answers must reassemble the reasoning, the numbers and the documentation, often from people who have moved on. The planner's memo is missing. The preparer's workpaper references a schedule nobody can find. The local adviser's file sits on a personal drive. Weak responses here turn small queries into extended disputes.

Questions to ask the people who run it

What is documented and what actually happens tend to differ most at the handoffs. These questions help find where.

• When the business changes, who tells tax, and how do they find out if nobody does?
• Which workpapers get rolled forward without being rebuilt from source?
• What do local teams file that head office never reviews?
• Who decides the withholding treatment on a foreign payment, and do they know they are deciding it?
• Where do the facts for the deferred tax calculation come from, and which arrive after the deadline?
• What sits in the tax accounts on the ledger that nobody can fully explain?
• If an authority asked about a past position tomorrow, where would the reasoning be found?
• Which adviser holds knowledge that would leave with them?

Listen for workarounds. A spreadsheet one person maintains, a standing email to a colleague, a habit of checking something informally: these are signs of a gap the process does not cover.

Where to start a change

The most useful fixes connect the roles, not the systems. Give planners a way to flag the conditions their positions depend on. Make operational teams aware of which events matter for tax and give them an easy channel to report them. Require that reasoning is filed alongside the return it supports, in a place the next person can reach.

Automation helps preparers and accountants work faster, but it moves wrong assumptions faster too. Map who holds each piece of knowledge before redesigning anything, and test every handoff by asking the receiving person what they would do if the information never arrived.

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.