Bank statement rows matched and booked in sevdesk
Statement rows land in a Google Sheet. This flow matches each one to an open invoice or voucher in sevdesk, books the clear matches, handles personal items, and lists the rest for review.
The prompt
When a new bank statement row lands in our statement sheet in Google Sheets, get our open invoices, unpaid vouchers and private transaction rules from sevdesk. Match the row: an invoice or voucher only when the amount is exact and the reference or name points to that one document, private only for a recurring personal payment, and review for everything else. Post the row to our sevdesk file import account. Book a matched invoice or voucher against it. For a private item, create a private rule for that payee unless one already exists, and mark the row private. Add everything else to a review sheet with the reason. Never enshrine anything.
FlowRunner Prompt to Flow built this flow from that request. Here it is as it opens in the editor.
The flow
Download the file, then in FlowRunner click + beside Flows, pick it under Import a Flow Version and click Create. How importing works
What each step does
- New statement row Checks your statement sheet in Google Sheets every 5 minutes for new rows, whatever column names your bank's export uses.
- Get open invoices Lists up to 100 open invoices and up to 100 unpaid vouchers in sevdesk, along with the rules that already mark personal transactions as private.
- Match the row An AI agent reads the row and decides. It picks an invoice or voucher only on an exact amount that points to one document, private for a recurring personal payment, and review for anything else.
- Post the row to sevdesk Creates the transaction on your file import account, the one sevdesk fills from CSV or MT940 files. If there is none, the run stops with a clear error.
- Book the invoice Books the payment against the matched invoice and links the transaction, which marks the invoice paid. A matched voucher is booked and linked the same way.
- Mark the row private For a private item, the flow creates a rule for the payee unless one already exists, so their future rows mark themselves private. Then it sets the transaction to private, which keeps it out of the books.
- Add it to the review list Everything else goes to your review sheet in Google Sheets as one line with the date, amount, payee, purpose, the reason and the sevdesk transaction ID. Nothing in the flow enshrines a transaction.
Before you turn it on
- Enter your sevdesk API token and connect your Google account.
- Add your Anthropic key in the flow setting Anthropic key.
- Have one file import account in sevdesk for CSV or MT940 statements. Create it in sevdesk if you don't have one; the flow posts to the first one it finds.
- Pick your statement sheet in New statement row, and a review sheet with the columns Date, Amount, Payee, Purpose, Reason and Transaction ID in Add it to the review list.