#38 - October 2026
Receivables
Bulk transfer to Debt Collection from any journal entry index
What changed:
New bulk action "Transfer to Debt Collection" in the batch dropdown of the journal entry index (including all filtered/worklist views) and the customer's journal entry tab
A selection across many customers is handled in one go: a confirmation dialog shows the number of entries, the number of customers and totals per currency, then the handover runs in the background with a progress bar
A summary per customer at the end lists the entries that were transferred and the ones that failed, with the reason
Why it matters:
Until now, the manual handover only worked inside a single customer. AR teams that work from filtered lists can now escalate a whole batch of overdue items without opening every customer.
Journal entry text in clarification exports
What changed:
The clarification export layout has a new optional column "Journal Entry text" (DE: "Beleg Text"), placed next to the other journal entry columns
It works in CSV, XLSX and scheduled clarification exports that use the layout
The cell stays empty for clarifications without a journal entry, for example deduction-based ones
Pending reasons and free text answers in the clarification export
What changed:
The clarification export layout has three new columns: Latest reason, Latest additional reasons, Latest free text answer. They show the reply the clarification list displays, even when it is not yet accepted.
All reason columns at a glance:
Latest reason / additional reasons / free text answer: the reply currently in play in this round (pending, accepted, rejected or expired)
Current reason / additional reasons / free text answer: the reply accepted in this round
Last Accepted Reason: the last accepted reply across all rounds, also from before a restart
Refreshed top header bar
What changed:
Cleaner header: a smaller logo without the dark block, a labelled "Menu" button that opens on hover and works with the keyboard (arrow keys to move, Escape to close), and better contrast for the faint grey and blue text.
The bottom of the menu now shows the company name and company ID for every user. Click the ID to copy it. Users with several companies also see their company ID next to their profile picture on screens 1200px and wider. The feature group > page breadcrumb is gone because the subnav bar already shows it.
Shortcut hints show ⌘ on Mac and Ctrl on Windows. ⌘E (menu) and ⌘B (search) no longer trigger the browser's own shortcuts. Profile menu > Knowledge Base now opens docs.bilendo.de in German or English.
Why it matters:
The header is easier to read and quicker to use, and the company ID is always one click away when support or an integration asks for it.
Login authentication for inbound mail servers
What changed:
The authentication dropdown for inbound (IMAP) mail servers now offers "Login" next to "Plain". Login signs in with the IMAP
LOGINcommand using username and password.If the mail server has disabled login (
LOGINDISABLED), the connection test fails with a message naming the server and the rejected method.Changing the authentication method on an active server deactivates it. The customer has to activate it again, which runs the connection test with the new method. Existing servers stay on Plain and keep working.
Why it matters:
Customers running their own mail infrastructure couldn't connect reply tracking if their server doesn't support Plain, and Microsoft OAuth was the only alternative. Now they can connect with plain username and password.
Drill-down from Aging Report amounts to the journal entries
What changed:
The summary amounts in the Aging Report are now clickable: Due Receivables / Open (due), Open (not due), Total / Total Receivables and Total Credit / Unapplied Credit. This works in the header block and in every table row, including expanded nested rows.
A click opens the journal entries list (or, in a customer's Analytics tab, that customer's journal entries tab). It is pre-filtered to open receivables or open credits and keeps the report's item, custom field filters and currency, so the list total matches the clicked amount. Balance stays unlinked because it nets receivables against credits.
Why it matters:
Users no longer rebuild the report's filters by hand in the document overview to find out what makes up a figure. This matters most for credits, where it was previously impossible to see which documents make up the amount.
New PDF preview: works in every browser, with download and print
What changed:
PDF previews in Bilendo now use our own viewer instead of the browser’s built-in one. They load the same way in every browser, including Safari, where previews used to hang on the loading spinner.
The preview toolbar has page navigation with a page counter, zoom in and out, fit width, fit page, and now Download and Print. Download saves the file under its original name.
Previews open at page width, so documents are readable without zooming in. The quick file preview and the fullscreen clarification attachment preview still show the whole page.
Why it matters:
Reminders, letters, invoices and attachments can be checked, saved and printed straight from Bilendo, in any browser and without opening the file elsewhere first.
Dunning Block Reasons
What changed:
Every manual dunning stop on a customer or journal entry now carries a dunning block reason, picked from a per-System catalog (also when setting it on several journal entries from the customer page, on clarification close, in workflow side effects and for promises to pay; optional expiration date).
Dunning block reasons from the ERP (SAP field MANSP) are imported for customers and journal entries, shown read-only and expire when a later import no longer delivers them.
The reason shows up in the dunning stop history, as a column and filter in the customer and journal entry lists, and in the export with its description plus one field for the manual and one for the external ERP code, so reasons set in Bilendo can go back to the ERP.
Why it matters:
AR teams see at a glance why an account or item is blocked instead of looking it up in the ERP, and blocks decided in Bilendo carry a code the ERP understands. Every block is attributable in the history, which makes audits and handovers easy.
Dunning block reason preselected when closing a clarification
What changed:
When an account has exactly one selectable manual dunning block reason (in accounts without their own reasons, "Manual Dunning Block"), it is now preselected when a clarification is closed with a dunning stop ("Add a manual dunning stop until restart date" in the close dialog). The clerk can close without touching the dropdown, and the dunning stop is saved with that reason and shown in the dunning stop history.
The same preselection now applies in the batch "Add manual Dunning Stop" modal and in the dunning stop modal of a journal entry. Promise to pay already worked this way and now shares the same logic.
Accounts with several reasons see no preselection and pick a reason as before. In the journal entry modal there is also no preselection while another removable dunning stop is active on that entry, so no manual stop is added that the user did not ask for.
Why it matters:
Since dunning block reasons were introduced, closing a clarification with a dunning stop took an extra click, even where the dropdown offered only one option. That click is gone for these accounts, and the workflow is as fast as before.
Business unit in the clarification sales unit dropdown
What changed:
When a clarification is reassigned (edit dialog for area, business unit and sales unit), each sales unit in the dropdown now shows its area and business unit as grey subtext next to the name, in the form Area ➝ Business unit.
A sales unit without a business unit shows only its area. Search still matches the sales unit name.
Only this dropdown changes. All other places that list sales units keep showing just the area.
Why it matters:
The dropdown is already filtered to one area, so before every entry showed the same area name and sales units looked alike. Clerks who belong to several sales units can now pick the right one without guessing.
Filter clarifications by reason
What changed:
The clarification list has a new Reason filter (multi-select). It offers the company's required reasons plus "Other reason" (an accepted reply without a reason).
It combines with the other filters of the list. Drill-downs from the Clarification Reason reports now open the list with the Reason filter and that reason preselected, instead of an invisible filter.
Reasons that replies already use are no longer lost when someone deletes them: they are archived, stay selectable in the Reason filter with an "Archived" badge, and are hidden from the other reason lists.
Why it matters:
Clerks no longer scan long worklists by hand. They can jump straight to, for example, all clarifications answered with "continue dunning run" and accept or close them in one go.
Difference reason in the clarification
What changed:
The clarification now shows the difference reason (code and description, e.g. ST - tax) of the linked journal entry, in the expanded journal entry details (label "Differenzgrund" / "Difference Reason").
The same value appears in the journal entry hovercard.
If the journal entry has no difference reason, or the clarification has no linked journal entry, nothing is shown (no empty label).
Why it matters:
The difference reason is the ERP's own answer to why an item is disputed or short paid. Clerks no longer have to open the receipt to understand why a clarification exists.
Dunning Stop filter in the Aging Report
What changed:
The Aging Report has two new filters: "Dunning Stop" and "Dunning block reason", with the same options as in the open items list. The block reason filter only appears where the open items list shows it (dunning block reasons enabled).
Totals, aging buckets and credits count only the matching items, i.e. the same items the open items list shows with that filter. The filters carry through to the customers page, nested items and the drill-down to the journal entry list.
Both filters can be combined with each other and with existing filters (e.g. company code) and saved in a preconfigured Aging Report on a dashboard. Without a selection, the report behaves as before.
Why it matters:
Items with a dunning stop are on hold on purpose, but they inflate the Aging Report totals and hide what the team can actually work on. Now a saved report per company code can show only collectable receivables, or only those on hold.
Links in comments: autolink and new tab
What changed:
• A URL typed or pasted into a comment turns into a clickable link on its own once a space or Enter follows it. No more selecting the text and using the link toolbar button.
• Links in comments open in a new browser tab, so users stay on the Bilendo page. This also applies to comments that already exist, because the new tab is set when the comment is displayed.
• Works in the comment form and in the comment fields of the clarification flows (accept, reject, resolve conflicts, item-by-item group comment, clarification message).
Why it matters:
People who document external sources in comments, for example credit agency files, save several clicks per link. They also no longer lose their place in Bilendo when they open one.
Aging Report as of a key date
What changed:
The Aging Report filter bar now has a "Key Date (Current if empty)" filter, the existing "Open at" filter, capped at today. Left empty, the report behaves exactly as before and uses open amounts.
With a key date, only journal entries that were open on that date are included. Buckets age relative to the key date, not today. The "Oldest receivable" age on the customers page also counts from the key date.
With a key date, all amounts and totals are journal entry amounts instead of open amounts. A warning hint above the report and the customers page explains why. Drill-down links carry the key date, so the journal entry lists match the report.
A key date that cannot be parsed or lies in the future falls back to the current report.
The journal entry lists (filter bar, saved filters, exports) also change: combined with "Open at", the due status and time bucket filters now age against that date instead of today. "Open at" itself is unchanged.
Why it matters:
Customers can reconstruct the aging structure for a past reporting date (month end, quarter end, audit request) instead of seeing only today's live status. The hint makes clear that the numbers have a different basis than the live report.
Customer balance in the journal entry export
What changed:
The journal entry export layout has a new field "Customer balance" (DE: "Kunden-Saldo"). It is formatted like the other amount fields in CSV and XLSX.
The webhook journal entry export has a new customer_balance column, appended at the end so the existing column order stays the same (in XML: a <customer_balance> element).
Each row shows the balance of the entry's customer, the same value as the "Customer balance" column in the journal entry index. A customer without a stored balance shows 0.
Side effect to know about: JSON webhooks and the API v2 journal entry responses now also contain customer_balance.
Why it matters:
Clerks who process the open item list outside Bilendo no longer have to look up each customer's balance and add it by hand.
Global search results open in a new tab
What changed:
• Customer hits in the global search are now real links across the whole row, so right-click "Open in new tab", middle-click and Cmd/Ctrl+click work.
• The same applies to journal entry hits in the global search.
• Arrow-key navigation and Enter keep working as before.
Why it matters:
Users can open several customer records side by side without losing their search results or their place in the list. That saves repeated searching when comparing or working through multiple customers.
Calmer sidebar, scalable saved views and a quieter list footer
What changed:
• Sidebar: spacing instead of dividers, lighter section titles, one highlighted row at a time (light-blue pill), counts as badges on the right edge, zero counts hidden.
• Saved views: the section is collapsible and shows folders plus the first 5 views and the open one. "Show all N" opens the "All saved views" pop-up with search and an edit mode (reorder, rename, delete, add folders). A bin on hover deletes a view or folder after confirmation. The Save/Edit view modal can create a folder inline, offers "No folder" and explains "Default view". Drag and drop, the default-view trophy and the homepage pin still work, and removing the open view from its filter-bar chip now asks for confirmation.
• List footer (all list pages, plus Export in Settings → Users and Security events): the result count is plain text instead of a red badge ("9,999+" stays clickable to load the full count). Export and Table design are grey text buttons without icons, with a divider between them.
• Settings: the sidebar search stays on top while scrolling, and the Clarifications Settings section is collapsed by default.
Why it matters:
List pages are less noisy, and users with many saved views and folders find, sort and clean them up without scrolling through a long sidebar.
Own access right for custom fields
What changed:
• User roles have a new "Custom Fields" right nested under Customers, Journal Entries and Orders, with the usual levels: Read and Write, Read, No Access.
• A role can now edit a customer's custom fields without being allowed to edit the customer details. Only fields set up as user updatable can be edited at all; imported or API filled fields stay read only.
• "No Access" hides custom field values everywhere for that object: detail view, lists, filters, exports, reports and key stats tiles. Existing roles were migrated to the level of their parent right, so nobody gained or lost access on release.
Why it matters:
Teams that have colleagues maintaining custom fields (classifications, internal flags, data quality) no longer have to hand them write access to master data as well.
How to change:
• Settings > User Administration > User Roles: the new "Custom Fields" row sits directly below Customers, Journal Entries and Orders.
• The sub right can never exceed its object right: "Customers: No Access" also hides customer custom fields.
• Nothing changes until an admin adjusts a role, because every role kept its current access on release.
Manager on user as escalation target for clarifications
What changed:
Every user can now have one optional manager (an active user of the same company). It is set in the user's Responsibilities & Access tab (formerly Access rights), shown on the user page and in the user list, and can be imported through an optional "Manager E-Mail" column. A user cannot be their own manager, and reporting lines cannot form a cycle.
Clarification workflows offer the manager of the assignee in three places: as escalation level ("to Manager of Assignee"), as restart setting ("Include Manager (Assignee)") and as assignee source. It can be combined with team or BU manager on other levels of the same workflow.
When the level fires, the request goes to the manager of the current assignee, and the event log names that manager. If there is no assignee or no manager, nobody is newly assigned and the log records that no recipient existed (same as a BU manager escalation without a manager).
Why it matters:
Users in several teams no longer pull a whole crowd into every escalation, and matrix or shared-service setups reach the person who is actually responsible. The reporting line is maintained once in user management and every workflow can follow it.
Area manager as escalation target for clarifications
What changed:
Areas now have an optional manager, set on the area form in the settings like the manager of a business unit, and shown in the area list.
Clarification workflows offer the area manager as an escalation level ("to Manager of [Area]"), in the restart setting ("Include Manager ([Area])") and as assignee source. It can be combined with the business unit manager on another level, e.g. BU manager first, area manager second.
Area managers see the clarifications escalated to them under "Escalated to me". If an area has no manager, the level behaves like a BU manager level without a manager: no recipient, and the timeline says so.
Why it matters:
Customers organized by region or country get a real second escalation step above the BU manager. No more one workflow per area or teams that only exist to carry a manager.
Translation of custom fields
What changed:
• New settings area "Custom Field Translations" under Company Structure
• Title and description of each custom field can be translated into bg, cs, de, en, es, fr, hu, it, pl, ro (Bilendo supported languages)
• Users see custom field labels in their own language everywhere: detail views, edit dialogs, table headers, filters, key figures, table design
Why it matters:
Users in other countries no longer see labels they don't understand. This makes custom fields usable for international teams.
Comment notifications in interface templates
What changed:
• The Notifications tab of an interface template now has a Comments section. Admins can set email on/off and the cadence per role, and push or lock it via the template like the other notification areas.
Why it matters:
Admins can now set sensible comment notification defaults for whole roles instead of relying on every user to configure them. Users who chose a daily or weekly digest for comments now actually get their emails.
Risk
Risk Summary | Complete redesign of the Risk Management tab header
Before → After
Before: credit limit, risk class and score lived in separate blocks. The risk class reused the small label from the index page.
Before: you couldn't tell very well whether a risk class followed the score or was set manually, or where the score sat inside its class band.
Before: there were no trends anywhere on the page. To see if payment behavior was getting better or worse, you had to dig through reports.
After: one card, full width, that answers "How risky is this account right now, and which way is it moving?" without leaving the page.
What's new, area by area
Credit Limit
Amount, expiration date and a new utilization bar (used / free in € and %)
Conditions badge with a count. Clicking it shows the full text in a popover (no more "Show more")
Unsecured Limit with a covered-amount chip; Uninsured Exposure is shown when a cover has a deductible
Risk Class + Score
Risk class tile in the class color, with a change indicator (e.g. B → C) when the class moved at the last scoring run
Score tile next to it with a direct link to the Calculation Log
New risk class scale with all classes, band boundaries, and a score marker, so you see where the score sits inside its class
Manual classes are clearly marked: gray bar, class in the center, no score marker. A comment icon opens the full history
Bilendo Risk Assessment (new)
A short generated summary of payment behavior (ADP/DBT), score development, and limit utilization over the last 12 months
Fixed sentence structure, so customers can be compared. It classifies, it doesn't recommend
When is it shown? Only when there is enough data for a fair statement:
the customer has an active credit limit (not shown for suggestion-only customers)
score history reaches back 12 months
ADP and DBT can be calculated from paid items in the policy currency over the last 12 months
Extra clauses appear only when relevant: the uninsured amount (with credit insurance only) and the expiry warning (limit expires in ≤ 60 days)
"Noticeable" change = ±3 score points or ±2 days ADP/DBT. Below that, the text says the value barely moved / is steady
Trends — 12 months (new)
Score, ADP and DBT with sparklines and the 12-month change (red = material, amber = moderate)
Each metric is shown as soon as it is available, so a customer can have trends but no assessment
"Details" opens a combined modal with the Risk Class & Score chart and Payment Behaviour
Consistent everywhere
The new scale is also used in the risk class modal, the Score tab header and the credit limit suggestion overview
Customers with only a suggestion (no limit yet) get the same card instead of the old "pending" block
The conditions design is aligned across the card, sidebar and history
Why it matters
Credit managers see the full risk picture of a customer in seconds: current exposure, how the risk class came about, and whether things are getting better or worse. All without switching tabs or opening reports.
Currency conversion for 166 currencies in Credit Management
What changed:
Exchange rates now come from ExchangeRate-API (166 currencies) instead of the ECB reference feed (about 29 currencies).
Credit policies, credit limit suggestions and the FCS score can now convert currencies the ECB never covered, for example AED, SAR, MAD, EGP and NGN.
Rates sync daily at 06:00 UTC, weekends included (previously weekdays at 17:00 UTC). The tooltip on converted amounts now reads "Exchange rate of <date>" instead of "ECB rate of <date>".
Configurable Credit Limit Decision PDF
What changed:
Admins can configure the Credit Limit Decision PDF under Settings › Risk › Credit Limit Decision PDF: include/exclude sections, reorder them by drag & drop, set "Start on a new page" and "Hide section if there is no data" per section.
Three new sections: Key Stats (KPI tiles: Balance, Turnover YTD, Turnover Prev. FY, Open Items, ADP, DBT, selectable), Balance Sheet Analysis and Additional Information (filled-in additional information fields).
Live preview with page count, either as a structure preview. Read-only: no decision, no stored document, no notification.
Why it matters:
Customers have different approval processes and data sources. Until now, every change to the PDF meant a code change on our side. Admins can now adapt the document to their own process themselves.
Balance sheet analysis: yearly, quarterly and monthly views
What changed:
Balance sheet data is now split into three sections: Yearly, Quarterly and Monthly. Each shows its own data and KPIs.
After creating a balance sheet analysis from the customer page, users land directly in the new analysis.
Fixed a bug that prevented comments on balance sheet analyses from being saved.
Why it matters:
Customers can analyze trends per reporting period without mixing data, for example a 2026 annual balance sheet next to a Q1 balance sheet. Fewer clicks after creation, and notes are no longer lost.
Reuse one URL for multiple webhooks
What changed:
A URL could previously be used for only one webhook
The same URL can now be reused across multiple webhooks
Existing webhooks are not affected
Why it matters:
Customers are no longer limited to one URL per Webhook.
Credit limit suggestion comments no longer require a category
What changed:
Comments on credit limit suggestions can be saved again without selecting a category
The mandatory-category check is now disabled specifically for credit limit suggestion comments
Category requirements stay unchanged for all other comment types
Why it matters:
The credit limit suggestion comment form has no category selector. Customers with mandatory comment categories were therefore blocked from commenting on suggestions. This now works without a workaround.
Manual overwrite of deductible on credit covers
What changed:
The deductible of an individual cover can now be overwritten manually. Before, it always followed the policy default.
A new edit icon next to the cover's deductible field lets users enter a custom percentage (e.g. 20% instead of 10%).
Why it matters:
Credit insurers sometimes set non-standard deductibles for specific covers. Customers can now reflect these terms accurately in Bilendo instead of being stuck with the policy default.
Filter risk classes by origin (manual vs. automatic)
What changed:
The risk class filter now has a "Risk class origin" option: Automatic or Manual
Automatic = current risk class was calculated by the system
Manual = current risk class was set or overridden by a user (an overridden automatic class shows up under Manual)
Why it matters:
Customers can set automatic classes manually too. Until now the only way to tell the difference was the indication via the manual design. Now they can audit manual overrides in a single filtered view.
More Creditsafe Risk Alerts
What changed:
Bilendo now ingests an additional selection of country-specific Creditsafe alerts (~50 insolvency codes across 15 countries), not just global alerts and some French ones
New pre-insolvency (early-warning) indicators in the selection: payment behavior, debt enforcement/collection, court judgments, tax and social security debts
This first release covers the alert codes selected by Klüber Lubrication. Further Creditsafe alert codes will follow in a later release
Why it matters:
Customers with international debtors get earlier and more complete risk signals, so they can act before an insolvency hits.
BoniCheck Policy ID now shown on unnamed covers
What changed:
The Policy ID used in a BoniCheck request is now displayed on the resulting unnamed cover (Credit Covers widget).
Example: "Allianz Boni Check, Policy #WP21200004", next to the granted amount and status.
Why it matters:
Credit managers can trace an unnamed cover back to the BoniCheck request that created it, without searching through requests manually.
Secured amount now converted to the credit limit currency
What changed:
The secured amount (sum of all credit insurances) is now shown in the currency of the credit limit, with the original amount underneath (e.g. 2,532,911.60 zł / 578,000.00 €).
An info tooltip breaks the secured amount down per insurer (e.g. Atradius, Orvia), also converted. Converted values are marked with "≈" as approximations.
Available in the credit limit sidebar, the Risk Management tab and the credit limit suggestion detail view.
Why it matters:
Customers with limits in a different currency than their insurance cover can now compare limit and cover directly, without converting manually. This makes it immediately visible whether a limit is fully covered.
New custom field type: "Calculated"
What changed:
There is a new custom field type called "Calculated".
It is filled automatically with the values computed in the scorecard.
These values can now be mapped in the export layout and exported to ERP or other external systems.
Why it matters:
Until now, parameters calculated in Bilendo's scorecard could not be mapped to a dedicated custom field for data exports. Customers can now pass scorecard results straight into their ERP or external systems without a workaround.
Additional Information card: backend link removed from empty state
What changed:
If a company has no string custom fields, the "Additional Information" card no longer shows the "Configure custom fields" link to the backend (previously visible to Bilendo admin users only).
All users now see the same message: "Contact customer success to set up custom fields."
Why it matters:
The empty state is now consistent for everyone and no longer points to a backend that customers cannot access.
Create customers directly in Bilendo, incl. virtual customers
What changed:
The customer overview now has a "Create" button to add a customer manually. It works without an external connection (ERP/accounting integration). It's shown to companies with Scoring & Risk and to users with write access to customers.
In the "New customer" dialog and in the "Convert to customer" dialog (Scoring & Risk > New customers) you can now choose a Customer Type:
Customer: with customer number, company code and credit control area (default, flow unchanged)
Virtual Customer: for consolidation only, no business relationship. Only the name is required.
Switching the type keeps what you already entered. The "Create virtual customer" menu entry now opens the same dialog with "Virtual Customer" preselected.
Why it matters:
Customers can now build up their customer base manually, without an integration. They can also create virtual customers for consolidation right where they create or convert customers, without a separate dialog.
Good to know:
Virtual customers still need no customer number, company code or credit control area.
If a user doesn't see the "Create" button, check Scoring & Risk and their write access to customers.
Manual cover with an amount of 0
What changed:
Manual credit covers can now be created with an amount of 0 (the minimum was 1 before).
Credit Covers reports show "Granted: 0" for it.
Why it matters:
When a credit insurer declines a cover request, customers can now record this as a cover of 0. Their cover history and the insurance pool then show the real situation instead of the old cover.
Parent ID is now editable on the customer#show
What changed:
With the relationship structure enabled, the Parent ID can be edited via the sidebar on the customer page ("Edit").
The sidebar shows the Parent ID (editable) and the configured matching attribute (read-only).
The edit dialog warns that changes may be overwritten by the next ERP import.
Why it matters:
Parent-child assignments can be corrected in Bilendo right away, without waiting for an ERP fix and the next import.
Expired manual covers now visible in the Credit Covers report
What changed:
Manual covers that have expired are now shown in the Credit Covers report with an "Expired" badge
Shown only if there is no active cover on the same connection (the most recently expired one is displayed)
Expired covers are not counted in the total amount or cover count
Historic (point-in-time) reports show the covers that were active at that time, without the "Expired" badge
Why it matters:
Customers and credit managers no longer see an "empty" cover section once a manual cover has run out. They can see that a cover existed and when it ended, which makes renewal conversations easier.
Change log for Additional Information
What changed:
Each Additional Information field on a customer's Risk Management tab now shows who last changed it and when.
A clock icon opens the field's history: previous values, author, source and the date each value was replaced.
Removed values appear as "Removed" in the history.
Why it matters:
Teams can trace who edited risk-relevant notes, for example before a credit decision or in an audit conversation.
Important:
Every change to an Additional Information field is now traceable to a person and a point in time.
The full history per field is one click away, including removals.
Values saved before this release have no author or date. Tracking starts with the first change after release.
Internal comments on securities
What changed:
Securities now have a "Comments" tab in the security window, with a comment count.
A new "Comments" column shows the count in the securities overview and in the securities card on the customer's Risk Management tab.
Archived securities now also appear on the Risk Management tab (same logic as expired ones). The link to the security type settings was removed there.
Why it matters:
Teams can record internal context on a security (for example why it was archived or what the insurer said) right where they work, instead of in side channels.
Provider name in the tooltip of manual credit covers
What changed:
Hovering over the shield icon of a manual credit cover now shows the name of the linked provider (the one set up in Settings) instead of the generic "Custom" (DE: "Benutzerdefiniert").
This applies to the card view, the comparison mode and the legacy table/PDF.
If no provider is linked to the cover, the tooltip still shows "Custom".
Why it matters:
Users reviewing credit covers see at a glance who provides a manual cover, without opening it or looking it up elsewhere.
Custom sorting for securities and comment categories
What changed:
Securities and comment categories can now be reordered via drag and drop.
The saved order is reflected in the relevant securities and comment category dropdowns.
The reordering works the same way as for risk integrations.
Why it matters:
Users who work with securities and comment categories every day can put the items they use most where they want them, instead of living with a fixed order in the dropdowns.
Graph in the credit information history
What changed:
The Credit Information History modal now has a List and a Graph tab. The graph shows score and recommended limit over time, with a 1/2/3-year filter (default: 1 year).
A key-figure footer shows score, change since previous report, recommended limit and reports in period. Clicking a data point opens that report.
The existing score chart now uses the report date for its period, shows the Bürgel credit index for dd_monitor and leaves a gap for manual "-" entries instead of 0.
Why it matters:
Customers can spot score developments at a glance instead of comparing rows in a list. It works like the credit limit history they already know.
Open the history of a credit information and switch to the "Graph" tab to see the trend.
A graph needs at least two scored reports in the chosen period, otherwise it shows "not enough history yet".
Correct column label in the Uninsured Exposure hovercard
What changed:
The amount column in the Uninsured Exposure hovercard was labeled "Deduction". It is now "Deductible".
In German it now reads "Selbstbehalt" instead of "Belastungsanzeige". "Belastungsanzeige" is the term for the Deductions module, so it was confusing.
The figures are unchanged. Only the header text changed, and it now matches the credit security and credit cover screens.
Why it matters:
The column shows each security's deductible share, and the old label suggested something else. Customers now see the same term here as everywhere else in Credit Covers.
Reason shown for blocked unnamed covers
What changed:
The warning on the customer details ("This customer is blocked from receiving unnamed covers until ...") now has a line "Reason: ..." with either "Overdue open receivables" or "Receivables paid late".
Below the reason, the journal entries that caused the block are listed as links (if the user may access journal entries). Up to 10 are shown inline, and "and X more" opens a modal with all of them.
Customers blocked before this release have no recorded reason yet. A one-off backfill fills it in for them. Customers whose debt has since cleared keep no reason, so the warning looks as before for them.
Why it matters:
Users no longer have to dig through receivables to find out why a customer cannot get an unnamed cover. They see the cause and the invoices behind it right in the warning and can decide what to do.
Important:
• The block warning in the customer details now says why the customer is blocked: overdue open receivables or receivables paid late.
• The related journal entries are linked right below the reason, so the invoices behind the block are one click away.
• For older blocks the reason can be empty if it could not be reconstructed. The warning with the date still appears as before.
Requested amount in credit limit history and decision PDF
What changed:
The Approval Details section of the credit limit history detail and of the decision PDF now has a "Requested Amount" row (German: "Angefragter Betrag").
The requested amount is the amount in place before the first user edit. A system recalculation before any user edit counts as the request. Decisions made before this change show it too.
Amount changes now show who made them (avatar, name | Amount changed, with From/To). Every change is listed, not just the last one. Each change sits under the approval step that was still open when it was made. A change made after validation appears directly under the approval steps.
Why it matters:
When validators or approvers adjust an amount (for example 5,000 → 4,000 → 3,000), the history used to show only the final figure. Now the original ask and the final decision can be compared at a glance, in the app and in the PDF.
Credit scores as risk-colored badges
What changed:
External credit scores in the credit information sidebar card and in the Risk Management rows are now tinted badges instead of plain bold text.
Creditsafe, Creditreform, Atradius, D&B and Coface show green, orange or red where the provider's own scale supports it. Allianz keeps its grade colors.
DD-Monitor, Coface Icon, Skyminder and manual scores stay gray.
Why it matters:
Customers see the risk level of a debtor at a glance, without having to know each provider's scale. The history modal and the credit information list keep their current score style.
Manual covers now behave like insurer covers
What changed:
Manual covers in the credit covers report no longer show "—" in most cells. The column view shows a Manual badge, Granted Amount #2 / Expiry Date #2 and the policy terms. The card view shows the condition in the same warning strip as Atradius.
When creating a manual cover, you can now pick a policy (or "No policy") and add a condition ("Conditional Amount") with its own amount and expiry date. A single policy is preselected, and its deductible is shown as the default.
The deductible works like for Allianz and Atradius: it falls back to the policy of the manual connection and can be overwritten inline. Policies of a manual connection take a free-text policy ID.
Why it matters:
Internally agreed or negotiated covers can be maintained in the same place and format as insurer covers, so the total coverage per customer is easier to trust.
Manual covers use the same layout as connected covers and are marked with a Manual badge instead of an insurer logo.
A condition (amount plus validity date) on a manual cover feeds Granted Amount #2 / Expiry Date #2, as on Atradius covers.
Good to know: a manual cover links to its policy by policy ID only. If a policy is renamed or deleted in the settings, the cover keeps the old ID and loses the deductible fallback and policy terms. Conditions are not shown in the PDF export.
Trend color per balance sheet parameter and KPI
What changed:
Every balance sheet parameter and KPI in a balance sheet analysis template now has a "Higher is better" switch.
When it is off, a rising value in the Trend column shows red and a falling one green; the arrow still follows the value.
Applies to the balance sheet analysis on the customer page and to the credit limit decision PDF. The switch is on by default, so existing templates look exactly as before.
Why it matters:
Until now a rising value was always green. For figures like liabilities or debt that is the wrong signal, so the analysis could make a worsening customer look healthier at a glance.
Balance sheet analysis in the input currency
What changed:
When a customer's balance sheet analysis was entered in a currency other than its template's, the page header shows a Template currency / Input currency switch. Template currency stays the default.
In Input currency, parameters and KPIs show the values as they were entered; the tooltip shows the template amount and the exchange rate. If periods were entered in different currencies, each period column carries a currency badge, and trends between them are still compared in the template currency.
KPI colors are always based on the template currency, and the PDF keeps showing the template currency.
Why it matters:
Credit teams and regional colleagues can discuss and check balance sheet figures in the currency the company actually reports in, without losing the comparable converted view.
Important:
Nothing changes by default: the analysis opens in the template currency, so ratings and comparisons stay as before.
One click shows the figures as entered, handy when reviewing a foreign subsidiary's statements with regional colleagues.
The PDF export always uses the template currency, so shared reports stay consistent.
Manual credit covers with a past expiry date
What changed:
The expiry date field on the manual credit cover form ("New Credit Cover") now accepts dates in the past, so historical covers can be recorded.
A manual cover created with a past expiry date is stored as expired. It no longer expires the customer's current active manual cover of the same product type.
New manual covers and securities are rejected when the expiry date is before the start date. Insurer covers are not checked this way.
Why it matters:
Customers can now keep a complete cover history in Bilendo without disturbing the cover that is active today. Impossible date combinations no longer get saved.
Edit earlier balance sheet analyses
What changed:
• "Edit Previous Balance Sheet Analysis" used to open only the most recently created analysis. Picking an earlier year or period failed with "Period has already been taken".
• If no analysis exists for the chosen period, users see the message "No analysis found for that period".
Why it matters:
Customers who build up a history by entering several years at once can now fix a mistake in an older year. Trends and comparisons no longer rest on wrong figures.
Important:
• Any existing analysis of a customer can be reopened and corrected, whatever its position in the history.
• Editing an earlier analysis works like editing the latest one: same steps, same fields, same validation. Only step 1 now selects the period.
• Corrected figures flow into everything that uses them for that customer, such as KPIs, trends and comparisons with neighboring years. Locking older entries is not part of this change.
Decision PDF now shows the full picture for approval
What changed:
The customer block at the top shows the company code and the credit control areas the user is allowed to see.
The risk profile shows Unsecured Limit and Uninsured Exposure (same rules as the web credit limit card, same currency as the other amounts in the PDF).
Credit cover is printed like the web comparison view (three covers per table), including manual cover answers. Credit information now prints what the web only shows in tooltips and modals. Manual entries appear with their details, like provider entries.
Missing values show a dash instead of a zero. The existing PDF settings (show, hide, reorder sections) keep working.
Why it matters:
Approvers and auditors can judge a credit decision from the PDF alone, without opening the customer record or the insurer's portal.
Credit limit conditions in the credit limit export
What changed:
The credit limit export layout now offers a "Conditions" column. It is also part of the default export without a template.
Each condition is written as the approver's name, a colon and the text (e.g. "Anna Schmidt: Parent company guarantee required"). Several conditions are joined by " | " in the order they were given.
Line breaks inside a condition become spaces, so every credit limit stays on one line. Commas, semicolons and quotes do not shift other columns when the CSV is opened in Excel. Limits without conditions have an empty cell.
Why it matters:
Customers who send the credit limit export to group headquarters no longer have to collect the approval conditions by hand. The file now covers what HQ needs.
Credit limit approval email: key figures and a direct link to the suggestion
What changed:
The subject now names the suggested amount and the customer, e.g. "Approval required: Credit limit of €50,000.00 for Neon GmbH (10001)".
The email shows the suggested limit next to the current one with the change in amount and percent, its validity, credit policy, risk class, score, open balance and orders, secured amount and uncovered risk, active credit covers, credit information per provider, earlier approvals with their conditions, and the approval step ("step 2 of 3").
The button opens the suggestion itself in the right company instead of the suggestion list.
Approvers are often heads of credit or C-level who decide from their inbox. They now see whether the limit goes up or down and why before they click, and land directly where they approve or decline.
Archive manual credit covers and credit information
What changed:
Manual credit covers (active or expired) and manual credit information reports now have an Archive action, behind a confirmation dialog that names the provider, the amount or score and the date.
An archived entry stops counting for the customer: a cover leaves the insured amount, and a report is no longer the current credit information (the latest remaining report of that provider takes its place). The credit policy runs again, so limits and suggestions based on the wrong entry are corrected.
No "cover expired" entry, no expiry notification, no risk alert. The customer's activity shows who archived what and when, and archived entries stay visible under the status filter "Archived".
Why it matters:
Until now a wrong manual entry could only be edited (reports) or ended (covers), and an ended cover looked like an insurance that had really expired. Now a mistake is removed cleanly and the customer's history stays true.
Important:
• Archive is for mistakes. A cover that really ended is still ended with "Cancel Cover", so the history shows it as expired.
• Archiving cannot be undone. If the entry was right after all, enter it again; a cover that was ended when the wrong one was created stays ended and is entered again too.
• Only manual entries can be archived, by users who may edit manual credit covers or credit information. Covers and reports from connected providers such as Creditreform, Allianz Trade or Atradius do not offer the action.
Help article: Manual credit covers and credit information
Correct the input currency of a balance sheet analysis
What changed:
In "Edit Previous Balance Sheet Analysis", step 1 shows the input currency again and it can be changed, even after the figures were entered.
After a confirmation, the entered figures stay exactly as they are and only their currency label changes. KPIs are converted to the template currency with the new currency's exchange rate.
A customer group assigned automatically from balance sheet KPIs is reassigned based on the recalculated KPIs. Credit limit decision PDFs created before the correction keep their original values.
Why it matters:
A currency picked by mistake no longer distorts the KPIs and the credit decision, and customers no longer have to re-enter the whole balance sheet or ask Support to fix it.
Important:
• The figures are relabeled, not converted: use it when the numbers are right and only the currency was wrong.
• Only currencies offered when creating an analysis can be selected, and only users allowed to edit balance sheet analyses can change it.
• The score stays as entered, and the correction does not add an entry to the customer's activity stream. Deleting a wrong or duplicate analysis is not part of this change.
Filter orders by country and user
What changed:
The Orders list has two new filters under "+": Country (the country of the customer's default address) and User (the user assigned to the customer).
Both accept several values and combine with the existing filters (status, company code, dates); the sum on this page and the total sum follow the filtered result.
The same two filters are available in the filter step of webhooks on orders.
Why it matters:
AR clerks no longer scroll through every order to find the ones of their own customers or of one country. A long order list narrows to the relevant part in two clicks.