Section 14 transfer

Once these questions have been answered, the appropriate process can be followed. The user must ensure that the correct finalised Section 14 documentation has been received prior to commencing on Everest.

40

41

42

43

(% style="break-before: page; text-align: center;" %)

44

= (% style="color:#2980b9" %)**Section 14 Process for an Individual Member**(%%) =

== (% style="color:#2980b9" %)**Section 14 where the member is invested in a Managed Fund**(%%) ==

49

50

Generate a Member Statement and ensure that all transactions have been completed and priced. Exit the member using the standard Member Exit Batch. Ensure that the workflow process is completed in full. The Disinvestment Process, which is part of the workflow MUST be done to ensure that the investable portion is moved to Bank for payment. Tax must be applied for on all Section 14 Transfers, in line with SARS’ rules. Payment is then made to the receiving Fund.

51

52

53

== (% style="color:#2980b9" %)**Section 14 where the member is invested in a Unitized Fund**(%%) ==

54

55

Generate a Member Statement and ensure that all transactions have been completed and priced. Exit the member using the standard Member Exit Batch. Ensure that the workflow process is completed in full. The Disinvestment Process, which is part of the workflow MUST be done to ensure that the investable portion is moved to Bank for payment. Execute the transaction in Market and ensure that the transaction is priced before continuing. Tax must be applied for on all Section 14 Transfers, in line with SARS’ rules. Payment is then made to the receiving Fund.

(% style="break-before: page; text-align: center;" %)

60

= (% style="color:#2980b9" %)**Bulk Section 14 Process**(%%) =

== (% style="color:#2980b9" %)**Bulk Section 14 where the member is invested in a Managed Fund**(%%) ==

65

66

* Generate a few Member Statements and ensure that all transactions have been completed and priced. Check that there are no Outstanding Contributions.

67

* that the banking details of the receiving Fund has been loaded in the (% style="color:#2980b9" %)Administration > Financial Settings > System Bank Accounts > Transfer Funds (Bank Account Type)(%%) screen. Should the user not have access to this screen ensure that someone who does have access loads the banking details before commencing the process.

68

69

Select and generate the(% style="color:#2980b9" %) “**Client Member Investment Product”** (%%)batch.

70

71

(% style="color:#2980b9" %)**Effective Date:**(%%)** **Today’s date.

72

73

Click on (% style="color:#2980b9" %)“**Save**” (%%)and (% style="color:#2980b9" %)“**Execute**”.

74

75

76

(% style="text-align:center" %)

77

[[image:1633327074202-714.png||data-xwiki-image-style-alignment="center"]]

78

79

(% style="break-before: page" %)

80

A report will generate reflecting the member’s current Fund Credit.

81

82

83

(% style="text-align:center" %)

84

[[image:1633327282743-140.png||data-xwiki-image-style-alignment="center"]]

85

86

87

Using the (% style="color:#2980b9" %)**Import Unclaimed Benefit Template**(%%), create a file for import. This template will process the member’s exits in Bulk and write up the payment to be paid into the transferring Fund.

88

89

90

(% style="text-align:center" %)

91

[[image:1633327441733-379.png||data-xwiki-image-style-alignment="center"]]

92

93

94

Critical fields that must be considered are:

95

96

(% style="color:#2980b9" %)**System Number **(%%) This is the unique Everest generated number.

97

98

(% style="color:#2980b9" %)**Exit Type**(%%) The Exit type is depicted as a number that must be copied from the Key to ensure that the correct exit type is used.

99

100

(% style="color:#2980b9" %)**ID Number**(%%) Member’s Identity number.

101

102

(% style="color:#2980b9" %)**Tax Ref No**(%%) Member’s tax reference number.

103

104

(% style="color:#2980b9" %)**DOX **(%%) Date of exit, this is the Section 14 date.

105

106

(% style="color:#2980b9" %)**Gross Benefit **(%%) This is the Rand Amount of the member’s benefit to be transferred, if its not 100% of the members benefit. Leave blank if the full benefit is to be transferred

107

108

(% style="color:#2980b9" %)**Tax Upload Group**(%%) Set a tax group name, for example 22042020 (date of tax application)

109

110

(% style="color:#2980b9" %)**Effective Date **(%%) This is the Section 14 Date.

111

112

(% style="color:#2980b9" %)**Transfer **(%%) Always set this to Y

113

114

(% style="color:#2980b9" %)**Transfer Fund Type**(%%) This is the transfer fund type of the receiving Fund. This needs to match the System Bank Accounts screen exactly.

115

116

