GoBD Mode System Description

Process documentation (Verfahrensdokumentation): the technical part for Paperarchive customers

Version 2.1, last updated October 6, 2026

Draft, October 6, 2026. The retention periods and how the features map to the GoBD have not yet been reviewed by a tax advisor. This description is not legal or tax advice.

The German GoBD require every business to keep its own process documentation (Verfahrensdokumentation). This system description covers the part only I, as the maker, can describe: what Paperarchive does technically when a space runs in GoBD mode, and what it does not do.

Paperarchive supports GoBD-compliant archiving. Whether your bookkeeping and record keeping as a whole meet the GoBD depends on your entire process. Paperarchive is not certified and is not an accounting system.

For your own part there is a template to fill in (German): Process documentation template

General information

SystemPaperarchive, cloud-based document management (web app, iOS and Android app, API)
Maker and operatorMarcel Klein, Paperarchive, Auf der Weide 3, 58840 Plettenberg, Germany
Version2.1
DateOctober 6, 2026
ReferenceGoBD (BMF letter of 28.11.2019, BStBl I p. 1269, as amended), § 147 AO, § 257 HGB, § 14b UStG

1. General description

Scope

  • The GoBD rules apply only in spaces where you switched on GoBD mode. A space is a separate area in your account, for example "Business" next to "Personal".
  • File hashes (SHA-256) and the change log run for all documents. Archiving, retention periods, locks, deletion protection and the monthly integrity check exist only in GoBD mode.

Roles

RoleTask
Maker and operator (Marcel Klein)Development, operation, monitoring, this description. Paperarchive is run by one person.
Space owner (customer)Switches on GoBD mode, is responsible for capture, completeness, checking the details, their own process documentation and access.
Admin, editor, viewerMembers of a shared space with the rights of their role.
AuditorTime-limited read access for a tax audit.

Originals and recognized details

Paperarchive stores original files and recognizes details such as title, date, sender, category, amount, due date and reference number. The original file is what counts for retention. The recognized details are index data for search, deadlines and exports.

2. Capture

ChannelWhat arrivesNotes
Upload in the web appThe file as uploadedAt most 50 MB per file
Camera capture (web app, iOS, Android)Usually a PDF of the captured pagesImages are scaled down and compressed. The resulting file is the original; Paperarchive does not check image quality.
Email to the personal upload addressAttachments as separate documents; an email without a usable attachment as an .eml documentRaw message up to 25 MB, optional sender allowlist
Google Drive, DropboxFiles from a chosen folderAt most 50 MB; no XML files or emails
REST APIFile via API keyAt most 50 MB; the file type is checked against its content

Accepted formats

  • Web upload: PDF, JPG, PNG, GIF, WebP, TIFF, BMP, HEIC/HEIF, Office documents (DOCX, DOC, XLSX, XLS, PPTX, PPT, ODT, ODS, ODP) and XML if it is an e-invoice.
  • Email attachments: PDF, JPG, PNG, GIF, BMP, WebP, HEIC/HEIF and XML e-invoices. Office attachments are not taken over by email.
  • REST API: PDF, JPEG, PNG, TIFF, HEIC/HEIF, Office documents and XML e-invoices.
  • Google Drive and Dropbox: the same list as processing, without XML and emails; it also contains SVG, which the web upload does not accept.
  • XML is only accepted as an e-invoice (UBL Invoice/CreditNote or CII CrossIndustryInvoice). Password-protected PDFs are rejected.

E-invoices and emails

  • XRechnung (XML): the XML file is the original and stays unchanged. Paperarchive creates a PDF view for display only. Amount, dates, sender and payment details come from the invoice data. Downloads deliver the XML file.
  • ZUGFeRD / Factur-X: the PDF is the original and stays unchanged. The embedded invoice XML is read and its values replace the recognized values.
  • Email without attachment: the raw message is stored unchanged as .eml and converted to a PDF for display.
  • Source email in a GoBD space: when attachments of an email land in a GoBD space, Paperarchive also stores the raw message once per content and links it to every document created from it. If a further email later brings an attachment that already exists in the space, no new document is created: the new email is linked to the existing document as an additional source email and is kept, protected and exported like the first one.

Space and duplicates

