Skip to content
Aritma · Product updates

Release notes

What’s new in SweBase and Finance Manager. Browse the latest changes, improvements and fixes.

Subscribe to updates

Get release notes for SweBase and Finance Manager by email.

SweBase release notes

Version 28.5Latest · 5 entries
Requires

Version 28.0 of Business Central

Added

Banking - Added integration events for modifying General Journal Lines in Banking Payment API

Reference: #747

Added

Banking - Added support for specifying "Address format" to structured/hybrid or legacy on the VP Girotype card

Reference: #746

Fixed

SIE Export - Support for dates when exporting a broken fiscal year

Fixed

When printing a fully archived invoice, fetch information from archive instead of sales line

Version 28.43 entries
Requires

Version 28.0 of Business Central

Fixed

General - Improved VAT and currency calculations in Inward Registration for more accurate processing

Reference: #741

Fixed

Tax Reduction - Refined tax reduction calculations to improve accuracy and maintainability

Reference: #742

Version 28.35 entries
Requires

Version 28.0 of Business Central

Added

Banking - Added OnBeforeInsertInfoLineTempStrdInf event in Banking Payment API

Reference: #738

Added

Documents - Added OnBeforeC90_OnBeforeInvoiceRoundingAmount event for customizing invoice rounding amount handling i "PEB BaseCodeunits"

Reference: #737

Fixed

Documents - Fixed report selection so email attachments are included correctly when sending documents

Reference: #737

Fixed

General - Added funcionality to use alternative posting currency when posting inward registrations

Version 28.22 entries
Requires

Version 28.0 of Business Central

Improved

Banking - Updated SEPA country support to align with the current European Payments Council country list, enabling SEPA payment processing for additional participating countries and territories

Reference: #729

Version 28.15 entries
Requires

Version 28.0 of Business Central

Fixed

Banking - Payment files now clean unsupported characters from company addresses, improving compatibility with banks that validate Pain001 address data

Reference: #715

Fixed

Banking - Improved payment-pack status handling so closed vendor, customer, and employee ledger entries are associated with the correct payment pack

Reference: #715

Fixed

Inward Registration - Accounts Payable Inward reports now exclude entries with no amount, preventing empty or irrelevant lines from appearing in the report

Reference: #715

Improved

Developer Experience - Made report ID conversion available to extensions, making it easier to customize report selection and document delivery

Reference: #715

Version 28.021 entries
Requires

Version 28.0 of Business Central

Added

Banking - Added BACS ID field to VP Giro Type with updated logic in Pain001 for BACS payment processing

Reference: #681

Added

Banking - Enhanced IBAN handling for non-domestic Swedbank transactions with domestic/international routing check

Fixed

Banking - Added CheckVPPackNumberOnLedgerEntries procedure to validate VP pack numbers on ledger entries

Reference: #701

Fixed

Banking - File upload to journal now shows an error instead of silently clearing the journal

Fixed

Banking - Added FileName parameter to GetJournal procedure, fixing file name handling in Banking Payment API and Pagero Management

Reference: #684

Fixed

Banking - Removed redundant ReadingLineNo updates in CAMT Credit and Debit Management codeunits

Reference: #687

Fixed

Banking - Fixed vendor reference in bank account retrieval for Purchase Header

Reference: #698

Fixed

Banking - Bank accounts with pending approvals can no longer be deleted accidentally

Reference: #683

Added

Documents - Added VAT specification headers to PEB Sales Order report

Reference: #696

Added

Documents - Added option to exclude Item Reference No. in reports with enhanced Page Header setup

Reference: #702

Fixed

Documents - Finance Charge Memo report now correctly includes Total Rounding Amount in calculations

Reference: #685

Fixed

Documents - Item line numbers now correctly assigned for Sales Credit Memo and Invoice in PEB Preview Invoice

Reference: #682

Added

General - Added integration event for CheckMaxRounding procedure to allow partner extension hooks

Reference: #704

Added

General - PEB OCR No. is now correctly passed to General Journal Lines in VP Management

Reference: #671

Fixed

General - Enhanced posting period date validation to include DateFormula checks in GL Setup and User Setup

Reference: #699

Added

Tax Reduction - Added new fields for Fixed Other Cost % and Amount to Apply for improved ROT/RUT calculations

Reference: #624 #625

Added

Tax Reduction - New action to calculate share percentage automatically based on amount to apply

Reference: #624 #625

Added

Tax Reduction - Added FileNamePrefix handling for ROT and RUT types in tax reduction file creation

Fixed

Tax Reduction - Tax reduction entries now only inserted when a remaining amount exists

Fixed

Tax Reduction - Improved handling of not-granted amounts with new SweBase Setup configuration options

Reference: #624 #625

Earlier release notes

Earlier release notes

Version 27.25 entries
Requires

Version 27.0 of Business Central

Fixed

General - Removed non-deductible VAT translation entries from language files and locked relevant field captions in purchase and service document lines

Fixed

General - Refactored DocumentTextMgt to prevent unnecessary blank entries when extracting document text fields

Fixed

General - Refactored DocumentTextMgt data handling for improved performance and clarity

Added

General - Added customization permissions for several tables and fields

Version 27.121 entries
Requires

Version 27.0 of Business Central

Added

Banking - Added SvcLvl tag NURG for domestic non-Swedish payments in payment file

Added

Banking - Added dialog progress indicator when reading lines in CAMT Credit and Debit Management

Fixed

Banking - Fixed GiroTypeCode retrieval in VP Payment Suggestion page

Fixed

Banking - Fixed line number increment in TempTextLineEntry for BG Max and Total In imports

Fixed

Banking - Removed OnValidate triggers for Bank Branch No., Bank Account No., IBAN and SWIFT Code fields to allow freer data entry

Added

Documents - Added PEB Preview Invoice PDF codeunit with report handling and PDF generation

Added

Documents - Added Work Description to PEB Sales Service Invoice report with visibility control

Added

Documents - Added event OnAfterFindReportUsageForCust to increase customizability in report selection

Added

Documents - Added language handling in Email Body Management when inserting default texts

Fixed

Documents - Fixed Report Layout Name and reset of DesignTimeReportSelection

Fixed

Documents - Fixed field references for Registered Office Info and Plus Giro Number in Company Information

Added

General - Added OnAfterInsertGenJnlLine integration event after inserting journal lines

Added

General - Added "Item Charge Has Non-Deductible VAT" field to purchase document lines with translations

Added

General - Added "Export Zero Entries" option to SIE Export

Fixed

General - Fixed currency rounding precision handling in Inward Registration PostInwRegEntry

Fixed

General - Fixed missing find operation for WarehouseActivityHeader in sorting method

Fixed

General - Added validation for empty Security No. in Approver ID Information

Fixed

General - DateCheckDone is now respected in the date validation event

Fixed

General - Enhanced VAT handling in Inward Registration by correctly calculating total amount including VAT

Fixed

Tax Reduction - Validation logic for property designation and tenant association now correctly checks based on selected tax reduction type

Version 27.016 entries
Requires

Version 27.0 of Business Central

Added

General - Added support for external search to Denmark and Finland

Added

General - Note of goods on Purchase Order Archive

Fixed

General - Removed subscription to event OnBeforePostVendorEntry, it has been obsoleted by Microsoft in CU90

Fixed

General - Removed obsolete code that has been obsoleted for an appropriate amount of releases

Fixed

General - Performance enhancements adding "ReadUncomitted"

Added

Banking -Support for "Same Day Value"-express payments in the payment suggestion (Combine Financial payment + express) on Vendor Bank account

Added

Banking - Removed testfield for "Swift-code" for bank "Danske Bank" when generating the pain-file in payment suggestion

Added

Banking - Added support for BACS payments in GB, for domestic payments

Added

Banking - Added in the payment suggestion summary to see the amount of lines in the suggestion

Fixed

Banking - Merge payments also separating on vendor bank account in payment suggestion

Fixed

Banking - Possibility to filter for GiroType Code in the report Payment Suggestion report 12048859

Fixed

Banking - Fixed an error where Kid "No." with Modulus 11 was interpreted wrongly

Fixed

Documents - Rounding on finance charge memo now correctly appears on the page footer in report 12047979

Added

Documents - Added new event "OnBeforeSetEmailSubject" in SubjectAttachment codeunit, to increase customizability in what is written in the subject when sending documents as email

Added

SIE -New event added "OnBeforeWriteTransactionLine" in the SIE Export - for more customizability

Version 26.013 entries
Requires

Version 26.0 of Business Central

Added

General - Added support for ROT/RUT and Green technology when invoicing from a project (job)

Fixed

General - Update vendor bank account on purchase header validation of field "Buy from vendor no."

Fixed

General - When calculating inventory value in the revaluation journal, Swebase custom field "PEB Gen. Bus. Posting Group" is added to the calculated lines

Added

General - Set preferred bank account on purchase header, from vendor.

Added

Document - Made it possible to add more fields in to one in the page header setup separated by a "|".

Fixed

Document - fixed an error while printing a sales document with no lines.

Added

Document - Added support for QR code on service invoice (on a new layout)

Added

Document - Added support for work description on service orders

Added

Dependency code - Enable EditDocTextFromCaption and LookUpHeaderTableFields from internal to external procedures in DocumentTxtMgt

Added

Banking - Added functionality to add approver ID information to the PAIN001 file.

Added

Development - Added document Variant in the event "OnAfterSetPageFooterFilter" to be able to adjust which page footer is collected based on data on the document.

Added

Report - Fixed an issue while printing the Payment suggestion report and aggregating on due date.

Version 25.113 entries
Requires

Version 25.0 of Business Central

Added

Documents - Lot/serial number handling as a setting on page header setup. Available on Purchase Invoice, Sales Credit Memo, Sales Invoice and Sales Shipment

Added

E-mail - Added additional replaceable variables, %15 = Salesperson/Purchaser Phone No. and %16 = Salesperson/Purchaser Email

Added

Inward Registration - Inward registration transactions now show up in the Cash flow forecast

Added

SIE - Added a possibility on the SIE-export to turn off the labels OIB and OUB (Dimension balances), to be able to handle larger datasets with a lot of dimensions

Added

SIE - Made available to export SIE of type 1

Added

SIE - Archive function when using the SIE-import, saving the exact transactions that have been imported. Also gives a warning if you're trying to import the same file (based on name) again

Added

SIE - A new way to import SIE3, opening balances with dimensions, new menu item "Opening Balance per Dimension to the Journal"

Added

ROT/RUT/Green technology - It is now possible to assign two different types of deductions on the same invoice

Added

ROT/RUT/Green technology - Ability to import a file from Skattemyndigheten with approved tax-reductions

Added

Development - Added a new variable in documents that use page header setup PageHeader: Record "PEB Page Header". This is useable in report extensions to use information on the page-header when developing custom functionality on Swebase documents. Populated in DocMgt.SetHeaderAndLineColumnCaption

Fixed

SIE - Control of "direct posting" on G/L Account when importing SIE-file now has support. The control comes first when trying to post the journal

Fixed

Banking - When recreating a VP Pack that contains deleted transactions it will keep the same SEPA references as before the recreation. Disabled the possibility to recreate a PAIN-file where "Aggregate on debitor level" has been changed in the VP Giro-type.

Version 25.08 entries
Requires

Version 25.0 of Business Central

Added

External Search - Powered by Inyett See the manual

Added

Banking: Import of Camt054 extended with adding different "domns" (Domains)

Added

Documents: Prepayment Invoice header now supported by Document Texts

Added

Documents: Availability through event to print Resource Code on Swebase Documents

Added

Documents: Translation of additional fee on finance charge memos fixed, using document texts

Added

ROT/RUT/Green technology: Added new temporary levels starting 2025-05-11

Fixed

Reports: Payment Suggestion report - now includes credit notes when summarized on due date

Version 24.424 entries
Requires

Version 25.0 of Business Central

Added

Compatible with BC26.0 (2025 Wave 1)

Added

General: SIE-export list now includes a possibility to log last entry no exported, to make sure there is consistency in the exported verifications

Fixed

SIE: Fixed an error where if the export did not have start or end-date it gave error.

Added

General: Disabled the message about rounding when sending out reminders (PEB0101)

Added

Banking: Camt054 Credit fetch currency from file for bank charge

Fixed

Documents: Purchase Invoice, Error when VAT was higher than gross invoice amount.

Fixed

Payment Suggestion: Confusing error message Released/Open when creating file

Fixed

Documents: Resolved bug in new automatic reminder attachment function.

Added

ROT/RUT/Green technology: Reapply if rejected

Added

ROT/RUT/Green technology: Added error message if application contains too many lines

Added

Documents: E-mail body support for Service Credit Memo

Added

Development: Possibility to extend the amount of fields in the Page Header Setup

Added

General: PEB Note of goods added to Sales Blanket order

Fixed

Documents: Work Description sometimes caused long pages of white text, this is fixed.

Fixed

General: Error when creating draft invoice if last line had deferral and rounding.

Fixed

General: More clear error message when allocationg budget 12 months if next accountingperiod is not created.

Added

SIE: When importing new feature to fetch standard dimensions from chart of accounts (must still map in configuration to get dimensions from the file).

Added

Banking: Additional support to exclude Prtrys in the Camt054C-import

Fixed

Documents: Error VAT% does now show on Sales Order Confirmation if last line is a comment.

Fixed

SIE: SIE-import list if remapping to bank account and have boolean "Ignore automatic

Added

General: "Shipment Date "XXXX-XX-XX" Is before workdate "XXXX-XX-XX"" message removed with function PEB0135

Added

Documents: Support for Service-documents when attaching original documents to reminders.

Fixed

Documents: Fixed an error when e-mailing invoices and using an email body layout caused "No. Printed" to increment twice

Version 24.317 entries
Requires

Version 24.4 of Business Central

Added

Banking: Connection to Inyett Detect. Do you want to easily ensure that you have control over your payments and vendors, just a click away? See the manual

Added

Banking: New event “OnBeforeProcessPaymentReferenceSearch” in codeunit 12047992 "PEB Camt054 Credit", makes it possible to interpret PaymentReference strings in the CAMT054C process

Added

Documents: Possibility to attach original pdf invoices/credit memos to emailed reminders

Added

Documents: Added the possibility to put net weight on lines in the "PEB Proforma Inv. from Order" (12048010) using “DATA[2]” in the page header setup

Added

General: Added the possibility to “Cancel Finance Charge” from a “Finance Charge line”

Changed

General: When a “Sales Quote” is converted to an order, erase the “VAT reporting date” if posting date is blank

Changed

General: “PEB Note of goods” is added to “Sales Quote” and “Sales Quotes”, and editable in “Sales Quote”

Changed

Banking: When importing Direct Debit payments, connecting to oldest Customer ledger entry is possible

Changed

Banking: Changed the increment in general journal line numbers when using direct debit from 10000 to 100

Changed

Banking: Improvements in Pain001 file

Changed

Banking: New tag for Citibank domestic payments in Sweden (CITI147)

Changed

Banking: When using the SIE-import function, choose number series based on “Fiscal Year End (Current) date, instead of workdate

Changed

Documents: In the report "PEB Customer Reminder" (12047978) VAT summary is printed if the reminder line includes VAT

Changed

Documents: Possibility to add Item-fields and Item Attribute-fields to report "PEB Inventory Picking List" (12047962)

Fixed

Documents: “OnBeforeSetHeaderAndLineColumnCaption” in “PEB Document Text Mgt.” (12047969) now properly handles “IsHandled”

Fixed

Banking: SIE-export, UB-1 on balance accounts fixed

Version 24.211 entries
Requires

Version 24.4 of Business Central

Added

Documents: New layout for reminder with a QR code on is now available.

Added

Documents: Possibility to e-mail blanket orders, both purchases and sales, including predefined e-mail body texts.

Added

Documents: Possibility to send service invoices by e-mail, including predefined e-mail body texts.

Added

Documents: New event "OnAfterSetPageFooterFilter" which allows to change the filter to select the right footer.

