AI can prepare most of the yearly transfer pricing file: pull every intercompany transaction from the ledger, match it to the agreement and the pricing policy that should govern it, show where the booked amounts and the policy disagree, and redraft last year's local file with this year's facts, numbers and changes marked. Your transfer pricing lead still chooses the method, reviews the benchmark and signs the position. What changes is that the review starts from a reconciled draft, not from twelve spreadsheets and last year's Word file.
The pressure on this file is rising in the UK. HMRC's transfer pricing statistics for 2024-25, published on 11 March 2026, show the yield from transfer pricing work nearly doubling in a year, and the enquiries that settled took longer than in any of the five years before.
The yield is not tax from 143 companies alone: it also counts advance pricing agreements and mutual agreement cases, and one large settlement can move a year. But it shows the stakes. The groups that must keep these files have revenue of €750m or more, and a single adjustment can be worth more than the whole tax team's annual cost. The work behind the file is done by in-house tax teams and by the transfer pricing practices of advisory firms, from the large networks to boutiques that serve mid-size groups.
What the rules ask for now
In the UK, the Transfer Pricing Records Regulations 2023 require UK members of groups that meet the country-by-country reporting threshold to keep a master file and a local file in the form set out in Annexes I and II to Chapter V of the OECD Transfer Pricing Guidelines, for accounting periods beginning on or after 1 April 2023. Regulation 6 leaves out most transactions between two UK-resident parties. The files are kept, not filed, but HMRC's policy paper explains that failing to keep them or produce them on request leads to a presumption that a transfer pricing inaccuracy was careless, which affects both penalties and how far back HMRC can assess.
Next comes a yearly filing. HMRC's technical consultation on the International Controlled Transactions Schedule ran from 16 June to 31 July 2026. The ICTS would report cross-border related party transactions in a standard format every year, for automated risk profiling, for accounting periods beginning on or after 1 January 2027. Thresholds and the template were still drafts in that consultation. Once it applies, the numbers in your local file and the numbers HMRC's systems see will have to agree.
In Germany, § 90 Abs. 3 and 4 AO has required a transaction matrix since 1 January 2025, and the documentation must be produced within 30 days of a request. In a tax audit, the matrix, the master file and the records of extraordinary transactions are due within 30 days of the audit order, without being asked. My German version of this article covers those rules in detail.
Why the file takes weeks
The transaction list is rebuilt by hand. Intercompany flows sit in different ledgers, account codes and currencies. Someone exports them, maps them to transaction types and counterparties, and reconciles them with what the other side booked.
The agreements and the bookings drift apart. A service agreement says cost plus 5%. The year-end true-up was booked at 4.2%, or not at all. A new entity started buying from the group in June, without a signed agreement. Nobody notices until the file is written.
The narrative is last year's text with new numbers. The functional analysis was written once after interviews and copied forward. Restructurings, new products, a moved team: if nobody tells the tax team, the file describes a group that no longer exists.
The benchmark and the result are checked at the end. The interquartile range is refreshed, and only then does someone see that the distributor's margin fell outside it.
What the documentation assistant does
Builds the transaction list. It reads the intercompany accounts from each entity's trial balance or ledger export, maps each flow to a transaction type and counterparty, converts currencies at the rate your policy names, and shows pairs where the two sides booked different amounts.
Matches transactions to agreements. For each flow it finds the intercompany agreement and the pricing policy, quotes the clause that sets the price, and recalculates the expected charge. Flows with no agreement, an expired one, or a booked margin different from the contract are listed for a person.
Asks the business what changed. It drafts short questionnaires for the people who know: finance leads, heads of sales, R&D managers. The questions come from last year's functional analysis, so answers map back to paragraphs.
Redrafts the local file. It updates last year's text with the new facts, transactions and financials, marks every changed sentence, and cites the source of each new figure. Nothing changed without a source behind it.
Checks the result against the benchmark. It compares each tested party's margin with the range your adviser or database produced and lists where a year-end adjustment may be needed before the books close.
- ExtractAIhoursIntercompany flows from every entity mapped to types, counterparties and agreements, with mismatches listed.
- ConfirmFinance and business1 to 2 weeksQuestionnaires answered, missing agreements and booking errors resolved.
- DraftAIhoursLocal file updated from last year's version, changes marked, each new figure sourced.
- TestTransfer pricing leaddaysMethod, benchmark and margin outcome reviewed, adjustments agreed with finance.
- SignTax directorper entityFile approved and stored with the evidence pack it cites.
The numbers for one mid-size group
- Entities that need a local file (assumption)
- 12
- Specialist time per file today, data to final draft (assumption)
- × 40 hours
- Hours today
- 480 hours
- Time per file with reconciled data and a marked draft (assumption)
- 12 × 18 hours = 216 hours
- Specialist time saved per year
- about 260 hours, moved from copying numbers to testing the positions
The hours matter less than the timing. If the reconciliation runs monthly, a margin drifting outside the range shows up in September, when finance can still correct the pricing, rather than in the following summer, when the only fix is an adjustment that has to be explained.
Where it goes wrong
The benchmark comes from a database, not from the model. Comparable company searches use licensed databases and documented screening steps. The assistant can read the search report and apply its range. It must not invent comparables or margins.
Facts must come from the business. A functional analysis written by a model from last year's text is still last year's analysis. If a team moved or a risk changed hands, only the people involved can say so.
Group data is confidential. Intercompany agreements, margins and restructuring plans are among the most sensitive data a group holds. Run the assistant in your own environment or under contracts your tax and IT teams accept, never through a public chatbot.
Tools that fit
Most groups already have the data: an ERP with intercompany accounts, a contract repository, last year's files and the adviser's benchmark report. Specialist transfer pricing software and the documentation platforms of the large advisory firms generate files from templates. Mid-size groups and smaller advisers often work in spreadsheets and Word. Start with the reconciliation, because every later step depends on a transaction list that ties to the ledger.
- Export last year's intercompany balances and flows from every entity
- Collect the signed intercompany agreements and the group pricing policy in one folder
- Have the assistant build the transaction list and the mismatch report for last year
- Compare it with the transactions in last year's local file and fix the mapping until they agree
- Run the same reconciliation on this year's first nine months and fix pricing before year-end
- Draft one local file from last year's version and review every marked change
Questions tax teams ask about AI and transfer pricing
Who has to keep a master file and local file in the UK?
UK companies, trusts and partnerships that are part of a multinational group meeting the country-by-country reporting threshold, global revenue of €750 million or more, for accounting periods beginning on or after 1 April 2023. Transactions where both parties are UK-resident are mostly left out of the local file under regulation 6.
What is the International Controlled Transactions Schedule?
A planned annual filing to HMRC of cross-border related party transactions in a standard format, used for automated risk assessment. The draft regulations consulted on in 2026 apply to accounting periods beginning on or after 1 January 2027, with thresholds and the template set in an HMRC notice.
How long do UK transfer pricing enquiries take?
HMRC settled 143 transfer pricing enquiries in 2024-25. Their average age was 41.0 months, up from 33.1 months the year before. Advance pricing agreements took 43.9 months on average.
Can AI write a transfer pricing local file?
It can draft one: build the transaction list, update the narrative from last year's file and new facts, and fill in the financials with sources. The method, the benchmark and the conclusions are judgements a qualified person has to make and sign.
Keep the file in step with the books
A local file is only as good as the transaction list under it. Let AI reconcile the ledger with the agreements every month, draft the update from evidence, and keep the decisions with the people who sign them.
If your local files still start from last year's Word document, tell me how many entities you document and which ERP holds your intercompany accounts. I'll suggest whether the reconciliation, the drafting or the evidence pack is the right first step. Audit firms chase the same records in client request lists, R&D tax advisers turn interviews into claims in claim narratives, and the same intercompany agreements turn up in a buyer's due diligence questions.
Building something with AI?
I help small businesses turn ideas into software that pays off. Tell me what you’re working on and get a free first assessment.