(% style="color:#2980b9" %)**Transfer Fund Name**(%%) This is the name of the receiving Fund. This needs to match the System Bank Accounts screen exactly.

117

118

(% style="color:#2980b9" %)**FSB Transfer Fund No **(%%) This is the FSB number of the receiving fund and must match the System bank account screen exactly.

119

120

(% style="color:#2980b9" %)**Transfer Participating Employer **(%%) This is only required if the last 6 digits of the FSB Transfer number(% style="color:#2980b9" %)** **(%%)does not end in zeros (0)

121

122

123

Once the file has been updated, save the file for import into the system.

124

125

Select and generate the (% style="color:#2980b9" %)“**Import Unclaimed Benefits**”(%%) batch.

126

127

128

(% style="text-align:center" %)

129

[[image:1633327705654-665.png||data-xwiki-image-style-alignment="center"]]

130

131

132

(% style="color:#2980b9" %)**Client **(%%) This is the Client for which the Section 14 is being processed.

133

134

(% style="color:#2980b9" %)**File Name**(%%) Click on the (% style="color:#2980b9" %)“**Browse**” (%%)button and locate the saved file.

135

136

(% style="color:#2980b9" %)**Batch Reference**(%%) This is defaulted by the system.

137

138

(% style="color:#2980b9" %)**Client Parent **(%%) This is the Parent that the client belongs to.

139

140

141

Click on the (% style="color:#2980b9" %)“**Save**”(%%) and (% style="color:#2980b9" %)“**Execute**” (%%)button.

142

143

Two reports will generate. The first being confirmation of the fields that were required and what was supplied to generate the report.

144

145

146

The second report will confirm if the import was successful or not. If the import was not successful, the errors will need to be rectified before the import is run again. The(% style="color:#e74c3c" %) batch ref number(%%) of the successful import, as highlighted below, (% style="color:#2980b9" %)**must**(%%)** **be kept as it will be used later in the process.

147

148

149

(% style="text-align:center" %)

150

[[image:1633327962522-699.png||data-xwiki-image-style-alignment="center"]]

151

152

153

The tax information will be populated with the transfer details contained in the file and under System Bank Accounts. The tax application will need to be submitted to SARS and a response is required before processing with payment.

154

155

The member records now appear in (% style="color:#e74c3c" %)RED(%%) with an exit date and an exit type.

156

157

(% style="text-align:center" %)

158

[[image:1633328086509-533.png||data-xwiki-image-style-alignment="center"]]

159

160

Once the tax response is received, the (% style="color:#2980b9" %)**“Import Unclaimed Benefits – Creditor Payment” **(%%)batch needs to be run.

161

162

163

Insert the (% style="color:#e74c3c" %)Batch Number(%%) from your first import, that was done previously, into this Batch Ref field.

164

165

The Administrator Bank field is the name of the creditor being paid that has been set up under System Bank Accounts (Transfer Funds).

166

167

168

A report will generate confirming which benefits have been populated for payment. Only benefits where tax has been received back will be populated. The report will clearly highlight which members are ready for payment and which are not.

169

170

171

(% style="text-align:center" %)

172

[[image:1633328312880-362.png||data-xwiki-image-style-alignment="center"]]

173

174

175

Click on the (% style="color:#2980b9" %)__**cflo**__(%%) button on the member record. A line would have been created for payment.

176

177

178

(% style="text-align:center" %)

179

[[image:1633328484167-380.png||data-xwiki-image-style-alignment="center"]]

180

181

182

The payment can now be made in Bulk at the Parent Level.

183

184

Go to (% style="color:#2980b9" %)Accounts > Debtors and Creditors Menu (%%)item.

185

186

Select (% style="color:#2980b9" %)“**Creditors**”(%%). A creditor payment reflects in the Creditor Payment.

187

188

189

(% style="text-align:center" %)

190

[[image:1633328582529-671.png||data-xwiki-image-style-alignment="center" height="189" width="466"]]

191

192

193

(% style="text-align:center" %)

194

[[image:1633328678458-232.png||data-xwiki-image-style-alignment="center"]]

195

196

197

Select (% style="color:#2980b9" %)**__eft__ **(%%)hyperlink and a batch editor screen will open to generate the Payment.

(% style="text-align:center" %)

202

[[image:1633328773306-793.png||data-xwiki-image-style-alignment="center"]]

203

204

205

The payment can be approved on the Payment Management screen as a bulk payment. The process has been completed and the necessary payment records have been created.

206

207

208

(% style="break-before: page" %)

209