The space comes from the upload details, otherwise from the existing document, otherwise from the default space. For incoming email, the space short name in the address or rules by sender and subject decide. If a file has the same SHA-256 hash as an existing document of the same user, Paperarchive does not create a second document; for an upload into a GoBD space only a document in the same space counts, a copy in another space is no duplicate. An email whose sender check (SPF, DKIM, DMARC) fails is not dropped in a GoBD space: it is kept in quarantine with a Needs input item for review.

3. Processing

Every upload creates a document record and starts processing in seven stages:

  1. Validation: compute the SHA-256 of the stored file, compare it with the app hash (if any), check for duplicates, store the hash, assign the space, check size, type and password protection.
  2. Conversion: Office documents to PDF (LibreOffice), HEIC to JPEG, XML invoices and emails to a PDF view. The conversion is stored next to the original; the original stays unchanged.
  3. Malware scan with ClamAV. If malware is found, the file is deleted and processing stops.
  4. Text recognition: locally for PDFs with a complete text layer, otherwise via Google Cloud Vision at the EU endpoint (eu-vision.googleapis.com), up to 100 pages, with a content check (SafeSearch). E-invoices and emails bring their own text.
  5. AI analysis via Azure OpenAI (Germany West Central, EU Data Zone): title, date, category, sender, amount, due date, reference number, structured details and an event (invoice, receipt, contract and so on). In a GoBD space a provisional retention period applies from the upload (end of the upload year plus 10 years); at archiving it is replaced once by the period of the document type.
  6. Tagging: optional topic tags, never stops processing.
  7. Matching: embeddings for search (Azure OpenAI, EU Data Zone) and similar documents.

Afterwards Paperarchive marks the document as completed and, in a GoBD space, archives it (see section 4). In production the API does not start if an AI or OCR provider is missing or document data would be processed outside the EU.

Every processing run is logged with trigger, status, duration per stage and, on failure, the stage and error code. A failed document can be processed again. In a GoBD space a failed document is not archived automatically and needs a decision (see section 4).

Uncertain details create a Needs input item for confirmation. In a GoBD space a document without open items is archived right after processing; a document with an open Needs input item is archived once it has been reviewed, at the latest 10 days after the upload. Until then the document can still be edited, moved to the trash, deleted, split, merged and moved to another space; every step is in the change log. After archiving, only the owner or an admin of the space can correct index data, with a mandatory reason, through the correction function: document date, sender, category, reference number, structured details and the values of the event (amount, currency, due date, reference number, type, period, cash discount); a missing event can be added. The web app offers date, sender, category and due date in its edit form. The change log keeps the old value, the new value and the reason. The file and its derived files, the hashes, the capture time, the archive date and reason, the retention date, the space and the uploader can never be corrected. The original file is what counts.

4. Archiving and retention

When documents are archived

  • Archiving starts only when processing is complete and a SHA-256 hash of the original exists. Right before archiving, Paperarchive checks the stored original against that hash. On a mismatch the document is not archived and the space owner is notified.
  • Automatically at the end of successful processing, if the document is in a GoBD space and has no open Needs input item. Documents with an open item are archived once they have been reviewed, at the latest 10 days after the upload.
  • Manually from the document menu or as a bulk action (admin or owner role). When GoBD mode is switched on, the app offers to archive existing documents.
  • An hourly run archives completed documents that were not archived right away, for example after a review or documents moved into the GoBD space later (they get the provisional retention when they are moved in), once they are 6 hours old; with an open Needs input item, as above.
  • Warning: failed uploads and documents whose processing failed are not archived automatically. They need a decision: retry the processing, or archive the document explicitly with a written reason (owner or admin). A document still not processed after 10 days is not archived automatically either; the owner gets a weekly in-app notice until it is processed or archived explicitly. The explicit archiving and its reason are logged.
  • Each archiving is logged with its reason: after processing, hourly check, after confirming a review, at the 10-day limit with an open question, manually, by DATEV export, explicitly for an incomplete document.
  • Until archiving, users cannot change or delete the original or its derived files in a GoBD space; only Paperarchive's own processing (conversion, split, merge) can.
  • Archive time, archiving person and end of retention are written in one step. Archiving cannot be undone.
  • When GoBD mode is switched on, every document of the space gets a retention period. GoBD mode cannot be switched off while documents are under retention or a retention hold is active. A GoBD space can only be deleted when it holds no archived documents and no retention hold is active: archived documents whose retention has expired must go to the trash first, never-archived documents move to the space the owner chooses. The app says so before switching it on. Every switch is logged.

