Open kk09v opened 1 day ago
@kk09v Thank you for standing up this work item, Karl! Could you add at least one use case in the format of our use-case library? Also, data examples will be very helpful in telling this story -- could you add at least one example of how the data looks from one of the existing CSP exports?
Problem Statement
The "Procure to Pay" process (P2P) is pretty well defined:
Also see EDI (Electronic Data Interchange) the set of standards which include how data will be exchanged for this process as it relates to physical goods.
With Public Cloud, the Procure to Pay process still exists, but it is much less mature than in other industries. Cloud Service Provider invoices do not typically contain a complete list of all goods and services purchased; it is often summarized and usually refers to the the CSP's cost and usage data export process (including FOCUS, if available).
Inclusion of the invoice # in the FOCUS data will allow teams to positively identify which charges, credits, adjustments, etc. are applied to each invoice and improve the 3-way match process.
Use cases:
Verify accuracy of provider invoices
Perform showback / chargeback activities
Analyze credit memos
Objective
Success Criteria: A practitioner should be able to tie out their invoice from a CSP (to the penny or lowest denomination of billing currency) to the sum of BilledCost having the corresponding InvoiceId (presumptive column name) in their FOCUS dataset from that CSP.
Supporting Documentation
Discussion Documents: Proposal from 1.0 https://github.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/issues/302 Duplicate issue created in Oct 2024 #607
Proposed Solution / Approach
Epic or Theme Association
TBD
Stakeholders
Primary Stakeholder: TBD
Other Parties Involved: