Executive answer
Mexico’s Anexo 9 Multiple Information Return should be prepared from a reconciled inventory of related-party transactions, not by copying isolated fields from the transfer pricing study. Article 76, section X, of the Mexican Income Tax Law requires the requested information to be filed by May 15 of the following year through the approved official form. The SAT portal identifies Anexo 9 as the related-party annex and publishes field-level frequently asked questions.
Reliable preparation connects four layers: accounting, economic characterization, transfer pricing analysis and the form. Every amount should trace to accounts and entries. Each operation code should reflect substance. The method and result should agree with the supporting file. Any adjustment should reflect what was actually recorded and reported.
The electronic receipt proves that a file was accepted; it does not prove consistency. The greatest exposure arises when Anexo 9, the annual income tax return, local return, ISSIF, statutory-audit schedules and study tell different stories about the same dealing. The core control is a bridge by taxpayer, counterparty and transaction type.
What Anexo 9 reports
The official form has historically been titled “Information on transactions with related parties resident abroad.” The SAT portal has also published instructions for reporting transactions with Mexican related parties through Anexo 9. The tension between the historical name and the operating guidance makes it essential to review the fiscal-year software, fields and current instructions rather than treating the title as the complete population rule.
Depending on the applicable fields, the form requests identification and relationship data, operation codes, amounts, method, comparable information, indicators or ranges, and adjustments. SAT’s FAQs address how to select the relationship type, capture certain asset sales, complete mandatory SIC fields when no SIC code was used, and report adjustments resulting from a transfer pricing analysis.
Anexo 9 does not replace Article 76, section IX supporting documentation. The study preserves reasoning and evidence; the return structures data and answers. It also does not replace the Article 76-A local return. Although data overlaps and both can be due on May 15, legal scope and filing population differ.
Confirm the requirement before data entry
The first control is to document who files, under which rule, for which fiscal year and for what dealings. Article 76, section X contains the corporate requirement. Article 110 contains a related rule for individuals carrying on business and professional activities. Tax regime, fiscal year, dealings and current operating rules must be considered.
Do not use the presence or absence of a preloaded system obligation as the only evidence. Retain an applicability memorandum identifying the legal text, official form and transaction population. If the portal preserves answers referring to older fiscal years, distinguish useful form guidance from the cited rule’s current status.
Then confirm the date. For ordinary fiscal years, current section X states May 15 of the immediately following year. Materials predating the 2021 reform may show a different date. Use current law and confirm any official extension or relief.
Build the transaction master table
The table begins with accounting. Extract intercompany subledgers, electronic invoices issued and received, foreign payments, receivables, payables, interest, royalties, asset movements, true-ups and manual entries. Reconcile the population to the related-party map and agreements.
Use one row for each controllable combination. Minimum columns are taxpayer, counterparty, country, tax identification, relationship type, economic nature, account, currency, accounting amount, tax amount, income or deduction, method, indicator, result, range, adjustment and source. If the form aggregates data, retain the underlying detail used to construct the aggregate.
Do not classify only from the account description. “Corporate services” may combine services, pass-through costs and royalties. A “current account” can be financing. “Other expenses” can represent an asset purchase. The reported operation code should follow the facts and agreement.
Reconcile before entering the form
The bridge begins with accounting and ends with the tax amount reported. Document VAT removal, foreign-exchange differences, accruals, nondeductible amounts, capitalization, credit notes, reclassifications and transfer pricing true-ups. State the source and approver for each difference.
Compare the result to the annual return. Totals may not match directly because forms classify items differently, but every difference should be explainable. Repeat the comparison against the study, local return and tax-situation information. A reconciliation is a quantified explanation, not a generic note saying “tax differences.”
Freeze one controlled version. If a later adjustment changes an amount, record which returns are affected and whether an amended filing is needed. Do not edit each deliverable independently without a central change log.
Method, comparables and result
Report the method actually applied. If the study analyzed services using TNMM, do not select cost plus merely because the charge uses costs and a markup. If an internal comparable was used, document how fields designed for external searches were completed and follow SAT’s guidance for mandatory fields.
The range, indicator and result should be reproducible from workpapers. Check signs, units, percentages, currency, rounding and period. A 5% margin can be entered incorrectly as either 0.05 or 5 depending on the field’s units. Require an independent second review.
Where there is a true-up, distinguish calculation, booking and reporting. SAT’s FAQ describes the adjustment field as an adjustment resulting from a study to bring a dealing to independent-party conditions. The answer should match the accounting and tax treatment actually adopted, not an unexecuted scenario.
Ledger-study-Anexo 9 bridge
| Control | Starting source | Validation | Closing evidence |
|---|---|---|---|
| Population | Related-party map | Reconcile customer, vendor and treasury records | Legal and tax approval |
| Dealings | Subledgers, invoices, agreements | Substance and code by type | Frozen master table |
| Amounts | Trial balance and entries | Accounting-to-tax bridge | Quantified reconciliation |
| Method | Study and workpapers | Agreement with actual analysis | Method memorandum |
| Comparables | Database and search | Code, range, period and units | Reproducible file |
| True-up | Closing calculation | Entry, invoice and tax effects | Aligned entry and returns |
| Filing | DIM software | Cross-review and validation | Submitted file and receipt |
| Post-filing | Changes and amendments | Effect on other forms | Version log |
Zugzwang’s Anexo 9 Reconciliation Sprint builds the bridge by counterparty and transaction, reviews method and true-ups, and delivers a difference matrix before data entry. The objective is for every form to originate from one controlled source.
Preparation checklist
Before data entry, confirm the obligation, period, software version and credentials. Validate related parties and tax identifiers. Close the trial balance and obtain subledgers. Approve economic classification. Complete the study or a controlled technical position. Prepare the accounting-to-tax bridge and decide true-ups.
During data entry, maintain versions and evidence for every field. Review codes, country, currency, method, indicators, ranges and mandatory answers. Do not use convenient placeholders for unknown fields. Consult official FAQs and record the conclusion used.
After validation, compare totals to workpapers, generate the filing file, retain the submitted version and obtain the receipt. Record the operation number and date. For an amended return, SAT states that the prior folio and date are needed and that corrected annexes include both changed and required unchanged information.
Common errors
Copying the study without reconciling to the ledger is the principal error. Others include omitting domestic dealings because of the annex’s historical title, aggregating incompatible items, selecting a code based on the account, reporting a different method, using another transaction’s range, or confusing a hypothetical adjustment with an executed one.
Operational errors include reusing last year’s DIM without review, assigning data entry to someone who cannot access the study, overwriting files, failing to retain an imported layout and discovering later that the local return used a different transaction table. A common transaction identifier across deliverables is the simplest control.
Recommended timeline
Sixty days before the deadline, close the population and assign owners. Forty-five days before, freeze the preliminary ledger and classifications. Thirty days before, conclude methods, comparables and true-ups. Fifteen days before, run reconciliation and test entry. Reserve the final week for review and signature, not transaction discovery.
If the deadline has passed, compare the filed version to the final study and other returns. Classify differences as filing, classification or amount issues. Assess amendments in a coordinated way; correcting only Anexo 9 may create a new inconsistency.
Related topics
Management questions before sign-off
Management should ask whether all entities and counterparties were compared against the legal map, whether the reported amounts reconcile to the final rather than preliminary ledger, and whether every true-up has actually been booked. It should also ask who reviewed mandatory technical fields and whether any answer was inserted merely to pass software validation. A clean validation message is not a technical conclusion.
The reviewer should receive a compact sign-off package: filing population memorandum, frozen master table, accounting-to-tax bridge, study conclusion, adjustment evidence, software validation output and final receipt. Where a field cannot be traced to one of those sources, the return is not ready. This package also makes next year’s roll-forward faster because the team can distinguish stable classifications from facts that must be refreshed.
If several Mexican entities file, do not assume one review proves all. Use common classification rules but preserve entity-level tables, approvals and receipts. Differences in tax regime, transactions or accounting can require different answers even within the same group.
- PT-004: annual calendar.
- PT-005: study and evidence.
- PT-007: local return.
- PT-010: ISSIF.
- PT-014 and PT-016: foreign obligations and transaction inventory.
Review-ready reconciliation file
Closing the DIM appendix should create a file that another person can reconstruct without relying on the preparer. Include the downloaded ledger, chart of accounts, counterparty universe, currency bridge, transaction classification, accumulated amount, method, range, adjustment and study reference. Document exclusions with a reason and approver; even a zero closing balance may need explanation where activity occurred during the year.
Before filing, a second reviewer samples in both directions: ledger to appendix to detect omissions, and appendix to accounting to prove existence. Cross-check the annual return, Local File and agreements. Record each difference, cause and resolution. Archive the receipt with a locked reconciliation version and the queries used.
This discipline answers later questions without rebuilding figures months afterward. It also separates capture errors, timing differences and substantive inconsistencies requiring tax analysis.
Sources and verification date
- Mexican Income Tax Law, current text, Articles 76, 110, 179 and 180.
- SAT Multiple Information Return portal.
- SAT Anexo 9 frequently asked questions.
- 2026 Miscellaneous Tax Resolution.
Sources checked on August 2, 2026. Confirm the software, instructions and taxpayer facts before filing.
If your Anexo 9 cannot be reconstructed from the ledger or does not agree with the study, request a reconciliation review before filing or amending it.