How to Regenerate an Old Invoice PDF Identically in Node.js: A Dispute Workflow

When handling a dispute involving an old invoice PDF in Node.js, it is important to avoid recreating the invoice by rerunning the current template. Instead, preserve the original PDF bytes and verify their hash. Only render a replacement if the original artifact is unavailable. This approach ensures that the visual similarity between files does not equate to identical byte data.

Before attempting to regenerate an old invoice PDF, treat it as an evidence package and store the following information: the source PDF, the invoice's business inputs, the template revision, font files, locale, timezone, and the rendering tool version. Additionally, maintain a SHA-256 digest alongside the object to prove which bytes were examined.

Store the digest in a content-addressed path, such as invoices/{invoiceId}/{sha256}.pdf, to clearly identify the specific object selected by an auditor and prevent accidental overwrites.

If the original bytes are available, create a byte-for-byte copy of the verified object and hash the result for comparison. This method is useful when a case-management system needs a local working copy while the evidence vault remains untouched. Conversely, if the original bytes are not available, the reconstruction path involves replaying a controlled rendering recipe, documenting every input, and labeling the output as reconstructed. This process ensures that the visual output is not mistaken for an identical evidence piece.

To regenerate an old invoice PDF identically for a dispute, you have two options: streaming the verified object to a new location and hashing the result for the verification path, or freezing every input, serializing monetary values, sorting line items, using explicit timezone information, and pinning the runtime environment for the reconstruction path. These steps help maintain the integrity of the document and provide a clear audit trail for any disputes that may arise.