Overview:

In automated fee/fine notices, IF 2nd decimal  = 0 (e.g. 25.9*0*), THEN it gets droped in the amount tokens (i.e. shows as: 25.9).
This does NOT happen if 2nd decimal ≠ 0 (e.g. 25.9*9*); in this case, the 2nd decimal is shown (i.e. 25.99). 

Affected notice categories:
_ Automated fee/fine charge
_ Automated fee/fine action (refund or cancel)

These categories are NOT affected (even though they use the same tokens):
_ Manual fee/fine charge
_ Manual fee/fine action (pay, waive, refund, transfer or cancel/error)

Affected tokens: 
_ feeCharge.amount
_ feeCharge.remainingAmount

Steps to Reproduce:

1. Log into Lotus

2. To get an automated notice with all amount tokens, send yourself a notice with trigger event = Lost item returned - fee(s) adjusted (see here: https://folio-org.atlassian.net/wiki/display/FOLIOtips/C%29+How+to+generate+a+loan...+that+ages+to+lost)
   NB: But any automated fee/fine notice works.

Expected Results:

If amount in Lost item fee policy = 25.90, then the amount shown = 25.90.

Actual Results:

The amount shown = 25.9 .

Additional Information:
_ P4, because: Technically, the information is not wrong. It's rather that: Because the 2nd decimal is shown in the manual fee/fine notices, even if it's 0, the tester then assumed that the missing 2nd decimal meant that there was something wrong with showing the token content. This just causes unnecessary questioning. 

_ I could replicate in Snapshot. Cannot check in https://folio-kiwi.dev.folio.org/ because emails are turned off.