3790877 - Supplier Invoice: Synchronize Transaction Type And Document Type; Validate Posting Date Equals Tax Reporting Date (BAdI Feasibility)

• You require synchronization of Transaction Type and Document Type fields in Supplier Invoice applications.
• If Transaction Type = Credit Memo, Document Type should automatically be determined as Customer Credit Memo.
• A suitable Change/Derivation or Validation BAdI specific to Supplier Invoice applications is required to implement this logic without affecting other modules or processes.
• A validation is needed to ensure Posting Date equals Tax Reporting Date during supplier invoice creation and parking.
• No suitable application-specific BAdI or extensibility option has been identified to implement this validation.

• Product: SAP S/4HANA Cloud Public Edition
• Tax (Public Cloud)

1. In a Supplier Invoice application, select a Transaction Type (for example, Credit Memo).
2. Observe that the corresponding Document Type is not automatically derived to a matching type.
3. Enter a Posting Date; the system copies it to the Tax Reporting Date initially.
4. Manually change the Tax Reporting Date; the system allows saving/parking with mismatched dates.

• The system copies the Posting Date to the Tax Reporting Date by default, but the Tax Reporting Date remains editable for legal reasons, allowing differences.
• No no-code change/derivation extension point exposes the Tax Reporting Date at supplier-invoice entry; the supplier-invoice check extension does not include this field and cannot change values.
• The only extension point that exposes the Tax Reporting Date applies to all accounting documents, not only supplier invoices.
• Document Type behavior depends on document flow: for direct Financial Accounting vendor credit memos, Document Type is determined by standard FI configuration; for purchase-order-based invoices, standard Document Type is RE for both invoices and credit memos, and users set it manually. Automatic mapping from Transaction Type to a non-standard Document Type would require custom logic.

1. Retain the standard behavior: Posting Date is copied to Tax Reporting Date; if users do not edit it, both dates remain equal.
2. Test standard validations: try posting/parking with different Posting Date and Tax Reporting Date and confirm whether a standard message blocks the mismatch. If blocked, no extension is needed.
3. Note limitation: a supplier-invoice-only rule to enforce equality is not possible because the supplier-invoice check extension does not expose the Tax Reporting Date and cannot change values.
4. If a hard block is essential, implement a check at accounting-document level and initially run it as a warning in a test system. Restrict scope to supplier invoices via document-source information and confirm the design with tax specialists to avoid unintended VAT impacts or blocking cancellations.
5. If a targeted supplier-invoice check is desired in future, submit an improvement request to have the Tax Reporting Date added to the supplier-invoice check. Refer to the link in See also.
6. For Document Type derivation/validation:
   • For direct Financial Accounting vendor credit memos (non-PO), rely on standard FI document-type configuration; no development required.
   • For PO-based Logistics Invoice Verification, standard Document Type is RE for invoices and credit memos; users choose it manually. If automatic derivation from Transaction Type is mandatory, implement a BAdI that supports this (as in self-billing/ERS-type examples).
7. To validate Document Type on supplier invoices only, use the supplier-invoice check extension to raise a blocking message based on allowed Document Types. Be aware that the extension may not expose Transaction Type for conditional rules.

• refer to: Create Supplier Invoice
• refer to: Create Incoming Invoice
• refer to: Park Supplier Invoices
• refer to: Custom Fields (F1481) and Custom Logic (F6957)
• refer to: 2963059 - How to Submit Feature Requests for SAP S/4HANA Cloud Product

supplier invoice, transaction type, document type, derivation, validation, tax reporting date, posting date, badi, supplier-invoice check, liv, credit memo, document type mapping, accounting document check, public cloud, s/4hana cloud , KBA , MM-IV-INT-TAX-2CL , Tax (Public Cloud) , Problem