The following points describe when match events are created for open-item accounts:
Match events are only created for open-item accounts (i.e., those accounts with an account type 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 FTs with the debit and credit FTs from bill segments and adjustments. The FTs that are linked to the match event are controlled by the payment's match type and match value (payments made by open-item taxpayers 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 taxpayers that pay automatically (i.e., direct debit taxpayers). 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.
Refer to Bill Lifecycle for more information about what happens during bill completion.
The system creates a match event when an obligation closes and the obligation has unmatched FTs. For example, consider an obligation for debt that is written off. This obligation closes when the system creates transfer adjustments to transfer the debt to a write-off obligation (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.
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 taxpayer 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.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.