Scenario

When posting an invoice (Free Text Invoice, Sales Invoice, or Project Invoice), and if the following conditions are met:

1. e-Invoice attachment is activated on the customer card.
2. “Print invoice” is activated on the posting form.

Then the following actions occur automatically:

• The invoice is printed.
• The invoice is posted.
• A PDF copy of the printed invoice is attached to the respective journal (CustInvoiceJour or ProjInvoiceJour).
• The e-invoice file is generated and stored under Electronic Reporting jobs.

Current Behavior

The attached PDF file uses a generic file name regardless of whether users apply standard SSRS reports or CBD formats.

The default names are as follows:

• SalesInvoice.Report.pdf – Sales Invoice
• FreeTextInvoice.Report.pdf – Free Text Invoice
• ProjInvoice.Report.pdf – Project Invoice
• CustCollectionJour.Report.pdf – Collection Letter

This causes two main issues:

1. User Experience – Users can't easily identify the document before opening it due to the generic naming convention.
2. System Conflict – When used in e-invoice XML files or exposed via access points, these non-unique names can result in duplicates issues.

Proposed Solution

To resolve this, we recommend:

• Updating the logic to follow the file name format defined in CBD or SSRS reports so that attachments have unique and descriptive names.
• Implementing a check to prevent duplicate attachments: if an attachment already exists for an invoice, the system should not recreate the same file when users reprint.

This enhancement would greatly improve document management, streamline user interaction, and avoid issues in systems that consume these attachments.