A.2.45 Mock Statement Maintenance
Generating a Mock Statement helps to mock the asset billing process with a future date and to get an upfront statement indicating future dues of Master and Associated Accounts. In Vacation Ownership industry, such statements are required to forecast future dues based on current Timeshare holdings.
In Servicing, the Mock Statement preferences displayed in Customer Service > Account Details tab and Contract Information tab are propagated from Origination > Contract screen and are displayed in View mode.
You can update the Mock Statement generation preferences at Master Account level by posting MOCK STATEMENT MAINTENANCE TRANSACTION FOR MASTER ACCOUNTnon-monetary transaction in Customer Service > Maintenance > Transaction Batch Information section.
This transaction can be posted only from Master Account. In case this transaction is used to deselect the option Mock Statement Req to No, system refreshes the other fields making them Null and Read-Only.
Table A-146 To Post Mock Statement Maintenance to Master Account
| Transaction | Parameters |
|---|---|
| MOCK STATEMENT MAINTENANCE TRANSACTION FOR MASTER ACCOUNT |
TXN DATE Select the transaction posting date from adjoining calendar. |
|
MOCK STATEMENT REQUIRED IND Select this check box to indicate if the account is to be included in Mock statement Generation. |
|
|
MOCK STATEMENT DATE Select the start month of Mock Statements period using the adjoining calendar. |
|
|
MOCK CYCLES Select the total number of billings (between 1-12) that are to be generated post Mock Statement Start Date. |
|
|
MOCK PRE BILL DAYS Specify the number of Pre bill days for Mock Statements generation. |
While generating Mock Statement, system considers the Mock Statement Date and Pre Bill Days to generate the next Mock Statement Run Date. In case the Mock Statement Next Run Date is less than Contract Date or GL Date which does not match the criteria, system moves the Mock Start Date to same month of next year.
For example,
If Contract date = 6/1/2018
First Payment Date = 7/1/2018
Mock Start Month = July
Mock Start Date = 7/1/2018 (Derived based on Start Month)
Mock Pre Statement days = 60
Mock Statement Run Date Next = 7/1/2018 - 60 days = 5/2/2018 which is Less than Contract Date.
Here the Mock Statement Start Date is moved to 7/1/2019 so that Mock Statement Run Date Next = 7/1/2019 - 60 days = 5/2/2019
On successfully posting the transaction, a confirmation message is displayed in the Results section indicating the Transaction Processing Details and when the transaction Posting occurs.
The batch job TXNMDT_BJ_100_01 (MOCK BILLING/DUE DATES PROCESSING) available in SET-TPE batch job set generates the future dues/balances based on the parameters defined in the criteria. This batch job is a prerequisite run for the mock statements to get generated.
The batch job OMSPRC_BJ_100_01 (MASTER ACCOUNT CUSTOMER MOCK STATEMENT GENERATION) available in SET-ODD2 batch job set generates Mock Statements based on Mock Statement Details.
While processing, the batch job picks only those accounts with Mock Statement Req = Y and Master Account Flag = Y. This batch job is run on Mock Statement Run Date Next and generates the number of dues based on Mock Statement Cycles.
The structure of the Mock Statement generated is controlled based on Record and Column definitions maintained in the data file MASTER_ACCOUNT_MOCK_STATEMENT (MASTER ACCOUNT CUSTOMER MOCK STATEMENT) defined in Setup > Administration > System> Data Files screen’s Output tab.
Parent topic: Nonmonetary Transactions