FR #962: Adding Correction Handling and Delivery Handling attributes #1501
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nch 'origin/working_draft' into 962-correction-handling-attribute
…m/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec into 962-correction-handling-attribute # Conflicts: # specification/attributes/correction_handling.md
…nch 'origin/working_draft' into 962-correction-handling-attribute
shawnalpay
commented
Oct 5, 2025
Co-authored-by: Irena Jurica <[email protected]>
Co-authored-by: Irena Jurica <[email protected]>
shawnalpay
commented
Oct 5, 2025
shawnalpay
commented
Oct 5, 2025
shawnalpay
commented
Oct 6, 2025
| * Invoice issuer MUST perform *Invoice reconciliation* between an *invoice* and its associated FOCUS *dataset artifacts* before issuing the invoice. | ||
| * *Invoice reconciliation* process MUST include (but is not limited to) the following metric and dimensions: BilledCost, BillingCurrency, InvoiceId, InvoiceIssuerName, BillingAccountId, BillingPeriodStart, and BillingPeriodEnd. | ||
| * Invoice issuer MUST document which FOCUS dataset columns are included in the *invoice reconciliation* process. | ||
| * The data generator MUST notify the customer if the contents of a *dataset artifact* associated with an *issued invoice* are altered after final delivery. |
Contributor
Author
There was a problem hiding this comment.
Per @ijurica: after final delivery of what?
26 tasks
Contributor
Author
|
We had a good discussion about this PR in Oct 6 Maintainers. While there is possibly a path forward with some subset of the content here, we decided that it would be best to defer this work until we can tackle the creation of an Invoice dataset per FR #1500, which would then unlock the authorship of more concrete, enforceable normative requirements for corrections that pertain to the invoice lifecycle. Lots of the verbiage in this PR is correct and useable in the future, but we will wait until #1500 is done to keep moving on this. Closing this PR for now. |
…on-handling-attribute-shawn-refactor # Conflicts: # specification/attributes/invoice_handling.md # specification/datasets/cost_and_usage/dataset.md # specification/glossary.md
…draft' into 962-correction-handling-attribute-shawn-refactor
…draft' into 962-correction-handling-attribute-shawn-refactor
…draft' into 962-correction-handling-attribute-shawn-refactor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a fork of the branch from PR #1368 and makes the following changes:
It also makes some editorial changes vis a vis changing the term invoiced to closed.