Getting Started
Accounts, navigation, settings and sessions — the foundations every REGREP module depends on.
Read the guide →Preparing, validating and submitting financial account information under the UK automatic exchange of information regime.
AEOI is the United Kingdom’s implementation of the automatic exchange of financial account information. It applies the OECD Common Reporting Standard to UK reporting financial institutions, which identify accounts held by tax residents of other jurisdictions and report them annually to HMRC.
The module is the same engine as CRS and DAC2. If you have used either, everything here will be familiar — the difference is the receiving authority and the submission type you select when you create the session.
The REGREP AEOI module takes your account data as a spreadsheet, checks it against the structural and regulatory rules, tells you what is wrong with it, and produces the OECD-compliant XML package for submission. It works in three stages, shown as three cards on one screen: data input, regulatory validation, and conversion to the submission format.
All three report the same kind of data through the same engine, and which one you use is determined by where you file, not by what you hold. AEOI is the UK regime and files to HMRC. DAC2 is the EU regime and files to an EU member state authority. CRS covers the jurisdictions outside both. If you are unsure which applies, check the jurisdiction on your corporate profile.
Complete Settings → Corporate Information before creating a AEOI session. The reporting institution’s identity is written into the package directly from these fields, and an incomplete profile produces a package HMRC will reject.
The fields AEOI requires are:
| Field | Why AEOI needs it |
|---|---|
| Legal Entity Name | Identifies the reporting institution in the XML. |
| LEI Number | The 20-character Legal Entity Identifier. Check that the field validates — an invalid LEI is carried into the export. |
| Type of Entity | The entity classification for reporting purposes. |
| Country of Incorporation | Determines the transmitting jurisdiction. |
| Company Type | The business entity structure. |
| Tax Identification Number (TIN) | The reporting institution’s own TIN. |
| GIIN | The Global Intermediary Identification Number. |
| FATCA Filer | The filer status or code. |
Save the tab before leaving Settings.
Solutions → Regulatory Reporting → Tax Reporting Engine → AEOI.
A AEOI session is one submission: a reporting year, a submission type, and the data that goes with it. Corrections to a submission you have already filed are handled as separate, linked sessions rather than by editing the original.
The list shows, for each session, its name, reporting year, report type, version, the parent session where one applies, the submission type, and when it was created and last opened. Two row actions are available: open the session, and delete it.
Deleting a AEOI session removes it and its uploaded data permanently, and there is no archive tab in this module to fall back on. If the session produced a package that has been filed, keep it — it is your record of what was submitted, and a later correction session needs it as its parent.
Use this for the first submission covering a given reporting year. Select + on the session list.
| Field | What to enter |
|---|---|
| Session Name | A descriptive name. Including the year and the words “original” or “correction” makes the list readable later. |
| Session Year | The tax reporting year the data covers — not the year you are submitting in. |
| Submission Type | Open the Submission Type list and choose the new-submission entry for AEOI. |
| Version | Fixed at 1 for an original submission. |
Select SAVE. You are taken to the file upload screen.
If an error or omission is found in a submission that has already gone to HMRC, do not edit the original session. Create a correction session linked to it. The link preserves the audit trail and tells the receiving authority which report is being corrected.
| Field | What to enter |
|---|---|
| Session Name | Something that identifies what is being corrected — for example “AEOI 2025 — Correction of TIN errors”. |
| Session Year | The same reporting year as the parent session. |
| Submission Type | The correction entry in the Submission Type list. |
| Dependent / Parent Session | The original session in which the error occurred. Selecting it links the two. |
| Version | Increments automatically — 2 for the first correction, 3 for the next, and so on. |
A newly created session opens on the upload screen. Drag a file onto the upload area, or select it to browse. Accepted format: .xlsx.
The sidebar on the left shows the session’s parameters — jurisdiction, creation timestamp, reporting year, submission type and version — so you can confirm you are loading data into the right session before you upload. Once the file is attached, REGREP begins processing immediately and the screen changes to the three processing cards.
The three cards run in order. Each has to be satisfied before the next is meaningful: Data Input reports what was read from your file, Regulatory Validations reports what passes the AEOI rules, and XML Conversion builds the submission package.
This card confirms the file was structurally readable and reports what it contained. A progress indicator runs during ingestion and is replaced by “Structural Validation Successful” when the file has been read.
| Count | What it means |
|---|---|
| Total | All rows processed from the file. |
| Accounts | Financial accounts identified. |
| Parties | Account holders and controlling persons. |
| Undocumented | Accounts with insufficient documentation to establish tax residence. |
| Closed | Accounts closed during the reporting period. |
| Dormant | Accounts classified as dormant. |
| TINs | Tax identification numbers detected across all parties. |
Check these counts against your own source system before going further. If the count is materially different from what you expect, the file is wrong or has been truncated — reconciling now is far cheaper than discovering it after submission.
UPLOAD NEW replaces the file with a revised one and re-runs the whole process.
This card checks the ingested records against the AEOI reporting rules — formatting, structure and logical consistency.
| Figure | What it means |
|---|---|
| Valid Records | Rows that pass every regulatory check. |
| Errors | Rows that fail at least one check. These will not be included in a compliant package. |
| TINs Identified | The total number of tax identification numbers found. |
| Valid TINs | How many of those pass format validation for the jurisdiction they claim. |
Select DOWNLOAD ERRORS to export the error log. It lists each failing record and the reason it failed. Correct the records in your source data, return to the Data Input card and select UPLOAD NEW with the corrected file. Repeat until the error count is zero, or until every remaining error is one you have consciously accepted.
The error log contains the failing records themselves, which means it contains names and tax identification numbers. Treat the downloaded file as personal data.
The third card builds the submission package. The gauge shows conversion progress. Where the receiving authority expects one file per reportable jurisdiction, a Countries filter lets you produce a package for a single jurisdiction or for all of them at once; where it expects a single consolidated package, the filter is not shown.
| Download | Use it for |
|---|---|
| DOWNLOAD XML | The OECD-compliant XML package. This is the file you submit. |
| DOWNLOAD JSON | The same data in a structured format, for API integration or internal record-keeping. |
| DOWNLOAD EXCEL | A readable summary workbook of the validated data, for internal review and sign-off. |
Before you submit, open the XML and confirm the reporting institution block carries the correct legal entity name, LEI, TIN and GIIN. These come from Settings, and an error there is invisible in the counts on screen but fatal at HMRC.
Confirm Settings → Corporate Information is complete and saved, and that the LEI field validates.
Create the session: name, reporting year, the AEOI new-submission type, version 1.
Upload the account data file (.xlsx).
Check the Data Input counts against your source system.
Review the Regulatory Validations card. Download the error log if there are errors.
Correct the source data and re-upload. Repeat until you are satisfied with the error count.
Have the submission reviewed by someone other than the preparer, using the Excel download.
Download the XML package and check the reporting institution details inside it.
Submit to HMRC through their own portal.
Record the submission reference against the session, and retain the session — a later correction will need it as its parent.
AEOI files are unlike most of the data you load into REGREP. They contain named individuals, their addresses, their tax residences and their tax identification numbers, together with financial information about them. That is personal data under the GDPR.
| Symptom | Likely cause and fix |
|---|---|
| AEOI is greyed out in the menu | The module is not enabled for your firm. Contact your REGREP account manager. |
| The upload is rejected | The file is not .xlsx, or its structure does not match what the module expects. Check the format before re-uploading. |
| The counts do not match my source system | The file is wrong or truncated. Reconcile before going further — the engine will happily validate an incomplete file. |
| Valid TINs is lower than TINs Identified | Some numbers fail format validation for the jurisdiction claimed. Use the TIN Validation module to check them individually. |
| The Countries filter is missing | Expected behaviour where the authority wants one consolidated package. Otherwise, check the country of incorporation in Settings. |
| The package is rejected after filing | Most often the reporting institution block. Re-check the legal entity name, LEI, TIN and GIIN in Corporate Information, then produce a correction session. |
| Version | Date | Change |
|---|---|---|
| 1.0 | January 2026 | First issue. Documents the shared Tax Reporting Engine workflow as it applies to AEOI. Screenshots and the numeric submission-type codes are pending. |
REGREP is an independent software provider. This manual describes how to operate the platform and is not legal, tax or regulatory advice. Confirm scope, thresholds and submission dates with your competent authority before you file.
The rest of the documentation set.
Accounts, navigation, settings and sessions — the foundations every REGREP module depends on.
Read the guide →Calculating own funds, fixed overheads, K-Factors and concentration risk, and producing regulatory submissions.
Read the guide →Assessing the harms your firm can cause, and the capital and liquidity you hold against them.
Read the guide →Producing the public disclosure of your capital position from the Pillar 1 and Pillar 2 work already done.
Read the guide →