A jointly scoped pilot with agreed systems, examples and acceptance criteria.
Clarify supported EBICS order types, file formats and permissions with the bank
Set up a read-only statement import and reference mapping
Reconcile balances, transactions, batch entries and repeated imports
Scope, project price, schedule and required provider services are agreed before commissioning. Handover includes the agreed technical documentation and introduction.
Monitor one read-only bank data import and handle format changes and technical responses.
Technical takeover of the agreed existing solution
Agreed monitoring, troubleshooting and change maintenance
Documented handover of open issues and completed changes
Monthly price, allowance, service hours, term and cancellation are agreed separately. Infrastructure, licences and on-call support are included only when explicitly offered.
Bank, number of accounts and existing EBICS/software version
Anonymised statements and the required processing in the target system
A description is enough for your first enquiry. We will then agree suitable ways to exchange files and arrange access.
What the scope covers
The initial package covers read-only data imports only. Payment authorisation, bank contracts and signing keys remain with the customer. Supported formats and retirement dates are checked with the specific bank.
We check the package against your project. Your enquiry is non-binding; commissioning and scheduling are agreed afterwards.
UNDERSTAND THE TOPIC
From MT940 to camt: more than a different filename.
Deutsche Kreditwirtschaft has no longer listed MT940 and MT942 as DK standards since 23 November 2025. This does not mean every bank switched off these files on the same day. Other announced retirement dates for payment formats have also been postponed. Your specific bank connection is therefore the starting point for any migration.