EBICS is the Electronic Banking Internet Communication Standard, which is used to communicate with your bank on your behalf.
EBICS is an internationally agreed ISO standard that is supported by all European banks. Accounting as a Service is already connected to the following banks:
To enable Accounting as a Service to communicate with your bank, the Accounting as a Service Team needs to receive EBICS users (technical users that are allowed to receive the settlement files and provide payouts and direct debit requests). The user has to have transport- and read-only-rights. All approvals, e.g. for outgoing payments from returns, have to be made by you yourself (the merchant) due to regulatory reasons.
Please contact your bank and ask for the EBICS request form, which needs to be filled by Riverty and signed by you (as the owner of the account).
Please note: For every business code that will be used, a separate bank account needs to be set up. Therefore the users need to have access to all accounts.
To enable Accounting as a Service to process the account statements, these need to be in a supported format. Accounting as a Service currently supports the CAMT-format (link). Bank statement format needs to be CAMT.053
CAMT.053 for incoming payment transfers and sums
CAMT.054 for direct debit transactions
The following structure is defined by ISO and should be used:
For payouts (bank transfers to your end-customers bank accounts), Accounting as a Service uses the file-format pain.001, which will be handed over by Accounting as a Service to your bank.
For captures using direct debit, Accounting as a Service uses the file format pain.008, which will be handed over by Accounting as a Service to your bank. Please make sure to ask your bank partner for your SEPA creditor identification number.
Furthermore, Accounting as a Service is set up to process the CAMT.054 for the reveresed direct debit single transactions. This must be requested from your bank.