What is locked

The locks are database triggers and apply to the app, the API and the internal service access of the API. The only path past them is the account deletion, after an explicit retention acknowledgement for the user's own GoBD spaces; archived uploads in GoBD spaces of other owners and uploads under a retention hold are not deleted but transferred to that owner (see section 11). An active retention hold blocks this account deletion until the hold is released or the space is transferred.

  • Document: text content, title, file name, document date, capture time, sender and category (also the stored sender and category names), reference number, structured details, hash fields, file, file path references, archive details with reason, retention period and the time of a transfer to the space owner. A missing event is linked only through the correction. An archived document cannot be moved out of the GoBD space; the original file cannot be overwritten or deleted.
  • The document's event: amount, currency, due date, reference number, type and document link; deletion only after the retention period. The status (for example paid) stays editable and is logged.
  • Index data (including the file name) is corrected only through the correction function with a mandatory reason (owner or admin, see section 3). Tags and similar secondary details stay editable. Every change is logged.

Retention periods

The period depends on the type of the event that belongs to the document. The values are an operator decision of October 2026 and must be confirmed by a tax advisor.

Event typePeriodLegal basis
Invoice, receipt, bank statement, credit note8 years§ 257 (1) no. 4, (4) HGB; § 147 (1) no. 4, (3) AO (BEG IV)
Contract, insurance policy10 years§ 257 (1) no. 1, (4) HGB; § 147 (1) no. 1, (3) AO
Letter, offer6 years§ 257 (1) no. 2, 3, (4) HGB; § 147 (1) no. 2, 3, (3) AO
Notice, payslip6 years§ 147 (1) no. 5, (3) AO
No event or other type10 yearsDefault (longest period)
  • The period ends on December 31 of the year "year of the document date + period". Example: invoice dated March 15, 2026, period ends December 31, 2034. Without a document date the capture time counts.
  • A period is never shortened. Documents archived earlier keep their period even if the table changes. Before archiving, the provisional period applies; at archiving it is replaced once by the period of the document type (the change log notes this as policy_applied). For contracts and policies the owner or an admin can set the end of the contract; the period then runs from there.
  • The suspension of expiry under § 147 (3) sentence 5 AO is not detected automatically; it is covered by a retention hold that the owner or an admin sets (see below).
  • 60 days before the retention of archived records ends, the space owner gets an in-app notice.

Retention hold (Löschsperre, Ablaufhemmung)

  • Owners and admins of a GoBD space set a retention hold for the whole space or for one document, with a reason and an optional end date. Setting and releasing are logged with the reason (retention_hold.set, retention_hold.released).
  • While a hold is active, covered documents are not finally deleted, also after their retention has ended. Moving them to the trash is still possible, but the 30-day trash purge skips them. Their change log values stay. The space cannot be deleted and cannot leave GoBD mode.
  • An active hold blocks the account deletion of the space owner: the deletion is refused until the hold is released or the space is transferred.
  • Retention holds are set in the web app. The iOS and Android apps do not show them yet.

Deletion

  • An archived document with a running period can neither be moved to the trash nor deleted. An archived document without an end of retention stays protected.
  • A document that is not archived yet can be moved to the trash, deleted, split and merged, also while its provisional period runs. Every step is in the change log with the person who did it. When such a document is deleted from a GoBD space, its logged values are kept until the end of the year of intake plus 10 years (at least the provisional retention) and stay in the change log of the GDPdU export; if the space owner deletes their own account, these values are removed.
  • A never-archived document can be moved out of a GoBD space. Its retention ends, and the move is logged with the old and the new space.
  • After the period ends, an archived document can be moved to the trash, restored and deleted; its other details stay locked. Paperarchive does not delete automatically after the period ends.
  • The trash is emptied after 30 days; archived documents under retention and documents under a retention hold stay. When a document was split and one of its parts is archived, the source stays in the trash. Every step is in the change log.
  • Archived documents in GoBD spaces stay readable, downloadable and exportable even above the plan limit.

5. Immutability and logging

What a change log entry contains

