armslength
armslength
Documentation software

Transfer pricing documentation software for Local Files and Master Files

Use your existing files and templates to collect facts, prepare drafts and update annual documentation in TP/OS. Your team reviews changes and signs off on the final documents.

See TP/OS Book a demo

From existing files to the next annual update

TP/OS turns prior-year documentation, source files and your templates into a reusable documentation process. It helps extract and organize facts, draft sections, and prepare outputs in your chosen structure. For the next year, reuse the mappings and templates while reviewing changes to the business, transactions and financial information. The team retains responsibility for technical positions and local requirements.

For teams preparing recurring TP documentation

Keep the methodology and templates your team already works with.

Advisory teams preparing Local Files and Master Files in firm or client templates, with recurring sections they can reuse.

In-house tax teams collecting inputs from several entities and checking that shared facts remain consistent across documents.

Reviewers managing annual updates who need to distinguish reusable material from facts and conclusions that require a fresh review.

What your team supplies and what happens next

  1. Step 1:

    Start with prior-year documentation, source documents, supporting data and the templates your team already uses.

  2. Step 2:

    Set up the entity and transaction structure, recurring sections and review checkpoints for your documentation process.

  3. Step 3:

    Use AI to help extract facts and draft sections. Review source inputs and changed assumptions before approving the text.

  4. Step 4:

    Prepare documentation in your agreed templates and route it for final review. Reuse the structure for the next annual update.

What to reuse and what to review again

Agree the scope during setup and keep technical approval with your team.

  • Roll forward the structure, not unexamined conclusions.

    Review changes to transactions, functions, financials and local requirements each year.

  • Keep your templates and review standards.

    Agree the country-specific setup and required outputs before implementation.

  • People approve the final documents.

    AI-assisted extraction and drafting do not establish that a file is complete or compliant.

See TP/OS or review the documentation requirements

Explore the product workflow alongside the underlying documentation guidance.

Have other questions or want to discuss collaboration?

Talk to us Book a demo