TP/OS · Documentation software
Transfer pricing documentation software
Prepare, review and update Local Files and Master Files in TP/OS. Work from your source documents and templates, collect missing inputs, and export to Word with your team's approval.
Explore TP/OSOne connected workflow
3.1 Company overview
Helios Deutschland GmbH is a limited-risk distributor of home and personal care products in Germany. It is wholly owned by Helios Consumer Products B.V.
4.1 Transactions and financial flows
In FY2025 the company purchased finished goods of EUR 412.6m from the principal.
Approved by your team.
Your templatesKeep your firm's structure
Shared factsConnect group and entity inputs
Editable WordFinish in your house style
A Local File, step by step
From source documents to a reviewed Word file
TP/OS brings source files, group and entity facts, templates, information requests and review into one documentation workflow. AI helps extract supported facts and prepare draft text; your team checks the evidence, resolves gaps and approves the document. Export an editable Word file in your house style, then reuse the structure for the next year while reviewing what has changed.
Set up the group, entities, financial year and transactions. Bring prior-year documentation, source files and the template your team uses.
Step 01 / 04
Report sectionsYour firm template · v32
Word design
Your firm · Classic
Data
Reads the project's entities, transactions, policies and benchmarks.
Use AI to help extract facts and fill supported sections. Check the source inputs and suggestions before saving the draft.
Step 02 / 04Assign missing information to an owner with a due date. Review responses, follow up on gaps and resolve comments with the team.
Step 03 / 04Approve the document and export to Word in your house style. Reuse the setup next year, with a fresh review of changed facts and requirements.
Step 04 / 04Illustrative TP/OS workflow with fictional example data.
Different teams.
The same need for consistency.
Use the workflow for client engagements or an in-house tax function, with your own methodology and review standards.
For advisory teams
Preparing files for several clients? Advisory teams can work in firm or client templates, reuse recurring sections and keep engagement review with the responsible team.
Explore your team's workflowFor in-house tax teams
Collecting inputs across a group? In-house tax teams can organize group and entity information, request missing facts and keep Master File and Local File inputs consistent.
Explore your team's workflowNext year starts with this year's work.
Managing the next annual update? Reviewers can start from the existing structure and concentrate on changes to the business, transactions, financials and technical conclusions.
AI assists. People decide.
What still needs your team's judgment
Use AI assistance for the preparation work while keeping technical decisions and approval with the responsible people.
Technical judgment
Keep technical decisions with your team. The characterization of transactions, functional analysis, method selection and conclusions require professional review.
Local requirements
Review local requirements before signing off. Agree the countries, templates, languages and required outputs during setup; a draft does not establish compliance.
Annual review
Roll forward the structure, not unexamined conclusions. Check current-year facts, contracts, financial data, analysis and any changes in applicable rules.
Make the demo yours
What to check in a documentation-software demo
Use a representative prior-year file and source pack. Follow one transaction from inputs to the exported Word document, and check who makes each decision.
Start with one representative file
A guided trial lets your preparer and reviewer test the workflow against real work before extending the setup to more entities or clients.
- Bring your existing documentation. A prior-year Local File and its source pack help establish the structure, available evidence and recurring sections.
- Choose the template and output. Bring the Word design you want to keep, including the sections, cover, headers and formatting that matter to the team.
- Agree the scope and reviewers. Identify the entities, transactions, countries and financial year, then involve the people who prepare, supply information and approve the file.
01Source extraction
Which facts are supported, current and appropriate for this entity?
- AI support
- Suggest facts from the documents you provide.
- What to inspect
- Source documents and the corrections made during review.
02Drafting in your template
Does the wording reflect the actual conduct, transactions and agreed approach?
- AI support
- Help fill supported placeholders and prepare draft sections.
- What to inspect
- Your template, the underlying facts and the approved text.
03Missing information
Who can confirm the point, and is the response sufficient?
- AI support
- Help identify gaps and possible inconsistencies for follow-up.
- What to inspect
- Information requests, responses, owners and review comments.
04Final output and annual update
Is the Word output usable, and what needs to change for the next year?
- AI support
- Support preparation using the saved structure and inputs.
- What to inspect
- The exported document, current-year inputs and the team's sign-off.
Before you choose documentation software
Can TP/OS prepare both Local Files and Master Files?
Yes. TP/OS supports both using your templates and shared group information. The Master File covers the group, while each Local File needs its own entity and transaction inputs. Your team reviews consistency between them and any country-specific requirements.
Can we keep our own Word templates?
Yes. Your template structure and Word design are part of the setup. Test the exported document during the guided trial, including the sections, formatting, cover and headers you need, before rolling it out more broadly.
What does the AI do, and what does the reviewer do?
AI helps read source documents, suggest facts, fill supported placeholders and surface gaps or possible contradictions. A person reviews and saves the suggestions. The team remains responsible for the analysis, local requirements and final approval.
How does this differ from the free Local File Template Builder?
The free builder helps you work through a Local File structure, enter facts and export a Word draft. TP/OS is a separate product for a recurring team workflow: source files, shared information, AI-assisted drafting, requests, review and annual updates. Both require technical and local-law review.
What should we check before rolling documentation forward?
Check changes to the business, functions and risks, related-party transactions, agreements, financial results and supporting analysis. Revisit the relevant country requirements. Reusing a template or prior-year text is a starting point, not confirmation that the current-year file is complete.
How is TP/OS priced?
Pricing is scoped to your setup, including the number of groups or clients, files and countries, template work and support. Start with a documentation demo to establish the scope and request a quote.
See your documentation workflow in TP/OS
Start with one file, your template and the people who prepare and review it. Use the demo to check the inputs, review steps and Word output your team needs.