FieldContent
TimeSet by the database itself, no backdating
OwnerOwner of the affected document or event
Actor and actor typeWho triggered the change (user, system or processing); stays as a pseudonymous ID after account deletion
Action and recordFor example document changed, archived, deleted
Old and new valueOf the changed fields
ContextSpace and, for events, document; request ID
Hash chainPosition, hash of the previous entry, own hash

What is logged

  • Document: created, changed (display name, title, content only as "changed", sender, category, space with old and new space, reference number, structured details, document date, file, archiving, retention), archived with reason, corrected with reason, split (each part keeps a reference to its source), merged (the original file of a converted target stays referenced), moved to trash, restored, deleted.
  • Tags: added and removed. Event: created, changed (amount, currency, due date, reference number, type, status), deleted.
  • Space: GoBD mode on and off, ownership transferred to an admin, retention hold set and released, auditor access granted, changed and removed, every file an auditor opens or downloads, GDPdU export created, DATEV export created.
  • Integrity checks, broken hash chains and every removal of logged values.

Not logged: read access of members (viewing, searching, downloading), changes to settings, categories, senders and tags themselves, and the full text before and after a content change. Files an auditor opens or downloads are logged (see section 7).

Entries for documents, tags and events are written by the database in the same transaction as the change: if the entry fails, the change fails. The entries for auditor file access and DATEV exports are mandatory as well: if they cannot be written, no file and no export is handed out. Other entries the API writes itself (integrity check, GDPdU export) do not stop the operation on a write error; the error is noted in the application log.

Append-only and hash chain

  • Changing, deleting and truncating the change log are blocked in the database. Users have no write access. The only exceptions are the defined deletion rules for the stored values: final deletion after the retention, expiry of the retention (daily purge) and account deletion, which also removes the owner reference. A retention hold keeps the values. Values without a document are erased after 10 years, job run records after one year. On an account deletion the IP address and browser of the deleted user are removed from entries that stay (records transferred to a space owner); the values stay. Each removal is itself logged, and the monthly integrity run cross-checks the removals against these rules. The entry itself and the hash chain stay.
  • The entries of an owner form a hash chain (SHA-256): each entry contains the hash of the previous one. A change or removal becomes detectable (tamper-evident), but is not prevented.
  • Someone with superuser rights on the database (the operator) could recompute a chain from a given point. This shows up when you compare exported hash values with a later export.
  • Entries from before the hash chain are not chained, have no recorded actor and cover only part of the fields.

Viewing and export

  • Everyone who may open a document sees its history in the History tab, for the period the document has been in its current space. Only the uploader also sees the history from before.
  • Owners and admins of a GoBD space export the change log for a period as CSV or JSON, including the hash chain values. Auditors get it through the GDPdU export.

6. Integrity

On upload Paperarchive computes the SHA-256 of the stored file before any conversion and stores it. If the app computed its own hash during upload, both are compared; if they differ, processing stops.

  • Monthly: once per calendar month Paperarchive recomputes the hash of the original file of every archived document in a GoBD space, compares it with the stored hash, checks the owners' hash chains and cross-checks every removal of logged values against the deletion rules.
  • Before archiving: the stored original is checked against its hash; on a mismatch the document is not archived and the space owner is notified.
  • On demand: "Check integrity" in the History tab of an archived document runs the same check for that document.
  • Results (unchanged, mismatch, file missing, no hash, check failed) are in the change log and in the document history.

Mismatches and broken chains are also reported to error monitoring, with IDs and reason only. Paperarchive does not change anything automatically; I investigate the cause. A changed or missing original file cannot currently be restored from an independent backup (see 8).

7. Data access

Sign-in and permissions

  • Sign-in with email and password, Google or Apple, optionally with two-factor authentication. Exports and invitations require the second factor when 2FA is set up.
  • The web app and the apps access the database directly through the Supabase API; Row Level Security limits every access to your own data and the spaces you are a member of. The API checks permissions itself.
  • The operator technically has access to all data; such access is not logged separately.
  • The owner can transfer a space to an admin member (Transfer space); the transfer is logged in the change log of the space.
RoleRights
OwnerEverything, including transferring and deleting the space
AdminManage members and settings, edit, archive, correct with reason, retention holds, export the change log, GDPdU export
EditorUpload, edit, move, delete within the locks, DATEV export
ViewerRead and search
AuditorRead and search, history, GDPdU export, time-limited

