Invoice PDF storage
Invoice PDF storage
Generated invoice PDFs are handled through the attachments system. Invoice rows link to attachment identifiers, and the attachment metadata in attachments.csv records where the underlying file lives. A typical repository keeps the actual PDFs under ./attachments/yyyy/mm/yyyymmdd-filename... (for example attachments/2026/01/20260115-INV-1001.pdf), while preserving the stable link from invoices to attachments through attachments.csv.
Storing PDFs in Git is supported for completeness even though diffs for binaries are not meaningful; repository size concerns may cause users to store PDFs outside Git, but the default encourages “everything together” for audit completeness. Where long-term preservation is desired, PDF/A should be used for generated invoices (see PDF/A Family, PDF for Long-term Preservation (Library of Congress)).
When PDFs are stored outside Git, BusDK MUST still preserve attachment metadata and stable references so that vouchers and postings can be verified. See Finnish bookkeeping and tax-audit compliance.