Reconciliation Procedure

Create API

Reconciliation is the obligation of the partner, as an effort to monitor and mitigate the risk of financial transactions that occur, which is usually done on H + 1.

Partners who are allowed to go into production, especially for Fund Transfer, Direct Debit and BRIZZI products, must include a reconciliation procedure that is carried out and validated by the BRIAPI team.

There are three data source options that can be used to perform the reconciliation process.

1. Account Statement

Account Statement (current account or mutation info), can be obtained in two ways:

Via Account Statement API
Download from CMS application

Some things to note when using Account Statements as data reconciliation sources:

Account Statements can be obtained on the same day or the next day. However, there are differences in the remark structure for Fund Transfer transactions, as follows:
- Example of remark field: REMARK TEST BRIAPI
- Current account H+0: remark will contain REMARK TEST BRIAPI
- Current account H+1: remark will contain REMARK TEST BRIAPI WS_OB;<referral number>;<additional information>
- Additional information obtained from the system includes institution code and bookkeeping tellers
Therefore, for FT product partners, it is necessary to include a unique code in the Remark column, to make it easier to identify transactions on H+0.

Any error response not listed in the BRIAPI response list is considered pending and requires further investigation.

Please see the Account Statement API documentation for a more detailed explanation.

2. Direct Debit Report

This report is generated specifically for Direct Debit products. Please see the documentation on the Direct Debit product or contact the BRIAPI team to read the report.

3. MT940 File

MT940 is a swift format file that displays the transactions that took place.

BRI will provide MT940 files through two methods:

SFTP (partners will be given a username and password to access the SFTP file)
Sent via Email

Each MT940 file represents all transactions that occur H-1. To get this MT940, please contact the BRIAPI team for a more detailed explanation.

MT940 File Naming uses the following format "042801020365703.202107140256 042801020365703 -> Account Number 20210714 -> Transaction Date H-1 0256 -> Generating Time to SFTP"

Sample File:


               
            {1:BRI}{2:940SI}{4:
            :20:20161116022517
            :25:042801020365703
            :28C:321
            :60F:C161116IDR1100000
            :61:161116D1469582861NTRF
            :86:GFV844469 0749 TJBB 16112016
            :62F:C161116IDR1100000
            -}

Component	Mandatory	Description	Sample
Statement Date	M	Date mt940 was generated	`:20:20161116022517` 20161116022517 follow the format YYYYMMDDHHMMSS
Account Number	M	Account Number, 15 numeric characters	`:25:042801020365703` 042801020365703 → account number
Sequence	M	Statement number / sequence number, 3 numeric characters	`:28C:226` 226 → sequence number
Opening Balance	M	Starting Balance, consisting of: Debit / credit balance status Date Currency Total of balance (position)	`:60F:C161116IDR1100000` C → debit/credit balance status (D/C) 161116 → 6 numeric characters format YYMMDD IDR → 3 currency characters 1100000 → balance, numeric
Statement Line	M	Statement Line, consisting of: Date Debit/credit balance status Nominal Transaction code identification	`:61:161116D1469582861NTRF` 161116 → 6 numeric characters format YYMMDD D → debet / kredit (D/C) 1469582861 → nominal TRF → transaction code (please see the list of transaction codes below)
Information Account / Header	O	description, a maximum length of 40 characters	`:86:GFV844469 0749 TJBB 16112016` GFV844469 0749 TJBB 16112016 → description/remark
Account Header	M	Final Balance, consisting of: Debit/credit balance status Date Currency Total balance (position)	`:62F:C161116IDR1100000` C → Status saldo debet/kredit (D/C) 161116 → 6 numeric characters format YYMMDD IDR → 3 currency characters 1100000 → saldo, numerik