== (% style="color:#2980b9" %)**Bulk Section 14 where the member is invested in a Unitised Fund**(%%) ==

210

211

1. Generate a few Member Statements and ensure that all transactions have been completed and priced. Also ensure there are no Outstanding Contributions.

212

1. Ensure that the banking details of the receiving Fund has been loaded in the (% style="color:#2980b9" %)Administration > Financial Settings > System Bank Accounts > Transfer Funds (Bank Account Type)(%%) screen. Should the user not have access to this screen ensure that some who does have access loads the banking details.

213

214

Ensure that the client has been selected.

215

216

Go to the (% style="color:#2980b9" %)Accounts > Investment Switch Menu(%%) option and create the switch, moving 100% of the member’s Fund Credit into the bank account.

217

218

219

(% style="text-align:center" %)

220

[[image:1633328856464-285.png||data-xwiki-image-style-alignment="center"]]

221

222

223

The system has the option to import the member switch as well. Should only a select number of members be transferring out, the preferred option would be to complete the (% style="color:#2980b9" %)**“Investment Switches Import”** (%%)template and import the members for switching.

224

225

226

(% style="text-align:center" %)

227

[[image:1633328913530-279.png||data-xwiki-image-style-alignment="center"]]

228

229

230

Please refer to the (% style="color:#2980b9" %)**Investment Switches**(%%) guide for the full process to be followed.

231

232

233

Once the switch has been generated (as per the Investment Switches guide), go to (% style="color:#2980b9" %)Accounts > Cashflow Unit Prices (%%)screen at a Parent level to obtain the number of units that must be disinvested from the market.

234

235

236

(% style="text-align:center" %)

237

[[image:1633328986406-762.png||data-xwiki-image-style-alignment="center"]]

238

239

Only once the disinvestment process has been finalised in full can the user continue with the process.

240

241

242

(% style="break-before: page" %)

243

Select and generate the(% style="color:#2980b9" %) “**Client Member Investment Product**”(%%) batch, once the disinvestment has been actioned and priced.

244

245

(% style="color:#2980b9" %)**Effective Date:**(%%) Today’s date.

246

247

Click on (% style="color:#2980b9" %)“**Save**”(%%) and (% style="color:#2980b9" %)“**Execute**”.

248

249

250

(% style="text-align:center" %)

251

[[image:1633330252894-988.png||data-xwiki-image-style-alignment="center"]]

252

253

254

A report will generate reflecting the member’s current Fund Credit.

255

256

257

(% style="text-align:center" %)

258

[[image:1633330357571-100.png||data-xwiki-image-style-alignment="center"]]

259

260

261

Using the (% style="color:#2980b9" %)**Import Unclaimed Benefit Template, **(%%)create a file for import.

262

263

This template will process the member’s exits in Bulk and write up the payment to be paid into the transferring Fund.

(% style="text-align:center" %)

268

[[image:1633327441733-379.png||data-xwiki-image-style-alignment="center"]]

269

270

(% style="break-before: page" %)

271

Critical fields that must be considered are:

272

273

274

(% style="color:#2980b9" %)**System Number **(%%) This is the unique Everest generated number.

275

276

(% style="color:#2980b9" %)**Exit Type **(%%) The Exit type is depicted as a number that must be copied from the Key to ensure that the correct exit type is used.

277

278

(% style="color:#2980b9" %)**ID Number **(%%) Members Identity number.

279

280

(% style="color:#2980b9" %)**Tax Ref No **(%%) Members tax reference number.

281

282

(% style="color:#2980b9" %)**DOX **(%%) Date of exit, this is the Section 14 date.

283

284

(% style="color:#2980b9" %)**Gross Benefit **(%%) This is the Rand Amount of the member’s benefit to be transferred, if its not 100% of the members benefit. Leave blank if the full benefit is to be transferred

285

286

(% style="color:#2980b9" %)**Tax Upload Group **(%%) Set a tax group name, for example 22042020 (date of tax application)

287

288

(% style="color:#2980b9" %)**Effective Date **(%%) This is the Section 14 Date.

289

290

(% style="color:#2980b9" %)**Transfer **(%%) Always set this to Y

291

292

(% style="color:#2980b9" %)**Transfer Fund Type **(%%) This is the transfer fund type of the receiving Fund. This needs to match the System Bank Accounts screen exactly.

293

294

(% style="color:#2980b9" %)**Transfer Fund Name**(%%) This is the name of the receiving Fund. This needs to match the System Bank Accounts screen exactly.

295

296

