New Feature: Blocked Business Partners will not be predicted
Adjustments to the Bank Transactions Module
New Feature: Loading Spinner in the Search Field
New Feature: "Goods/Services" as a Booking Text Option
Improvement: Larger Field for IBAN
New Feature: Transport of XML E-Invoices to Accounting Systems
Improvements to the DATEV Interfaces: “Buchungsdatenservice” and “Rechnungsdatenservice”
Improvement: Optimization of the DATEV Batch Format for Data Transfer
Note: Release Pause over the Holidays
Blocked business partners are excluded from predictions by Finmatics models, ensuring more precise and tailored processing.
How does blocking business partners work?
API Integration Only: Blocking information is transmitted directly from the accounting system (ERP) to Finmatics.
Automatic Synchronization: The ERP system determines which business partners should be marked as blocked.
Currently available interfaces:
Microsoft Business Central (NAVAX interface)
REST API (for customers connected via this interface)
Not available for:
BMD
RZL
DATEV
Other accounting systems
Advantages:
Avoid unwanted business partners in predictions.
Improve data quality and achieve more accurate processing.
Direct control via your existing ERP system.
👉Here you can find more information about the REST API: First Steps with REST API
Export Enhancements:
The client number is now added at the beginning of the file name during export. This facilitates the search and assignment of export files to the corresponding clients when importing into the accounting system. The file names now follow this format:
[ClientNumber]_Finmatics_bank_transaction_[Date]_[Time].
There was previously a restriction that bank accounts had to be unique per client. Customer feedback has shown that this was too restrictive and presented a limitation in certain use cases. This restriction has now been removed.
👉In this article you can read more about how Finmatics processes bank transactions.
To enhance user experience in the Finmatics web app, we have introduced a loading spinner in the search field.
What does the loading spinner do?
When searching for clients, users, or documents, complex queries may occasionally take a few seconds to load results.
The new loading spinner clearly indicates that your search is being processed, keeping you informed about the status of your request.
Advantages:
Improved transparency during searches.
Clear visual feedback on the loading process.
Optimized user experience for extensive search queries.
In this screenshot you can see the loading spinner:
The "Goods/Services" booking text option has been optimized to automatically detect and standardize the business transaction (e.g., goods or services) using an advanced language model.
What’s new?
Previously, both the raw output and the standardized version were displayed.
Based on customer feedback, only the standardized "Goods/Services" booking texts will now be output.
Why this change?
Avoid configuration errors.
Ensure more uniform and clearer booking texts.
With this adjustment, we ensure that your booking texts are always precise and error-free.
Based on customer feedback, we have adjusted the IBAN field in the Finmatics web app.
What has changed?
The IBAN field has been enlarged to ensure that the IBAN is always fully visible and easy to read.
Why this change?
Customers noted that the previous field was too small, making it difficult to view the full IBAN.
This adjustment improves clarity and simplifies working with IBAN data.
Our interfaces have been enhanced to enable the transport of XML E-invoices to supported accounting systems. This feature ensures the seamless transfer and integration of your invoice data.
How does it work?
No API Support for XML Data?
If the target accounting system does not support a direct API interface for XML data:
The original invoice (XML) is embedded in a PDF file.
The PDF contains the invoice visualized by Finmatics.
The original XML is also embedded within the PDF.
Transfer to Accounting System:
Via the interfaces, the PDF with the embedded original XML is transferred to the accounting system.
Supported Systems:
DATEV
BMD
RZL
Microsoft Business Central (Navax interface)
Notes:
For customers already using API interfaces, this feature must be activated by your account manager.
Contact us to activate the feature or for questions about integration at support@finmatics.com.
With this enhancement, we ensure that your XML E-invoices can be efficiently and seamlessly integrated into your accounting systems!
Additional Information:
The original XML can also be retrieved via API interface.
If the feature is not available in your settings, please contact support@finmatics.com.
We have optimized the integration with DATEV services, particularly with regard to year-end processes, to facilitate the work at the year-end transition between Finmatics and DATEV.
Key Improvements:
Master Data Export for Both Fiscal Years:
At the year-end transition, master data is now automatically exported to both fiscal years.
This feature applies exclusively to the “Buchungsdatenservice”
Short Fiscal Year:
The short fiscal year can now be reconfigured.
For activation and configuration, please contact support@finmatics.com.
For customers using the DATEV batch format to manually transfer data from Finmatics to accounting systems such as Agenda, Addison, or Simba, the download function has been improved.
What has been optimized?
New Naming Conventions for Downloaded Files:
Files are now consistently and clearly named as follows:
Client number – Date – Time
Advantages:
Improved clarity.
Easier assignment and faster processing of files in target systems.
This change makes the manual data transfer more efficient and user-friendly.
The next release will take place on January 10, 2025.
Please note that no releases will be conducted during the holidays.
We wish you happy holidays and a great start to the new year! 🎉