Added

SIE: Support for export balances summed per dimension. Tagged in the SIE file as OIB and OUB. Comes with type 3 and 4 of the file.

Changed

Banking: Option to choose whether to only read transactions with payment status 0 when importing withdrawals via direct debit.

Changed

Documents: New field on the order line "Qty. On Pro Forma Invoice”, is used to set the quantity printed on the Pro Forma Invoice.

Changed

General: Permission sets do not have access internal anymore.

Changed

Documents: Filters set in the Accounts Payable and Accounts Receivable reports are saved.

Fixed

General Ledger: Adjustment to round e.g. a purchase invoice that has 3 decimal places.

Version 24.114 entries
Requires

Version 24.4 of Business Central

Added

General: Compatible with Business Central 25.0

Added

Banking: Support for payment files via Bank of Valetta.

Added

Documents: New document "Pick Instruction" is available, integrated with the page header setup.

Added

Documents: The vendor template is added with the field "Document Code".

Changed

Banking: Manage multiple bank account reconciliations simultaneously with transfer from banking import files.

Changed

Banking: New events in report 12048860 "PEB VP Get Pack Ledger Entry", OnBeforeInsertGenJnlLineFromVendor, OnBeforeInsertGenJnlLineFromCustomer, OnBeforeInsertGenJnlLineFromEmployee, OnBeforeInsertGenJnlLineBalAccount

Changed

Banking: Ability to format the pain filename using % formatting. New options are %5 = YYYY Year, %6 = MM Month, %7 = DD Day, %8 = HH Hour, %9 = mm Minute, %10 = ss Second, %11 = sss Mille second.

Changed

Documents: Hyperlinks can now be used in all reports and documents.

Changed

Documents: Work description is printed on the pro forma invoice.

Changed

Documents: If an invoice discount is specified on an order, it is printed on the proforma invoice.

Changed

Email: Ability to format subject and attachment filename when email is sent. New options are %13 = Note of Goods, %14 = External Document No./Vendor Order No.

Fixed

Banking: Changes in the Painfile to better support JyskeBank, SydBank and CitiBank.

Fixed

Documents: If an order is handled via warehouse shipment and picking created, the quantity printed on the proforma invoice is retrieved from the Take line.

Version 24.010 entries
Requires

Version 24.4 of Business Central

Added

Banking: Support for payment file SUS by Swedbank.

Added

Banking: A new way is introduced to configure the Banking module. See the manual.

Added

Tax Reduction: It is now possible to preview tax reduction entries before posting.

Added

Email: It is now possible to translate the subject and attachment filename for the reminder and finance charge memo documents.

Changed

Banking: The file format of Total IN is changed from ASCII to UTF8.

Changed

Banking: When changing status, e.g. deletion, of a pack or pack entry, the user ID and time of the status change are now logged.

Changed

Banking: The date format in the tag CreDtTm in the pain file regarding Citibank has changed.

Fixed

Banking: When the "Check Giro Account" field in SweBase Setup is selected, the vendor's bank giro and plusgiro are now also checked.

Fixed

Tax Reduction: Detailed tax reduction entries were always displayed in the "Find entries" function.

Version 23.142 entries
Requires

Version 23.1 of Business Central

Changed

Tax Reduction: The maximum amount for ROT deductions will be increased on 1 July 2024. This means that you can receive SEK 75,000 in both ROT and RUT deductions. The increase applies for the rest of the year. The due date controls your tax reduction: You get a maximum of SEK 50,000 in deductions for work that you pay before July 1 - later payments are based on the new amount.

Version 23.132 entries
Requires

Version 23.1 of Business Central

Fixed

Banking: The tag ChrgBr in the pain file was populated in a wrong way.

Version 23.128 entries
Requires

Version 23.1 of Business Central

Added

Email: Predefined email body text when sending the Shipment Document.

Added

API: New API pages are available with added SweBase fields. The pages added in this version are: Sales Header and Lines, Sales Shipment and Lines, Purchase Header and Lines and Purchase Receipt Header and Lines. See the manual

Added

Banking: Improved support for CitiBank Denmark.

Added

Banking: Support for managing one where a currency account is located. See the manual

Added

General: New function to find Dimension Set ID with a search function. See the manual

Changed

Documents: When e.g. an invoice number contains a prefix with letters, the check digit is calculated on the numerical part of the number. Which is then returned for printing.

Fixed

Tax Reduction: The calculation per person of already used tax reduction.

Version 23.112 entries
Requires

Version 23.1 of Business Central

Added

General: Compatible with Business Central 24.0

Version 23.104 entries
Requires

Version 23.1 of Business Central

Added

Banking: Support for payment files via Swedbank Latvia.

Added

Banking: Support for payment files via Sydbank.

Fixed

Documents: Sales Credit Memo was printed with a blank layout (rdlc).

Version 23.912 entries
Requires

Version 23.1 of Business Central

Added

Email: Predefined email body text. It is also possible to adjust these texts with language support in a simple way.

Added

Email: The name of the attached file in an email can now be changed. Supports translation in the document texts.

Added

Email: The subject line of an email can now be changed. Supports translation in the document texts.

Added

Banking: Integration to bank account reconciliation with a camt053 file. Both from disk and via the Pagero integration.

Added

Development: New event OnBeforeClearDatesOnDocuments in codeunit BaseCodeunits which makes it possible to change how fields in table 36 and 38 are to be handled after posting.

Changed

Banking: Pagero import files has been renamed to Banking import files. New function to import files from disk in this page.

Changed

Banking: The Camt Exceptions feature is complemented by the Method field. Choose whether the import should exclude the value or include the value.

Changed

Documents: Expiration Date when printing Lot Nos is added to the invoice and shipment documents.

Changed

Administration: In the case of a new installation of SweBase, billing of the app is handled via PaymentProvider instead of LicenseProvider.

Fixed

Tax Reduction: The total maximum amount for tax reductions is calculated for all types of e.g. an invoice.

Fixed

Warehouse: The sorting function of Bin/Shelf and Bin Ranking on an inventory pick is adjusted.

Version 23.88 entries
Requires

Version 23.1 of Business Central

Changed

Documents: Service Quote and Service Order have a total line with net amount, VAT amount and gross amount and slightly adjusted layouts.

Fixed

Budget: The function "Allocate Budget 12 Periods" could only allocate one g/l account at a time.

Fixed

Banking: Fees from Handelsbanken could in some cases appear twice in the journal when importing camt-files.

Fixed

Banking: The merge function of payments is adjusted to better support the "By date" option.

Fixed

Banking: Adjustment of the pain file regarding domestic payments via Jyske Bank.

Fixed

Banking: Adjustment of the pain file regarding Bank Giro payments via Citibank.

Fixed

Banking: Import of Camt files could give error message that Amount (VAT) must be filled.

Version 23.711 entries
Requires

Version 23.1 of Business Central

Added

Banking: Import of Direct Debit Payment Specification (new format) can be done from the cash receipt journal.

Added

Reports: The reports that is shipped with SweBase now include the total number of pages that will be printed.

Added

Banking: By setting the field "Use Due Date on Credit Memos" in the payment suggestion, only the credit memos that have a due date before or equal to the "Last Payment Date" will be included in the suggestion.

Changed

Banking: The banks in the pain001 file are now managed with an interface. This means that the field with codeunit number is set obsolete and will disappear in a future version of SweBase.

Fixed

Documents: The line Lot No./Serial No. is adjusted to follow the item line it belongs to.

Fixed

Documents: There will only be one line on the finance charge memo if the interest has changed during the period in which the calculation of interest lines took place.

Fixed

Banking: The code for bank of Sweden was missing in certain situations when creating the payment suggestion.

Fixed

Banking: The Purp/Prtry tag in the camt credit files is used for matching payment entries.

Fixed

Banking: Adjustment in the pain001 file for Jyske Bank when paying a domestic vendor.

Fixed

Banking: When reconciliation of camt files, you could get errors in searching the number series where the length was over 10 positions.

Version 23.62 entries
Requires

Version 23.1 of Business Central

Added

Upgrade: By entering the code "---NO-UPGRADE---" in the standard texts, the upgrade script in SweBase is disabled.

Version 23.54 entries
Requires

Version 23.1 of Business Central

Fixed

Banking: Camt Credit file import did not handle unstructured data correctly.

Fixed

Banking: Merge of only negative lines combined with the setting merge due date "Per Date" did not work.

Fixed

VAT: Testing that the "Allow VAT Date From/To" fields are registered should not be done for localization US and CA.

Version 23.48 entries
Requires

Version 23.1 of Business Central

Added

Banking: Banking: Support for payment files via Danske Bank Latvia.

Added

Banking: Banking: Support for payment files via Citibank.

Added

Banking Remaining Amount and Remaining Amount (LCY) are added to the page Direct Debit Payment Entry.

Added

VAT: If VAT Date Usage is enabled the new fields Allow VAT Dates From/To are updated when updating Allow Posting From/To.

Added

VAT: When creating a new company the default value of the field VAT Date Usage in General Ledger Setup i set to Disabled.

Added

General: A new field Balance After Posting is introduced in the pages general journal, cash receipt journal and payment journal. With the function Calculate Balance After Posting you can directly see the balance after you have posted the line. See User Guide for more information.

Fixed

General: When upgrading to BC 23.1, a blank user is added to the user setup. This may have consequences for functionality in SweBase regarding only being able to post on today's date.

Version 23.35 entries
Requires

Version 23.0 of Business Central

Added

Banking: A customer matched to an invoice when reconciling the Camt file is logged so that when the next import takes place and an invoice cannot be matched to the customer, the customer is still found via the log. Can be switched off using SweBase Function PEB0131.

Changed

Banking: Support for adding/removing multiple ledger transactions at the same time in direct debit pack.

Changed

Document: New event "OnBeforeGiveErrorDocPrintedMoreThanOneCopyWithRecord" to turn off the block to print only one copy of document. Now with the possibility to take into account which table is printed.

Fixed

Tax Reduction: Export of the file for RUT is adjusted to correspond to the tax authority's requirements.

Version 23.24 entries
Requires

Version 23.0 of Business Central

Added

Banking: Support for payment files via Danske Bank UK.

Fixed

Document: Sorting of Picking List. Can be switched off using SweBase Function PEB0130.

Fixed

Document: Support for translating the country when printing the address information.

Version 23.15 entries
Requires

Version 23.0 of Business Central

Added

SIE: Support to export SRU codes.

Added

Report: The Accounts Payable report is supplemented with External Document No.

Added

Report: Possible to print Balance Report and Income Statement with rounding factor 1/1000/1000000.

Added

Document: Possible to use DATA[80] in the page header setup to show an invoice number without a prefix but with a Finnish check digit.

Version 23.02 entries
Requires

Version 23.0 of Business Central

Changed

Sales/Purchases: Document Date and Due Date are set on the documents in a different way due to changed behavior in the base application.

Version 22.75 entries
Requires

Version 22.1 of Business Central

Fixed

Document: Inventory Picking List could not be printed.

Fixed

API: It was not possible to create e.g. a purchase invoice via the standard API if the supplier's invoice number was registered before the supplier number.

Fixed

Banking: Matching of payments could not be done if the name of the payer contained certain special characters, e.g. ( ).

Fixed

Merge Per Date did not work in payment suggestion. All transactions received the same merge no. regardless of which due date was registered.

Version 22.610 entries
Requires

Version 22.1 of Business Central

Added

SIE Import: New function to insert G/L accounts in the mapping table that are not in the chart of accounts.

Added

Document: New invoice layout that prints QR codes. In the page header setup, it is now possible to make settings to print a QR code on the sales invoice. QR code for Swish and Bankapp are available.

Added

Warehouse: New document Inventory Picking List. Possible to configure in the page header setup.

Added

Documents: New event "OnAfterSetAccountFilterSelectionForPageHeader" is added to codeunit PEB BaseCodeunits. Useful for controlling how a page header setup is retrieved.

Added

Tax Reduction: Export of the file for Grön Teknik is adjusted to correspond to the tax authority's requirements.

Added

Direct Debit: The field Approval Status from the customer appears in the list of direct debit payment entries.

Fixed

Ledger: External document no. is only transferred to the documents if the field is registered to a customer or vendor.

Fixed

Cash Receipt: The Information field is extended to 100 characters.

Fixed

Sales: Connect a text line to item line, on e.g. a sales order, takes place only when the previous line is line type item.

Version 22.54 entries
Requires

Version 22.1 of Business Central

Added

Budget: Possible to create a budget that is distributed over 12 periods.

Changed

Telemetry: Telemetry will not be sent for background sessions.

Fixed

Documents: Possible to print a document that has two lines in the report selection.

Version 22.421 entries
Requires

Version 22.1 of Business Central

Added

Banking: Possible to exclude e.g. some customers when importing Camt Credit files. Useful if you get reconciliation in another way for these customers.

Added

Banking: Possible to exclude e.g. certain payment methods when importing Camt Credit files. Useful if you get reconciliation in another way for one of these payment methods, such a method can be Swish.

Added

Banking: New event "OnBeforeSearchDocNo" in codeunit "PEB Search Document No. Mgt." which makes it possible to develop an own function to find e.g. an invoice number when reconciling a Camt Credit file.

Added

Banking: Possible to reconcile Camt files where balance accounting is to be done using bank giro number.

Added

Documents: New field on extended texts, "No Connection to Item Line", which enables the extended text not to be connected with an item line on e.g. a sales order.

Added

Documents: Information from the variant table can now be used at the line level of the documents. Setup is made on the page header setup.

Changed

Banking: When running the import of reconciliation files via the API, the following imports will not delete any already registered journal lines.

Changed

Banking: Adjustment of how unstructured and structured Camt Credit files from Danske Bank are imported, as both can appear in the same payment.

Changed

Banking: Support for debits in Camt Credit files from Danske Bank.

Changed

Banking: Support for finding the document number regarding credit memos in Camt Credit files from Danske Bank in another tag (AddtlRmtInf).

Changed

Banking: Support for handling bank charges via difference between amounts in Camt Debit files from Danske Bank.

Changed

Banking: The layout of the payment suggestion has been changed to better categorize the information.

Changed

SIE: The question when updating the journal in an SIE Import regarding whether you want to delete all lines is not displayed if there are only blank lines in the journal.

Changed

SIE: When a SIE file is imported via API and there are unposted lines in the journal, you get an error message.

Fixed

Banking: When importing the reconciliation Camt Debit file, there was a possibility that settlement was made against the wrong transaction if there were several transactions with the same document number. If there are such transactions, the transaction is linked via Applies-to ID instead of Applies-to Doc. no.

Fixed

Banking: Invoices with a payment discount date are filtered with the payment discount date instead of the due date in combination with “Payment Immediately” and “Payment Date” when creating a payment suggestion.

Fixed

Reminder: When the interest rate has changed within a payment reminder period, two lines are created on the reminder. Only one of these should be printed.

Fixed

SIE: When a line in an SIE file with type #TRANS is exported, dimensions should not be surrounded by quotation marks.

Fixed

Documents: An email address registered under document layouts on the customer has priority over the email address on the customer card when a document layout is registered on the page header setup.

Fixed

Documents: When a purchase invoice is printed, filtering of the page header is done with source type vendor.

Version 22.38 entries
Requires

Version 22.1 of Business Central

Added

SIE: Support for export of SIE type 2 file.

Added

SIE: New setting when importing SIE to ignore automatic account group.

Changed

Banking: Import of e.g. camt credit files is improved.

Fixed

Pagero: Improvement of setting up Pagero.

Fixed

SIE: Incorrect document number was assigned, when choosing to sort the journal lines.

Fixed

Posting: Posting payments with large amounts of entries caused performance issues.

Fixed

Documents: Printing with serial number/lot number stops with an error if there are capacity entries that have no item ledger entry.

Version 22.210 entries
Requires

Version 22.1 of Business Central

Added

Banking: Support for transactions with ACMT and CAMT and bank costs for reconciliations of vendor payments.

