2.2.4 Assumptions, Validations and Comments

This topic provides the information about the assumptions, validations and comments.

1. If any of the mandatory field input is not provided, the system validates the input.
2. If the user selects any fee other than 'Fee Periodic Maintenance Fee' category, system does not allow posting the transaction and raise an error → only Fee category Fee Periodic Maintenance Fee only allowed to post.
3. The system considers the account billing frequency as the periodic maintenance fee frequency.
4. System inserts record with Enabled flag = Y.
5. This transaction date is effective from the date of posting, referring to the next billing cycle date of the account. Backdating or reversal of transactions is not in scope of the current development.
6. This transaction will not do any catchup of back dated fee and users are expected to handle operationally.
7. On successful posting of the transaction, the system does the following actions:
   1. If the fee balance selected for posting of fee is not loaded on the account, the system raises an error → Selected balance does not exist on account. (Here user is expected to post 'ADD_NEW_ACCOUNT_BALANCE' transaction to add any missing balances to account operationally.
   2. System defines the recurring fee for the selected fee and existing behavior of the periodic maintenance fee will prevail.
   3. Applicability of fee (selection criteria) of the transaction will take reference from the account for the values Company, Branch, Channel, Product, State, and Currency.
8. The effective date of fee calculation is driven by the next billing date of the account.

Table 2-19 Transaction 1: ACC_START_PMF_MAINT

Transaction Code	Description	Group	Action	Monetary	System defined	Enabled	Transaction / Balance Type
ACC_START_PMF_MAINT	START PERIODIC MAINTENANCE	NON MONETARY	POST	N	Y	Y	NONE

If the fee balance selected for posting of the transaction is already configured for recurring fee posting, on posting of this transaction, the system will do the following actions:

1. Set the RUN_DATE NEXT as DT MAX.
2. Set the record enabled flag = N.

Table 2-20 Parameter Code

Parameter Code	Default	Sort	Displayed	Required	Comment
Transaction Date	System Date	1	Y	Y
PMF TYPE Code		2	Y	Y	Refer Fee Type lookup filtered with only Fee Periodic Maintenance Fee.

If the fee balance selected for posting of the transaction is already configured for recurring fee posting, on posting of this transaction, the system will do the following actions.

1. Set the RUN_DATE NEXT as DT MAX.
2. Set the record enabled flag = N.

Table 2-21 Transaction 2: ACC_STOP_PMF_MAINT

Transaction Code	Description	Group	Action	Monetary	System defined	Enabled	Transaction / Balance Type
ACC_STOP_PMF_MAINT	STOP PERIODIC MAINTENANCE FEE	NON MONETARY	POST	N	Y	Y	NONE

If the fee balance selected for posting of the transaction is already configured for recurring fee posting, on posting of this transaction, the system will perform the following actions:

1. Set the RUN_DATE NEXT as the NEXT BILL DATE.
2. Set the record enabled flag = Y.
3. If the user initially stops the periodic fee posting and subsequently posts the transaction again to re-post, the system will set the next run date as the next billing cycle date and will not catch up any past fee.

Table 2-22 Parameter Code

Parameter Code	Default	Sort	Displayed	Required	Comment
Transaction Date	System Date	1	Y	Y
PMF TYPE Code		2	Y	Y	Refer Fee Type lookup filtered with only Fee Periodic Maintenance Fee.

1. If the fee balance selected for posting of the transaction is already configured for recurring fee posting, on posting of this transaction, the system will do the following actions:
   1. Set the RUN_DATE NEXT as the NEXT BILL DATE.
   2. Set the record enabled flag = Y.
2. If the user initially stops the periodic fee posting and subsequently posts the transaction again to re-post, the system will set the next run date as the next billing cycle date and will not catch up any past fee.