Today, Incoming Documents are matched to posted records using only the Document Number and the Posting Date. The Document Type and source table are not taken into account.

As a result, when two records from different posting sources — for example a General Journal entry and a Posted Sales Invoice — share the same Document Number and Posting Date (even when they originate from different number series), the same Incoming Document is associated with both. Opening the Posted Sales Invoice can therefore display an Incoming Document that actually belongs to the General Journal entry.

Business impact:

• Incorrect document associations reduce trust in the Incoming Documents feature.
• Users may open, reference, or audit the wrong source document.
• Reconciliation, audit, and compliance reviews become harder when attachments don't reliably map to the correct posted record.
• The existing workarounds (separate number series or separate posting dates) aren't always practical for customers with established numbering conventions.

Requested enhancement:

Extend the Incoming Document matching logic to include the Document Type and/or source table as part of the association key, in addition to Document Number and Posting Date. This would ensure that records from different posting sources sharing the same Document Number resolve to the correct Incoming Document, without requiring changes to a customer's numbering or posting-date practices.