3757634 - Days Payable Outstanding Calculation Logic - Missing of Relevant Documents - SAP S/4HANA Cloud Public Edition

• Clarification required on how the Days Payable Outstanding app computes the DPO value.
• System's calculation result is different from user's manual calculation although all RE invoices within the same period is considered. 

SAP S/4HANA Cloud Public Edition.

1. Run application Days Payable Outstanding with selected supplier and company code for 12 months reporting.
2. Manually calculate DPO for the same selections of supplier and time periods, following the Calculation Logic: Days Payable Outstanding.
3. Compare the manually calculated DPO to the value shown in the Days Payable Outstanding app and observe the numbers do not match.

The difference in system and manual calculation happens because system's calculation includes both invoice documents of type RE and other relevant journal entry types, such as migrated invoices (journal entry type UE - Data Transfer) that were cleared within the last 12 months, this is the correct behavior.

Besides Gross Invoice Posting documents (RE), there are some other journal entry types also relevant for the calculation of Days Payable Outstanding. Make sure to include all relevant invoice journal entry types in the calculation, for example KR and UE... limited to items cleared within the last 12 months (or an applicable period).

• Calculation Logic: Days Payable Outstanding | Help Portal
• Days Payable Outstanding - Detailed Analysis

dpo, days payable outstanding, last 12 months, migrated invoices, journal entry type ue, re, kr, manage supplier line items, clearing date, posting date, weighted average, ap analytics, discrepancy, calculation logic, s/4hana cloud , KBA , FI-FIO-AP-ANA-2CL , Accounts Payable Analytics: Public Cloud , Problem