> ## Documentation Index > Fetch the complete documentation index at: https://docs.fyvel.io/llms.txt > Use this file to discover all available pages before exploring further. # DATEV GDPdU > Upload accounting data as a GDPdU ZIP from DATEV Kanzlei-Rechnungswesen ### Overview On the GDPdU path you upload **one complete fiscal year as a ZIP file**. The package is created in **DATEV Kanzlei-Rechnungswesen** via the GDPdU export (also called "Vorabprüfung") and is usually provided by the tax advisor. A package always covers one whole fiscal year. That does not mean you import only once a year: you can request a new package as often as you want, for example monthly for ongoing reporting. The content stays year-based. Each package simply brings the current state of the year. GDPdU is usually the simplest way to start with Fyvel. This path fits when: * you do not have your own access to DATEV Unternehmen Online, because enabling it depends on the tax advisor, * you want to try Fyvel first and enabling DATEV Connect depends on your tax advisor, * or you want to take over whole fiscal years at once, for example the history when you start with Fyvel. **The advantage over the account-ledger export:** GDPdU is a standardised format. The export always contains the same set of files, and Fyvel checks the package on import against the included monthly movement totals. The [account-ledger export from DATEV Unternehmen Online](/en/documentation/getting-started/datev-unternehmen-online) depends heavily on the right settings, which is why the wrong file often comes back. If you do not have your own DATEV access, a GDPdU request to the tax advisor is much clearer. An overview of every import path is on [Uploads](/en/documentation/getting-started/uploads). ### Request the package Ask your tax advisor for the **GDPdU data export from Kanzlei-Rechnungswesen**, one export per fiscal year, as a ZIP file. Important for the request: * **One fiscal year per ZIP.** If the archive contains several years for the same client, the upload is rejected. * **A complete export**, not limited to individual accounts or periods. * The package must stay **unchanged**. Do not re-zip it, rename it, or remove individual files. **For ongoing use:** Request the export on the cadence you want to report, typically monthly after the books are closed. Each time you receive the complete fiscal year again, including retrospective bookings in months you already imported. It helps to agree the request as a fixed monthly appointment with the tax advisor. ### Requirements for the ZIP file A valid GDPdU package contains an `index.xml` description file plus the exported CSV files: | File | Contents | | - | - | | `index.xml` | Description of the package and the tables it contains | | `mandantendaten.csv` | Advisor and client number, year, chart of accounts, account number length | | `kontobuchungen.csv` | The individual bookings | | `sachkontenstamm.csv` | General-ledger accounts with names | | `debitorenkreditorenstammdaten.csv` | Debtor and creditor accounts | | `bereichsuebersicht.csv` | Accounting areas | | `buchungsstapelliste.csv` | Overview of posting batches | | `mvz.csv` | Monthly movement totals, the basis for the reconciliation | In addition: * Format **ZIP**, at most **200 MB** per file. * Exactly **one** ZIP file per upload. ### Master data must match Fyvel checks that the package belongs to the selected company. These fields from `mandantendaten.csv` must match [Company settings](/en/documentation/export-and-settings/company-settings): * **Client number** * **Chart of accounts** (SKR03 / SKR04) * **Account number length** If the values differ, the upload stops. In that case either correct the master data in Fyvel or upload the package to the matching company. ### Upload in Fyvel 1. In Fyvel, open the **Uploads** page. 2. Drag **exactly one** ZIP file into the upload area. 3. Fyvel unpacks the package, checks it, and imports the bookings. Depending on the size of the year, this takes a few minutes. The status is shown in the upload table. After successful processing, transactions, accounts, and balances are available. ### What happens on import * **Reconciliation against monthly movement totals:** Fyvel sums the bookings per account and month and compares them with `mvz.csv`. Data is imported only when both sides match. * **The fiscal year is replaced:** Uploading the same fiscal year again overwrites the previous state. The old upload appears in the table as **"Replaced"**. * **Mappings are kept:** Categories you already assigned are linked to the bookings again after the replacement. **Tip:** Before replacing a fiscal year, create a **snapshot** so you can see how the figures changed (see [Booking layers & snapshots](/en/documentation/working-with-fyvel/booking-layers-snapshots)). Fyvel reminds you at upload time. ### Common errors | Cause | What to do | | - | - | | No valid GDPdU package in the ZIP (`index.xml` or `mandantendaten.csv` is missing) | Use the original export. Do not repackage it. | | Required files are missing | Request a complete export (see the table above) | | Several fiscal years in the ZIP | Upload a separate ZIP per fiscal year | | Client number, chart of accounts, or account number length do not match | Check master data in Fyvel, or upload the package to the correct company | | Bookings do not match the monthly movement totals | Generate the export again. The package is incomplete or was changed afterwards. | *** This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.