Financial Transactions And Aged Debt

When a financial transaction's related bill segment / payment segment / adjustment is frozen, the financial transaction (FT) is also frozen. When an FT is frozen, its service agreement's debt is impacted. It is important to stress the following in respect of this impact:

  • The FT's GL details will be interfaced to the GL when the GL interface next executes.
  • If the FT decreases the amount of debt, the customer's aged debt is affected immediately regardless of whether the FT appears on a bill.
  • If the FT increases the amount of debt, the amount the customer owes from an aged debt perspective may or may not be affected by the FT. There is a switch on an FT called New Charge that controls the arrears behavior. If this switch is on, the customer's aged debt will not reflect the FT amount until the FT is swept onto a bill. The moment the FT is swept onto the customer's bill, the debt starts aging. If this switch is off, the date on which the FT starts aging must be defined in the Arrears Date field.
  • The amount a customer owes in total is immediately affected by the FT regardless of whether the FT appears on a bill. This means that the amount of aged debt may not be in sync with the total amount owed. This seems odd, but is useful from a credit and collections perspective. You see, you probably don't want to start aging a FT until the customer has actually seen it.
Fastpath:

For more information, refer to Financial Transactions Created Between Bills.