anchor.diff:  <disableEntitlementAndChangesBlocked>
   true
   </disableEntitlementAndChangesBlocked>
  -|autoReevaluationInterval   |Tag within `state`   |Specifies the duration after which the overdue state should be reevaluated. The duration needs to be specified with a `unit` (one of `DAYS`, `WEEKS`, `MONTHS`, `YEARS`, `UNLIMITED`) and an integer value |  [source, xml]
  +|autoReevaluationInterval   |Tag within `state`   |Specifies the duration after which the overdue state should be reevaluated. The duration needs to be specified with a `unit` (one of `DAYS`, `WEEKS`, `MONTHS`, `YEARS`, `UNLIMITED`) and an integer value. |  [source, xml]
                   <autoReevaluationInterval>
                    <unit>DAYS</unit>
                    <number>4</number>
  
positive.code: 
  === Overdue Conditions
  
  The following table lists the various overdue conditions. Note that it is also possible to combine multiple conditions in which case all the specified conditions need to evaluate to true for the account to enter the particular overdue state.
  
  [cols="a,a,a"]
  |===
  
negative.code: |name   |Attribute on `state` tag   |Name given to the state | 
  [source, xml]
  <state name="WARNING">  
  |condition     |Tag within `state` |Specifies the condition to be evaluated. The account will enter this overdue state only if the condition evaluates to true.  | See <<Overdue Conditions>>
  |externalMessage   |Tag within `state`    |Optional message which can be retrieved by plugins listening to overdue events, and displayed to the user. Any String value can be specified  |
  [source, xml]
  <externalMessage>
  