Documenting international transactions before the method debate

International transactions are easy to under-specify. A row that says "goods, INR 40 crore, AE in Singapore" does not tell you whether you are looking at a full-fledged manufacturer, a contract manufacturer, or a limited-risk distributor with a marketing intangible problem. FAR, method, and benchmarking cannot repair a vague schedule. They will only decorate it.

This checklist is the deal-level work behind international transactions in TP DOC GEN AI.

Name the contract, not just the counterpart

For each line, capture: legal counterpart, associated-enterprise or connected-person basis, contract or invoice series, nature of the dealing, amount and currency, who invoices whom, and which entity's FAR will be tested. India's section 92B (including deemed international transactions) and the UAE related-party / connected-person definitions overlap but are not identical. Do not collapse them into one undifferentiated list.

The Local File wizard asks for related parties and connected persons before economic analysis. UAE connected persons also get their own annexure and the AED 40 million / AED 500,000 disclosure thresholds on the CT form. That duplication is intentional. Disclosure forms and Local Files that disagree are an audit invitation.

Unbundle composite charges

Management fees, "support services," and IT recharges are where characterisation dies. If a single invoice covers a seconded director, a shared ERP, and a parental guarantee, you have at least three transactions and probably three methods. Split them in the schedule even if the ERP cannot. The study can still tell the truth the GL flattened.

Intragroup financing, intangibles, and services each have Master File toggles. Empty chapters are a tell. Missing agreements in the retrieval store are another. Upload the contracts you want cited.

FX belongs on the same record

Amounts in a second currency need a documented rate and date. The platform's converter keeps an audit trail of the conversion you used. We do not attribute those rates to RBI, ECB, or OANDA, because that is not how the data is sourced. Reviewers ask "which rate, which day," not "which logo."

Keep languages consistent without letting digits drift

Groups filing in Spain, the UAE, and Germany often need the same international transactions in several languages. Local File translation covers six languages. Numbers are localised in code. A digit-integrity validator rejects fragments whose digits changed. Entity legal names, citation numbers, database names, and currency codes never translate. If English is edited later, translations badge as outdated.

Align the schedule with TP compliance clocks (3CEB, UAE disclosure) and with the Local File outline. To walk a multi-entity deal list, book a demo.

Guarantees and deemed transactions

If the FAR says a parent guarantees facilities, the schedule should say so even when the GL never booked a fee. Deemed international transactions and secondments billed as salary recharge are easy to omit because they do not look like invoices. Omit them and the characterisation chapter will describe a company that does not match the contracts.

Intangibles and financing belong in the deal list and in the Master File toggles. If those two artefacts disagree, you have written two studies. Capture the contract once.