Introduction
SlimPay allows merchants to generate a range of reports offering information about their business activity. These include account statement reports, mandate reports and R-transaction files.
This article covers:
- Account Statement Report
- How to read the balance summary
- How to download reports
- How can I read my reporting?
- Mandate Report
- Unpaid Transaction Report
Account Statement Report
An account statement report contains a summary of all transactions that impact the merchant’s SlimPay bank account over a specific analysis period. Available in CSV format, the report will help merchants reconcile their financial data by recording all incoming credits (SDD and card payments) and outgoing debits (SEPA Credit Transfers and SDD fees).
|
Important note: Fees associated with executed transactions are directly applied to your SlimPay account and indicated in your monthly invoice (sent by mail to your nominated contact person). Fees linked to card transactions are not in the reporting. These fees will be available on your monthly invoice. |
How to read the balance summary
The balance summary is here to help you understand what is happening on your SlimPay account. It is a summary of the important numbers (the details will be then available on your reporting).
|
|
DASHBOARD V.2
|
DASHBOARD V.1 also called Back Office |
|---|---|---|
|
Where can I find it |
Reporting tab |
Manage payments tab > Reporting |
|
Details of the amounts |
Statement balance: €1000 Variable reserve: €550 Available funds: €450 |
Statement balance at 01/01/2019: 0€ Statement balance at 31/01/2019: €1000 Transfers/Reimbursements in progress: €0 Current costs: €10 Minimum balance: €300 Available funds at 31/01/2019: €690 |
How to download reports
|
DASHBOARD V.2
|
DASHBOARD V.1 also called Back office |
API |
|---|---|---|
|
Reporting tab>select dates > Download Report |
Manage payments tab, Reporting section>select dates > search > Download report |
|
NB: If you are still using the first version of the Dashboard (also known as the Back Office), do not hesitate to request access to the Dashboard V.2 at support@slimpay.com |
How can I read my reporting?
The reporting allows you to have a global overview of your activity for a specific period of time. The information you can find in it are:
| Column name (see header) | Description |
|---|---|
| "Line" | Number of the line, from 1 to N |
| "ExecutionDate" | Execution date of the transaction |
| "Transaction_ID" | Unique reference of the transaction |
| "ClientReference" | Unique client reference provided by the merchant |
| "DebtorName" | Debtor's first and last name (individual) or the company name (corporate) |
| "OPCode" | Type of the transaction (you can find all the operational code here) |
| "Amount" | Amount of the transaction |
| "ValueDate" |
For direct debits, it is the date when the funds are credited to the account. For rejects and returns, it is the date when the funds are debited from the account. For other operations, the value date is generally equal to the execution date. |
| "Creditvalue" | Amount credited to the account |
| "Debitvalue" | Amount debited from the account |
| "Label" | Label of the transaction |
| "InvoiceReference" | Invoice reference provided by the merchant |
| "InitialTransactionID" | For rejects and returns, the "Transaction_ID" value of the initial transaction |
If you want more information and reporting examples, you can visit the dedicated page on our Dev Center.
Mandate Report
Merchants can nominate to receive a mandate report, which offers a complete overview of all SEPA mandates that have been created, amended or revoked for a given period of time. Transmitted in CSV format, the file can be generated automatically at regular intervals, or manually via the Dashboard. Click here for instructions on downloading a mandate report using the Dashboard.
Unpaid Transaction Report
In the event that payments fail, SlimPay generates a file detailing the reasons why the transactions were not successful. A merchant can nominate to have these R-transaction files generated automatically in hourly, daily, weekly or monthly intervals. These files are transmitted in CSV or camt.054 (XML) format.
R-transaction file names have different prefixes, depending on the type of payment failures it contains:
- An NOP file is a summary of all transactions that were rejected by SlimPay before execution for internal system reasons
- A REJ file is a summary of all transactions that were rejected by the banks after execution (separate REJ files are created for SDD, SCT and card transactions)
- A CRE file is a summary of card transactions that were rejected by the banks after execution
A merchant can choose to combine the NOP and REJ files into a single REJ, rather than receiving them separately. If you would like to activate this option, get in touch with our Customer Success team.
For more details on the structure of R-transaction files, please refer to our Dev Center.