Actions8
- Account Actions
- Transaction Actions
- User Management Actions
Transaction → Export Transactions
AI-generatedOverview
This node operation exports bank account transactions using the AqBanking interface, supporting the FinTS/HBCI protocol commonly used by German banks. It allows users to specify the account by IBAN or account number and bank code, select a date range for the transactions, and choose the output format (CSV or JSON). The node is useful for automating the retrieval and export of transaction data for further processing, reporting, or integration with other financial tools.
Use Case Examples
- Export transactions for a specific bank account over the last 30 days in CSV format for accounting purposes.
- Retrieve all available transactions in JSON format for data analysis or integration with a financial dashboard.
Properties
| Name | Meaning |
|---|---|
| Account Number/IBAN | The bank account number or IBAN to query for transactions. |
| Bank Code (BLZ) | Bank code (BLZ), required only if using account number instead of IBAN. |
| Date Range | The date range for which to export transactions, with options like all available, last 30 days, last 90 days, or a custom range. |
| Start Date | The start date for the transaction query, used only if a custom date range is selected. |
| End Date | The end date for the transaction query, used only if a custom date range is selected. |
| Additional Options | Additional options to customize the export, including simplifying output, including raw AqBanking output, limiting the maximum number of results, and selecting the output format (CSV or JSON). |
Output
JSON
transactions- Array of transaction objects including details like amount, currency, date, remote name, purpose, remote IBAN, remote BIC, and transaction code.count- The number of transactions returned.accountNumber- The account number or IBAN used for the query.bankCode- The bank code (BLZ) used for the query, if applicable.dateRangestartDate- The start date of the transaction query range.endDate- The end date of the transaction query range.
timestamp- The timestamp when the data was retrieved.csvData- The exported transaction data in CSV format (present only if CSV output format is selected).format- The format of the exported data, either 'csv' or 'json'.rawOutput- Optional raw output from AqBanking if requested in additional options.
Dependencies
- AqBanking CLI tools or native FinTS client implementations
Troubleshooting
- Ensure the account number or IBAN is provided; missing this will cause an error.
- If using account number instead of IBAN, the bank code (BLZ) must be provided.
- Date range parameters must be valid; custom ranges require both start and end dates.
- Errors from the underlying AqBanking CLI or native client will be propagated; check logs for detailed error messages.
- If the output format is CSV, ensure the data is properly parsed and formatted; malformed CSV may indicate parsing issues.
Links
- AqBanking Official Website - Official site for AqBanking, the software used for FinTS/HBCI banking protocol interaction.
- FinTS (Financial Transaction Services) - Wikipedia page explaining the FinTS protocol used by German banks.