v16.0.0

Features

• Adds "Create SEPA Payment Order" action in Expense Claim form and list views, allowing approved claims to be converted into SEPA Payment Orders using the employee’s bank details and recording their new SEPA status. (#352)

Authors: @MarcCon
Reviewers: @barredterra

AI content

For these release notes, we used an LLM (OpenAI o3) to review and summarise the code changes, along with the associated issue and PR descriptions. It may contain typical errors and inaccuracies. You can read the prompt here.

Changes with the following labels were excluded:

• skip-release-notes

Changes with the following types were excluded:

• ci
• build
• refactor
• style
• docs
• chore
• test

v15.34.0

Features

• Adds a Cross-Currency option in Bank Reconciliation so you can match a bank transaction to vouchers in a different currency. A guided dialog requests the exchange rate and validates the converted amount before completing the reconciliation. (#343)
• Adds the new Bank Reconciliation Rule DocType; when you submit a Bank Transaction, the first matching rule now automatically creates and reconciles a Journal Entry. (#347)

Authors: @barredterra
Reviewers: @0xD0M1M0

AI content

For these release notes, we used an LLM (OpenAI o3) to review and summarise the code changes, along with the associated issue and PR descriptions. It may contain typical errors and inaccuracies. You can read the prompt here.

Changes with the following labels were excluded:

• skip-release-notes

Changes with the following types were excluded:

• ci
• refactor
• style
• build
• test
• chore
• docs

v15.33.0

Features

• Adds "Add Recipient" button to SEPA Payment Order, letting users pick an existing Supplier or Employee; the dialog also opens on new rows and automatically fills the recipient’s name and IBAN in the payments table. (#354)

Bug Fixes

• Adds specific permissions that let Accounts Managers fully manage SEPA Payment Orders and allow Accounts Users to create and update their own orders. (#356)
• Uses the bank transaction’s Date when creating payment entries in Bank Reconciliation Tool (Beta), so early-payment discounts are correctly applied. (#357)
• Creating SEPA Payment Orders for employee expenses now uses the employee’s IBAN if no Bank Account is linked. The warning in the Employee form is updated to state that this IBAN is ignored once a Bank Account is present. (#358)

Authors: @barredterra, @MarcCon, @PatrickDEissler
Reviewers: @barredterra, @greptile-apps[bot]

AI content

For these release notes, we used an LLM (OpenAI o3) to review and summarise the code changes, along with the associated issue and PR descriptions. It may contain typical errors and inaccuracies. You can read the prompt here.

Changes with the following labels were excluded:

• skip-release-notes

Changes with the following types were excluded:

• test
• style
• refactor
• docs
• build
• ci
• chore

v15.32.1

What's Changed

• Adds a fallback that fills Bank Party Name with the counterparty’s address when importing SEPA statements, so Bank Transaction entries from certain Swiss banks still display useful payer information even if no name is provided. (#355)

Full Changelog: v15.32.0...v15.32.1
Authors: @barredterra

AI content

For these release notes, we used an LLM (OpenAI o3) to review and summarise the code changes, along with the associated issue and PR descriptions. It may contain typical errors and inaccuracies. You can read the prompt here.

Changes with the following labels were excluded:

• skip-release-notes

Changes with the following types were excluded:

• test
• build
• style
• refactor
• ci
• docs
• chore

v15.32.0

Features

• Adds the party’s title to each entry in the "Match Voucher" tab of Bank Reconciliation so users can immediately see who the voucher relates to.
  Also hides the Party filter when no parties exist and refines the filter labels and layout for clearer navigation. (#327)
• Importing MT940 bank statement files now accepts UTF-8, Latin-1, and CP1252 encodings, preventing errors when a file uses non-UTF-8 characters. (#336)
• Adds a filter that hides Journal Entries whose Reference Number matches the current bank transaction from the matching list in Bank Reconciliation Tool Beta, preventing auto-generated entries from cluttering the suggestions. (#330)
• The Bank Reconciliation Tool Beta now lets you create and edit a draft Journal Entry even when the selected account is in a different currency, and stops submission only if the currencies still don’t match. (#329)
• Adds support for "Read Only" field type when selecting reference fields in Banking Settings, so you can now pick read-only fields alongside link or data fields. (#344)
• Converts any negative numbers in imported Bank Transaction Deposit, Withdrawal, and Fee fields to positive amounts, preventing wrong balances during reconciliation. (#345)
• EBICS imports now read charges from SEPA CAMT files and fill the Included Fee amount in each new Bank Transaction when the fee currency matches the transaction currency. (#348)

Bug Fixes

• Fixes incorrect currency handling in Bank Reconciliation Tool Beta: it now shows the correct outstanding amount for multi-currency Purchase Invoices and produces matching Payment Entry values during reconciliation. (#338)
• Adds "Skipped" status to EBICS Request and treats unresolved batch transactions as skipped, so they are automatically retried during the next sync instead of being marked successful and overlooked. (#332)

Authors: @0xD0M1M0, @barredterra, @PatrickDEissler
Reviewers: @barredterra

AI content

For these release notes, we used an LLM (OpenAI o3) to review and summarise the code changes, along with the associated issue and PR descriptions. It may contain typical errors and inaccuracies. You can read the prompt here.

Changes with the following labels were excluded:

• skip-release-notes

Changes with the following types were excluded:

• chore
• docs
• test
• ci
• style
• refactor
• build

v15.31.1

What's Changed

• Currency fields in Bank Reconciliation now display the transaction’s currency even when no Bank Account is selected. The "Submit" button is replaced by a "Save" button that only becomes visible after you edit the details. (#323)
• Imports CAMT and MT940 statements even when the provided IBAN is invalid, recording the value in Bank Party Account Number instead of Bank Party IBAN. (#334)

Full Changelog: v15.31.0...v15.31.1
Authors: @barredterra
Reviewers: @0xD0M1M0

AI content

For these release notes, we used an LLM (OpenAI o3) to review and summarise the code changes, along with the associated issue and PR descriptions. It may contain typical errors and inaccuracies. You can read the prompt here.

Changes with the following labels were excluded:

• skip-release-notes

Changes with the following types were excluded:

• style
• build
• test
• refactor
• ci
• docs
• chore

v15.31.0

What's Changed

• Adds "Re-Import" button to EBICS Request, letting you import transactions again from the stored bank response and showing an error if Download Batch Transactions is turned off. (#320)

Full Changelog: v15.30.0...v15.31.0
Authors: @barredterra

AI content

For these release notes, we used an LLM (OpenAI o3) to review and summarise
the code changes, along with the associated issue and PR descriptions. It may
contain typical errors and inaccuracies. You can read the prompt
here.

v0.25.0

What's Changed

• Uninstalling the banking app now also deletes the custom fields it added and rolls back its form property changes, restoring the original setup. (#312)
• Assigns a unique ID to each sub-transaction imported from CAMT batch files, so every payment in a batch now appears separately in Bank Transaction. Removes the uniqueness requirement on Transaction ID, allowing entries that share the same bank reference to be saved together. (#313)
• Automatic bank transaction sync now runs every four hours between 06:14 and 22:14 instead of once overnight. It retries until a successful C53/Z53 EBICS Request is logged, reducing missed late-day transactions while preventing duplicates. (#317)

Full Changelog: v0.24.0...v0.25.0
Authors: @barredterra
Reviewers: @barredterra, @PatrickDEissler

AI content

For these release notes, we used an LLM (OpenAI o3) to review and summarise
the code changes, along with the associated issue and PR descriptions. It may
contain typical errors and inaccuracies. You can read the prompt
here.

v15.30.0

What's Changed

• Automatically recalculates payment amounts in SEPA Payment Order based on the execution date, taking early-payment discounts into account. Shows an "Update Amounts" button and a confirmation prompt so users can refresh these figures before submitting the order. (#310)
• Automatic bank transaction sync now runs every four hours between 06:14 and 22:14 instead of once overnight. It retries until a successful C53/Z53 EBICS Request is logged, reducing missed late-day transactions while preventing duplicates. (#316)

Full Changelog: v15.29.0...v15.30.0
Authors: @PatrickDEissler, @barredterra
Reviewers: @PatrickDEissler, @barredterra

AI content

For these release notes, we used an LLM (OpenAI o3) to review and summarise
the code changes, along with the associated issue and PR descriptions. It may
contain typical errors and inaccuracies. You can read the prompt
here.

v15.29.0

What's Changed

• Shows the Party IBAN on the "Match" tab in four-character blocks for easier reading. (#302)
• Updates Bank Reconciliation Tool Beta to fetch transactions based on their Status rather than skipping those with an Unallocated Amount under 0.001, so very small-value entries now appear in the list. (#303)
• Makes the Bank Account filter optional in Bank Reconciliation Tool; you can filter by Company or Bank instead, while each transaction still displays its Bank Account in the Details tab. (#289)
• Fixes the bank filter in Bank Reconciliation Tool so that it displays all available banks once, sorted alphabetically. (#304)
• Uninstalling the banking app now also deletes the custom fields it added and rolls back its form property changes, restoring the original setup. (#311)
• Assigns a unique ID to each sub-transaction imported from CAMT batch files, so every payment in a batch now appears separately in Bank Transaction. Removes the uniqueness requirement on Transaction ID, allowing entries that share the same bank reference to be saved together. (#305)

New Contributors

• @0xD0M1M0 made their first contribution in #304

Full Changelog: v15.28.0...v15.29.0
Authors: @0xD0M1M0, @barredterra
Reviewers: @0xD0M1M0, @barredterra, @PatrickDEissler

AI content

For these release notes, we used an LLM (OpenAI o3) to review and summarise
the code changes, along with the associated issue and PR descriptions. It may
contain typical errors and inaccuracies. You can read the prompt
here.