updated post tf1 17.12.24

specification/appendix/refunds.md

@@ -5,6 +5,8 @@
 
 //applies where charge class is correction????
 
+REMINDER: need a headline on why REDUND is not a first class item... i..e. it is meant to be captured in usage and purchase make this clearer
+
 Refunds & late arriving costs are examples of....
  represent line items that appear in the FOCUS data set to support any scenarios where providers need to adjust a charge to a consumer. These scenarios include: 
 
@@ -85,6 +87,8 @@ Current values observed in billing data for various scenarios:
 
 ## Examples
 
+Show scenarios where correction happens within current billing periond and also where it applies to previous billing period.... highlight charge period differences and itemized vs not itemized... note in billing period segmentation 
+
 Within the FOCUS specification, the following examples demonstrate how a refund or credit appears across various usage scenarios.
 
 ### Bulk Refunds

specification/columns/chargeclass.md

@@ -19,6 +19,7 @@ Charge Class
 ## Description
 
 Indicates whether the row represents a correction to a previously invoiced *billing period*.
+OCI INDICATED: this restriction may need to be removed as corrections can happen in month... need to be aware of this to avoid historic reprocessing 
 
 ## Content Constraints