Documentation · Tax transparency

DAC2.

Preparing, validating and submitting financial account information under the EU automatic exchange framework.

Manual Tax Reporting Engine → DAC2 · Version 2.0 · 6 screenshots
NoteThis guide assumes you know how to sign in, navigate the Solutions menu, complete Settings and work with sessions. Those are covered in the Getting Started guide and are not repeated here.

What this module does

DAC2 is the EU framework for the automatic exchange of financial account information between member states. Reporting financial institutions identify accounts held by tax residents of other jurisdictions and report them annually to their local tax authority, which passes the information on.

The REGREP DAC2 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.

The module works in three stages, shown as three cards on one screen: data input, regulatory validation, and conversion to the submission format.

Before you start

ImportantComplete Settings → Corporate Information before creating a DAC2 session. The reporting financial institution's identity is written into the XML package directly from these fields, and an incomplete profile produces a package the tax authority will reject.

The fields DAC2 requires are:

FieldWhy DAC2 needs it
Legal Entity NameIdentifies the reporting financial institution in the XML.
LEI NumberThe 20-character Legal Entity Identifier. Check that the field validates — an invalid LEI is carried into the export.
Type of EntityThe entity classification for reporting purposes.
Country of IncorporationDetermines the transmitting jurisdiction.
Company TypeThe business entity structure.
Tax Identification Number (TIN)The reporting institution's own TIN.
GIINThe Global Intermediary Identification Number used for FATCA alignment.
FATCA FilerThe filer status or code.

Save the tab before leaving Settings.

Opening the module

Solutions → Regulatory Reporting → Tax Reporting Engine → DAC2.

The Tax Reporting Engine. Modules not enabled for your firm appear greyed out
Figure 1 — The Tax Reporting Engine. Modules not enabled for your firm appear greyed out.
NoteIf DAC2 appears greyed out, the module is not enabled for your firm. Contact your REGREP account manager. Other tax frameworks — CRS, FATCA, CbCR, DAC6, DAC7, DAC8 — are separate modules with their own entitlements and their own guides.

Sessions

A DAC2 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 — see section 2.2.

The DAC2 session list before any sessions exist
Figure 2 — The DAC2 session list before any sessions exist.
  1. 1The jurisdiction this module is configured to report to, taken from your corporate profile.
  2. 2Add (+) — creates a new session.

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.

Note

Warning — this cannot be undone

Deleting a DAC2 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 with the tax authority, keep it — it is your record of what was submitted, and a later correction session needs it as its parent.

Creating a new submission

Use this for the first submission covering a given reporting year.

Add Session, configured as an original submission
Figure 3 — Add Session, configured as an original submission.
FieldWhat to enter
Session NameA descriptive name. Including the year and the words "original" or "correction" makes the list readable later.
Session YearThe tax reporting year the data covers — not the year you are submitting in.
Submission TypeNew Submission - 701.
VersionFixed at 1 for an original submission.

Select SAVE. You are taken to the file upload screen.

Correcting a submission you have already filed

If an error or omission is found in a submission that has already gone to the tax authority, 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.

Add Session, configured as a correction
Figure 4 — Add Session, configured as a correction.
  1. 1Submission Type set to Correction submission - 702.
  2. 2The parent session — the original submission containing the error. Selecting it links the two.
FieldWhat to enter
Session NameSomething that identifies what is being corrected, for example "DAC2 2025 — Correction of TIN errors".
Session YearThe same reporting year as the parent session.
Submission TypeCorrection submission - 702.
Dependent / Parent SessionThe original session in which the error occurred.
VersionIncrements automatically — 2 for the first correction, 3 for the next, and so on.
NoteA correction session carries only the records being corrected, not the whole original file. Check your tax authority's guidance on whether corrected, deleted or added records are expected, and prepare the upload file accordingly.

Uploading your data

A newly created session opens on the upload screen.

The upload screen for a new session
Figure 5 — The upload screen for a new session.
  1. 1Drag a file onto this 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.

Processing and validation

The three cards run in order. Each has to be satisfied before the next is meaningful.

The three processing cards after a successful upload
Figure 6 — The three processing cards after a successful upload.
  1. 1Data Input — what was read from your file.
  2. 2Regulatory Validations — what passes the DAC2 rules.
  3. 3XML Conversion — building the submission package.

Data Input

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.

CountWhat it means
TotalAll rows processed from the file.
AccountsFinancial accounts identified.
PartiesAccount holders and controlling persons.
UndocumentedAccounts with insufficient documentation to establish tax residence.
ClosedAccounts closed during the reporting period.
DormantAccounts classified as dormant.
TINsTax identification numbers detected across all parties.
ImportantCheck these counts against your own source system before going further. If the account or party 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.

Regulatory Validations

This card checks the ingested records against the DAC2 reporting rules — formatting, structure and logical consistency.

