Account Statement Report
Using your Dashboard, you can generate an account statement report that includes all the debits and credits on your account for a specific period of time. Simply login and choose the range of dates for your reporting period. Alternatively, you can schedule a regularly recurring account reporting file to be generated automatically.
The resulting CSV file contains a header, the debit and credit transactions, and a footer.
Header
The header contains 5 lines, each with its own structure:
| Line\Column | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | "Line" | "Execution_Date" | "Transaction_ID" | "Client_Reference" | "Debtor_Name" | "OP_Code" | "Amount" | "Value_Date" | "Credit_value" | "Debit_value" | "Label" | "Invoice_Reference" | "Initial_Transaction_ID" | |
| 2 | Number of transaction lines in the file | Date of the report (YYYY-MM-DD) |
Merchant's company name | |||||||||||
| 3 | Empty line | |||||||||||||
| 4 | "Previous balance" | Previous balance date | Previous balance amount | |||||||||||
| 5 | Empty line | |||||||||||||
Below is an example of a header for an account statement report containing 6 transactions:
"Line";"Execution_Date";"Transaction_ID";"Client_Reference";"Debtor_Name";"OP_Code";"Amount";"Value_Date";"Credit_value";"Debit_value";"Label";"Invoice_Reference";"Initial_Transaction_ID";
"6";"2020-09-01";;"CyberPress";
;;;;"Previous balance";;;"2020-08-01";"4383.08";
Transactions
Following the header, each line represents a single transaction on the account. There are several types of transaction, each defined by a code in the "OP_Code" column. The meaning of each of these codes is outlined below:
| Code | Description | Impact on account |
|---|---|---|
| SDD | SEPA Direct Debit | Credit |
| REJ | Reject of an SDD | Debit |
| RET | Return of an SDD | Debit |
| REV | Reversal of an SDD | Debit |
| SCT | SEPA Credit Transfer | Debit |
| OCT | Reject of an SCT | Credit |
| PIS | SlimCollect Pay payment | Credit |
| REB | Reimbursement by credit transfer | Debit |
| ORB | Reject of a reimbursement by credit transfer | Credit |
| FEE-XXX | SlimPay fee for the transaction of type XXX (e.g. FEE-SDD) | Debit |
Each transaction line contains up to 13 values. Some values do not apply to all transaction types, in which case, the column will be empty.
| Column name (see header) | Description | Format | Max length |
|---|---|---|---|
| "Line" | From 1 to n | Integer | |
| "Execution_Date" | Date of the transaction | ISO 8601 Date format (2020-07-25) | 10 |
| "Transaction_ID" | Unique reference of the transaction | Alphanumeric | 35 |
| "Client_Reference" | Unique reference of the subscriber provided by the merchant | Alphanumeric | 35 |
| "Debtor_Name" | Debtor's first and last name (individual) or the company name (corporate) | Alphanumeric | 32 |
| "OP_Code" | Type of the transaction | Alphabetic | See list above |
| "Amount" | Signed amount of the transaction | Decimal | |
| "Value_Date" | Value date of the transaction on the account | ISO 8601 Date format (2020-07-25) | 10 |
| "Credit_value" | Amount credited to the account | Decimal | |
| "Debit_value" | Amount debited from the account | Decimal | |
| "Label" | Label of the transaction | Alphanumeric | 140 |
| "Invoice_Reference" | Invoice reference provided by the merchant | Alphanumeric | 35 |
| "Initial_Transaction_ID" | For rejects and returns, the "Transaction_ID" value of the initial transaction | Alphanumeric | 35 |
Below are 6 example transactions of type (in order) SDD, REJ, REB, ORB, SCT, FEE-SCT:
"1";"2020-08-17";"REF-Trans-01000012";"REF-Cli-65412";"John Doe";"SDD";"157.23";"2020-08-18";"157.23";;"First payment of tuition fees for 2020";"Bill_1647";
"2";"2020-08-17";"REJ-EXE-20200817-194";"REF-Cli-65412";"John Doe";"REJ";"-157.23";"2020-08-18";;"157.23";"R-Transaction: AM04 - Insufficient funds";"N/A";"REF-Trans-01000012";
"3";"2020-08-23";"REB-EXE-20200823-286";"A64323";"Jane Doe";"REB";"-16.55";"2020-08-23";;"16.55";"Reimbursement for our Golden Ticket operation";"N/A";
"4";"2020-08-26";"REB-REJ-20200826-281";"A64323";"Jane Doe";"ORB";"16.55";"2020-08-27";"16.55";;"R-Transaction: AC04 - Account is suspended / terminated";"N/A";"REB-EXE-20200828-286";
"5";"2020-08-29";"SCT-EXE-20200829-282";"153";"Hooli";"SCT";"-600.00";"2020-08-30";;"600.00";"SlimPay credit transfer";"N/A";
"6";"2020-08-31";"SCT-FEE-20200831-202";"153";"Hooli";"FEE-SCT";"-0.22";"2020-08-31";;"0.22";"Execution fee of 1 credit transfer(s) at 0.180 euro per unit";"N/A";Footer
The footer contains 7 lines, each with its own structure:
| Line\Column | 1 to 4 | 5 | 6 | 7 | 8 | 9 | 10 | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | "TOTAL" | Credits minus debits | Value date of this report's last transaction (YYYY-MM-DD) | Total credits | Total debits | ||||||
| 2 | Empty line | ||||||||||
| 3 | "New balance" | Effective date (YYYY-MM-DD) | Amount | ||||||||
| 4 | "Outstanding credit transfers/reimbursements" | Effective date (YYYY-MM-DD) | Amount | ||||||||
| 5 | "Outstanding fees" | Effective date (YYYY-MM-DD) | Amount | ||||||||
| 6 | "Minimum balance" | Effective date (YYYY-MM-DD>) | Amount | ||||||||
| 7 | "Available funds" | Effective date (YYYY-MM-DD) | Amount | ||||||||
Below is an example of a footer:
;;;;"TOTAL";;"-600.22";"2020-08-31";"173.78";"774.00";
;;;;"New balance";;;2020-09-01;;3782.86;
;;;;"Outstanding credit transfers/reimbursements";;;2020-09-01;;0.00;
;;;;"Outstanding fees";;;2020-09-01;;0.00;
;;;;"Minimum balance";;;2020-09-01;;2000.00;
;;;;"Available funds";;;2020-09-01;;1782.86;Check the file integrity
You can ensure the integrity of the reporting file by using these two formulas:
Previous balance + Total credits – Total debits = New balance
New balance – Outstanding credit transfers and reimbursements – Outstanding fees – Reserve = Available funds
Complete example
"Line";"Execution_Date";"Transaction_ID";"Client_Reference";"Debtor_Name";"OP_Code";"Amount";"Value_Date";"Credit_value";"Debit_value";"Label";"Invoice_Reference";"Initial_Transaction_ID";
"6";"2020-09-01";;"CyberPress";
;;;;"Previous balance";;;"2020-08-01";"4383.08";
"1";"2020-08-17";"REF-Trans-01000012";"REF-Cli-65412";"John Doe";"SDD";"157.23";"2020-08-18";"157.23";;"First payment of tuition fees for 2020";"Bill_1647";
"2";"2020-08-17";"REJ-EXE-20200817-194";"REF-Cli-65412";"John Doe";"REJ";"-157.23";"2020-08-18";;"157.23";"R-Transaction: AM04 - Insufficient funds";"N/A";"REF-Trans-01000012";
"3";"2020-08-23";"REB-EXE-20200823-286";"A64323";"Jane Doe";"REB";"-16.55";"2020-08-23";;"16.55";"Reimbursement for our Golden Ticket operation";"N/A";
"4";"2020-08-26";"REB-REJ-20200826-281";"A64323";"Jane Doe";"ORB";"16.55";"2020-08-27";"16.55";;"R-Transaction: AC04 - Account is suspended / terminated";"N/A";"REB-EXE-20200828-286";
"5";"2020-08-29";"SCT-EXE-20200829-282";"153";"Hooli";"SCT";"-600.00";"2020-08-30";;"600.00";"SlimPay credit transfer";"N/A";
"6";"2020-08-31";"SCT-FEE-20200831-202";"153";"Hooli";"FEE-SCT";"-0.22";"2020-08-31";;"0.22";"Execution fee of 1 credit transfer(s) at 0.180 euro per unit";"N/A";
;;;;"TOTAL";;"-600.22";"2020-08-31";"173.78";"774.00";
;;;;"New balance";;;2020-09-01;;3782.86;
;;;;"Outstanding credit transfers/reimbursements";;;2020-09-01;;0.00;
;;;;"Outstanding fees";;;2020-09-01;;0.00;
;;;;"Minimum balance";;;2020-09-01;;2000.00;
;;;;"Available funds";;;2020-09-01;;1782.86;
And if we check:
4383.08 + 173.78 - 774.00 = 3782.86
3782.86 - 0.00 - 0.00 - 2000.00 = 1782.86
Reporting via camt.053 Family/Subfamily
It is possible to utilize the ISO20022 CAMT.053.001.02 format from the CFONB as the account statement for the reconciliation process. This format incorporates families and sub-families, which serve as standard tags employed to specify the nature of each transaction.
Below is a table illustrating the definition of each family and sub-family with the corresponding direction (C for Credit, D for Debit) and operation type:
| Category | Family | Sub-Family | Direction | Operation Type |
|---|---|---|---|---|
| SDD | IDDT | ESDD | C | SDD |
| SDD | IDDT | BBDD | C | SDD B2B |
| SDD | IDDT | UPDD | D | R-Transaction of SDD |
| SDD | IDDT | UPDD | D | R-Transaction of SDD B2B |
| SCT | RCDT | ESCT | C | SCT in (including PIS payments) |
| SCT | ICDT | ESCT | D | SCT out (Payout and reimbursements) |
| SCT | ICDT | RRTN | C | R-Transaction SCT out |
Understanding the XML Tags
The CAMT.053 format uses specific XML tags to categorize and describe the types of transactions. Below is an example of how these tags are structured:
<BkTxCd>
<Domn>
<Cd>PMNT</Cd>
<Fmly>
<Cd>IDDT</Cd>
<SubFmlyCd>ESDD</SubFmlyCd>
</Fmly>
</Domn>
</BkTxCd>
This XML structure is used to define the domain, family, and sub-family codes for a payment transaction. In this example:
- Fmly > Cd: This tag represents the family code, "IDDT" in this case.
- SubFmlyCd: Defines the sub-family code, "ESDD" indicating a specific type of direct debit transaction.
For more information on the camt.053.001.02, refer to the official documentation in the CFONB - CAMT.053 Guide