Direct access (Z1): auditor role

  • Owners and admins invite by email with the role "Auditor (read only, limited time)" and pick an end date at most one year ahead. The invitation link is valid for 7 days, the person needs a Paperarchive account, and the space owner needs an active plan or trial.
  • The auditor sees documents, files, events, details and history, can search and create the GDPdU export. They cannot upload, change, delete, archive or invite.
  • Access ends automatically on the chosen day, after at most 366 days; the database checks this on every query. Owners and admins can extend, shorten and remove it at any time; the auditor cannot end it or leave the space. The role itself cannot be changed. Everything is logged in the change log of the space.
  • Every file an auditor opens or downloads (web app, iOS, Android, public API, MCP) is logged as auditor.document_viewed in the change log of the space before the file is handed out. Auditors cannot read files directly from the file storage; files reach them only through this logged link. If the entry cannot be written, no file is handed out. Exports of the auditor are logged too.

Indirect access (Z2)

You or a person you appoint evaluate the data in Paperarchive as the auditor requests: full-text search, filters, downloading originals, exporting the change log and the exports below. Paperarchive does not include its own audit software.

Data carrier handover (Z3): GDPdU export

  • For owners, admins and auditors, signed in only (no API key), with the second factor when 2FA is set up.
  • All documents of the space whose document date (otherwise capture time) is in the period, without the trash except archived documents moved to the trash after their retention (column Papierkorb); at most 11 years.
  • ZIP with index.xml following the description standard of the German tax authorities (DTD gdpdu-01-09-2004.dtd), dokumente.csv, ereignisse.csv, aenderungsprotokoll.csv with every entry of the space in the period and the hash chain, fehlende_dateien.csv for files that could not be included, and the original files. UTF-8, semicolon, decimal comma, dates DD.MM.YYYY in Europe/Berlin time, values unchanged.
  • Large exports are split into parts of up to 400 MB, each with all tables. Every export is logged in the change log.
  • Also included: visualizations (the PDF view of e-invoices and emails), source emails including further emails that carried the same attachment, and the source files of merges.

DATEV export

Handover to your tax advisor for at most one year: DATEV booking batch (format 7.0), receipt overview and the originals of completed invoices, receipts and credit notes of the whole space. For owners, admins and editors of the space; viewers and auditors cannot start it, because it archives the exported documents in a GoBD space. Not an audit export. Every DATEV export is logged in the change log of the space (space.datev_exported). From a GoBD space the export archives every exported document; documents with an open question are not exported but listed in belege.csv with a note; if archiving fails, no export is created. In addition, every user can request a complete export of their data at any time.

8. Data security and backups

  • TLS for all connections, encryption of stored data at Supabase/AWS (AES-256), private storage, file access only through short-lived signed links.
  • Malware scan of all uploads, checks of file type and size.

Backups

  • Database: daily backups by Supabase, kept for 7 days, region Frankfurt. No point-in-time recovery; up to 24 hours of data loss are possible.
  • Files (originals, conversions, emails): stored in Supabase Storage in Frankfurt, not part of the database backups, and currently without a copy independent of the system. This is a known gap.
  • Planned: a nightly encrypted copy of the files to storage at Hetzner. There is no date yet.
  • Until then: create a GDPdU export or your account data export regularly and keep it outside Paperarchive.

Recovery

  1. Restore the database from the matching daily backup of the last 7 days.
  2. Run the integrity check for all archived documents and check the hash chains.
  3. Reconcile changes since the backup using the change log and existing exports; have missing documents captured again.
  4. Document the result and the affected documents.

9. Operations

ComponentLocation
Database, file storage, sign-inSupabase on AWS, Frankfurt am Main
API, web app, website, reranking, malware scanOne VM at Hetzner, Falkenstein (Germany)
Incoming emailCloudflare Email Routing, then the API on the VM
Text recognitionGoogle Cloud Vision, EU endpoint
AI analysis and embeddingsMicrosoft Azure OpenAI, Germany West Central, EU Data Zone
  • Source code and database migrations are versioned in Git. Changes go through pull requests with automated tests.
  • After merging, GitHub Actions build the services and copy them to the VM; migrations run with a dry run first. A schema contract then checks that all required tables, views and functions exist. A CI guard blocks unreviewed DROP statements.
  • Monitoring: health checks and processing reports via n8n, error monitoring with Sentry (EU region, without names or content), automatic security updates on the VM. The GoBD monitoring warns if the hourly archive check has not run for 2 hours, the monthly integrity check is missing, GoBD documents stay unarchived for more than 10 days, the storage protection trigger is missing, or the daily retention purge failed or did not run.
  • Every version of this description is versioned with its date. Save the version valid at the time of your process documentation as a PDF.

