German GDPdU DTD File

Hi,

you don’t need to generate this file just provide it to the customer if needed. 

Unfortunately I coudl not upload the DTD file because the file type is not supported.

I will send it to you via E-Mail.

Best regards

Georgios

Hi Georgios,

Thanks for the information!

Are there any other challenges that you have faced with related to GDPdU files generated from IFS?

Thanks

Gayan

Hi!

When I run the Audit Interface Assistant with format GDPDU i get 2 files. One XML file only explaining the content and one csv file with all the transaction. Should I also get a third file? Reading your earlier comments about this subject, I get the impression that I should also have a DTD file??

I would be very happy for any kind of input regarding this...

We are using IFS version 10 update 14, so we have a very new version.

 \Mats

I am also trying to report according to GDPDU.

Is it correct that the DTD file is not created by IFS, but must be created by another software ?

Hello, even if this is a bit longer ago, but we currently also have problems to generate the requested DTD-file by IFS. Is it possible to get it also by mail?

Best regards

Florian

Hi ​@Georgios Schmidt  Is there a Index.XML file needed for this?

Below is what i got from local finance team.

------------------------------------

A GDPdU/GoBD-compliant index.xml file serves as a standardized machine-readable data description layout. It acts as a map for the tax auditor's software (usually IDEA) to read and interpret the exported raw financial data (usually CSV or TXT files).

It must follow the official Audicon Description Standard v1.0 and relies on the accompanying schema file (gdpdu-01-08-2002.dtd).

A compliant index.xml contains the following core logical and technical elements:

1. General Metadata (<Version>, <Media>)

This section contains general information about the data export package:

• Version details: Specifies the format standard and export software details.
• Company data: The name of the company, location, and comments regarding the audited tax period.
• Creation date: The exact timestamp of when the export was generated.

2. Table and File Descriptions (<Table>)

Every exported data file (e.g., Journal.csv, Accounts.csv) is defined as a logical table:

• URL: The exact physical file name and relative path in the export folder.
• Format type: Specifies whether the data uses fixed column widths (FixedLength) or character-delimited columns (VariableLength).
• Delimiters: Defines the column separator (e.g., semicolon, comma), text qualifiers, and row/line endings.
• Decimal and thousands separators: Essential for the software to parse financial amounts correctly.

3. Field Definitions & Data Types (<Field>)

For every single column within a data file, the index file explicitly declares:

• Name & Description: The technical header and a human-readable explanation (e.g., "Invoice Number", "Posting Date", "Gross Amount").
• Data Type: A strict classification of the content:
  • Alpha (Text/Alphanumeric string)
  • Numeric (Numbers, quantities, or financial amounts)
  • Date (Calendar dates, along with the precise mask, such as DDMMYYYY)

4. Relations and Keys (<ForeignKey>, <PrimaryKey>)

To allow the tax auditing software to reconstruct the relational database structure, the index file defines links between files:

• Primary Key: The unique identifier for a row in a specific table.
• Foreign Key: The relational links connecting different files (e.g., linking a transaction in the Journal file to the Chart of Accounts file via the account number).

--------------------------------------------------------------------