Payment Application and Unapplication Event Scenarios Guide
This article lists payment application and unapplication scenarios and the events that are triggered by them. Each scenario describes a common workflow from an Aria system perspective.
| Scenario | Events |
|---|---|
|
Event 952 should be fired on step 2 |
|
Event 952 should be fired on step 2 |
|
Event 952 is generated on step 2 Event 953 is created on step 3 because the payment should be unapplied as part of credit memo application Event 952 is generated on step 4 because the unapplied balance from the payment created on step 2 gets applied to the new invoice |
|
Event 952 is generated on step 2 Event 953 is generated on step 3 because payment will be unapplied from the invoice as it gets voided |
|
Event 952 is generated on step 2 Event 953 is generated on step 3 Event 952 is generated on step 4 as the payment is applied to the refund transaction? |
|
Event 952 is generated on step 2 Event 953 is generated on step 3 Event 952 is generated on step 4 Event 953 is generated on step 5 |
|
Event 956 should be fired on step 2 |
|
Event 956 should be fired on step 2 |
|
Event 956 is generated on step 2 Event 957 is created on step 3 because the cash credit should be unapplied as part of credit memo application Event 956 is generated on step 4 because the unapplied balance from the cash credit created on step 2 gets applied to the new invoice |
|
Event 956 is generated on step 2 Event 957 is generated on step 3 because cash credit will be unapplied from the invoice as it gets voided |