10. Internal control system

ControlTypeWho
Locks, deletion protection, periods never shorter, GoBD mode cannot be switched offDatabase triggersSystem
Hash at upload, comparison with the app hash, duplicate checkProcessingSystem
Hash check of the original right before archiving, no automatic archiving of incomplete documentsAPI and databaseSystem, owner decides on incomplete documents
Retention hold for a suspension of expiryDatabaseOwner or admin sets it
Warnings on missed archive runs, missing checks, unarchived documents, missing storage protection and failed retention purgeMonitoringSystem, operator responds
Monthly check of files and hash chains with alertingAPISystem, operator responds
Append-only log with hash chainDatabaseSystem
Roles, Row Level Security, time-limited auditor access, 2FA for exportsDatabase and APISystem, customer assigns roles
Tests, migration guard, schema contract on every deploymentCI/CDOperator
Checking uncertain details, completeness, legibilityUser actionCustomer

Known weakness: Paperarchive is run by one person. There is no four-eyes principle for deployments and no arranged deputy yet.

11. Limits: what Paperarchive does not do

  • No certification and no audit under IDW PS 880 or other standards.
  • No process documentation for you: you need your own (template below).
  • Not an accounting system: no books, no cash register, no financial accounting.
  • No image quality check: whether paper may be destroyed after scanning is your decision under your documented scanning process.
  • Corrections after archiving only with a reason: in a GoBD space documents are archived after processing (with an open Needs input item after review, at the latest 10 days after the upload); afterwards only the owner or an admin can correct index data, with a mandatory reason (see section 3), and the file, the hashes, the capture time and the archive data never change.
  • No automatic archiving of failed or unprocessed documents: they need a decision (retry or explicit archiving with a reason).
  • Periods by event type: a wrongly recognized type or date leads to a wrong period. The suspension of expiry is not detected automatically; it needs a retention hold.
  • No automatic deletion after the period ends.
  • No independent backup of the files and no point-in-time recovery.
  • Read access of members is not logged (files auditors open are); older log entries are not chained.
  • Account deletion is the only path past the locks: it also deletes archived documents with a running period in your own GoBD spaces, after an explicit confirmation that you keep the records yourself; an active retention hold in one of your spaces blocks it until the hold is released or the space is transferred; archived documents you uploaded to a GoBD space of another owner stay there and pass to that owner with tags, sender and category, without your IP address and browser in the change log. Export first, also before cancelling.
  • Retention holds are set in the web app only; the iOS and Android apps do not show them yet.
  • Email does not take over Office attachments and does not store messages over 25 MB.

Your tasks: switch on GoBD mode for the right spaces, check completeness and legibility, check recognized details, type and date, grant and revoke access, keep your own process documentation, agree the periods with your tax advisor and export regularly.

12. Change history

VersionDateChangeResponsible
1.0February 2026Initial versionMarcel Klein
1.1July 2026Processing updated to seven stagesMarcel Klein
2.0October 5, 2026Rewritten as the GoBD mode system description: capture and formats, e-invoices and emails, automatic archiving, locked events, periods of 6, 8 and 10 years, deletion after expiry, change log with actor and hash chain, integrity check, auditor role, GDPdU and DATEV export, backups, limits. Incorrect statements of the previous version removed.Marcel Klein
2.1October 6, 2026Incorrect statements corrected: DATEV exports are logged and archive in a GoBD space; contents of the GDPdU export; moved and failed documents are archived automatically only after completed processing, otherwise after an explicit decision; deletion rules for logged values; only archived documents are blocked from split and merge; account deletion named as the only exception to the locks; space transfer possible; emails of unverified senders quarantined in a GoBD space; duplicates per space; scope of corrections described the same everywhere. New: hash check before archiving, archiving reason in the log, logged auditor file access on all channels, retention hold with a notice 60 days before the end of retention, lineage of split and merge, further source emails, monitoring of the daily retention purge.Marcel Klein

Appendix