anchor.diff:  
   [source,json]
   ---
  -{ "blockChanges": true,
  -"clearState": false,
  -"daysBetweenPaymentRetries": 1,
  -"disableEntitlementAndChangesBlocked": false,
  -"externalMessage": "Reached WARNING",
  -"name": "WARNING",
  -"reevaluationIntervalDays": 4 }
  +{
  +  "blockChanges": true,
  +  "clearState": false,
  +  "daysBetweenPaymentRetries": 1,
  +  "disableEntitlementAndChangesBlocked": false,
  +  "externalMessage": "Reached WARNING",
  +  "name": "WARNING",
  +  "reevaluationIntervalDays": 4
  +}
   ---
   
   If the `disableEntitlementAndChangesBlocked` is set to true, it means that the customer is not entitled to the service associated to any subscriptions.
  
positive.code: 
  The overdue configuration will define the three states the account will go through:
  
  1. The account will enter the WARNING state 10 days after the first unpaid invoice
  2. 4 days later, the account will move to the BLOCKED state
  3. 7 days later, the account will move to the CANCELLATION state
  
  
negative.code: [[customers]]
  == Example of Customers
  
  Let's take the case of a customer who subscribed to the service. Immediately after the subscription was created, a $0 invoice is created to indicate the customer is in TRIAL. Let's assume his credit card does not have enough funds. 10 days later, the customer moves out of TRIAL and the system generates a $10 invoice for the month. At this point, the system attempts to make a payment, but the payment does not go through:
  
  * Day 1: the system will retry the payment one day later and fail again
  * Day 2: the system will retry the payment one day later and fail again
  