File Layout (Walker Interface)

Header record

Seq.

 No.

Data Field

O/M

Start

Pos.

Length

End

Pos.

Format

Default / System value

1

PARAMETER IDENTIFICATION

M

1

5

5

A/N

GRP01

2

COST CENTRE

M

6

6

11

A/N

BB0077

3

RECORD TYPE

M

12

1

12

A/N

P

4

RECORD VERSION

M

13

2

14

A/N

00

5

FORCED INDICATOR

M

15

5

19

A/N

See 2.3.1.1 Note below

6

CONTRA INDICATOR

M

20

1

20

A/N

Space

7

TABULATION INDICATOR

M

21

1

21

A/N

Space

8

POSTING INDICATOR

M

22

1

22

A/N

Space

9

JDL

M

23

6

28

A/N

D017

10

FILLER

M

29

1

29

A/N

Space

11

EDM AMOUNT

M

30

16

45

N

Spaces

12

EDM SIGN

M

46

1

46

A/N

Space

13

GRP01 & GRP05

O

47

124

170

A/N

Spaces

 

Notes

-     The header record is a single line and the first line of the file.

-     Each transaction will appear as one line on the file, i.e. the debit transaction of a BT will be one line followed by the credit transaction on the next line.  Both lines of the same BT must have the same journal number (see fields 1, 2 and 3 of the content record below).

-     The sum of the amounts for all of the lines with the same journal number must be equal to zero.

-     The sum of all of the amounts for all of the lines in the file must equal zero.

-     The forced indicator must be set to F followed by the posting month if transactions must be posted to a closed financial period.  This can only be done between the 4th and 6th working day of the month after the closed period.

-     If the month of the transaction date of a business transaction (BT) is equal to the month prior to the current month and the current date is less than or equal to the 6th working day of the month and greater than the 4th working day, a separate file for these transactions must be created.  For this file the value for the FORCED INDICATOR field must be set to F followed by the year and month of the transaction date, in the format YYMM, e.g. if the current date is 05/09/2009 and the transaction date is 25/08/2009, this value must be F0908.

-     If the transaction date of a content record is less than the current month and the date is greater than the 6th working day of the month, processing will be stopped and an error message will be displayed (Transaction Date is less than the month prior to current month).

-     If the transaction date is not less than current month, this will be set to spaces.

 

Content record

Seq

No

Data Field

O/M

Start

Pos

Length

End

Pos

Format

Default / System value

1

JOURNAL NUMBER – PROGRAM INDICATOR

M

1

2

2

N

99

2

JOURNAL NUMBER – PROGRAM REFERENCE

M

2

3

5

N

422

3

JOURNAL NUMBER – JOURNAL COUNTER

M

6

7

12

N

Sequential number per BT.

This number must be unique for each journal for the same linked date. See 1.2.3 below.

Set up a control record to record the last sequence number used. Create the first record with a number of 0000001 and increment it by 1 each time a journal number is allocated.

1,2,3

JOURNAL NUMBER

M

1

12

12

N

This value is a concatenation of values in fields 1, 2 & 3. e.g. 992130000123.

This number links the Debit and Credit legs of a transaction.

One sequential number must be allocated for each Business Transaction i.e. the Debit Transaction and the Credit Transaction for the same BT.

4

TRANSACTION DATE

M

13

8

20

N

Transaction Date on BT in the format CCYYMMDD

5

ACK: COMPANY CODE

M

21

4

24

A/N

Read the Translation Value table where the Purpose is INP TO SANLAM and for which the Source System ID is SANLAM LEDGER and the Source System Attribute is ACCOUNT/COMPANY, and the Target System ID is SANLAM LEDGER and the Source System Attribute is COMPANY CODE.

Read the Target System value for the Account Code in field 6.  If a Translation Value is not found for the Account Code in field 6, default the value to A200.

6

ACK: ACCOUNT CODE

M

25

5

29

A/N

Read the Translation Value table where the Purpose is INP TO SANLAM and for which the Source System ID is IN.PENSIONS and the Source System Attribute is ACCOUNT/QUAL, and the Target System ID is SANLAM LEDGER and the Target System Attribute is ACCOUNT. If the Account on the BT is qualified by Global Type read the Target System value for the Source System combination of Account Code and Global Type on the BT. If the Account is not qualified by Global Type, read the Target System value for the Source System value for Account.

If the Account is PENSIONTAX read the Tax Territory on the Membership Payment Detail linked to the Membership record. If it is NAMIBIA then make the value for ACK: ACCOUNT CODE equal to GF600.

The Fund level BT’s for tax will be created for the individual member tax amount and therefore the BT will have the Membership Reference Number.

7

ACK: TAX TYPE / FUND

M

30

6

35

A/N

