This file layout enables the history of contributions to be loaded.
Note:
This layout is also used for the creation of contributions in bulk or the bulk load of individual Retirement Annuity Fund member contribution amounts via the CONH layout. For more information, refer to
Processes
File Transfer
File Layouts
Contribution Updates
Processes
File Transfer
File Layouts
Retirement Annuity Fund Contributions
The following validations are performed during the process:
- The date format must be correct (e.g. a date of 19521560 will reject because the month and day are invalid).
- The member must exist on the system.
- The effective date of the contribution may not be prior to the member’s date of entry, i.e. member’s original date of joining the scheme.
- Where records have rejected, the user is able to make the necessary amendments, and validation will continue.
- If multiple records are found in the same file for the same member, the existing record will be updated with the new data.
- The processing of contributions for exited members is allowed.
- Multiple schemes can exist within a file. Each scheme record should have a header, detail, and a footer/trailer. The file will then be split automatically per scheme and processed individually.
Header record
|
Field Name |
Field Size |
DEC |
ATTR |
Start |
End |
Description / Value |
1 |
File ID code |
4 |
|
Char |
1 |
4 |
AB00 |
2 |
Fund number |
7 |
|
Char |
5 |
11 |
Fund number |
3 |
IN.pensions scheme code |
7 |
|
Char |
12 |
18 |
IN.pensions scheme code |
4 |
Conversion date |
8 |
|
Num |
19 |
26 |
CCYYMMDD - conversion date |
5 |
System date |
8 |
|
Num |
27 |
34 |
CCYYMMDD - system date |
6 |
System time |
6 |
|
Num |
35 |
40 |
Hhmmss - system time |
Detail record
|
Field Name |
Field Size |
DEC |
Start |
End |
ATTR |
O/M |
Description / Value |
1 |
File indicator |
4 |
|
1 |
4 |
Char |
M |
CONH |
2 |
Scheme code |
7 |
|
5 |
11 |
Char |
M |
Scheme code |
3 |
Member number |
20 |
|
12 |
31 |
Char |
M |
Member reference number |
4 |
Start date |
8 |
|
32 |
39 |
Char |
M |
CCYYMMDD |
5 |
Contribution type |
15 |
|
40 |
54 |
Char |
M |
Basic, PSD (PSD = Pensionable Service Date backdated) |
6 |
Monetary amount |
11 |
|
55 |
65 |
Num |
M |
Actual Contribution Amount |
7 |
Filler |
1 |
|
66 |
66 |
|
M |
Space |
8 |
Increase Type |
15 |
|
67 |
81 |
Char |
O |
ANN ESCALATION
Type of Increase on Membership Payment Detail. |
9 |
Increase Percentage |
7 |
2 |
82 |
88 |
Num |
O |
Annual increase percentage.
Percentage on Membership Payment Detail. |
10 |
Payment Day |
2 |
0 |
89 |
90 |
Num |
O |
Day of the month on which the member’s contribution is to be collected.
Payment Day on Membership Payment. |
11 |
Date of last payment |
8 |
|
91 |
98 |
Char |
O |
Day last contribution was collected |
12 |
Date of Retirement |
8 |
|
99 |
106 |
Char |
O |
Member’s normal retirement date |
13 |
Income Type |
4 |
|
107 |
110 |
Char |
O |
Income Type REC FEEP |
14 |
Frequency |
15 |
|
111 |
125 |
Char |
O |
MONTHLY QUARTERLY ANNUAL |
O = Optional field
M = Mandatory
Trailer record
|
Field Name |
Field Size |
DEC |
Start |
End |
ATTR |
Description / Value |
1 |
File indicator |
4 |
|
1 |
4 |
Char |
AB99 |
2 |
Number of detail records |
13 |
|
5 |
17 |
Num |
Total number of detail records (Prefix AB22) |
3 |
Fund number |
13 |
|
18 |
30 |
Num |
#total of scheme codes on file |
4 |
Member number |
13 |
|
31 |
43 |
Num |
#total of member numbers |
5 |
Contribution amount |
13 |
2 |
44 |
56 |
Num |
#total of salary amounts (total must take sign into account) |
Note:
All optional text fields must be padded with trailing spaces.
All numeric fields must be padded with leading zeroes.
If the member reference number is greater than 20 characters, the trailer record will not produce the correct results.
The system will take action as follows:
Detail Record
Field Name |
Action |
File indicator |
Must be CONH for contribution updates. |
Scheme code |
If not the same as in the Header record, reject the record with an error message to the error log |
Member number |
If not a valid member number, reject the record with an error message to the error log |
Start date |
The Start Date must be a valid date (i.e. CCYYMMDD), the Contribution Type must be one that is used by the scheme on the Start Date, and the Monetary amount must be numeric. If not, reject the record with an error message to the error log. |
Payment type |
If the member has no contribution records of type Contribution Type, create a new contribution record of that type, with the Start Date and Monetary amount provided, unless the monetary amount is zero, in which case reject the record with an error message to the error log. |
Monetary amount |
If the member has contribution records of type Contribution Type, check that the Start Date is later than the Start Date of the last contribution of that type. If it is not, reject the record with an error message to the error log. If it is, end-date that contribution with a date one day prior to Start Date, and create a new contribution record of that type, with the Start Date and Monetary amount provided, unless the Monetary Amount is zero, in which case do not create a new record. |
Increase Type |
If there is a value for Increase Type, the system will update the Type of Increase on the Membership Payment Detail record. |
Increase Percentage |
If there is a value for Increase Percentage, the system will update the Percentage on the Membership Payment Detail record. |
Payment Day |
If there is a value for payment Day, the system will update the Payment Day on the Membership Payment record. |
Date of last payment |
If there is a value for Date of Last Payment, the system will update the Date of Last Payment on the Membership Payment Detail record. |
Date of Retirement |
If there is a value for Date of Retirement, the system will update the Date of Retirement on the Membership Payment record. |
Income Type |
If there is a value for Income Type, the system will update the Income Type (Inst_ID_JUF03) on the Membership Payment record. |
Frequency |
If there is a value for Frequency, the system will update the Frequency on the Membership Payment Detail record.
If no value for Frequency is supplied, the system will default the value to MONTHLY as per the current functionality. |