When Are Match Events Created?

The following points describe when match events are created for open-item accounts:

Note:

Match events are only created for open-item accounts (i.e., those accounts with a customer class that indicates open-item accounting is practiced). Match events may not be created for balance-forward accounts.

  • The system can create one or many match events when a payment is added. This match event matches the payment's credit FT's with the debit and credit FT's from bill segments and adjustments. The FT's that are linked to the match event are controlled by the payment's match type and match value (payments made by open-item customers must reference a match type and match value). Refer to Payments And Match Events for more information.
  • The system may create a match event when any type of financial transaction is cancelled. This match event groups together the original FT with its cancellation FT. Refer to How Are Match Events Cancelled? for more information.
  • The system creates a match event when a bill is completed for customers that pay automatically (i.e., direct debit customers). The match event groups together the bill's new charges against the automatic payment's payment segments.
  • The system creates a match event when a bill is completed where the new charges are offset by other financial transactions. For example,
    • Consider a bill that contains a deposit refund. If the sum of the deposit refund equals or exceeds the amount of the bill, the bill's FT's can be matched against the debit refunds FT's. Refer to Refunding Deposits for more information about deposit refunds.
    • Consider a bill whose new charges are offset by a previous overpayment. Refer to Over Payments for more information about overpayments.
Fastpath:

Refer to Bill Lifecycle for more information about what happens during bill completion.

  • The system creates a match event when a service agreement closes and the service agreement has unmatched FT's. For example,
    • Consider a deposit service agreement that closes when the deposit is refunded to the customer. The system will create a match event with the deposit SA's FT's (the original credit and the debits used to refund the deposit) when the deposit SA closes (i.e., when its credit balance falls to zero). Refer to Refunding Deposits for more information about deposit refunds.
    • Consider a service agreement for utility debt that is written off. This service agreement closes when the system creates transfer adjustments to transfer the utility debt to a write-off service agreement (or writes down the debt). The system creates a match event to match the original debt to the transfer adjustments used to write-off the debt. Refer to How Is Debt Financially Written Off for more information about write-off processing.
  • A user can create a match event manually at any time. Manual match events would be created under a variety of situations. For example:
    • If a customer disputes a charge. Refer to Disputing Items for more information about disputes.
    • To handle unusual situations when the system is unable to automatically match FT's together.