Read the Translation Value table where the Purpose is INP TO SANLAM and for which the Source System ID is SANLAM LEDGER and the Source System Attribute is ACCOUNT/TAX, and the Target System ID is SANLAM LEDGER and the Source System Attribute is TAX TYPE. Read the Target System value for the Account Code in field 6.

If a Translation Value is not found for the Account Code in field

6, create this field with spaces.

8

ACK: COST CENTRE

M

36

6

41

A/N

Read the Translation Value table where the Purpose is INP TO SANLAM and for which the Source System ID is SANLAM LEDGER and the Source System Attribute is ACCOUNT/COST, and the Target System ID is SANLAM LEDGER and the Source System Attribute is COST CENTRE. Read the Target System value for the Account Code in field 6. If value of SCHEME CODE is found create this field with the Scheme Code on the BT prefixed by P and zeroes if the Scheme Code is less than 6 characters.

If a Translation Value is not found for the Account Code in field 6 default the value to spaces.

9

ACK: PRODUCT

M

42

9

50

A/N

Spaces

10

ACK: TXNTYPE

M

51

3

53

A/N

Spaces

11

ACK: CHANNEL

M

54

1

54

A/N

Spaces

12

BOOK MONTH DATE EFFECTIVE DATE

M

55

8

62

A/N

Transaction Date on BT in the format CCYYMMDD.

 

If the current date is less than or equal to the 3rd working day of the previous month’s accounting period is still open and for transactions with a transaction date equal to previous month, this date must be set to Transaction Date on the BT. 

 

If the current date is greater than the 4th working day and less than or equal to the 6th working day then these transactions can be posted to the previous month but with the FORCED INDICATOR field in the header record set to F followed by the year and month of the Transaction Date.

 

If the Transaction Date on the BT is less than the current month and not less than the previous month and the current date is greater than the 6th working day of the current month, set this date to the first day of the current month.

 

If the Transaction Date on the BT is less than the previous month and the current date is less than the 4th working day, set this date to the first day of the previous month.

 

If the Transaction Date on the BT is less than the previous month and the current date is greater than or equal to the 4th working day and less than or equal to the 6th working day, set this date to the first day of the previous month.  These transactions must be created in a separate file with the FORCED INDICATOR field in the Header record set to F followed by the year and month of the Transaction Date.

 

See examples under Book Month Effective Date below.

13

AMOUNT

M

63

16

78

N

BT Amount without the decimal point e.g. 123 = R1.23

14

SIGN

M

79

1

79

A/N

+ = Debit

- = Credit

15

ANALYSIS

M

80

20

99

A/N

Read the Translation Value table where the Purpose is INP TO SANLAM and for which the Source System ID is SANLAM LEDGER and the Source System Attribute is ACCOUNT, and the Target System ID is SANLAM LEDGER and the Target System Attribute is RECON CRITERIA. Read the Target System value for the Source System value of the Account Code in field 6.

The Analysis Codes for different accounts are composed of one or more different elements. Each of these combinations is covered below under a heading of the combination defined in Walker.

 

Cost Centre / Fund Code / Member No

If the Target System value for the Account is COST CENTRE/SCHEME/MEMBER NO create this with the Cost Centre (field 2 in the parameter record), Scheme Code prefixed with P and spaces if the Scheme Code is less than 5 characters, and Membership Reference number prefixed with zeroes if it is less than 8 characters. If there is no Membership Reference Number on the BT create this field with 00000000 for the Membership Number.

The length of each of these components of this field must be:

Cost Centre: 6

Scheme Code: 6

Membership Number: 8

 

Cost Centre / Date

If the Target System value for the Account is COST CENTRE/DATE create this field with the Cost Centre (field 2 in the parameter record) and the month and year of the Transaction Date e.g. 0809 if the Transaction Date is 31/08/2009 followed by spaces.

The length of each of these components of this field must be:

Cost Centre: 6

Date: 4

 

Date

If the Target System value for the Account is DATE create this with the month and year of the Transaction Date e.g. 0809 if the Transaction Date is 31/08/2009 followed by spaces.

 

Cheque / Deposit Number

If the Target System value for the Account is DEPOSIT NUMBER create this with the value for CHEQUE / DEPOSIT NUMBER in field 17 followed by spaces.

The length of this must be 6.

 

Document Number

If the Target System value for the Account is DEPOSIT NUMBER create this with the value for DOCUMENT NUMBER on the Business Transaction in field 15 followed by spaces.

The length of this must be 7.

 

Fund Code

If the Target System value for the Account is SCHEME create this with the value Scheme Code prefixed with a P and spaces if the Scheme Code is less than 5 characters followed by spaces.

The length of this must be 6.

If no translation value is found for the Account default the value of this field to spaces.

 

Consultant Code / Broker Code / Client Name

If the Target System value for the Account is BROKER/COSTCENTRE/SCHEMENAME read the Scheme Name and the Code for the Intermediary linked to the Scheme. Create this field with the value of Intermediary Code followed by the first 15 characters of the Scheme Name.