(% style="color:#2980b9" %)**FSB Transfer Fund No**(%%) This is the FSB number of the receiving fund and must match the System bank account screen exactly.

297

298

(% style="color:#2980b9" %)**Transfer Participating Employer **(%%) This is only required if the last 6 digits of the FSB Transfer number(% style="color:#2980b9" %)** **(%%)does not end in zeros (0)

299

300

301

Once the file has been updated, save the file for import into the system.

302

303

(% style="break-before: page" %)

304

Select and generate the (% style="color:#2980b9" %)“**Import Unclaimed Benefits**”(%%) batch.

305

306

307

(% style="text-align:center" %)

308

[[image:1633327705654-665.png||data-xwiki-image-style-alignment="center"]]

309

310

311

(% style="color:#2980b9" %)**Client **(%%) This is the Client for which the Section 14 is being processed.

312

313

(% style="color:#2980b9" %)**File Name**(%%) Click on the (% style="color:#2980b9" %)“**Browse**” (%%)button and locate the saved file.

314

315

(% style="color:#2980b9" %)**Batch Reference**(%%) This is defaulted by the system.

316

317

(% style="color:#2980b9" %)**Client Parent **(%%) This is the Parent that the client belongs to.

318

319

320

Click on the (% style="color:#2980b9" %)“**Save**”(%%) and (% style="color:#2980b9" %)“**Execute**”(%%) button.

321

322

Two reports will generate. The first being confirmation of the fields that were required and what was supplied to generate the report.

323

324

325

The second report will confirm if the import was successful or not. If the import was not successful, the errors will need to be rectified before the import is run again. The (% style="color:#e74c3c" %)Batch Ref number(%%) of the successful import, as highlighted below, (% style="color:#2980b9" %)**must**(%%) be kept as it will be used later in the process.

326

327

328

(% style="text-align:center" %)

329

[[image:1633327962522-699.png||data-xwiki-image-style-alignment="center"]]

330

331

332

The tax information will be populated along with the transfer details contained in the file and under System Bank Accounts. The tax application will need to be submitted to SARS and a response is required before processing with payment.

333

334

The member records now appear in(% style="color:#e74c3c" %) RED(%%) with an exit date and an exit type.

335

336

337

(% style="text-align:center" %)

338

[[image:1633328086509-533.png||data-xwiki-image-style-alignment="center"]]

339

340

341

Once the tax response is received, the (% style="color:#2980b9" %)“**Import Unclaimed Benefits – Creditor Payment**”(%%) batch needs to be run.

342

343

344

Insert the Batch Number from your import, that was done previously, into this Batch Ref field.

345

346

The Administrator Bank field is the name of the creditor being paid that has been set up under System Bank Accounts (Transfer Funds).

347

348

349

A report will generate confirming which benefits have been populated for payment. Only benefits where tax has been received back will be populated. The report will clearly highlight which members are ready for payment and which are not.

350

351

352

Click on the (% style="color:#2980b9" %)cflo (%%)button on the member record. A line would have been created for payment.

353

354

355

(% style="text-align:center" %)

356

[[image:1633328484167-380.png||data-xwiki-image-style-alignment="center"]]

357

358

359

The payment can now be made in Bulk at the Parent Level.

360

361

Go to (% style="color:#2980b9" %)Accounts > Debtors and Creditors(%%) Menu item. Select (% style="color:#2980b9" %)**“Creditors”.**

362

363

A creditor payment reflects in the Creditor Payment.

364

365

366

(% style="text-align:center" %)

367

[[image:1633328582529-671.png||data-xwiki-image-style-alignment="center" height="189" width="466"]]

368

369

370

(% style="text-align:center" %)

371

[[image:1633328678458-232.png||data-xwiki-image-style-alignment="center"]]

372

373

374

Select (% style="color:#2980b9" %)**__eft__ **(%%)hyperlink and a batch editor screen will open to generate the Payment.

375

376

377

(% style="text-align:center" %)

378

[[image:1633328773306-793.png||data-xwiki-image-style-alignment="center"]]

379

380

381

The payment can be approved on the Payment Management screen as a bulk payment. The process has been completed and the necessary payment records have been created.

(% style="break-before: page; text-align: center;" %)

387

= (% style="color:#2980b9" %)**Disclaimer and Copyright**(%%) =

(% style="color:#2980b9" %)**DISCLAIMER**

393

394

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.

395

396

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.

397

398

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.

399

400

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.

(% style="color:#2980b9" %)**COPYRIGHT**

405

406

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.

407

408

409

EBSphere (Pty) Limited

P.O. Box 785803

Sandton