Bank Integration Service - Gasell Requirements

This document outlines what data Gasell needs from a Bank Integration Service.

1. Payment File Formats

Gasell processes (parses) the following payment file formats:

• BgMax (Bankgirot, legacy flatfile format)
• Autogiro (Bankgirot legacy flatfile format)
• Leverantörsbetalningar (Bankgirot refund report,legacy flatfile format)
• Avtalegiro (rejected payment orders avtalegiro, legacy flatfile format, Only Norway)

• ISO 20022 camt.054 credit (Nordea, Only Norway)
• ISO 20022 camt.054 debit (Refund report, Nordea, Only Norway)
• ISO 20022 pain.002 (Error list for refunds, Nordea, Only Norway)

Gasell produces (generates) the following payment file formats:

• Autogiro (Bankgirot legacy flatfile format)
• Leverantörsbetalningar (Bankgirot legacy flatfile format)
• ISO 20022 pain.001 (refunds, Nordea, Only Norway)
• Avtalegiro (Norwegian direct debit, legacy flatfile format, Only Norway)

2. What Gasell Needs

Gasell needs bank integration for Swedish banks currently using Bankgirot legacy file formats for payments and refunds.

Swedish banks in Gasell currently used by active organization:

• Swedbank
• SEB
• Handelsbanken
• Danske Bank

1. Implement processing of camt.054 for incoming payments and Swedish banks
2. Implement generation of pain.001 for outgoing payments and Swedish banks
3. Implement processing of camt.054 for outgoing payments and Swedish banks
4. Implement processing of pain.002 for error handling of outgoing payments and Swedish banks
5. SFTP-integration with Swedish banks. Danske Bank already supported.
6. Handle various tamper protection mechanisms for Swedish banks. Danske Bank already supported.

Common parsing data requirements

Fields handled today for each payment file:

• payment_file_type_id (provided by Gasell)
• bank_account_id (extracted from file)
• msg_date (extracted from file)
• filename (provided by Gasell)
• organization_id (provided by Gasell)
• payment_file_category_id (provided by Gasell)

General payment information (extracted from file):

• ocr
• amount
• pay_date

Camt.054 parsing data requirements

Camt.054 specific fields (extracted from file):

• payer_name
• payer_address
• payer_information
• payer_account

Pain.002 parsing data requirements

Pain.002 specific fields (extracted from file):

• repayment_number
• repayment_code
• error_code

We are also using the following field(s) for validation of signer id: CstmrPmtStsRpt->GrpHdr->InitgPty->Id->OrgId->Othr→id (when SchmeNm->Cd == 'CUST')