Added

Documents: Possible to turn off printing of serial nos/batch nos on documents via SweBase Functions PEB0125.

Added

SIE: New field on the SIE Import Card, "Get Posting Date From" with option to either retrieve posting date from the verification line (#VER) or the transaction line (#TRANS).

Added

General: New field on the customer "External Document No.". This field is transferred to quote, order, invoice, credit memo, return order and blanket order.

Changed

General: Registration No. is added to the contact in BaseApp. This field was previously in SweBase and has been removed.

Changed

Banking: If the posting date when registering a payment is before the posting date of e.g. an invoice, you get an error message in BaseApp. This error message is suppressed.

Changed

Banking: If Transit No. is used, the creditors address is retrieved from the vendor bank account.

Changed

Banking: The information when importing files for Cash Receipt has been improved, now has two types Error and Message.

Changed

Documents: The text space shown in e.g. "Invoice Line 1..." and "Invoice Line 2..." can grow to show all text registered in document translations.

Version 22.17 entries
Requires

Version 22.0 of Business Central

Added

Banking: Support in the pain file for the bank ING Luxembourg.

Added

Banking: New field in the giro type "XML Without BOM" to create the pain file without BOM in the character set for UTF8.

Changed

Reports: Heading in "Accounting Voucher" changed to "Reversed Accounting Voucher", when the journal was posted as reversed.

Changed

Posting: The default option "Ship" when posting orders with combined shipments only works when the field "Sales Invoicing Posting Policy" in user setup is set to "Allowed".

Fixed

Banking: When matching credit memos with e.g. BG Max, the sign of the amount was revered incorrectly.

Fixed

Documents: The field "Qty. to ship" is used to determine which lines on the proforma invoice that should be displayed. This now also works when running with warehouse functionality.

Version 22.07 entries
Requires

Version 22.0 of Business Central

Added

OCR-control: Various adjustments such as the OCR field is always being presented on purchase invoices, credit memos and return orders. If OCR is mandatory, a check also takes place during posting. Selection of OCR control is extended with Norway modulus 10 and Denmark.

Changed

Registration No.: The field registration no. is removed from customer and vendor is replaced with the registration number field in the Base App.

Changed

Item Description 2: The old way of registering item description 2 on a document line has been removed. This is now done via extended texts on the item.

Fixed

Banking: When checking length for OCR in Denmark, an error message points to another record.

Fixed

Banking: Unstructured information in the pain file for Poland does not support all characters.

Fixed

Banking: Import of Camt053 for debiting inserts blank lines in some cases.

Version 21.98 entries
Requires

Version 21.0 of Business Central

Added

Banking: Possible to merge payment directly in the create payment suggestion.

Added

Banking: Possible to set filter on the field "Giro Type Code" in the create payment suggestion. Useful when running from e.g. the job queue.

Added

Banking: Possible to run a payment file export from report 12047961 "Export Payment File". Useful when running from e.g. the job queue.

Added

Template: Possible to register document layouts on template customer and vendor.

Fixed

Banking: In Sweden and payment in SEK to another country will be without Regular Reporting Cross Border. In Norway and payment in NOK to another country will be without a Regular Reporting Cross Border.

Fixed

Documents: Sales service quote and order handles text lines.

Fixed

SIE Export: The fields RAR and TAXAR in the file are calculated in a different way.

Version 21.83 entries
Requires

Version 21.0 of Business Central

Added

SIE Import: Support default dimensions for all Account lines, during processing the SIE file. Insert exception for certain Account No.

Changed

Banking: Test field for not blank address on the vendor bank account is removed.

Version 21.710 entries
Requires

Version 21.0 of Business Central

Changed

Banking: Credit Suisse now supports QR payments.

Changed

Banking: Camt Credit, now support structed information better.

Changed

Autocreate payment suggestion: if there is lines in the Payment suggestion there will be a new question, "Do you want to delete these lines?"

Changed

Banking: Bank Account on the Giro Type is change from 20 Char to 30 Char.

Changed

Banking: If the Due date is passed in the Payment Suggestion the Due date is changed to today, instead of stopping with an error.

Changed

Direct Debit: support more Document Types.

Fixed

Sales Return Order document: don’t support Invoice Discount Amount, causes wrong total amount.

Fixed

Banking: Camt Debit, don’t show the mapping page.

Fixed

SIE Import: If Charge of Account in the file has the same Account No twice, import stopping with an error.

Version 21.65 entries
Requires

Version 21.0 of Business Central

Added

Banking Setup supplemented with new menu actions to setup, e.g. mapping of accounts.

Added

Extended API for SIE with report for export of SIE file. Report No. 12047960 "PEB Export SIE File".

Added

Extended API for Banking with the possibility to import reconciliation files such as Camt053, Camt05, BG Max, Total In and BG återredovisning.

Fixed

The field "Registration No." in the tables customer, vendor and contact are set to obsolete pending while waiting for the Base App to be updated with these fields.

Version 21.56 entries
Requires

Version 21.0 of Business Central

Added

Support for KID in Norway for modulus 10.

Added

Support for OCR in Sweden without length digit.

Added

Posting with a blank VAT Registration Date or that the VAT Registration Date is not within the open posting period produces an error message. The function can be deactivated by SweBase Functions PEB0123.

Fixed

Posting of an inward registration causes a blank VAT Registration Date.

Fixed

Camt debit files. Filter for Family removed, as it does not work for all banks.

Version 21.417 entries
Requires

Version 21.0 of Business Central

Added

Support of Bank "Credit Suisse" for Pain001.

Added

Support of Bank "Royal Bank Of Scotland" for Pain001.

Added

Support of Bank "BNP Paribas" for Pain001.

Added

Import of Camt files has support by an API.

Changed

Camt file Debit now supports transaction level better.

Changed

Deduction for tax reduction regarding solar cells has been changed to 20%.

Changed

Camt file with OCR and leading zeros is handled better.

Changed

Support for "Code for Bank of Sweden" regarding domestic payments.

Changed

No requirement for "Swift Code" for bank account deposits.

Changed

Possible to include VAT and posting groups when importing a SIE file.

Changed

Possible to make a choice how the document number should be set when importing a SIE file.

Changed

Possible to import a SIE file with calculated amounts by a currency.

Changed

The variable DocMgt used in the documents can now be reached from e.g. a report extension.

Changed

When the "Quantity to Ship" field is zero when printing a proforma invoice, the quantity field is used from the "Outstanding Quantity" field instead.

Changed

Instead of using "DownloadFromStream" when creating files, the BLOBExport function is now used.

Fixed

Posting date is cleared when a part of a drop shipment is posted.

Version 21.36 entries
Requires

Version 21.0 of Business Central

Changed

Domestic payments for country code CH (Switzerland) is now supported.

Changed

The variable DATA[nn] used in the documents can now be reached from e.g. a report extension.

Changed

Some promoted actions in page SweBase Setup, Pagero Setup and Pagero Import Files will become obsolete.

Fixed

The Get Ledger Entries from Pack function does not work when reconciliation of employee entries.

Fixed

Specifying payment immediatley or payment date in the payment suggestion does not work together with credit memos.

Version 21.22 entries
Requires

Version 21.0 of Business Central

Changed

Publisher changed to Programekonomi Svenska AB.

Version 21.12 entries
Requires

Version 21.0 of Business Central

Fixed

Change of Pagero Secret.

Version 21.012 entries
Requires

Version 21.0 of Business Central

Added

New events are published in codeunit VP Management. OnBeforeInsertTempLedgerEntryForVendor, OnBeforeInsertTempLedgerEntryForCustomer and OnBeforeInsertTempLedgerEntryForEmployee. Useful for changing the information in the payment files.

Added

Import of SIE now has an API for automated import from external systems.

Changed

If the payment suggestion contains several currencies, a summary per currency will be at the bottom of the report.

Changed

The general ledger report has changed, it can now in addition to dimensions 1 and 2 also show extended dimensions and source names.

Fixed

The summary level is missing for camt 053/054 credit from Handelsbanken in Norway.

Fixed

It is now possible to leave the account number for bank charges blank in the settings for reconciliation of camt053/054 credit.

Fixed

If extended texts have been registered for a VAT clause, these will now appear on the invoice.

Fixed

Missing translations in page Update Vendor OCR info.

Fixed

Blank "Allow Posting To" gives an error if the field "Extend Allow Posting To" in SweBase setup is entered.

Fixed

When comparing with previous year in the income statement, any journals are not taken into account.

Fixed

Include vendor payments in the payment suggestion had not affect in the suggestion.

Version 20.61 entries
Fixed

Permissions to approval entries were missing.

Version 20.51 entries
Fixed

Breaking change for Exflow when setting a global variable.

Version 20.41 entries
Fixed

When running the client with the swedish language, the page "SweBase Function" where closed with an error.

Version 20.39 entries
Added

The fields "Journal Template Name" and "Journal Batch Name" is available for filtering in the report "Get Ledger Entries from Pack".

Added

It is now possible to add information from the salesperson/purchasers table on documents.

Added

It is now possible to add two lines of extra information after the specification of tax reduction on an invoice.

Added

When the workflow for payment suggestions is approved, tracking is created to posted approvals with the pack no.

Changed

When posting deferrals the allow posting to where extended with an date formula from the SweBase setup. This function is now changed to fit into the standard deferral function. The field "Allow Deferral Posting To" is now calculated by the SweBase setup field "Extend Allow Posting To".

Changed

When printing a purchase order the item reference is shown under the item no. If there is no item reference entered, the vendor item no. from the item is shown. It is possible to turn of this function by inactivate SweBase function PEB0122.

Changed

When the field "Merge Due Date" is set to "With Earliest Date", the merging is now done to the earliest due date, not the latest.

Fixed

The field "Entry/Exit Point" can now be shown as a description on the documents.

Fixed

When importing e.g. Camt-files into a cash receipt journal the field "Document Type" is now validated.

Version 20.26 entries
Added

The Pagero connection now supports multicompanies on the same account, e.g. accounting firms.

Added

The field ”Notes of goods” is now available on the following pages: sales order list, purchase order list, sales return order list, purchase return order list.

Added

In codeunit 12047960 "PEB Base Mgt." a new event is published, OnAfterInsertTempDocNoRec, to handle unmatched lines when importing customer receipts.

Added

In codeunit 12047969 "PEB Document Text Mgt." a new event is published, OnBeforeGiveErrorDocPrintedMoreThanOneCopy, to provide the possibility to print several documents at the same time. Use with caution as there is a risk of incorrect printing when page breaks.

Changed

The text "Amount Incl. VAT" in the order confirmation is changed to "Total Amount".

Fixed

Permission to the employee entries were missing when creating the pain file.

Version 20.118 entries
Requires

Version 20.2 of Business Central

Added

It is now possible to temporarily inactivate a registered currency account. Partly in the currency account settings, partly in the payment suggestion.

Added

It is now possible to define a cash receipt number series to search both with and without a prefix. Solves the problem when the customer do not registering the prefix when payment reference was entered.

Added

It is now possible to enter several journal names when printing a balance report or income statement.

Added

The line number interval in the journal for SIE import is now configurable. The default value is 10000.

Added

The proforma invoice now contains any VAT clauses.

Changed

On the order confirmation, the VAT amount is specified if the field "Prices Including VAT" is set to false on the order.

Changed

You can now enter the dimension number instead of the dimension code in SIE dimension mapping.

Changed

Handle of "PEB0109 Item Description 2 as new line on document" is redesigned. Item description 2 is now handled by the extended texts. This function is activated in SweBase settings.

Fixed

Removal of various tests on VP Giro Type Card that are not necessary.

Fixed

When the exchange rate changed between e.g. shipment and invoice, the invoice discount was reset.

Fixed

When sending e-mail or attaching a PDF, a custom report layout is not included if entered on the page header settings. We have found out that the events take place in different order. Therefore, we have changed the logic so that the document code and the responsibility center are retrieved from the customer.

Fixed

Date filters must be entered on options in the income statement.

Fixed

The function show prices in the purchase order did not work when send by e-mail or attach as a PDF.

Fixed

Comparison of the previous year in the income statement for leap years gave incorrect date ranges.

Fixed

The invoice rounding setting did not work on draft invoices. There was always rounding on the draft invoice.

Fixed

Shortcut for find entries follows the new keyboard shortcut according to base app.

Fixed

The deferral report showed an incorrect amount if the first deferral date and posting date on the original entry were the same.

Version 20.08 entries
Requires

Version 20.0 of Business Central

Changed

Improved performance of text file export codeunit.

Changed

Performance improvement for SIE exports for large number of transactions.

Changed

Banking Countries HK, PL, and CN supports local currency.

Changed

Banking the requirement to enter Nordea Signer ID has been removed.

Fixed

The income statement report has been adjusted to be more user-friendly.

Fixed

The report payment suggestion wrote the last column on a new page.

Fixed

Printing “Draft Invoice” and Post + Email could stop with error “Posted Sales Invoice ### do not exist”.

Version 19.99 entries
Added

SweBase now supports all available localizations.

Changed

Swedish caption “Samsortera betalning” changed to “Samsortera markerade rader” in the payment suggestion journal.

Changed

The setup of the field show no prices when printing a purchase order is changed. This setup is now done with the field “Show prices on purchase order” in SweBase setup.

Changed

When showing text line entries in a cash receipt journal post code and city is now added.

Fixed

Checkdigit for Norway was not correct calculated for kidnumbers with modulas 11.

Fixed

When importing dimension 1 and 2 with a SIE file the global dimension number was not updated.

Fixed

The timestamp in the reports is now showing the clients date and time.

Fixed

It is now possible to sort the payment suggestion report in due date order.

Fixed

The fieldname “SEPA No. Serie” in the giro type setup is changed to “Pain001 No. Serie”

Version 19.821 entries
Requires

Version 19.2 of Business Central

Added

Send and receive payment files direct to and from the bank via Pagero Online.

Added

We have now added a new module to handle ROT, RUT and green technology.

Added

Pick data from different tables in page header, customer, vendor or contact.

Added

In the cash receipt and payment journals, Account names are now available in the lines as supplier name, customer name, person name, or account name.

Added

Reconciliation Pain001 with the camt files, now supports customer credit and employee payouts.

Added

Reconciliation LB Bankgiro files is now supported by camt files, useful when switching to Pain001. Payments made by the LB Bankgiro file and paid in the future, transferring to camt files there may be references that originate from the LB Bankgiro file.

Added

There is now support for reconciliation of pain001 and cash receipt with the file camt053.

Added

A change in BC means that the template customer no longer handles fields that come from another app. An adjustment is required to solve that. We have now added support for the field Document code on template customer.

Added

Invoice discount is now also available on the document quote.

Added

If the RDL layout changes and is linked to a SweBase document, there is a limitation. It is not possible to use "General report selection" to redirect to the document, the document prints with standard DL. This must be done by Report Selection Sales / Purchasing instead. It is now handled also by the “General report selection".

Added

Import cash receipt files, now have increased flexibility. You can choose to search for document number, external document number or customer number. It is also possible to choose the settlement method for customer entries “Manual”/“Apply to oldest”. If you apply by customer number, the settlement must be “Apply to oldest”.

Added

Setting up banking on VP Giro Type have been further simplified. Select bank and only the fields that are affected are visible. We have also changed the names of the fields "Org Id Bank" and "Org Id Cust" to descriptive names for each bank. It is possible to display all fields as before.

Added

Description 2 on the item now becomes an extra row on purchase documents, in the same way as on sales documents.

Added

In journals, document numbers are increased at balance, now the number stays.

Added

If there is a line with an old document number in a journal (not the next) that gives an error during the posting, this will be corrected automatically to the correct number on.

Added

Renumbering of more than one document number in the journal is redesigned, so that the document numbers are kept in place and with the correct numbers.

Changed

VAT specification on the documents shows separated negative and positive lines for the same VAT percentage. They are now added to a row and then no VAT specification.

Fixed

Banking improvement of pain001 for structured information in SCOR, credit note was vaguely marked at the Danske Bank.

Fixed

In version 19.6, an error in banking was introduced. if the supplier is blocked, the invoices will still be included in the payment suggestion.

Fixed

An error was introduced in version 19.6. It is not possible to register SWIFT code together with Bankgiro number in VP Giro Type for Swedbank and domestic payments.

Version 19.72 entries
Added

Camt054 Debit has improved support for Danske Bank.

Added

SIE import has got an improved API.

Version Description
19.6 It is not possible to preview the draft invoice/credit note if the document is not open.
It is now corrected.
19.6 Banking camt054. Bank fees can now be turned off by leaving the account for bank charges blank, in the mapping table.
19.6 Captions for the documents are adjusted so that the they do not contain åäö, that can give problems with the attachment to an email.
19.6 Banking camt054 can cause rounding problems in currency management.
It is now corrected.
19.6 The prepayment invoice does not support the vendor's bank account and OCR no.
It is now corrected.
19.6 Banking camt054 debit can now be selected by level for totals. There are two options, account level or transaction level.
19.6 The report "Accounts Payable Inward" takes a long time to print out, if there is a lot of transactions.
It is now corrected.
19.6 The function Creating payment suggestion has improved performance for large numbers of payments.
19.6 SIE exports now support the opening and closing balance according to filters instead of financial year.
19.6 In the case of a language code blank on the documents, it will now be the language code on "SweBase Setup" in the field "Local language for documents". It is changed to support the change that Microsoft made in version BC19.1 (the language is setting the region).
19.5 New API for bank files (Import), it is now easy to make connections to import bank files.
19.5 When creating bank files, the due date does not change. We have received comments that it should be set o the same date as the co-sorting has.
It has now been changed so that it is set with the same date
19.5 Merge in payment suggestion now has three choices.
- Set the due date manually per merge no. (Blank).
- Set the due date to the earliest per merge no.
- Merge by due date. (New).
If you have a lot of invoices to the same vendor and with the same due date. This option can be helpful.

The setup is on "Banking Setup".
19.5 Workflow in Banking does not support rejection.
It is now added.
19.5 New event in Pain001. Support customization of the logic how to set the paying from account No.
OnBeforeGetCurrencyAccount
19.5 The setup of "LB Giro Type" is improved, select the Bank in a drop down. Correct code unit will be set and red stars for mandatory (Show Mandatory) fields.
19.5 Reconciliation with "Camt054 Debit" has now better support for fees, to SEB.
19.5 Logos are not always printed. If the document suppresses the first line because of zero qty and will not be printed, the logo is also dropped.
It is now corrected.
19.5 "Article cross-reference" of the new variant is now supported in all documents.
19.5 Reminder documents now handle texts across the hole page.
19.4 For custom fields on document lines, it is a requirement to enter the corresponding fields in the temporary tables for the lines to the documents. When you test the report and have entered that field in the page header setup, it now stops with an error message that better describes what to do.
19.4 Permissions have been reviewed as there have been problems restricting access. The permission set BAS-Base have been updated.
19.4 Document dates become blank after posting a residual order. Previously, the due date was calculated from the document date. It is now calculated based on the posting date. It has now been changed so that the document date remains after posting.
19.4 The field "Structured Remit. Inform. SE" on VP Giro Type has been changed from data type option to boolean. The default value is now true.
19.4 Camt054 Debit and Camt054 Credit entries can now be in the same file.
19.4 There is now an available event "OnBeforeImportFile()" on all imports to Banking.
19.4 There is now an extended API for managing Banking.
19.4 Camt054 debit reconciliation stops with an error. It is now corrected.
19.3 Correction of an error introduced in version 19.1
19.1 FlowField on document lines gives no value, it was introduced when we switched to temp records for the lines. It is now corrected.
19.1 The recipient's bank account cannot be selected if it is different pay-to vendor on the purchase document. It is now corrected.
19.1 The function to transfer the description from e.g. a purchase invoice to the general ledger entries has been removed and replaced by standard functionality. To activate this function go to purchase setup/sales setup and set the field "Copy Line Descr. to G/L Entry"
19.1 Suggest lines in the arrival registration did not pass two different VAT Business Groups on the same invoice/credit memo. It is now corrected.
19.1 The number of countries SweBase supports has increased with Portugal, France, the Netherlands, the United Arab Emirates and Italy.
19.0 Banking: Camt054 does not handle local currency specified as SEK instead of blank. It is now corrected.
19.0 Banking: the function "Transfer from VP Pack" is perceived to take a long time. The reason was missing filters for accounts receivable. It is now corrected.
19.0 Banking: cash receipt invoice no-series with a suffix set can give an error "Value for CPYSTR…". It is now corrected.
19.0 On page header setup, you can now add a logotype for the document.
19.0 On page header setup, you can now add a heading for the document.
19.0 General report selections function "Init Base Reports" can sometimes refer to itself, it does not give an error but the line is unnecessary. It is now corrected.
19.0 Document finance charge memo and reminder now support the development model to be able to easily add and adjust the information at line level, like other documents.
19.0 It is now selectable which VAT business posting groups are covered by the functionality for reverse VAT on certain goods.
19.0 Registration number can now be showned in the customer list.
19.0 The draft invoice from invoice and order could not be printed if the document was open. It is now corrected.
19.0 Draft credit memo is available to run on credit note and return order.
18.4 Banking: Camt054 reconciliation includes lines that are not reconciliation entries. It is now corrected.
18.3 Banking: it is now possible to choose that a payment suggestion is created automatically when the payment suggestion is opened. Setting to activate and set filters is done in SweBase setup.
18.3 Banking: payment suggestion is now searchable (Alt + Q) directly without going through the VP giro type list, it is possible to select the giro type code in the payment suggestion, in the same way as in the standard journals.
18.3 Banking: Unfortunately, SEB's test tool does not handle UTF-8-BOM, it is considering excellent to have it in production. If you want to remove the error during testing, SEB gives the recommendation to remove BOM from the file (edit the file) and then test. SEB comes with a new tool that will handle BOM.
18.3 Banking: we have expanded the support for OCR for pain001. It is now possible to sort OCR that is included in a structured form in the file. It is also possible to broadcast OCR domestically structured for countries outside Scandinavia. There are now requirements that you must choose whether you want structured information to the vendor or not on the girotype. It may be that the bank does not support structured format.
18.3 Banking: When paying out to a bank account, Danske Bank sends the bank a payment notice that requires the tag to avoid it. You can now chose codeunit for Danske Bank to handle it.
18.3 Banking: in certain circumstances, the VP pack have not been completed after the ledger has been closed. It is now corrected.
18.3 The work description is missing on the document draft invoice. It is now corrected.
18.3 Incorrect layout of the document pro forma invoice. It is now corrected.
18.3 Document purchase invoice is now available with the same design as other documents with page header setup. Can be used for self billing.
18.3 Permission for the table, PEB Translation Text-2 ”, table number 1204799 is missing. It is now corrected.
18.3 SIE is now adjusted so you can freely specify mapping without first reading the table relationships from the SIE file. They also remain at the next import. Suitable for recurring wage imports or similar.
18.3 SIE import with an opening balance that is zero, requires that the account is available when loading. That requirement no longer exists.
18.2 Banking: credit note from a customer stops with error that Merge Lines is not allowed. It is now corrected.
18.2 Banking: now allows to use IBAN for Sweden domestic payments.
18.2 Documents: Service invoice and Service Credit memo have the wrong RDLC layout. It is now corrected.
18.2 If the OCR number contains letters, now only checks the numeric part of the OCR number.
18.2 It was not possible to enter an Inward registration with an advance. It is now corrected.
18.2 In the draft invoice, no reverse VAT was processed for certain goods. It is now corrected.
18.2 New features to enable work flows for the vendors bank account and during creation of a vendor payment.
18.2 New feature to quickly register a vendor together with bank details directly from the purchase document.
18.2 Translation of G/L Account and resources is global for all companies. It is improved to support per company and global for all companies
18.1 “Always copy VAT setup” is a new field on the G/L Account that overrides all other setups so the VAT setup on this G/L Account always is used, this is on the Journal lines and SIE Import (SweBase SIE). This feature is great to use on VAT accounts, so the VAT report will be updated for manual entries and SIE Import.
18.1 In a bill that comes into force on 1 April 2021, it is proposed that the so-called Reverse tax liability shall be introduced in national trade between taxable persons in the sale of various IT products. There is now support for this handling, see the manual for more information.
18.1 In the report Income statement, the comparison with the previous year was incorrect when the previous annual period was leap years. for example, period 21-02-01--21-02-28 is compared with 20-02-01-20-02-29. This has now been corrected.
18.1 If item reference is activated, this reference will be printed on purchase order. If it is blank, the cross-reference of the article will be printed.
18.1 The payment journal now contains a fact box that shows associated lines of text from the import of, for example, BG-max and Camt054.
18.1 If control of the total amount against the amount of the rows is activated on the purchase documents, the field "Gross invoice amount" will be marked with a red star.
17.4 Banking payment suggesting with credit memo and " Payment Immediately" stops with an error. Is now corrected.
17.4 Printing purchase and sales orders does not handle all fields on the order line. It is missing fields in the temp records used for printing. Now all fields are included for all documents.
17.4 On the documents it is now possible to print text that runs over several lines (floating text), this is done by an event that can handle up to 2000 characters on the description field.
17.4 Camt054 for payment has been improved.
17.3 The VAT specification on the documents is incorrect. It is now Corrected.
17.3 Camt054 file for feedback, Inserts incorrect Counter Accounts for certain banks. Is now Corrected.
17.3 Camt054 file for feedback, missing support for Currency Pockets to Nordea. Is now supported.
17.2 Banking now supports payment to both Customer and Employee.
17.2 Banking now supports intercompany and salary payment (Employee).
17.2 Banking now supports partial utilization of credit.
17.2 Banking with pain001 accepts a due date up to 365 days ahead for both domestic and foreign payments. Instead of blocking it, users can check with the bank how long they accept.
17.2 The interface for Banking is improved.
- Fields that are no longer used have been deleted.
- Moved the fields on vendor and customer bank accounts to Banking groups.
17.2 Banking now has more flexibility when a payment suggestion is created. You can change the OCR number, External document no. and bank account.
17.2 The inventory journal now handles the General Business Posting Group when creating a proposal.
17.2 On an invoice with several lines where one line is negative, there will be two lines on the VAT specification.
There will now be one line per VAT rate.
17.2 Being able to select a document's formatting for shipment date from the SweBase setup is removed. It has blocked the ability to enter any formatting in the Page Header setup. The setup for shipment date will now be set in the Page Header setup instead.
17.2 OCR is now available on an Finance Charge Memos in the same way as on the Sales invoice.
17.1 On the Service Invoice is not possible to translate the Description of G/L Accounts and Resources. It has now been corrected.
17.1 In the list of Bank Accounts, there are now two new fields that can be added with Amounts, “Net Change (LCY)” and “Net Change”
17.1 The VP Payment Suggestion now includes the filed OCR No.
17.1 Pain001 will now always have unstructured reference for Account Payment for Sweden.
17.1 In Camt054 there is normally a tag that describes what type of file it is, DEBIT for payment information. Unfortunately, that tag is not in the file for the Danske Bank. When that bank is selected, that check is no longer performed.
17.1 Feedback from pack now handles Cash Discount for all modes.
17.1 All documents now have extended support to handle document lines.
- You can insert any numbers of lines with or without amounts at the top or at the end of the document.
- You can insert one or more lines after each line in the document.
- It is possible to enter rows that have amounts and it is also possible to make a choose whether the line should be included in the Total Amount or not.
- It is possible to change the title to something else and this is supported by the Document Texts translation.
- Everything is handled by new events.
- This has been added due to handle RUT and ROT Tax Reduction, this feature is under development coming in future release.
17.1 Camt054 for payment and feedback has been improved
17.1 In version SweBase 17.0, we introduced a bug that caused unwanted behavior when loading Total-IN. It is now corrected.
17.1 In the Inward registration, we introduced a bug that made it difficult to register lines with only VAT. It is now corrected.
17.0 Assist Edit has now been removed for the File Name field, in the report Create Payment Suggest for Banking. To enter a file Path is not supported ana longer, only the File Name could not be specified. The file will always be placed in the folder for downloaded files.
17.0 Feedback file in baking module with the format Camt054 do not stops if the amount in the file deviates from the vendor ledger.
17.0 Reporting in Banking for Danske Bank deviates by a tag DBIT instead of DEBT that other banks use. If selecting the bank Danske Bank when import the file, there will not be any warning message.
17.0 Merge payment for a Swedish Bank Account could not be done. The reason is that there are very few characters that can be sent to the recipient. This stop is removed is now possible to Merge Bank Accounts.
17.0 In the Accounting Voucher report, the Document Number has been extended on the printout.
17.0 The work description is now selectable on the Settings header. To be included, it is activated by Header Settings.
17.0 The Files for Customer Payments delivered from the banks of types BG-Max, Total-In and Camt054, is improved for handling Credit Notes better.
17.0 Total-In now handles Line Code 40 to find Invoice No references.
17.0 Pain001 for Swedbank also requires Swift / Bic for Bank Account Numbers on the VP Girotype. If you do not enter the Code, it will be an incomprehensible Error message from the bank. Now it will be a check for not blank, when the file is created.
17.0 Context help and Tool Tip are now supported.

Hotfix release notes

Version 23.13.152.12 entries
Requires

Version 23.1 of Business Central

Fixed

Email: GlobalLanguage removed from email body management

Version 23.13.152.21 entries
Fixed

Email: Wrong fieldnumber (43) used when setting language for subject. The right one is 41.

Finance Manager release notes

Version Released
26.26 2026-11-06
26.25 2026-10-13
26.24 2026-09-22
26.23 2026-08-25
26.22 2026-08-24
26.21 2026-07-09
26.20 2026-07-02
26.19 2026-06-29
26.18 2026-06-24
26.17 2026-06-16
26.16 2026-06-04
26.15 2026-06-02
26.14 2026-05-28
26.13 2026-05-22
26.12 2026-04-30
26.11 2026-04-19
26.10 2026-04-01
26.9 2026-03-25
26.8 2026-03-23
26.7 2026-03-16
26.6 2026-03-14
26.5 2026-02-27
26.4 2026-02-14
26.3 2026-02-10
26.2 2026-02-06
26.1 2026-01-24
26.0 2025-12-29

Release notes for the Aritma Finance Manager library for Microsoft Dynamics 365 Business Central, newest release first.

Each entry is written from the code changes in that release rather than from commit messages, and describes what changed for people using the app.

26.26

Finance Manager 26.26 reduces the amount of manual reconciliation. Bookkeeping rules can now build their own posting descriptions and be limited by currency, field and priority, which means that more bank transactions are posted correctly without manual handling. Payments that still need attention can be applied to open entries directly from the transaction journal, and cash discounts are taken into account automatically. Bank onboarding requires fewer steps, and bank accounts are identified by IBAN. The release also contains a number of fixes that make matching, posting and Excel import more reliable.

Dynamic descriptions in bookkeeping rules

The description of a bookkeeping rule can contain placeholders, %1 to %10, that are filled in with values from the bank transaction when the rule posts, for example a date or a reference. This gives postings descriptions that identify the underlying transaction.

The placeholders are set up with the Description Parameters action on the Bookkeeping Rules page. For each placeholder, the source (bank transaction, transaction line or bank account) and the field are selected, optionally together with a format, for example to show a date as 06.11.2026. The resulting description is limited to 100 characters.

Currency, field and priority on bookkeeping rules

Bookkeeping rules can be limited more precisely with three new settings:

  • Currency Code – the rule is only used for transactions in the specified currency.
  • Field No. – the search text is compared with a field other than the remittance text. The Source Table column shows whether the field belongs to the transaction header or line.
  • Priority Order – decides which rule is used when several rules could apply. A lower number means a higher priority.

Currency Code is shown in the list. The other fields can be added with Personalize.

Apply entries in the transaction journal

Payments that are not matched automatically can be applied without leaving the transaction journal. The Apply Entries action (Shift + F11) on customer and vendor lines opens the standard Business Central page for applying entries, and the selected entries are used when the transaction is posted.

The new Applied (Yes/No) column shows which lines are already applied, both in the journal and in the transaction details.

Automatic handling of cash discounts

Payments made within the discount period are often reduced by the cash discount. When the matched lines do not add up to the bank amount, Finance Manager now first tries the amounts after cash discount and then the full amounts, and uses the alternative that matches. Fewer transactions are left for manual handling.

Simpler bank onboarding

Bank onboarding has been simplified:

  • Banks that require an Activation Code or a Function Identification are asked for it once per bank. These banks do not require BankID signing, and the authentication steps are skipped when no selected bank requires them.
  • Number of Approvers for payments is set directly in the list of bank accounts. The value applies to all accounts in the same bank.
  • A technical contact is no longer required. Tenant Name and Contact Email are sufficient.
  • Bank accounts are identified by IBAN and currency. Accounts that cannot be matched are listed under Unmatched Banks, where a new lookup shows the Business Central bank accounts to choose from.

Transaction type per bank account

Fetch Transaction Type is now set on each Bank Account Card instead of once for the company. This makes it possible, for example, to fetch only incoming payments on one account and all transactions on another. The current setting is copied to the connected bank accounts during the upgrade.

Bank transaction code

The transaction code reported by the bank is shown on the Bank Transaction page and indicates the type of transaction.

Other improvements

  • On the Manual Payment page, Save as template has been renamed Save recipient.
  • In the Swedish version, "Betalningskod" has been renamed "Riksbankskod", the term used by the banks.
  • The Danish, German, Finnish, Norwegian and Swedish translations cover all new fields, actions and messages.

Fixes

  • Error "Valutafaktor kan inte specificeras utan Valutakod" on bank accounts in local currency. The error occurred when the local currency was also set up as a currency. These lines are now posted correctly.

  • Posting preview used numbers from the number series. A posting preview no longer uses a document number.

  • EUR payments to Swedish recipients were rejected by the bank (RR05). The payments were sent as domestic payments. A payment is now treated as domestic only when both the country and the local currency match.

  • A rejection could be marked as handled on a bank transfer with a validation error. The validation error must now be resolved and the bank transfer validated again first.

  • Negative available balance was not always shown in red in the bank transfer summary. This has been corrected.

  • Posted G/L entries could get an empty description. The remittance text from the bank is now used when no other description exists.

  • Long additional information from the bank was truncated. Up to 250 characters are now kept, and the text is used when a receipt has no remittance text.

  • Remittance text could be incomplete or contain extra spaces. All parts of the text are now included and extra spaces are removed, which also improves matching.

  • Payments could be matched to the wrong invoice or to an invoice that was already paid. The document number search now checks all variations of the number and prefers open entries.

  • A bank ledger apply rule without a clear match stopped the remaining rules. The next rule is now tried.

  • Excel export and import of the transaction journal lost information. Dimensions are now included with readable column headers, values no longer carry over between rows, Yes/No is read correctly in all languages, and account and document numbers are exported as text.

  • Error messages from the bank connection were always in Swedish. They now follow the user's language.

Upgrade notes

An upgrade is required. The existing Fetch Transaction Type setting is copied automatically to each connected bank account.

The standard permission sets ARIFM BASIC and ARIFM EXECUTE include the permissions for the new features. Custom permission sets need the new tables Bookkeeping Rule Param and Bank Consent Input, the Bookkeeping Descr. Mgt. codeunit and the pages Bank Consent Input Part, Bookkeeping Rule Params and Descr. Field Lookup.

Behaviour changes after the upgrade:

  • Bookkeeping rules are tested in Priority Order. The order should be checked where several rules can apply to the same transaction.
  • Payments in a foreign currency to a recipient in the same country are sent as international payments.
  • Bank accounts are matched on IBAN and currency.

For partners and extension developers: new tables ARIFM Bookkeeping Rule Param and ARIFM Bank Consent Input (temporary). New fields Currency Code, Table No., Field No. and Priority Order on Bookkeeping Rule, Fetch Transaction Type on Bank Account, Applies-to ID on Transaction Detail and Transaction Jnl Line, and Available Balance is Negative on Bank Transfer Summary. Additional Information on Bank Transaction grows from 50 to 250 characters. The upgrade copies the setup value to every bank account with an ARIFM Account Id and is registered with the per-company upgrade tag ARIFM-TransferFetchTransactionType. Fetch Transaction Type on Finance Manager Setup and the technical contact fields in the onboarding wizard are marked obsolete (pending, tag 26.25).

26.25

This is a feature release. The main addition is Manual Payments: you can now create ad-hoc payments to any recipient and upload a salary pain file, without needing a ledger entry to pay against. The release also reworks onboarding and assisted setup, adds matching on payment reference, and fixes several matching and currency issues.

Manual payments

A new Manual Payment page lets you pay someone who has no open ledger entry. Open it with the new Process Payment action on Bank Account Balance or on the Bank Account Card.

Fill in the recipient and address, IBAN, SWIFT, bank branch, account number, a message (optionally structured), the amount, the currency and the payment date. Choose Save as template to keep the recipient for later, and use the lookup of saved recipients (Manual Payment Entries) to fill in the details next time.

Before anything is created, you are asked to confirm the amount. The payment is then created as a bank transfer with the new account type Manual Payment, and its end-to-end ID starts with "M" so it is easy to recognise.

Finance Manager checks the entry first: recipient name, message and amount are required, and the payment date cannot be in the past.

Upload a salary pain file

The Manual Payment page has a new Upload Salary Pain File action. Choose a pain XML file and Finance Manager reads it, shows you the total amount for confirmation, and then creates a manual payment entry for each payment in the file.

Bank signing page opens after sending

When you send bank transfers to the bank, from the Bank Transfer card, the Bank Transfer list or Send Selected Bank Transfers, the page set in Bank Signing URL on the setup page now opens, if you have filled it in. This takes you straight to where you sign and approve the payments.

Payment suggestion report and due date formula

The Bank Transfer List has a new Payment Suggestion Report action with a Group by due date option, so you can review suggested payments by the day they fall due.

The Transfer Suggestions report has a new Last Due Date Formula option, so you can set the last due date as a formula instead of a fixed date.

Balance check on the transfer summary

The Bank Transfer Summary now checks the available balance against a minimum balance. If sending would take the account below it, the check can stop the send, so you do not submit payments the account cannot cover.

Finance Manager in assisted setup

Finance Manager Setup is now registered in assisted setup under a new Finance Manager group, so you can find and start it from the standard Business Central assisted setup list.

Onboarding wizard handles missing bank accounts

The onboarding wizard has a new step, No Bank Accounts Configured. It is shown when no bank account is ready to be onboarded, or when all of them are already onboarded. The step has an Open Bank Accounts action that takes you to your bank accounts so you can add or correct them, instead of leaving you on an empty page.

Get Redeem from setup

Finance Manager Setup has a new Get Redeem action. If you do not have write access to Job Queue Entry, you now get a message pointing you to this action instead of an error.

Matching on payment reference

Bank transactions can now be matched on the payment reference. If a match is found against a closed customer ledger entry, you are told so with the message "There is a match against a closed customer ledger entry. Document No. %1", so you can see why it was not applied.

More validation of payment details

Bank transfer validation gives clearer messages in more cases:

  • the SWIFT code is not valid
  • the Bank Account No. or IBAN is missing
  • the Bank Giro or Plus Giro is missing

In the Swedish version, when the SWE Base App is installed and a workflow is enabled, validation also checks that the vendor bank account is approved. If it is not, you see "The vendor bank account must be approved".

Translations

Finance Manager now has a full German (de-DE) translation. The Danish (da-DK), Finnish (fi-FI), Norwegian (nb-NO) and Swedish (sv-SE) translations have been updated with smaller changes.

Fixes

  • Foreign-currency payments had the wrong Transaction Amount. The currency is now taken from the bank transaction header, and the amount uses the exchange rate from the bank's response.

  • Receipt details were incomplete. Receipt transaction details now fill in Instructed Amount and Currency.

  • Additional remittance text was overwritten. It is now appended to the existing text and limited to 250 characters, instead of replacing what was there.

  • Payment approval could fail. The authorization request for the signing basket has been corrected.

  • "Set Unmatched Transaction Open" used the wrong condition. The condition has been corrected so it applies to the right transactions.

  • Document lookup could disturb the record being worked on. It now uses a temporary record.

  • The creditor address was missing the building number. The building number is now included.

  • The Main Category Setup page description could not be translated. It is now translatable.

  • Empty instructional texts on the wizard could be edited. They are now locked.

26.24

This release focuses on giving you more control before you post. You can now preview the accounting entries for a bank transaction before committing them, post transfers between your own bank accounts directly from the transaction list, and open the underlying invoice as a PDF without leaving the page. Bank transfer validation now works line by line, so a single excluded vendor no longer discards an entire transfer.

Preview posting before you commit

You can now review exactly which entries a bank transaction will create before you post it. Open a bank transaction and choose Preview Posting (or press Ctrl + Alt + F9) to see the general ledger, customer, vendor, bank and VAT entries that posting would produce. Nothing is written to your books until you post for real.

The transaction must be fully matched before you can preview it. If something is still unmatched you will be told to match it manually first, which makes the preview a useful completeness check in its own right.

The preview is available both from the bank transaction list and from the individual bank transaction page.

Post internal transfers between your own bank accounts

When you move money between two of your own bank accounts, the transfer shows up as two separate bank transactions — a payment from one account and a receipt into the other. Previously these had to be handled separately. You can now select both lines in the bank transaction list and choose Post Internal Bank Transfer to post them together as a single internal transfer.

Finance Manager checks that your selection makes sense before posting and tells you specifically what is wrong if not:

  • exactly two transactions must be selected
  • one must be a payment and the other a receipt
  • both must have the same booking date
  • neither may already be posted

Transfers between accounts in different currencies are supported. Finance Manager works out the exchange rate from the two transaction amounts and posts any realised exchange rate gain or loss automatically, so the transfer balances. If the entries do not balance, posting stops and reports the difference rather than leaving your books skewed.

Both bank account ledger entries are applied and marked as posted together.

Open the invoice behind a line

A View Document action (Ctrl + F6) has been added so you can see the source document for a line without navigating away. It is available on transaction detail lines and on bank transfer lines.

For payments to vendors and receipts from customers, this opens the PDF attached to the related incoming document. For receipts, it can also generate the posted sales document — invoice, credit memo, finance charge memo or reminder — as a PDF on the fly using your standard report selection. The action is only enabled when a document is actually available, so you are not left clicking something that does nothing.

Reverse an incorrect "Mark as Posted"

If you marked a bank transaction as posted by mistake, there is now a Reverse Mark as Posted action to undo it. Any error messages recorded against the transaction are cleared at the same time.

The posting actions on the bank transaction page have been grouped together under a Posting menu, so Post, Mark as Posted, Reverse Mark as Posted and Preview Posting now sit together instead of being spread across the ribbon.

Send only the bank transfers you select

The bank transfer list previously offered a single Send Bank Transfers action that sent everything suggested. That action is still there, now named Send All Suggested Bank Transfers, and it is joined by Send Selected Bank Transfers, which sends only the lines you have picked.

The two actions are grouped as a split button, so the full-send action is still one click away but is no longer the only option. Only transfers with status Suggested can be sent; anything else is rejected with a clear message.

Payment practice exclusions now follow the ledger entry

Bank transfer validation previously read the exclusion from the vendor record, so one excluded vendor affected the whole transfer. Validation now reads the exclusion from each individual ledger entry instead.

To keep entries in step with the party they belong to, changing Exclude from Pmt. Practices on a vendor or customer now prompts you to apply the change to that party's existing ledger entries as well, so you decide whether it takes effect retroactively.

When bank transfers are validated, excluded entries are dropped from the transfer rather than the whole transfer being discarded because of one excluded party. A transfer is only removed entirely if every line on it is excluded. The validation applies to both vendor and customer transfers; previously only vendors were checked.

Regulatory reporting codes no longer required in FI, DK, DE and GB

Validation of regulatory reporting codes on cross-border transfers is now skipped entirely for the Finnish, Danish, German and British application families, where the requirement does not apply. Transfers in those markets are no longer blocked by a missing reporting code.

Choose where exchange rates come from

Bank accounts have a new Exchange Rate Source field with three options: Calculated, Exchange Rate From Bank and Currency Factor From Bank.

Previously Finance Manager always took the exchange rate and unit currency from the bank's transaction data when it was present. If you set the source to Calculated, that data is now ignored and the rate is derived instead, which is useful when your bank's reported rates do not match the basis you want to post on. The other two options keep using the bank-supplied values. This affects both payment and receipt transactions.

Account for overdraft in the balance summary

Bank accounts have a new Overdraft field. Where an account has an overdraft limit, the bank transfer summary now adds it to the net available amount and shows it as its own line, so the figure you are working from reflects what you can actually spend rather than just the cleared balance.

The summary also gains a View All Accounts action. By default the summary shows only accounts with bank transfers currently in progress; this action widens it to every bank account.

Onboarding matches bank accounts more accurately

When connecting bank accounts during onboarding, Finance Manager now reads the IBAN and currency reported by the bank and uses the currency when matching against existing bank accounts in Business Central. Accounts in your local currency are matched against accounts with a blank currency code, following the standard Business Central convention. The IBAN is now shown during onboarding too.

Bank consent requests now identify accounts by IBAN rather than by bank account number, which is what banks expect, and accounts without an IBAN are excluded from onboarding. An account is also only added when its bank could actually be identified from the SWIFT code, so unrecognised banks no longer produce half-configured entries.

Onboarding also reuses an existing resource group if one is already set up, instead of always deriving one from the company registration number — so re-running onboarding no longer risks creating a parallel setup.

Bank transfer status is checked less aggressively

The Bank Transfer Status Update job queue entry previously ran every minute. It now runs every 720 minutes (twice a day) within its existing 06:00–18:00 window, substantially reducing background load and the number of calls made to your bank.

This applies to new installations. Existing job queue entries keep their current schedule, so adjust the interval manually if you want the new cadence.

A Verify Grant Consent action has been added so you can confirm that the Entra consent for your tenant, environment and company is in place, and get a clear answer back rather than discovering a consent problem later as a failed sync.

The Finance Manager Setup page now has a Go to Webhook Subscriptions action, so webhook subscriptions are reachable directly from setup.

Fixes

  • Applying bank ledger entries could use the wrong sign. When applying entries, the amount to apply is now given the same sign as the entry it is applied to. Previously the raw remaining amount was used regardless of whether the entry was positive or negative, which could produce incorrectly signed applications.

  • Matching bank ledger entries filtered the wrong record. Apply rules for transaction type and currency were being evaluated against the rule record instead of filtering the bank ledger entries, so rules did not narrow the candidates as intended. Receipt and payment rules now correctly restrict matching to positive and negative entries respectively.

  • Matching a receipt could modify the record being iterated. Receipt matching now works on a copy of the transaction detail, preventing the loop from being disturbed partway through.

  • Posting a bank transaction no longer closes the page. Post and Mark as Posted previously closed the bank transaction page, so you lost your place. The page now stays open.

  • Deleting a webhook subscription could target the wrong environment. Deletion now only proceeds when the subscription's delivery URL matches the environment you are in — development URLs in sandboxes, production URLs in production — so a subscription belonging to the other environment cannot be removed by accident.

  • Webhook errors appeared in Swedish regardless of language. Five hard-coded Swedish error messages ("Kunde inte skicka request.") have been replaced with a single English label.

  • Banking role centre layout and labelling. The cue caption has been shortened from "Bank Transfers To Handle" to "To Handle", and the bank account balance part has been moved out of the cue group so it sits on its own rather than among the activity tiles.

  • Bank messages were lost when a code or text was missing. When your bank returned a status message, Finance Manager built the message text assuming both a code and a message were present. If either was missing the message could be malformed. Each part is now read independently, so you still get whichever part the bank supplied.

  • Copying a production environment to a sandbox left live webhook subscriptions behind. Webhook subscriptions are now cleared automatically when a company is copied into a sandbox, so a test environment cannot keep delivering against production subscriptions. Upgrade logic is also skipped in sandboxes.

  • First Due Date on payment suggestions was not reset. The field has been removed from the request page and is now cleared each time the report runs, so a value left over from a previous run no longer silently narrows your suggestions.

Upgrade notes

This release adds fields and tables, so an upgrade is required. No data is removed and no existing field changes meaning.

New fields: Exchange Rate Source and Overdraft on Bank Account, IBAN on the onboarding bank account buffer, and an internal preview flag on General Journal Template.

Permissions for the new objects have been added to the ARIFM EXECUTE permission set. If you assign permissions through a custom set rather than the supplied one, add execute rights for the Internal Transfer Mgt., Preview Posting, Reverse Mark As Posted, View Document Mgt., Copy Environment Logic and Onboarding Consent JQ codeunits, and for the Payment Plan and Validation Error Log tables and pages.

If you rely on payment practice exclusions, note the behaviour change described above: bank transfer validation now reads the exclusion per ledger entry, and you are prompted to decide whether to apply it to existing entries when you change it on a vendor or customer.

Preview posting creates a temporary journal template and batch while it runs and deletes them afterwards. These are internal and are not intended to be edited.

Onboarding now requires bank accounts to have an IBAN. If accounts in your setup are missing one, populate it before connecting them.

For partners and extension developers: the ARIFM Transac. Posting Prev. codeunit is now marked obsolete (pending) in favour of ARIFM Preview Posting. If you reference it, migrate before it is removed. A new integration event, OnBeforeOnRun_CodeunitTransReverseMarkAsPosted, lets you intercept the reverse-mark-as-posted logic.

26.23

A maintenance release containing build and tooling updates plus a small extensibility hook for partners. There are no functional changes for everyday users.

Upgrade notes

The OnAfterInitPaymentPlanGenJnlLine_CodeunitTransactionPosting method in the internal event handler was missing its [IntegrationEvent] attribute, so partner extensions could not actually subscribe to it. It is now a real integration event and can be subscribed to in order to adjust the journal lines created when a payment plan is posted.

26.22

This is a large release centred on payments. The headline addition is payment plans, which let you split a single invoice into several instalments and post them directly from the bank transfer. Payment validation has been rebuilt so that every problem with a transfer is listed individually in a new side panel instead of being squeezed into one combined message, and transfers are now blocked from being sent when the amount no longer matches the underlying ledger entry. Account balances update automatically when your bank reports a change, and the onboarding wizard has been reworked and simplified.

Payment plans

You can now split a suggested bank transfer line into several payments. On a bank transfer line with status Suggested, a new Payment Plan action opens a worksheet showing the creditor, the payment reference and the original amount. Add lines with their own amounts and payment dates, and the worksheet shows a running difference between the line amount and the sum of your plan lines. You cannot leave the worksheet until the two match, and the original source line cannot be deleted.

When you confirm, the instalments are posted to the ledger and applied against the original entry, and the bank transfer line is updated with the remaining amount so only the first instalment goes to the bank now. Each posted line gets a description that defaults to "Payment Plan \<Document Type> - \<Document No.>", which you can change before posting. Payment plans are supported for vendor, customer and employee entries.

Validation errors shown as a list

Bank transfer validation no longer concatenates problems into a single message field. Every transfer now has its own validation error log, shown in a new fact box on both the bank transfer list and the bank transfer card, with each error on its own line and highlighted. Where before a missing bank account and an invalid SWIFT code would be merged into one string, you now see them separately and can work through them one at a time. The error log is cleared and rebuilt each time the transfer is revalidated, and is removed when the transfer is deleted.

Validation itself is also more thorough:

  • Missing account details are reported as either "Bank Account No. or IBAN must be specified for the bank account" or "Bank Giro No. or Plus Giro No. must be specified for the bank account", rather than one generic message.
  • A missing bank account record no longer stops the rest of the validation from running — previously a missing customer or employee bank account could cause a hard error instead of a validation message.
  • SWIFT codes are validated only when present; a blank SWIFT code is no longer flagged.
  • Cross-border transfers are now checked for a regulatory reporting code. If the paying bank account and the creditor are in different countries and any line is missing a code, validation fails with a message telling you to fill in the code on the line and update the pay-to bank account. The Regulatory Reporting Code field is now visible on the transfer lines so you can correct it there.

Payments are blocked when amounts drift

When you send a transfer to the bank, each line is now checked against its ledger entry before anything leaves Business Central. If the entry has been closed, or the remaining amount no longer matches the transfer line amount, you get an explicit error naming the entry, the ledger amount and the transfer line amount, instead of the payment going out with a stale figure. This check applies to vendor, customer and employee entries, and takes any applied payment discount into account.

Related to this, transfer lines now keep themselves in step with the ledger. If an open vendor entry changes while the transfer line is still only Suggested, the line amount is updated to the new remaining amount. If the entry is closed, a Suggested line is removed altogether, and the transfer header is deleted when its last line disappears. The same cleanup happens when you exclude a document from payment practices. You can now also delete a bank transfer that is in Await Net Balance status.

Creditor addresses taken from the bank account

Addresses sent to the bank now prefer the address on the vendor's or customer's bank account when one is filled in, falling back to the address on the vendor or customer card otherwise. If the primary address line is blank, the second address line is used. This applies to vendors, customers, employees and bank accounts, and means payments carry the address the bank actually expects.

Automatic balance updates and onboarding changes

Bank account balances are now refreshed automatically when your bank reports a balance change, via a new balance notification subscription that is set up during onboarding and added to existing installations on upgrade. The balance comparison on the bank account balance page now compares against entries up to and including the working date rather than the previous day.

The setup wizard has been reworked. The terminology changed from "workspace" to "tenant" throughout, the instructional text is considerably shorter, and phone numbers can now be entered for both the main contact and the technical contact. The technical contact name and email are now mandatory. The wizard no longer asks you to complete Entra admin consent in the browser during setup. The authentication step now explains that a signatory must complete each bank link, and that Aritma will follow up before activation if they are not completed. Bank instruction links now point at the production site when you are in a production environment.

Two new ways to check bank connection status are available. A Get Consent Status action on the bank account list refreshes consent status for all connected accounts on demand, and after completing the wizard a daily background job does the same automatically until every connected account has been activated, then removes itself. On the role centre, once your subscription is set up but no bank accounts are connected yet, you now get a notification with a Start Bank Account Onboarding action.

Other improvements

Bank transfer lines now carry the document date from the underlying ledger entry, available on the transfer line page and in the bank transfer data query.

When posting the balancing bank account entry for a transaction, the description is now taken from the transaction detail line where that is unambiguous, falling back to the bank's additional information. Previously the additional information was always used. Mixed transactions that combine G/L and subledger details are left alone.

A Bank Signing URL field has been added to Finance Manager Setup. When filled in, bank signing redirects you back to that address after approving payments in your bank, instead of the generic Business Central landing page.

Fixes

  • Bank transfer fact box showed stale details. The fact box did not clear its fields between records, so when you moved to a transfer whose bank account had no SWIFT code, IBAN or similar, you could still see the values from the previously selected transfer. The fields are now cleared first.
  • Transfers already handled as rejected were re-polled. The background status update job now skips transfers whose rejection has already been handled.
  • Transactions could stay stuck as not completely fetched. Transactions that had details fetched but had never been posted were not marked as completely fetched and so were repeatedly re-processed. They are now corrected automatically.
  • Account numbers with separators broke onboarding. Bank account numbers and company registration numbers are now stripped of dots, dashes and spaces before being sent for onboarding, so formatted numbers no longer cause the registration to fail.
  • Connection test could pass on a stale token. Testing the connection from Finance Manager Setup now always requests a fresh token, so it reflects the current state of the connection rather than a cached one.
  • Background jobs retried too long after failing. The retry limit for the Finance Manager background jobs was reduced from 60 attempts to 5, so a persistent problem surfaces far sooner instead of being retried for hours.

26.21

This release corrects the amounts shown on transaction details for customer and employee payments, changes when a transfer is put on hold to await a net balance, and clarifies two confusing bank status names.

Clearer bank statuses

Two transfer statuses had captions that did not describe what the bank was actually reporting, and one of them was duplicated word for word. The status previously shown as "Awaiting banks acceptance" is now Accepted technical validation, meaning the bank has accepted the technical validation of the payment. The status previously shown as "Awaiting banks acceptance." is now simply Pending.

Fixes

  • Transaction detail amounts were wrong for customers and employees, and ignored the actual transfer amount. When matching a bank transaction detail back to a ledger entry, the amount was only filled in for vendor entries, and it always used the full remaining amount on the entry. Customer and employee entries are now handled as well, and the amount is taken from the matching bank transfer line where one exists, so partial payments show the amount that was actually sent rather than the full outstanding balance. The remaining amount on the ledger entry is still used as a fallback.
  • Transfers were sometimes incorrectly put into Await Net Balance. The decision to put a vendor transfer on hold pending a net balance was made before all lines, including watched invoices, had been added. The check now runs on the completed transfer, so a transfer is only held when its total is actually positive.
  • Error message about duplicate advanced setups listed a field that is not part of the check. The Danish, Finnish, Norwegian and Swedish translations mentioned a recipient account number that the uniqueness check does not include. The message now matches the English original.

26.20

A fix release addressing missing detail lines on outgoing payment transactions.

Fixes

  • Payment transaction details were silently skipped. When fetching details for an outgoing payment, the app checked whether any transaction detail already existed for that transaction and, if so, stopped without adding anything. This meant a transaction that had been partly filled in earlier never received its remaining detail lines. The check has been removed, so details are now written whenever the bank returns them.

26.19

A fix release addressing missing detail lines on incoming payment transactions.

Fixes

  • Receipt transaction details were silently skipped. As with outgoing payments, fetching details for an incoming payment stopped early if any transaction detail already existed for that transaction, leaving the remaining detail lines unwritten. Details are now written whenever the bank returns them.

26.18

A small corrective release that stops already-posted bank transactions from being picked up again when transaction lines are fetched.

Fixes

  • Posted bank transactions are no longer re-processed when fetching transaction details. When the app filled in the detail lines for transactions that had not yet been completely fetched, it also included transactions you had already posted, which could cause unnecessary work and repeated processing of closed items. Posted transactions are now excluded, and any older posted transactions still flagged as incompletely fetched are marked as complete automatically the first time you fetch after upgrading.

26.17

This release reworks how bank transactions are brought into Business Central so that fetching is more robust, and it cleans out a number of long-deprecated settings and objects. It also corrects the document reference written on customer payment suggestions.

More reliable transaction import

Previously, each bank transaction had its detail lines fetched immediately as the transaction header was created. If anything interrupted that process part way through — a timeout, a connection problem, an error on one transaction — you could be left with transactions that had no detail lines and no easy way to complete them.

Fetching is now split into two stages. Transaction headers are read from the bank first, then detail lines are filled in for every transaction that is not yet marked as completely fetched. Each transaction is committed as it completes, so an interruption no longer loses the work already done, and the next fetch simply picks up where the previous one stopped. The app also now refuses to create duplicate detail lines for a transaction that already has them.

A transaction that ends up with no detail lines at all is now left with the status Open rather than being treated as fully processed, so it stays visible for you to deal with.

Cleanup of deprecated setup fields

Two setup fields that had been hidden and marked for removal for several releases are now gone for good: Include Credit Memos on the Finance Manager setup (its behaviour is covered by the Merge Payment options) and the old Tenant field (replaced by Subscription Name). The obsolete Global Tenant list has also been removed; environment configuration lives entirely in Global Environment now.

Fixes

  • Customer payment suggestions now carry the correct document reference. The external document number on a suggested customer transfer was being filled with the ledger entry's external document number, which did not always identify the entry in your own system. It now uses the document number instead, making it easier to recognise the entry the payment belongs to.

Upgrade notes

Several integration events that were deprecated in version 24.5 have now been removed, along with the codeunits that only existed to host them. If you have a customisation subscribing to those events, move it to the replacement events before upgrading.

26.16

A small release that smooths out webhook setup.

Fixes

  • Setting up webhook subscriptions no longer fails when the required app registration already exists. Creating a new subscription now ensures the Entra application the integration needs is in place first, and the setup step exits quietly if that application has already been registered instead of attempting to add it again.

26.15

This release gives you direct control over webhook subscriptions and improves bank account selection on vendor payment suggestions.

Managing webhook subscriptions

The Webhook Subscriptions list is no longer a read-only view that you edit by hand. You can now create the consent and payment status subscriptions in one step with a New Subscription action, and remove one or several selected subscriptions with a Delete action. Direct editing of the list has been disabled, since the subscriptions are maintained on the service side.

Fixes

  • Vendor payments now pick a bank account matching the invoice currency. When a vendor had several bank accounts and no preferred bank account set, the app gave up and skipped the suggestion. It now narrows the vendor's bank accounts to those in the currency of the entry being paid, so vendors with one account per currency get a suggestion instead of being passed over.

26.14

This release introduces a guided setup experience for connecting your organisation and bank accounts to Aritma, and adds push-based status updates so payment and consent changes arrive without you having to ask for them.

Guided setup for new companies

A setup wizard now walks you through getting started. It explains what will happen, lets you either create a new workspace for your organisation or pick an existing one, and collects the main contact (who becomes the workspace owner and receives an invite by email) and an optional technical contact.

The wizard then reminds you of the prerequisites your bank accounts need in Business Central — account number, IBAN and SWIFT code — and presents the accounts that qualify so you can choose which ones to connect. Where an account reported by the bank cannot be matched automatically to a Business Central bank account, a matching screen lets you pair them up by hand rather than failing silently.

The final steps cover bank authentication. You can either authenticate each bank connection yourself with BankID using the links shown in the wizard, or enter recipient and sender details so the authentication links are sent to whoever will perform the signing. When everything is submitted, the wizard shows per-bank instructions for the remaining steps on the bank's side.

If Finance Manager has not been configured yet, a notification appears on the Finance Manager role centre with a button that opens the wizard directly. You can also start the wizard any time from a new Finance Manager Setup action on the Finance Manager setup page.

Bank connection status on the bank account

Bank accounts now carry the consent that authorises Finance Manager to read them, along with the current consent status — created, started, authorised, expired, revoked, awaiting approval or failed. This is what lets the system tell you that a bank connection has lapsed rather than simply returning no data.

Until now, the status of a payment only changed when something in Business Central went and asked the bank. The app can now receive pushed updates instead. When the bank reports that a bulk payment, an individual payment line or a bank consent has changed state, that status is written straight to the corresponding transfer, transfer line or bank account.

A Webhook Subscriptions page shows which subscriptions exist and which event types each one covers.

Fixes

  • Error messages from the bank no longer break processing when they are incomplete. When the bank returned a status message that was missing a category, code or text, reading it could fail outright. Partial messages are now handled gracefully and the status update completes.
  • Long values from the service no longer cause errors. Identifiers, links, names and similar values returned by the service are now truncated to fit the fields they are stored in instead of raising an error when they are longer than expected.
  • Two error messages that appeared in Swedish regardless of your language are now translatable.

26.13

This release brings project accounting into bank transaction handling, adds an Excel round-trip for transaction journal lines, gives you a printable view of a bank transaction as the bank delivered it, and considerably reworks how payments are applied to ledger entries.

Projects on bank transactions

You can now assign a project and project task to bank transaction lines, to transaction journal lines and to bookkeeping rules. Entering a project task pulls in its global dimensions and, where no description has been entered, its description. On a transaction journal line the project's currency is applied as well.

When a bookkeeping rule with a project is matched, the project and task flow through to the transaction line, and when the transaction is posted the resulting general journal line is created as a billable project line with a quantity of one. Projects are only allowed on lines posting to a G/L account. The project fields are hidden by default on the relevant pages — switch them on through personalisation if you work with projects.

Advanced setup now covers incoming payments

The advanced setup has been extended beyond merge-payment behaviour with a new Receipt Transactions category offering two options: Exclude from matching and Do not split by structured remittance information. The first stops selected incoming transactions from being matched automatically; the second keeps a transaction as a single line instead of splitting it into one line per structured remittance reference.

These options are driven by a new Advanced Setup Filter, reachable from the advanced setup line. There you choose a text or code field on the incoming transaction and the text it must contain for the rule to apply, so you can target, for example, transactions whose remittance text contains a particular reference. Filters are removed automatically when the setup line they belong to is deleted.

The uniqueness check on advanced setup lines now also takes the sub category into account, so you can set up more than one sub category for the same account, and the account number is only required where the chosen sub category actually needs one.

Bank transactions report

A new Bank Transactions report shows a bank transaction and its detail lines as the bank delivered them — account, sender or receiver, date, amount, booking reference and the message or remittance reference. The report carries a note making clear that it is a visualisation of the data Business Central received, and that the original accounting entry is in the file also linked to the transaction. Run it from the bank transaction list.

Original bank data kept with each transaction line

Incoming transaction lines now retain the raw entry details received from the bank. A new Entry Details Information field in the transaction detail fact box shows this content formatted for reading, and a Read Entry Details Information action displays the same thing in a message. This is useful when you need to see exactly what the bank sent, down to fields the app does not display. The stored data is cleared automatically when the transaction is posted.

Import and export journal lines through Excel

Transaction journal lines can now be exported to Excel and imported back. The export produces a sheet with account type and number, description, currency, instructed amount, amount, applies-to document type and number, posting type, VAT posting groups, the payment practices exclusion flag and all eight dimension codes. Importing replaces the lines for the transaction detail you are working on with the contents of the sheet, validating each value as it goes.

Reload a transaction from the bank

A Reload transaction action on the bank transaction list removes an unposted bank transaction and fetches it again from the bank for the same booking date. Use it when a transaction came in wrong or you want to start over on a transaction you have been editing. Posted transactions cannot be reloaded.

How payments are applied

Payments to vendors and customers are now applied using an application ID with an explicit amount to apply, rather than by pointing at a document type and number. This handles the case where several entries share a document number, and it makes the amount being applied explicit. The description on an automatically matched payment line now shows the document type, document number and ledger entry number, making it obvious which entry was picked.

Fixes

  • Payment statuses on customer, vendor and employee ledger entries no longer show the wrong account type's status. The payment status shown on a ledger entry was looked up only by entry number, so an entry could display a status belonging to a different account type that happened to share that number. The lookup now also matches on the account type.
  • Matching a payment to a customer or employee entry no longer stores a vendor entry number. When an incoming payment was matched to a customer or employee ledger entry, the reference written back to the transaction line was built from a vendor entry number instead of the matched entry. The correct entry number is now used.
  • Transactions no longer match against your own bank accounts in the wrong direction. Internal transfer matching looked at both the debtor and creditor account regardless of whether the transaction was money in or money out. Incoming transactions are now matched on the sending account and outgoing transactions on the receiving account, and internal transfers are only recognised when the remittance text carries the app's own transfer marker — so ordinary customer and vendor payments are no longer mistaken for internal transfers.
  • Bank transfer summary totals are now converted to the bank account's currency. Transfers in a foreign currency were added to the summary at face value, inflating or understating the total. Amounts are now converted using the exchange rate for the payment date. Transfers with the status received are also included in the committed total.
  • Rejected payment lines now show why they were rejected. When a payment line comes back rejected, the app now fetches the detailed status for that line and records the bank's reason codes and messages on it.
  • Employee payments now use the message to recipient as the payment reference. Employee transfer lines took their payment reference from a field that is generally empty for employee entries, leaving the payment without a reference. The message to recipient is used instead.
  • Vendor payment suggestions no longer stop at the first entry that cannot be paid. When creating suggestions for a vendor, an entry that could not proceed would end the run for that vendor, skipping the remaining open entries. Each entry is now evaluated on its own.
  • Deleting a bank transfer gives a correct explanation. The message shown when a transfer cannot be deleted now states that only transfers with the status Suggested or Validation Error can be removed, which is what the rule has always been.
  • The internal bank transfer description is no longer overwritten with a fixed text.

26.12

This release focuses on getting payment problems in front of you before the bank rejects them, and on making the app's background jobs set themselves up correctly. Bank account details on payment suggestions are now checked more thoroughly, a suggestion run no longer stops dead when one vendor is missing bank details, and the transaction journal shows the name of the account you are posting to.

Stronger checks on payment details

Payment suggestions and transfers are now validated against the SWIFT/BIC code on the recipient's bank account. If the code is not a valid SWIFT code, the transfer is set to Validation Error with a message naming the offending code, and the transfer cannot be sent to the bank. Previously an invalid code was passed on and the payment could be rejected later by the bank.

Missing bank account information is also handled better. Previously, if a vendor had no bank account at all, or had several bank accounts without a preferred one selected, the whole payment suggestion run stopped with an error and you had to fix the vendor before you could get any suggestions. Now the run continues, and the affected transfer is marked with Validation Error and the message that bank account information is missing, so you can see all problems at once and fix them from the transfer list.

Validation messages are now combined, so a transfer that has several problems lists all of them rather than only the first.

Vendors that are marked as excluded from payment practices no longer end up in payment suggestions — their suggested transfers are removed during validation.

Revalidating transfers

Validate Bank Transfers is now a promoted action on the bank transfer list, so you can re-run validation on transfers you have just corrected without digging through the menu. A background job is also available that periodically revalidates all transfers sitting in Validation Error, so transfers correct themselves once the underlying master data is fixed.

Account name in the transaction journal

The transaction journal lines now show the name of the account next to the account number, for vendors, customers, G/L accounts, bank accounts, fixed assets and employees. You can click the name to open the corresponding card.

Currency information from the bank

For transactions in foreign currency, the unit currency reported by the bank is now stored on the transaction and on its detail lines, and the exchange rate is now also picked up on incoming payments, not just outgoing ones.

Fixes

  • Instructed amount currency was read from the wrong place. When the bank reported both an instructed amount and a transaction amount, the currency code on the instructed amount could be taken from the wrong part of the bank's response, leaving it blank or wrong. The amounts and currencies are now read from the correct fields in all transaction types.
  • Transactions were wrongly flagged as not fully matched. Creating journal lines for a transaction could immediately set that transaction back to Open with a "not fully matched" message. That check no longer runs at that point.
  • Suggestion runs could hang when scheduled. When the payment suggestion report found validation errors it asked whether you wanted to open the transfer list. When the report ran unattended as a background job there was nobody to answer. The question is now only asked when a user is present.

Upgrade notes

Installing this version now creates the full set of background job queue entries for the app — status updates, fetching transactions, bookkeeping, mark as posted, scheduled bulk payment, transfer validation and the bank transfer suggestions report — with recommended intervals and run windows. All entries are created with status On Hold, so review them and set the ones you want to Ready. Any existing job queue entries for these objects are replaced.

A new extension point has been added for partners that need to adjust how customer ledger entries are filtered when direct debit suggestions are created.

26.11

A round of corrections to the bookkeeping rules, payment discounts in the transaction journal, and handling of internal transfers between your own bank accounts.

Internal bank transfers are now labelled for the bank

When you move funds between two of your own bank accounts, the payment is now sent to the bank with the standard internal-transfer purpose code and a description identifying it as an internal transfer of funds. This helps the bank classify the payment correctly and makes it easier to recognise on your statement.

Payment discounts when matching in the transaction journal

When you pick a customer or vendor ledger entry on a transaction journal line, the amount proposed now takes any available payment discount into account. If the discount date has not passed as of the booking date of the bank transaction, the proposed amount is the remaining amount less the remaining discount; otherwise the full remaining amount is proposed as before.

Fixes

  • Bookkeeping and apply rules ignored their first and last day. Rules limited by day in month used an exclusive comparison, so a rule set to apply from day 1 to day 5 only applied on days 2 to 4, and a rule for a single day never applied at all. The range is now inclusive at both ends.
  • Transfers stuck in Validation Error could not be deleted. Only transfers with status Suggested could be removed. You can now delete transfers with status Validation Error as well.
  • Error when matching a transfer of funds with a long remittance text. Looking up the internal fund transfer behind a transaction failed with a length error when the remittance text from the bank was longer than expected. The text is now truncated safely before lookup.
  • Account type was lost when inserting a journal line. Inserting a new transaction journal line above or below an existing one did not carry over the account type from the line it was inserted from.
  • Swedish translation. A missing full stop in the Swedish text for the "Awaiting bank's acceptance" status.

Upgrade notes

Two new extension points are available for partners: one that lets a partner take over how payment status is retrieved for a bank transfer, and one that is raised before a customer bank transfer suggestion line is inserted.

26.10

This is a large release for anyone who pays vendors that also send credit memos. How credit memos are netted against invoices is no longer a single on/off switch — you now choose a payment merge strategy, either for the whole company or per vendor. Payment discount handling in the suggestion run has also been reworked so that invoices with a discount are proposed on the discount date rather than being missed.

Choose how credit memos are merged into payments

The Finance Manager Setup page has a new Merge Payment field that replaces the old Include Credit Memos checkbox. You pick the option that matches how you work:

  • Only full deduction per payment date — a credit memo is only deducted when the invoices for that payment date fully cover it. This matches the previous behaviour.
  • Await net balance for payment — if credit memos exceed the invoices, the whole group is held back instead of being paid, and waits for future invoices to balance it out.
  • Merge via Finance Manager portal — invoices and credit memos are passed on and the netting is handled in Finance Manager.
  • No merging — payment per transaction — every invoice becomes its own payment.
  • Payments only (no credit memos) — credit memos are left out of the suggestion entirely.

A new Advanced Setup page, reachable from Finance Manager Setup, lets you override the company-wide choice for individual vendors. Each line links an account to one of the merge options, and each combination of account and category can only be set up once.

Transfers waiting for a net balance

Payment groups that are being held back get the new status Await Net Balance. A dedicated tile on the Finance Manager role centre and activities page shows how many transfers are waiting, so they do not disappear from view. The tile is only shown when you have selected the await net balance option.

On a held transfer line you can act on an individual invoice: Set Invoice as Suggested releases it into a normal payment suggestion, and Exclude from Payment Practices takes it out of the payment process entirely after a confirmation.

Each time you run the payment suggestion, held transfers for the vendor are rebuilt from the current ledger situation, so the held amounts always reflect open invoices and credit memos as they are today.

Payment discounts in the suggestion run

Invoices that carry a payment discount are now treated on their own terms. When you include payment discounts, an invoice whose discount date falls within the period you selected is proposed for payment on the discount date, even if the due date is later — previously such invoices could fall outside the due-date range and be skipped. The discount is only deducted when the proposed payment date actually falls on or before the discount date, so you no longer see a discount deducted from a payment that is too late to earn it.

Transfer lines carry a new Payment Discount Applied marker and an optional Pmt. Discount Date column, which you can add to the line view. The date is highlighted when a discount has been applied to that line.

Smaller improvements

The Include Credit Memos option has been removed from the payment suggestion request page; the merge strategy now decides this. Error messages on transaction detail lines are shown in red so they stand out. The client ID and subscription ID are now visible on the global environment page, which makes it easier to confirm which subscription an environment is connected to.

Fixes

  • Split transaction detail lines inherited the wrong values. When a transaction detail was split onto a new line, the amount and the remittance type, reference and text were copied from the original line. The new line now starts blank for these fields.

Upgrade notes

The Include Credit Memos setting is marked for removal and is no longer shown. If you relied on it, set Merge Payment instead. Vendors with no explicit merge setting fall back to Only full deduction per payment date, which matches the previous behaviour. Merge options are currently supported for vendors only.

26.9

A corrective release around sending payments to the bank. Several operations that loop over bank transfers were skipping records, and the status of a transfer immediately after sending is now set correctly.

Bank transfers waiting for attention stand out

Bank transfers waiting for your attention are now highlighted in red on the Finance Manager role centre and activities page whenever the count is above zero, so outstanding work stands out at a glance.

Fixes

  • Not all selected transfers were sent to the bank. When you sent several suggested transfers at once, processing one transfer disturbed the list being worked through, so some transfers were silently skipped. Each transfer is now processed independently and the whole selection is sent.
  • Scheduled status updates skipped transfers. The same problem affected the background job that refreshes payment status from the bank, so some transfers kept a stale status. All transfers with a payment reference are now refreshed.
  • Status after sending was unreliable. After a payment was accepted by the bank, the app immediately asked the bank for the status again, which could fail or return nothing useful. The transfer and its lines are now set directly to "received by the bank" and updated from the bank on the next status refresh.
  • Unclear error when the bank rejected a payment. The raw response from the bank was shown on its own, which could be mistaken for an application message. Rejections are now clearly presented as an error with the bank's response quoted.

26.8

This release protects you from sending the same payment to the bank twice, makes the bank balance comparison on the account balance overview correct, and lets you apply a bookkeeping rule to several transaction lines at once.

No more duplicate payments after an interrupted send

When a payment is accepted by the bank, the bank's confirmation is now stored on the transfer before anything else happens. If the session is interrupted part-way through — a timeout, a lost connection, an error while updating the transfer — sending the transfer again picks up where it left off using the stored confirmation instead of creating a second payment at the bank. Once the transfer has been fully updated, the stored confirmation is cleared.

As a safeguard, a transfer that has already been created at the bank can no longer be deleted. If you try, you are told to cancel the payment instead. Payment references received from the bank also cannot be overwritten by a second send.

Bank balance compared against the right day

The bank account balance overview previously compared the balance reported by the bank against your full bank account ledger, including entries posted today. Since the bank reports its balance as of the end of the previous day, the comparison was misleading. The ledger side is now calculated up to the previous day, so the difference you see is a real difference.

Apply a bookkeeping rule to several lines

On the transaction detail lines you can now select several lines and apply a bookkeeping rule to all of them in one go. Previously the rule was only applied to the line the cursor was on.

Fixes

  • Account balances were fetched from the wrong date. When you had more than one bank account connected, the "fetch balances from" date was taken from the first account and reused for all the others, so some accounts were queried from the wrong point in time. Each account now uses its own last known balance date.
  • Messages from the bank were overwritten or lost. Messages returned with a payment replaced each other, and long messages could overflow. Messages are now appended, and only as long as they fit.
  • Transfer lines kept a stale status. When the bank's reply covered the whole transfer rather than individual payments, the lines underneath were not updated. They now follow the status of the transfer.
  • Matched transactions stayed open. When a transaction detail was matched to a bank ledger entry by rule, the transaction itself stayed in status Open. It is now released.

26.7

A small corrective release for approving payments at the bank.

Fixes

  • Partially approved payments were left out of the approval request. When a payment group had already been partly signed, those payments were not included when you approved payments, so they stayed partly signed. Payments that are partially approved are now sent for approval together with the ones that are only received by the bank.
  • Approving with nothing to approve. If no payments qualified for approval, an empty request was still sent to the bank. The app now simply does nothing.

Upgrade notes

This release also contains an update of the build and tooling files, with no effect on functionality.

26.6

This release reworks how currency rounding is handled when posting bank transactions, introduces signing status tracking at the individual payment line level, and tightens the payment-sending flow. Several of the changes affect day-to-day posting, so read the upgrade notes before updating.

Automatic rounding correction when posting

Previously, if a bank transaction in a foreign currency did not balance to the last decimal after conversion to your local currency, posting either silently adjusted the bank line or stopped with an error telling you the difference was over the rounding precision. Now, when the remaining difference is small enough to be explained by rounding across the posted lines, the system posts a separate correction line to the rounding accounts configured on the currency, described as "Rounding correction for" followed by the currency code. You no longer have to intervene in those cases, and the correction is visible as its own ledger entry instead of being hidden inside the bank line.

Document numbering on posted bank transactions

Posted bank transactions now always take their document number from the remittance number series. Previously, if no number series was set up, the system fell back to using the bank's transaction ID (truncated to 20 characters) as the document number, which produced unreadable and inconsistent document numbers. The remittance number series is now required, and posting stops with a clear message if it is missing.

Signing status per payment line

Bank transfer lines now carry their own signing status, shown alongside the transfer status. When you create a signing basket, the basket is now built from the payment IDs of the individual lines that the bank has actually received, rather than from the transfer header alone. Status updates returned by the bank are matched back to the correct line by payment ID, so a transfer containing several payments that the bank handled differently now shows an accurate picture per line instead of stamping every line with the header's status.

Related to this, the transfer status previously labelled "Partially rejected" is now called Mixed Payment Status, which better describes the situation: some payments in the bundle succeeded and others did not, and you need to look at the lines to see which.

Payment control check before sending

When you send a bank transfer to the bank, the system now checks your Inyett Detect payment control state first, according to your setup. The confirmation message that previously appeared ("Payment sent successfully") has been removed — it was shown before the bank had confirmed anything, which was misleading. You now see the real status on the transfer instead. Cancelling a payment still confirms, and the message now names the payment ID that was cancelled.

Payment suggestions sent to Inyett Detect are now limited to vendor and customer lines, matching what the service supports.

Fixes

  • Payments in foreign currency were missing a currency on the debtor account. The account you pay from is now always sent to the bank with its currency code (falling back to your local currency when the bank account has none), which avoids rejections from banks that require it.
  • Posting a transaction with a zero transaction amount could fail with a division error. The exchange-rate calculation is now skipped when there is nothing to divide by.
  • Duplicate payment suggestions for customers and employees. The check for previously rejected transfer lines only looked at vendor lines, so rejected customer and employee payments were not recognised. It now checks the correct account type.
  • Charge Amount on a bank transaction could not be corrected. The field is now editable.
  • Fetching transactions could fail on an internal consistency check. Transactions are now written correctly even when details arrive in more than one step.

Upgrade notes

The No. Series Remittance field in Finance Manager Setup is now mandatory for posting. Make sure it is filled in before posting bank transactions after the upgrade.

26.5

This release adds full currency support to the transaction journal, so you can account for an incoming or outgoing payment in the currency it was actually invoiced in, and fixes several currency conversion problems when posting.

Currency in the transaction journal

When you do manual accounting on a bank transaction, the journal now works with two amounts. The header shows the transaction currency, the instructed currency and the exchange rate the bank applied — and the exchange rate is editable, so you can correct it when the bank's rate does not match what you need to post. On the lines there is now an Instructed Amount with its own Currency Code alongside the transaction amount.

In practice this means you enter the amount in the invoice currency and the system calculates the transaction-currency amount for you using the header's exchange rate. When you pick a document to apply to, the line now takes the currency and remaining amount directly from that customer, vendor or employee ledger entry, so applying a EUR invoice from a SEK bank account no longer requires manual conversion. The balancing line created for the remainder of a transaction also picks up the correct currency.

More reliable posting across currencies

Posting now handles the case where the transaction currency, the instructed currency and your local currency are all different — previously the conversion in that situation produced wrong amounts or an unwanted currency factor. Lines with a zero amount are no longer posted at all, and the balancing bank line now takes the transaction's own currency when that differs from local currency.

Rounding behaviour changed as well: where the difference between the posted lines and the transaction total previously had to be exactly one cent to be absorbed, the difference is now compared against the actual rounding precision of the currency. If it is larger than that, posting stops with a message telling you the exact difference so you can review the transaction before posting.

Fixes

  • Rejected bundles showed the wrong status on every line. When a bank reported a transfer as partially rejected, all lines were stamped with the header status. Each line now gets its own status fetched from the bank.
  • Bank transfer list refreshed unnecessarily when opened, which could discard unsaved edits.

Upgrade notes

The extension points used by companion and customer extensions have been reorganised. All integration events now live in a single internal event handler object, and the previous events in the individual objects are marked obsolete. Existing subscriptions keep working for now, but should be moved to the new events. The previous payment handler and get-transactions objects are also marked obsolete for the same reason.

26.4

This release makes transaction retrieval complete when a bank returns large result sets, reworks when and how payment suggestions report validation problems, and extends payment practices reporting to customers and employees.

All transactions are now retrieved, not just the first page

When a bank returns a long list of transactions, or a transaction with many detail rows, the response is split into pages. Previously only the first page was read, so transactions and detail lines could be silently missing. The system now follows the bank's "next page" links until everything has been retrieved. This applies both when fetching transactions for an account and when fetching the details of a single transaction, including the JSON download.

Clearer validation of payment suggestions

Validation of bank details has moved to a single consistent step that runs after the suggestion has been built. The practical differences are:

  • A transfer that previously stayed flagged as a validation error even after you fixed the bank account is now re-validated and returns to Suggested, with its message cleared.
  • Transfer lines now get the same status as their header, so a transfer in error state no longer shows lines claiming to be ready.
  • The prompt offering to open the list of failed transfers now appears once at the end of the run, and only when this run actually produced errors. Previously it could appear repeatedly, and could appear because of old errors from a previous run.
  • A suggestion in error state is no longer silently grouped together with a valid one for the same vendor, customer or employee.

Payment practices on customer and employee entries

The Exclude from Payment Practices flag now carries through the whole chain. You can set it on a transaction journal line (only for customer, vendor and employee lines — the system blocks it elsewhere), and it is carried to the transaction detail and onto the posted ledger entry. Customer ledger entries also pick up the exclusion setting from the customer card when nothing more specific is set, and employee ledger entries now carry the flag from the journal line.

Due dates on payment suggestions

Payment suggestions for customers and employees no longer propose a payment date in the past. If the due date has already passed, today's date is used instead — this already applied to vendor payments and is now consistent across all three.

A new Initial Due Date column is available (hidden by default) on bank transfer lines. It shows the due date from the original posted invoice or credit memo, so you can see what the due date was before it was changed on the ledger entry.

Fixes

  • Applied bank transactions were incorrectly flagged as "not fully matched". A transaction that you had applied to a bank account ledger entry still got a message asking you to match it manually. Applied transactions are now left alone.
  • Fetching transactions could stop with an error when a bank returned an end-to-end identification that was not a number.

26.3

A small corrective release.

Fixes

  • Bank transfer statuses were not being refreshed in the background. A malformed filter in the scheduled status-update job meant that transfers which should have been checked against the bank were skipped. Statuses now update as expected.
  • Transfers accepted by the bank were left looking as if they still needed signing. When the bank reported a payment as accepted for settlement or accepted technically, the signing status is now set to Finalized along with the transfer status.

26.2

This release introduces rules for automatically applying bank transactions to open bank account ledger entries, replaces the tenant-based connection setup with a subscription-based one, and makes validation errors on payment suggestions correctable without starting over.

Rules for applying bank transactions automatically

A new Apply Bank Ledger Rules page lets you define rules that recognise recurring bank transactions and apply them to the matching open bank account ledger entry without any manual work. Each rule has a search filter matched against the transaction's remittance text, and can be narrowed by transaction type (payment or receipt), currency, a range of days within the month, and a posting date formula that widens or narrows the date window around the transaction's booking date. A rule only applies when exactly one open entry matches on amount and date, so an ambiguous situation is always left for you to resolve.

If Mark as Posted is enabled on the rule, the transaction is also marked as posted automatically. Rules are evaluated as part of the normal matching process for both incoming and outgoing transactions, and are reachable from the Bank Transaction list and card.

Alongside this, there is now a Mark as Posted Batch action that processes all released, unposted, applied transactions in one go. The single Mark as Posted action now runs through the same mechanism. Posting a transaction that is applied to a bank document is now blocked with an explanatory message — applied transactions should be marked as posted, not posted again.

Subscription-based connection setup

The connection to the Aritma service is now configured against a named subscription rather than a tenant. Finance Manager Setup has a new Subscription Name field, and the underlying settings (tenant ID, client ID, subscription ID, environment scope) are maintained on a new Global Environment page. Your existing settings are migrated automatically on upgrade.

Correcting payment suggestions that failed validation

Transfers that fail validation because the recipient has no usable bank account details are now easier to deal with. The pay-to bank account, payment date and transfer lines are editable while a transfer is in Validation Error state, so you can correct the details in place. A new Validate Bank Transfers action re-runs validation on the transfers in view, moving the ones you have fixed back to Suggested. The message explaining the problem is now highlighted in the list so it is easy to spot.

The prompt offering to open the list of failed transfers now appears once when the whole suggestion run is finished, rather than after each vendor, customer and employee section.

Reconciliation report and activity overview

The bank account reconciliation report now takes an opening balance into account: it uses the start of your date filter as the opening date and shows the opening balance as its own column, so the report reconciles over a period instead of only to a date. You can also filter the report by bank account number.

On the Finance Manager role centre, the Bank Transfers To Handle tile now counts everything that genuinely needs attention — rejected, mixed status, cancelled and validation errors that have not been marked as handled. The separate Rejected tile has been hidden, since it is now covered by that count.

Most Finance Manager pages now have teaching tips explaining what the page is for.

Fixes

  • Fetching transactions re-downloaded from the wrong date. The starting point is now taken from the last posted transaction on the account rather than the last transaction of any kind, so already-fetched but unposted transactions no longer push the window forward and cause gaps. A date you enter manually is also no longer carried over to the next bank account in the run.
  • Sending a customer refund to the bank could fail or use the wrong account. The customer bank account was looked up with only one key, so it could not be found. It now resolves correctly.
  • Payment dates in the past. A vendor payment whose due date has already passed is now suggested with today's date instead of the overdue date.
  • Payment details with no reference block were skipped, so lines were missing from the transaction. They are now created from the available detail.
  • A transfer that failed validation could not be sent, but gave no indication why. It is now flagged with a validation error and an explanatory message instead of silently producing an incomplete request.

Other improvements

From the General Ledger Entries page you can now drill down on the External Document No. to open the bank transaction it came from. The Bank Transfers to Sign page has gained the bank transfer details FactBox showing the recipient's account details.

26.1

This release adds the ability to apply bank transactions directly against open bank account ledger entries, improves automatic matching of incoming payments, and brings currency handling and the transaction journal closer to how Business Central journals normally behave.

Applying bank transactions to bank account ledger entries

You can now apply a bank transaction to one or more open bank account ledger entries. Choosing the assist edit on Applies-to Bank Doc. No. opens a worksheet showing the open entries for the bank account, with the total amount to apply and a running remaining amount at the top. Tick the entries you want and adjust the amount to apply per entry; the system prevents you from applying more than an entry's remaining amount. When several entries are applied, the field shows "Multiple entries...". On a posted transaction the same action opens a read-only view of what was applied.

Marking a transaction as posted now settles each applied entry individually: the remaining amount is reduced by the applied amount, and the entry is only closed when nothing remains. Marking as posted is refused if the total applied amount does not equal the transaction amount, or if applying would push an entry's remaining amount below zero — so a partially applied transaction can no longer be closed by mistake.

Better matching of incoming payments

Matching of incoming payments against open customer invoices has been improved in two ways. The remittance reference is now searched together with the remittance text, so references the bank supplies in a separate field are no longer ignored. And the system now builds a picture of your document numbering from your open customer ledger entries — prefixes, number lengths and the ranges in use — and uses it to recognise document numbers in free-text remittance information, including numbers written without their prefix. For SCOR-type references, trailing check digits are also tried, so a reference that carries extra digits still finds the right invoice.

Transaction journal

When you pick a document to apply to on a transaction journal line, the line now fills in the account number, the remaining amount and the currency from that ledger entry, instead of leaving you to type them. Changing the account on a line now clears a stale application rather than leaving it pointing at the wrong document. Shortcut dimensions 3 to 8 are now available on the journal lines, and VAT amount and shortcut dimensions carry over from the transaction detail when the journal is created.

A transaction whose original amount is zero no longer blocks you with a balance warning when there is nothing to balance.

Fixes

  • Currency factor was applied even when there was no conversion, which could distort posted amounts. It is now only set when the rate actually differs from one.
  • Bank charges were posted in the wrong currency when the bank account was in a foreign currency. The charge now follows the currency being posted.
  • Transactions that did not balance by one cent after currency conversion are now adjusted automatically on the bank line instead of failing.
  • Update Payment Status was unavailable on the Bank Transfers to Sign page. The action is now visible and promoted.
  • The bank account on a suggested transfer could not be changed. It is now editable while the transfer is still Suggested.
  • Debtor and creditor account numbers could be truncated to the length of the IBAN field instead of their own.
  • The status-update background job had no interval set, so it did not run on a schedule. It now runs every five minutes.

Other improvements

The bank transfer list now shows a FactBox with the recipient's bank account details — account code, currency, SWIFT, IBAN, bank branch and account number — so you can check where a payment is going without opening the transfer. The transaction detail and transaction journal line FactBoxes show the account name, currency, remaining amount and the difference between the instructed amount and what remains, making over- and underpayments immediately visible.

26.0

Aritma Finance Manager is the first release of Aritma's open banking extension for Business Central. It connects your Business Central bank accounts to your banks through the Aritma service so that you can retrieve bank transactions, account balances and payment statuses directly in Business Central, and send outgoing payments to the bank without exporting and uploading files.

Incoming transactions and automatic accounting. Transactions are fetched from the connected bank accounts, either on demand or by a scheduled job, and appear as bank transactions with their full detail lines, including remittance information, creditor and debtor names and account numbers, currencies and instructed amounts. A matching engine then tries to account for each detail line automatically: incoming payments are matched against open customer invoices and credit memos using structured references and free-text remittance information; outgoing payments are matched back to the vendor, customer or employee ledger entry they were sent from; and transfers between your own bank accounts are recognised and paired up. Anything the engine cannot resolve is flagged with a message so you can handle it manually. You can also define bookkeeping rules that assign an account, posting groups and dimensions to recurring transactions based on a search text, an amount range and the day of the month.

Where a transaction needs manual work — for example, one payment covering several invoices — the transaction journal lets you split the detail line across several lines with their own accounts, applications, VAT posting groups and dimensions, with the original amount shown so you can see what still needs to be allocated. Transactions are released and then posted to the general ledger, settling the customer, vendor, employee, G/L and bank account entries, handling bank charges and payment tolerance against the accounts you configure in Finance Manager Setup, and closing the corresponding bank account ledger entry.

Outgoing payments. You can generate payment suggestions for vendors, customers and employees over a date range, choosing whether to include credit memos, invoices, payment discounts and employee debt, and whether to override due dates with a single payment date. Suggestions become bank transfers with lines per document, which you send to the bank, sign through a signing basket, and then track as the bank reports back — received, pending, accepted, settled, rejected or cancelled — with a background job updating the statuses and a dedicated page listing the transfers waiting to be signed. Rejected transfers can be marked as handled once dealt with. For Swedish customers, payment suggestions can be sent to the Inyett Detect payment control service before being released, and the warnings it returns are shown per line.

Balances, reconciliation and overview. Bank account balances are fetched from the bank and shown next to the Business Central balance, with the difference highlighted and drillable. A bank account reconciliation report compares the bank balance, the bank account ledger and the corresponding G/L account for a period. A Finance Manager role centre and activity cues give an overview of suggested, to-approve, in-process, recently completed and rejected transfers, and of bank transactions that still need handling or posting.

Payment practices. Entries can be excluded from payment practices reporting, with the exclusion flowing from the purchase document through the journal to the posted ledger entry.

The app ships with Danish, Finnish, Norwegian and Swedish translations in addition to English.