{
  "id": 14701045,
  "title": "Archiving Invoices as PDF/A: What the Format Forbids, and Why Your Pipeline Should Care",
  "url": "https://urgent.news/2026/10/15/archiving-invoices-as-pdf-a-what-the-format-forbids-and-why-your",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-15T13:16:04.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/marcushale/archiving-invoices-as-pdfa-what-the-format-forbids-and-why-your-pipeline-should-care-9k1"
  },
  "original_language": "en",
  "account": "A German client inquired about the long-term readability of invoices they receive. It became clear that German bookkeeping rules require business documents to remain readable and unaltered for at least a decade. PDF is not the same as an archival PDF. The process designed for that purpose is PDF/A. When invoices are converted to PDF/A, several issues may arise.\n\nPDF/A is a limited subset of PDF (ISO 19005). Its purpose is to make the file completely self-contained, as anything referenced externally can become obsolete within a decade. PDF/A requires all fonts to be embedded, uses device-independent color, does not allow encryption, JavaScript, audio/video, or external references. If a file validates as PDF/A, any conforming reader should render it identically decades later.\n\nThere are three levels of PDF/A: PDF/A-1 (oldest and strictest), PDF/A-2 (allows transparency and layers), and PDF/A-3 (permits embedded files, used in e-invoicing formats like ZUGFeRD/Factur-X). The choice of level depends on the specific requirements and the contents of the invoice.\n\nCommon issues encountered when converting real invoices to PDF/A include unembedded fonts, encryption or permissions flags, device-dependent color, and transparency and blend modes in logos and stamps. Choosing the appropriate level determines how much of the existing artwork will be preserved in the final archival copy.\n\nConversion should be an integral part of the production pipeline, not an afterthought. When invoices are issued, the same job that generates the PDF should also generate the archival copy and validate it. This ensures that conversion is controlled and consistent. Validation reports should be stored alongside the archival files for future reference and auditing.\n\nTo maintain the integrity of the conversion process, keep the original invoice and the archival copy together. Slight changes in appearance, such as color conversion, can occur during conversion. Storing the original and the archival copy together ensures that any potential discrepancies can be easily identified and addressed. Additionally, convert invoices at the time of issuance rather than in a bulk job years later, as the fonts and templates used for conversion are likely to remain accessible. This approach allows for a reliable and testable answer to the question, \"Will it open in ten years?\"",
  "summary": "A client in Germany asked me last year whether the invoices I send will \"still open in ten years.\" It was not small talk. German bookkeeping rules expect business documents to stay readable and unaltered for a decade, and \"it's a PDF\" is not the same as \"it's an archival PDF.\" The format designed for that promise is PDF/A — and the first time you convert real-world invoices to it, several of them…",
  "key_points": [
    "PDF/A is a restricted PDF subset for long-term readability",
    "Requires embedded fonts, device-independent color, no encryption",
    "Conversion should be part of production pipeline, not afterthought"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}