anchor.diff:  |`FLOAT64`
   |
   
  -|===
  -
  -The last possible setting for the `decimal.handling.mode` configuration property is `string`. In this case, the connector represents `DECIMAL` and `NUMERIC` values as their formatted string representation, and encodes them as shown in the following table.
  +|`MONEY[(M[,D])]`
  +|`FLOAT64`
  +|
  +
  +|===
  +
  +The last possible setting for the `decimal.handling.mode` configuration property is `string`. In this case, the connector represents `DECIMAL`, `NUMERIC` and `MONEY` values as their formatted string representation, and encodes them as shown in the following table.
   
   .Mappings when `decimal.handling.mode` is `string`
   [cols="30%a,30%a,40%a",options="header"]
  
positive.code:  +
  The `scale` schema parameter contains an integer representing how many digits the decimal point was shifted.
  
  |===
  
  There is an exception to this rule.
  When the `NUMERIC` or `DECIMAL` types are used without scale constraints, the values coming from the database have a different (variable) scale for each value. In this case, the connector uses `io.debezium.data.VariableScaleDecimal`, which contains both the value and the scale of the transferred value.
  
  .Mappings of decimal types when there are no scale constraints
  [cols="25%a,20%a,55%a",options="header"]
  |===
  |PostgreSQL data type
  
negative.code: |
  
  |`DECIMAL[(M[,D])]`
  |`STRING`
  |
  
  |`MONEY[(M[,D])]`
  |`STRING`
  |
  
  