7.1.1 FTI XML Template 1
Source: TI_Host_to_Host_Client_User_Manual_v52.pdf
Document pages: 128-130
PDF pages: 128-130
Appendix B
Herewith the layout for the standard XML transaction feeds for near real time:
XML Tag name Data type Expected Maximum size Description
| <CISNumber> Numeric 12 This field will display the client's CIS
number
<ProfileNumber> Numeric 10 This field will display the client's profile
number
<Product> Alpha 10 Will contain the F for the FTI product
<Instancenumber> Numeric 4
You can load up to 9999 different instances per profile. An instance is a group of accounts, settings and destination
<Instancename> Alpha
Numeric 30 Instance name as specified by the client
<Date> Numeric 8 Displays the date on which the file is
|
being sent. CCYYMMDD
| <Header>
<TIAccount>
<TIAccountHeader>
|
XML Tag name Data Type Expected Maximum size Description
Numeric 23 The transactions that follow are for this account
| <StatementNumber> Number 6 Provides a single statement number
per message
<StatementSequenceNumber> Alpha 6
If your statement is broken up into multiple messages it will have different sequence numbers.
<OpeningAvailableBalance> Decimal 16,2
This is the opening available balance for this statement. Available balance= (Actual balance + Account Overdraft facility) less uncleared funds (Cheque deposits)
<OpeningBookBalance> Decimal 16,2 Actual opening balance
<TotalDebits> Decimal 16,2 Sum of the debit transactions on this
statement for this account
<TotalCredits> Decimal 16,2 Sum of the credit transactions on this
statement for this account
<TotalDebitCount> Numeric 10 Number of debit transactions on this
|
statement for this account
| <TotalCreditCount> Numeric 10 Number of credit transactions on this
statement for this account
<ClosingAvailableBalance> Decimal 16,2
This is the closing available balance for this statement. Available balance= (Actual balance + Account Overdraft facility) less uncleared funds (Cheque deposits)
<ClosingBookBalance> Decimal 16,2 Actual closing balance
|
| <TIAccountHeader>
<TIRecord>
|
XML Tag name Data Type Expected Maximum size Description
| <TransactionKey> Numeric 16
Each transaction in Nedbank is allocated a unique key for FTI. IF you receive the same transaction key on another message it is for the same transaction
<ProcessKey> Numeric 9
Uniquely identifies the client preferences effective for this transaction
<ResendKey> Numeric 9
Any value greater zero means the transaction was resent on customer request
<DestinationKey> Numeric 9
If a single instance has more than one destination address it will have different destination keys. In the case of using Web Service only one destination allowed per instance
<TransactionListNumber> Numeric 6
Your transaction list number as you displayed on your official posted statement
<StatementLineNumber> Numeric 2
Each transaction list can have a maximum of 20 transactions. This indicates this was transaction 2 in statement list 1. Helps client match transaction to posted statement
<Account> Alpha 30 The transaction was affected on this
account
<TransactionCode> Numeric 4
Nedbank transaction codes identifying the type of transaction Refer to no 4.9 for a list of Transaction and Sub Transaction codes
<SubTransactionCode> Numeric 4
Reserved for future use ie for multiple transactions using the same transaction code. Sub trancodes will be used to uniquely identify the type transaction Refer to no 4.9 for a list of Transaction and Sub Transaction codes
<Amount> Decimal 16,2 The actual transaction amount
<DebitCredit> AlphaNu 2 Is transaction a debit (Money out) or
|
meric credit (Money in) to the account being reported on. Values D = Debit, C = Credit, RD = Reversal of Debit, RC = Reversal of Credit
| <Date> Numeric 8 The date on which the transaction was
performed. Format 'CCYYMMDD'
<AccountAvailableBalance> Decimal 16,2
This is the available balance after this transaction has taken place. Available balance= (Actual balance + Account Overdraft facility) less uncleared funds (Cheque deposits)
<UserRef> Alpha 30 Statement description/narrative losing
|
of body for xml message
XML Tag name Data Type Expected Maximum size Description
| <TransactionKey> Numeric 16
Each transaction in Nedbank is allocated a unique key for FTI. IF you receive the same transaction key on another message it is for the same transaction
<ProcessKey> Numeric 9
Uniquely identifies the client preferences effective for this transaction
<ResendKey> Numeric 9
Any value greater zero means the transaction was resent on customer request
<DestinationKey> Numeric 9
If a single instance has more than one destination address it will have different destination keys. In the case of using Web Service only one destination allowed per instance
<TransactionListNumber> Numeric 6
Your transaction list number as you displayed on your official posted statement
<StatementLineNumber> Numeric 2
Each transaction list can have a maximum of 20 transactions. This indicates this was transaction 2 in statement list 1. Helps client match transaction to posted statement
<Account> Alpha 30 The transaction was affected on this
account
<TransactionCode> Numeric 4 Nedbank transaction codes identifying
the type of transaction
<SubTransactionCode> Numeric 4
Reserved for future use ie for multiple transactions using the same transaction code. Sub trancodes will be used to uniquely identify the type transaction
<Amount> Decimal 16,2 The actual transaction amount
<DebitCredit> AlphaNu
|
meric 2 Is transaction a debit (Money out) or credit (Money in) to the account being