FigureWhat it means
Valid RecordsRows that pass every regulatory check.
ErrorsRows that fail at least one check. These will not be included in a compliant package.
TINs IdentifiedThe total number of tax identification numbers found.
Valid TINsHow many of those pass format validation for the jurisdiction they claim.

Working through errors

  1. Select DOWNLOAD ERRORS to export the error log. It lists each failing record and the reason it failed.

  2. Correct the records in your source data.

  3. Return to the Data Input card and select UPLOAD NEW with the corrected file.

  4. Repeat until the error count is zero, or until every remaining error is one you have consciously accepted.

ImportantThe error log contains the failing records themselves, which means it contains account holder names and tax identification numbers. Treat the downloaded file as personal data — see section 6.
NoteA TIN that fails validation is not always an error in your data. Some jurisdictions do not issue TINs to individuals, and some issue them in formats that change over time. Where a TIN is genuinely unavailable, follow your tax authority's guidance on the permitted placeholder rather than inventing one. The TIN Validation module can check individual numbers or a batch outside a reporting session.

XML Conversion

The third card builds the submission package. The gauge shows conversion progress; the Countries filter lets you produce a package for a single reportable jurisdiction or for all of them at once.

DownloadUse it for
DOWNLOAD XMLThe OECD-compliant XML package. This is the file you submit to the tax authority.
DOWNLOAD JSONThe same data in a structured format, for API integration or internal record-keeping.
DOWNLOAD EXCELA readable summary workbook of the validated data, for internal review and sign-off.
ImportantBefore 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 the tax authority.

A complete submission

  1. Confirm Settings → Corporate Information is complete and saved, and that the LEI field validates.

  2. Create the session: name, reporting year, New Submission - 701, version 1.

  3. Upload the account data file (.xlsx).

  4. Check the Data Input counts against your source system.

  5. Review the Regulatory Validations card. Download the error log if there are errors.

  6. Correct the source data and re-upload. Repeat until you are satisfied with the error count.

  7. Have the submission reviewed by someone other than the preparer, using the Excel download.

  8. Download the XML package and check the reporting institution details inside it.

  9. Submit to the tax authority through their own portal.

  10. Record the submission reference against the session, and retain the session — a later correction will need it as its parent.

NoteREGREP produces the submission file; it does not transmit it. Filing is done through your tax authority's own portal.

Handling personal data

DAC2 files are unlike the other data you load into REGREP. They contain named individuals, their addresses, their dates of birth, their tax residences and their tax identification numbers, together with their account balances. That is personal data under the GDPR, and some of it is financial data about identifiable people.

The practical consequences for anyone operating this module:

  • Upload only the data needed for the reporting obligation. Do not load a fuller extract because it was easier to produce.

  • Treat the downloaded error log and the Excel summary the same way you treat the source file. They contain the same personal data, and they are the copies most likely to end up on a desktop or in an email.

  • Keep downloaded packages in the location your firm has designated for regulated records, not in a personal downloads folder.

  • Delete local working copies once the submission is filed and your retention copy is in place.

  • Restrict access to the DAC2 module to the people who need it. Access is controlled through Team Management.

NoteYour firm's retention policy governs how long submission packages and source files are kept. Consult your data protection officer or compliance function on where these files should live and for how long. If you need REGREP's own statement on where uploaded files are stored, how they are protected and how long they are retained, request it through Help → Contact Support.

Troubleshooting

SymptomLikely cause and fix
The upload fails or the file is rejected outrightThe file is not .xlsx, or its structure does not match the expected template. Check the format and the column headings.
Account and party counts are lower than expectedThe source extract is incomplete, or rows were filtered out during export. Reconcile against the source system before continuing.
Many TINs are flagged invalid for one jurisdictionUsually a formatting problem in the extract — leading zeros stripped by Excel is the classic cause. Check how the column was exported.
Errors persist after correcting the dataConfirm you re-uploaded the corrected file with UPLOAD NEW rather than leaving the original in place.
The XML is missing or has wrong institution detailsSettings → Corporate Information is incomplete. Complete it, save, and re-run the conversion.
The tax authority rejects the packageCheck the reporting year, the submission type, the LEI and the TIN in the XML header. For a resubmission, use a 702 correction session linked to the original rather than a new 701.

Document control

VersionDateChange
2.0January 2026Rewritten to start at the module. The navigation and Settings chapters move to the Getting Started guide. Adds module entitlement, a data protection section covering the error log and downloaded packages, guidance on unavailable TINs, a full submission workflow, and troubleshooting. Clarifies that REGREP produces but does not transmit the submission, and that a deleted DAC2 session cannot be recovered. Screenshots refreshed using fictional firm data.
1.0Original DAC2 manual.

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.

Other guides

The rest of the documentation set.

All documentation