The length of each of these components of this field must be:

Consultant Code/Broker Code (Intermediary Code): 5

Client Name (Scheme

Name: 15

 

Client Name

If the Target System value for the Account is SCHEME/BROKER/COSTCENTRE read the Scheme Name for the Scheme and the Code for the Intermediary linked to the Scheme and create this field with the first 9 characters of the Scheme Name followed by the first 3 characters of the Intermediary Code, the value of 0077 for the Department Code and the last 2 characters of the Intermediary Code prefixed with 2 zeroes.

 The length of each of these components of this field must be:

Scheme Name: 9

Consultant Code (Intermediary Code): 3

Department Code: 4

Consultant’s Cost Centre: 4

 

Fund Code / Fund Name / Broker Code / Marketer code

If the Target System value for the Account is SCHEME/SCHNAME/BROKER/MARKETER read the Scheme Name for the Scheme Code, the Code for the Intermediary linked to the Scheme. Create this field with Scheme Code prefixed with P and spaces if the Scheme Code is less than 5 characters followed by the first 8 characters of the Scheme Name, the last 3 characters of the Intermediary Code, and 3 zeroes.

The length of each of these components of this field must be:

Fund Code (Scheme Code): 6

Fund Name: 8

Broker Code (Intermediary Code): 3

Marketer Code: 3

 

Alphabetical / Numerical

 

If the Target System value for the Account is SCHEME (20) create this field with the Scheme Code prefixed with P and spaces if the Scheme Code is less than 5 characters and followed by 14 zeroes.

The length of this filed must be 20 characters.

16

POLICY NUMBER

M

100

12

111

N

Read the Translation Value table where the Purpose is INP TO SANLAM and for which the Source System ID is SANLAM LEDGER and the Source System Attribute is ACCOUNT/POLICY, and the Target System ID is SANLAM LEDGER and the Source System Attribute is POLICY NUMBER. Read the Target System value for the Account Code in field 6.

 

If a value of SCHEME/MEMBER NO is found for the Account Code in field 6, create the first 4 characters of this field with Scheme Code prefixed with zeroes if the Scheme Code is less than 4 characters and followed with the Membership Reference Number on the BT in the next 8 spaces prefixed with zeroes if the Membership Reference Number is less than 8 characters.

If no Membership Reference Number is found on the BT create this field with Scheme Code followed by 8 zeroes.

If the Scheme Code is more than 4 characters drop the first characters. 

If a Translation Value is not found for the Account Code in field 6, default the value to spaces.

 

If a value of POLICY NUMBER is found for the Account Code in field 6, create the characters for field 16 POLICY NUMBER with the value for Third Party Reference Number on the Client Relationship linked to the Annuitant with a Type of DEDUCTION. 

17

CHEQUE / DEPOSIT NUMBER

M

112

7

118

N

Document Number on the BT if the BANK account is the Credit account on the Business Transaction, else spaces.

18

RECONCILIATION INDICATOR

M

119

1

119

A/N

If the Account Code in field 6 is GA003 (Bank account) and the value in field 14 is ‘-‘ then create this field with T (Tjek (Cheque)).

If the value in field 14 is ‘+’ then create this filed with D (Deposit).   

19

SUNDRY

M

120

10

129

A/N

Read the Translation Value table where the Purpose is INP TO SANLAM and for which the Source System ID is SANLAM LEDGER and the Source System Attribute is ACCOUNT/SUNDRY, and the Target System ID is SANLAM LEDGER and the Source System Attribute is SUNDRY. Read the Target System value for the Account Code in field 6.

If a value of SCHEME CODE is found for the Account Code in field 6, create the first 5 characters of this field with Scheme Code prefixed with zeroes if the Scheme Code is less than 5 characters.

If the Scheme Code is more than 5 characters drop the first characters.

If a Translation Value is not found for the Account Code in field

6, default the value to spaces.

20

N FUND

M

130

1

130

A/N

Space

21

CO-ENT

M

131

7

137

A/N

Spaces

22

PAYEE / DEPOSITOR

M

138

30

167

A/N

Payee Name on BT if Type of Payment CHEQUE, EFT, BANK TRANSFER, FOREIGN DRAFT or JOURNAL ENTRY, else spaces

23

FUTURE USE

M

168

3

170

A/N

Spaces

24

END OF LINE

M

171

1

171

CRLF

End of Line

 

Book month effective date

The following table is an example of the date with which the book month effective date must be created based on the transaction and the run date.

 

 

Current Working Day

Transaction Date

1st  - 3rd  day September

4th  – 6th day September

7th – last day September

03/05

01/08

01/08 F*

01/09

14/08

14/08

14/08 F*

01/09

02/09

02/09

02/09

02/09

15/09

15/09

15/09

15/09

 

* Indicates a separate file with the Forced Indicator field in the Header Record set to F followed by the posting year and month.