Embedded Files
Turn your spreadsheet into scheduled bank payments
Turn your spreadsheet into scheduled bank payments
You already have the list of who to pay in Excel — or your accounting program exported a CSV. Each line can have a different payer and different payee, even from different banks or companies. This guide shows how to upload that file, turn it into proper bank payment files, save them, and let the system send them automatically on time — all from the app, with clicks only.
How it usually goes
How it usually goes
Your accounting exports a spreadsheet with dozens or hundreds of payments. One line: pay supplier A from your Berlin account. Next line: pay supplier B from your Paris account. Different payers, different banks.
Someone then has to split the file by bank, create the special bank format by hand, check each IBAN, and remember to upload each file at the right time. One typo and the bank rejects it — often just before the deadline.
How it goes with this flow
How it goes with this flow
You upload one spreadsheet file. The app reads every line.
It checks every account, creates any missing payees, and makes correct bank files for each bank automatically.
Files are saved in your Payment Library — you can open, check, or fix them anytime.
You put them into a scheduled queue and pick when they should be sent — e.g. every day at 9:30. The system sends them for you.
If you handle money for more than one account, this is for you
If you handle money for more than one account, this is for you
A group with several companies. One finance team pays suppliers for 5 companies. Each company has its own bank. One spreadsheet has all payments together — debtors are different on each line. The system sorts it out so each bank gets only its own payments.
An agency that pays for many clients. A payroll office or fiduciary that runs payments for dozens of clients. The file contains many client accounts as payers and many suppliers as payees. The library keeps each client's history; the scheduler makes sure nothing is sent late.
Finance team that lives in Excel. You don't want to learn bank file formats. You already work with spreadsheets. This flow feels like uploading an Excel file and clicking “Next” — no XML, no special knowledge.
For step-by-step visual instructions check out the presentation slides — they walk you through completing the setup.
- Prepare your spreadsheet
Prepare your file — one spreadsheet is enough. Use the export your accounting already makes, or create a simple Excel/Sheets file. One clean source for all banks. Create a single spreadsheet with all payments, even with mixed banks/companies, including payee/payer names+IBANs, amounts, optional currency/notes and delimiters vary.
2. Import payment from spreadsheet
2. Import payment from spreadsheet
Open Banking → Payments Library in the menu and click Import spreadsheet. A window guides you step by step: preview totals, resolve unknown accounts to the correct bank, confirm type — nothing is sent before you approve.
3. Manage payments in library
3. Manage payments in library
Every file you create is saved here. Think of it like a folder for bank payments — each file can hold many individual payments. You can keep as many files as you like, for different months, banks, or purposes. Keep bank files organized, reusable and easy to fix.
4. Schedule payment sending
4. Schedule payment sending
Saving is step one. Sending on time is step two. Deliver on time without manual clicks. Create a job per bank defining when to send, place library files in its queue which holds until the time (e.g. daily 09:30) and sends ready files automatically, skipping outdated.
FAQ – Spreadsheet to Scheduled SEPA Payments
FAQ – Spreadsheet to Scheduled SEPA Payments
- What file do I need to start?
One spreadsheet is enough — Excel/Sheets export or CSV from accounting. One row per payment with payer name+IBAN, payee name+IBAN, amount, optional currency/notes. Mixed banks, companies, payers and payees can stay in one file; the app sorts per bank automatically.
- How does import handle unknown accounts?
Banking → Payments Library → Import spreadsheet → Preview Orders (totals) → Check Accounts → select connection → Create Accounts → Import Payment. Unknown payees/payers are created, IBANs validated, correct pain.001/pain.008 files generated per connection. Nothing is sent before you approve.
- Where are generated payments stored?
In Payment Library — encrypted, searchable folder of bank files, each holding many orders. Open, check, edit, Store multiple to Library to split by connection (e.g. 2 payments for 2 banks). Export back to CSV anytime for audit.
- How do payments send automatically on time?
Per bank: Scheduler Jobs → Schedule Regular Job (connection + CCT/CDD + cron, e.g. daily 09:30) → Run → Queue → Upload payment to queue → Select in Library → Upload → Edit filename to match path mask. Job sends ready files automatically, skips outdated. No manual clicks, no XML knowledge needed.
- Who is this flow for?
Groups paying for 5+ companies from one spreadsheet, payroll/fiduciary agencies paying for dozens of clients (per-client history in Library), and Excel-based finance teams who want upload-and-click-Next without learning ISO 20022 or splitting files by bank by hand.
Page updated
Google Sites
Report abuse