Hi Team,

Please consider implementing a function that allows attachments to be carried forward from the source document to the final document and related ledger entries.

This enhancement would significantly improve traceability across transaction stages.

Ideally, the design could follow a similar approach to the 'Dimension Set ID' structure—where the attachment resides in a single table and is referenced across documents, rather than duplicating the file for each transaction.

This would help optimize database usage and maintain consistency.

For example:

1. PQ stage: user attach Doc. 1A & 1B > Make Order
2. PO stage: Doc. 1A & 1B auto populated, user add new attachment 2A > Post Receipt/ Create Warehouse Receipt (Get Source)
3. Posted Purchase Receipt: Doc. 1A, 1B, 2A auto populated. if possible, user can also add new attachment on the GR. user add document 3C
4. PI stage: user Get Receipt line, Doc 1A, 1B, 2A & 3C auto populated. User add new attachment 4B > Post Invoice
5. Posted Purchase Invoice: Doc. 1A, 1B, 2A, 3C and 4B auto populated. if possible, user can also add new attachment on the Posted Invoice. user add document 5B
6. Vendor Ledger Entry: the document attachment also carried forward to the ledger of invoice line.
7. Payment Journal: when user apply the payment line to the invoice, the user can navigate to the invoice and see all the attachment. (I think standard BC already covers point 7, with "Show Posted Document" function in the Apply Entries page)

Thank you.