Invoice Audit Trail PDF Export

[Kingsman-99]

Description

For financial compliance, organizations need a tamper-evident PDF document that records every state change, payment event, and user action on an invoice from creation to closure. This issue generates a formal audit trail PDF for any invoice on demand, including a chronological event table, transaction hashes with links, actor identities, timestamps, and an optional digital signature field for the creator. The PDF must be generated server-side to prevent client-side manipulation.

Technical Context

Create app/api/invoices/[id]/audit-pdf/route.ts as a server-side PDF generation endpoint using @react-pdf/renderer or pdfkit. The endpoint collects all AuditLog entries for the invoice (status changes, payment confirmations, co-creator actions, comment additions), sorts them chronologically, and renders them as a table. Each entry includes: timestamp, actor, action, previousValue, newValue, txHash (if applicable). Add a page header with the invoice ID, creator name, creation date, and platform logo. Append a SHA-256 hash of the event table data as a verification footer. Expose the download button on app/invoice/[id]/page.tsx in an "Audit" dropdown. The PDF must be generated with a consistent Content-Disposition: attachment header to trigger browser download.

Acceptance Criteria

• The generated PDF contains all audit log entries for the invoice in chronological order with no entries missing
• Each entry row shows the correct actor name, action description, before/after values, and timestamp in UTC ISO-8601 format
• Transaction hashes in the PDF are formatted as clickable links pointing to the user's preferred explorer (resolved server-side from settings)
• The SHA-256 verification hash in the footer matches the hash of the event table data computable independently from the raw audit log
• The download endpoint responds within 5 seconds for invoices with up to 500 audit entries and returns a valid PDF MIME type
• All CI checks (npm test, npm run build, ESLint/TypeScript) pass and the branch has no merge conflicts

---

[Emmanuel-Ugochukwu1]

Hi Maintainer, i would love to work on this issue

[Emmanuel-Ugochukwu1]

@Emmanuel-Ugochukwu1 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer, i would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emmanuel-Ugochukwu1 to this issue.

[maugauwi-hash]

@maugauwi-hash has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

may I work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @maugauwi-hash to this issue.

[drips-wave]

Congratulations, @maugauwi-hash! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @maugauwi-hash: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @maugauwi-hash as part of the Stellar Wave Program's 7th Wave 🥳

😎 @maugauwi-hash: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.