Wiki source code of Monthly Member Maintenance Workflow
Version 40.1 by Megan Kahl on 2021/11/29 08:48
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
25.1 | 1 | (% style="text-align: center;" %) |
| 2 | = (% style="color:#2980b9; font-size:28px" %)**MONTHLY MEMBER MAINTENANCE WORKFLOW**(%%) = | ||
| |
2.1 | 3 | |
| 4 | |||
| 5 | |||
| |
25.1 | 6 | (% style="text-align: center;" %) |
| 7 | (% style="color:#2980b9" %)**BY** | ||
| |
2.1 | 8 | |
| 9 | |||
| 10 | |||
| |
25.1 | 11 | (% style="text-align:center" %) |
| 12 | [[image:Group Risk Monthly Member Mainentance WFL_html_8cba33b1e8c9fa24.gif||height="128" width="463"]] | ||
| |
2.1 | 13 | |
| |
25.1 | 14 | {{info}} |
| |
40.1 | 15 | (% style="break-before: page; text-align: center;" %) |
| |
25.1 | 16 | (% style="color:#2980b9; font-size:20px" %)**TABLE OF CONTENTS** |
| |
2.1 | 17 | |
| 18 | |||
| |
25.1 | 19 | {{toc/}} |
| |
2.1 | 20 | |
| |
25.1 | 21 | |
| 22 | {{/info}} | ||
| |
2.1 | 23 | |
| 24 | |||
| 25 | |||
| |
40.1 | 26 | (% style="break-before: page; text-align: center;" %) |
| |
25.1 | 27 | == (% style="color:#2980b9" %)**Introduction**(%%) == |
| |
2.1 | 28 | |
| 29 | |||
| 30 | The purpose of the workflow batch is to assist the user with a controlled month end policy status maintenance. During this process, the system will: | ||
| 31 | |||
| 32 | * Reinstate the policies that were lapsed during last month’s run due to outstanding premiums will be reactivated if the premiums are now received this month. | ||
| 33 | * Lapse the policies that no premiums have been received for as per defined business rules. | ||
| 34 | * Terminate policies that were lapsed and still no premiums have been received. | ||
| 35 | * Generate letters for the policies that are in arrears. | ||
| 36 | * Generate letters for the child-dependents who will, within the next 3 months, be over the eligibility age as specified in the rules. | ||
| 37 | |||
| 38 | This process will need to be run prior the collection file is sent for debit and stop order payments but must be run after the premiums have been received for all other cash payments. | ||
| 39 | |||
| 40 | |||
| 41 | |||
| |
40.1 | 42 | (% style="break-before: page; text-align: center;" %) |
| |
25.1 | 43 | == (% style="color:#2980b9" %)**Policy Maintenance Process**(%%) == |
| |
2.1 | 44 | |
| 45 | |||
| 46 | |||
| |
25.1 | 47 | To initiate the process, select the (% style="color:#2980b9" %)**‘Monthly Member Maintenance’**(%%) batch from the Batch Management screen. |
| |
2.1 | 48 | |
| 49 | |||
| |
39.1 | 50 | (% style="text-align:center" %) |
| 51 | [[image:1638175073928-276.png]] | ||
| |
2.1 | 52 | |
| 53 | |||
| |
39.1 | 54 | Double-click the (% style="color:#2980b9" %)**‘Edit’** (%%)hyperlink to open the Batch Editor screen. |
| |
2.1 | 55 | |
| 56 | |||
| |
40.1 | 57 | [[image:Group Risk Monthly Member Mainentance WFL_html_97b35bfea8cc4e2b.gif||alt="Shape1"]] |
| |
2.1 | 58 | |
| |
39.1 | 59 | (% style="text-align:center" %) |
| 60 | [[image:1638175088225-988.png]] | ||
| |
2.1 | 61 | |
| |
39.1 | 62 | |
| |
25.1 | 63 | The Batch Editor screen need to be captured as follows: |
| |
2.1 | 64 | |
| 65 | |||
| |
25.1 | 66 | (% style="color:#2980b9" %)**Client:**(%%)** **This field will default to the selected client. |
| |
2.1 | 67 | |
| |
25.1 | 68 | (% style="color:#2980b9" %)**Paypoint: **(%%)This is a Paypoint the process is run. Select applicable paypoint from the drop-down list. |
| |
2.1 | 69 | |
| |
25.1 | 70 | (% style="color:#2980b9" %)**Date 1: **(%%)This is the effective date the process is run on. |
| |
2.1 | 71 | |
| |
25.1 | 72 | (% style="color:#2980b9" %)**Batch Ref:**(%%)** **System generated and must not be edited / altered. |
| |
2.1 | 73 | |
| 74 | |||
| |
39.1 | 75 | Then(% style="color:#2980b9" %)** ‘Save’**(%%) and (% style="color:#2980b9" %)**‘Execute’**(%%) the batch to implement the increase. |
| |
2.1 | 76 | |
| 77 | |||
| |
39.1 | 78 | (% style="text-align:center" %) |
| 79 | [[image:1638175113275-709.png]] | ||
| |
2.1 | 80 | |
| |
39.1 | 81 | |
| |
25.1 | 82 | The (% style="color:#2980b9" %)**‘Monthly Member Maintenance’** (%%)workflow will be initiated and will be listed on the Workflow sub-window on the bottom left of the main Everest screen. |
| |
2.1 | 83 | |
| 84 | Double-click it to open the workflow screen. | ||
| 85 | |||
| 86 | |||
| |
39.1 | 87 | |
| |
2.1 | 88 | |
| |
39.1 | 89 | (% style="text-align:center" %) |
| 90 | [[image:1638175134073-739.png||height="448" width="429"]] | ||
| |
2.1 | 91 | |
| |
39.1 | 92 | |
| |
25.1 | 93 | Click on (% style="color:#2980b9" %)**‘Done’**(%%) on the next screen to proceed to the next step. |
| |
2.1 | 94 | |
| 95 | |||
| |
39.1 | 96 | [[image:Group Risk Monthly Member Mainentance WFL_html_b9ed8be2610c2a4d.gif||alt="Shape5"]] |
| |
2.1 | 97 | |
| |
39.1 | 98 | (% style="text-align:center" %) |
| 99 | [[image:1638175154466-237.png]] | ||
| |
2.1 | 100 | |
| |
39.1 | 101 | |
| |
2.1 | 102 | The next step will reinstate and terminate policies. Please read the instructions on the screen carefully. |
| 103 | |||
| |
25.1 | 104 | Click on (% style="color:#2980b9" %)**‘Done’**(%%) to process these. |
| |
2.1 | 105 | |
| 106 | |||
| |
39.1 | 107 | |
| |
2.1 | 108 | |
| |
39.1 | 109 | (% style="text-align:center" %) |
| 110 | [[image:1638175179077-289.png]] | ||
| |
2.1 | 111 | |
| |
39.1 | 112 | |
| |
25.1 | 113 | The reinstatement letter will be generated for all policies that are reinstated. These will need to checked for correctness and sent out to policyholders. |
| |
2.1 | 114 | |
| 115 | |||
| |
39.1 | 116 | (% style="text-align:center" %) |
| 117 | [[image:1638175193627-120.png]] | ||
| |
2.1 | 118 | |
| 119 | |||
| |
25.1 | 120 | The next step will lapse applicable policies. |
| |
2.1 | 121 | |
| |
39.1 | 122 | Click on(% style="color:#2980b9" %)** ‘Done’**(%%) to process these. |
| |
2.1 | 123 | |
| 124 | |||
| |
39.1 | 125 | |
| |
2.1 | 126 | |
| |
39.1 | 127 | (% style="text-align:center" %) |
| 128 | [[image:1638175209284-732.png]] | ||
| |
2.1 | 129 | |
| |
39.1 | 130 | |
| |
25.1 | 131 | The lapse letter for all applicable policies will generate. |
| |
2.1 | 132 | |
| 133 | |||
| |
39.1 | 134 | (% style="text-align:center" %) |
| 135 | [[image:1638175227506-779.png]] | ||
| |
2.1 | 136 | |
| 137 | |||
| |
25.1 | 138 | In the next step the system will identify all policies that are in arrears. |
| |
2.1 | 139 | |
| |
39.1 | 140 | Click on (% style="color:#2980b9" %)**‘Done’** (%%)to produce letters. |
| |
2.1 | 141 | |
| 142 | |||
| |
39.1 | 143 | |
| |
2.1 | 144 | |
| |
39.1 | 145 | (% style="text-align:center" %) |
| 146 | [[image:1638175339482-431.png]] | ||
| |
2.1 | 147 | |
| |
39.1 | 148 | |
| |
25.1 | 149 | A letter will be produced for all policies that are in arrears. |
| |
2.1 | 150 | |
| 151 | |||
| |
39.1 | 152 | (% style="text-align:center" %) |
| 153 | [[image:1638175363139-666.png]] | ||
| |
2.1 | 154 | |
| 155 | |||
| |
25.1 | 156 | In the next step the system will identify children dependents that are within 3 months of maximum eligibility age as setup in the rules. |
| |
2.1 | 157 | |
| |
39.1 | 158 | Click on (% style="color:#2980b9" %)**‘Done’**(%%) to produce letters. |
| |
2.1 | 159 | |
| 160 | |||
| |
39.1 | 161 | |
| |
2.1 | 162 | |
| |
39.1 | 163 | (% style="text-align:center" %) |
| 164 | [[image:1638175397453-878.png]] | ||
| |
2.1 | 165 | |
| |
39.1 | 166 | |
| |
25.1 | 167 | A letter will be produced for all identified child dependents. |
| |
2.1 | 168 | |
| 169 | |||
| |
39.1 | 170 | (% style="text-align:center" %) |
| 171 | [[image:1638175520700-236.png]] | ||
| |
2.1 | 172 | |
| 173 | |||
| |
25.1 | 174 | This will now be the last step of the workflow. Click on (% style="color:#2980b9" %)**‘Done’** (%%)to end the process. |
| |
2.1 | 175 | |
| 176 | |||
| 177 | |||
| |
40.1 | 178 | (% style="break-before: page; text-align: center;" %) |
| |
25.1 | 179 | == (% style="color:#2980b9" %)**Disclaimer and Copyright**(%%) == |
| |
2.1 | 180 | |
| 181 | |||
| |
25.1 | 182 | (% style="color:#2980b9" %)**DISCLAIMER** |
| |
2.1 | 183 | |
| |
25.1 | 184 | Please note, whilst care is taken to illustrate numerous scenarios, it is impossible to detail all instances and therefore this document should merely serve as a guide for the purposes of demonstrating system functionality and conducting employee training. |
| |
2.1 | 185 | |
| |
25.1 | 186 | In accordance with the above paragraph, this training manual is published and distributed on the basis that EBSphere (Pty) Ltd is not responsible/accountable for any actions taken by users of information contained in this training manual nor for any error in or omission from this manual. |
| |
2.1 | 187 | |
| |
25.1 | 188 | EBSphere (Pty) Ltd does not accept any responsibility whatsoever for a misrepresentation performed by any person in respect of claims, losses or damage or any other matter, either direct or consequential arising out of or in relation to the use and reliance, whether wholly or partially, upon any information contained or products referred to in this manual. |
| |
2.1 | 189 | |
| |
25.1 | 190 | Further, the contents of this training manual are subject to change without any notice and further highlight the need for this training manual to serve only as a guide. |
| |
2.1 | 191 | |
| 192 | |||
| 193 | |||
| |
25.1 | 194 | (% style="color:#2980b9" %)**COPYRIGHT** |
| |
2.1 | 195 | |
| |
25.1 | 196 | This documentation and the software described in it is the exclusive property of EBSphere (Pty) Ltd. This manual or the software may not be copied in whole or part, without the express written consent of EBSphere (Pty) Ltd. Under the law, copying includes translating into another language or format. |
| |
2.1 | 197 | |
| 198 | |||
| |
25.1 | 199 | EBSphere (Pty) Limited |
| |
2.1 | 200 | |
| |
25.1 | 201 | P.O. Box 785803 |
| |
2.1 | 202 | |
| |
25.1 | 203 | Sandton |
| |
2.1 | 204 | |
| |
25.1 | 205 | 2146 |
| |
2.1 | 206 | |
| 207 | |||
| 208 | |||
| |
25.1 | 209 | [[image:Group Risk Monthly Member Mainentance WFL_html_8cba33b1e8c9fa24.gif||height="128" width="463"]] |