- Custom n8n node
- Banking & Finance
- AI-agent tool
Bulgarian Banks
Turn Bulgarian bank statements (PDF, Excel, CSV) into clean, uniform transaction rows.
How it works in practice
Every bank's statement, read the same way
How we apply it
In the bank reconciliation robot we built for a Bulgarian accounting firm, this is the step between the statement download and the posting: about 90% of bank transactions then reconcile and post without an accountant.
This node reads statement files exported from Postbank, Citibank, UBB and DSK Bank and emits one normalised transaction per n8n item: account, currency, credit or debit, counterparty and IBAN, amount, description, dates, document number and running balance. A separate Detect Bank operation identifies the bank, format and account holder from the file itself, so one mailbox of mixed statements can be routed without sorting by hand.
Stock n8n has no idea what a DSK daily statement or a Citibank details report looks like, and every Bulgarian bank exports something different. Until now that meant a Code node per bank, copied between workflows and broken by every column shuffle. Here the Excel and CSV parsers find columns by header, so a reordered export still works, and a built-in filter with nested AND/OR groups keeps only the rows a workflow cares about.
We use it every day in our own bank-statement and reconciliation automations: 22 production workflows at the time of writing, mostly on the UBB and DSK Excel parsers and Detect Bank. It sits between the mailbox or portal download and the step that posts to the accounting system.
Limits: PDF parsing depends on the bank's layout. UBB PDF is marked beta because the statement text is unstructured, and the Postbank PDF operation is a placeholder that returns a "not yet implemented" message, so use the Postbank Excel export instead. Only the four banks above are supported.
For your technical team: it installs from npm as
What it means for you
No more retyping of statement lines
The same clean result from every bank, so later steps stay simple
A reshuffled export from a bank does not break the process
More nodes we built
- Government & RegistriesBulgarian Registry AgencyA new customer, checked against the official registerNobody copies register data by hand from a browser tabAI-agent tool
- Documents & AIDocument AIA mixed scan, sorted into readable invoicesNobody splits or types invoices by handAI-agent tool
- Data & SpreadsheetsExcelA finance template, filled in without touching its lookNo copy-paste into spreadsheetsAI-agent tool
- ERP & AccountingMicroinvestPayments and invoices posted straight into the booksNobody re-keys entries one by oneAI-agent tool
- SecurityPassboltSigning in to a portal without a password in sightPasswords live in one place, not scattered across automationsAI-agent tool
- Documents & AIPDFOne big scan, cut into one file per documentNo manual splitting in a PDF viewerAI-agent tool
- Web AutomationPlaywright browserStatements collected from portals with no integrationNo more clicking through portals by handAI-agent tool
- Web AutomationRobot Framework runnerAn old Windows program, operated by a robotThe old software stays, with no forced replacementAI-agent tool
- Files & StorageSeaweedFS storageDocuments kept safely in storage you ownNo lock-in to a cloud vendorAI-agent tool
- Microsoft 365SharePointDocuments filed in SharePoint, where people lookNo manual filing or renamingAI-agent tool
- Files & StorageSMB network shareFiles exchanged with old systems through a shared folderOlder systems keep working as they areAI-agent tool
Want Bulgarian Banks in your n8n?
Tell us what the workflow has to do and what it connects to. We will say whether this node covers it as it stands, what we would add, and when a different approach is the better one.
