Bank, cash desk and statements
The statement goes straight into the ledger. The basic scenario does not depend on whether the bank is ready for integration: a statement file covers the main need, and payment orders go back to online banking in a format it understands.
Plan Statement import on all plans, cash desk, expense reports and payment orders from the “Accounting” plan.
What is inside
- Import of statements in 1C, CSV and MT940 formats for any period
- Counterparty matched by bank details, category by payment purpose
- Matching learns from decisions confirmed by the user
- Duplicate protection by bank transaction identifier
- Export of payment orders to online banking
- Cash registers, cash book, cash balance limit, cash orders, cash count
- Expense reports, monetary documents, acquiring registers with the bank fee
- Deposits, bank guarantees, letters of credit, account blocks and restrictions
Limits
Bank exchange runs on files: statements are uploaded, payment orders are exported. This works with any bank that offers online banking.
Frequently asked questions
Which banks are supported?
Any bank that exports a statement in 1C, CSV or MT940 format. Almost every online banking system in the five countries offers such an export.
What happens if I upload the same statement twice?
Repeated lines are rejected: the system recognizes them by the bank transaction identifier.
Is acquiring supported?
Yes. Acquiring registers come from A3.Sales, and the bank fee is booked as a separate posting and does not reduce revenue.
Use cases with this feature
Other features
Start with a bank statement
Upload last month’s statement and see your cash flow before setting anything up. If you need to move from 1C or work in several countries, we will show it on your data.