Fibunet (Return Channel)

As soon as Bilendo sends a dunning notice, the corresponding dunning level is automatically updated in your Fibunet system. Your accounting department sees the current dunning status of each receivable directly in the ERP — without duplicate maintenance, without manual reconciliation, without follow-up questions.

Note: Fibunet (Import)
You can learn how to configure the Fibunet Import here.

Why this feature?

In many finance departments, accounts receivable management and accounting work with separate systems: Bilendo handles dunning, while Fibunet remains the leading ERP for master data and accounting. Without synchronization, an information gap arises — the ERP shows an open invoice, Bilendo shows "dunning level 3," and no one has both at a glance.

The Fibunet backchannel integration automatically closes this gap. Your team immediately recognizes in the familiar Fibunet interface which dunning level each receivable is in.

How it works

  1. Dunning is triggered in Bilendo. A dunning level (1–7) is set for an invoice. Bilendo then fires a webhook to the importer.

  2. The importer handles the update. The request is authenticated and placed in a background queue — so the update is processed reliably even during temporary connection issues.

  3. Fibunet is updated. The importer connects to your Fibunet system, identifies the matching invoice, and writes the dunning level and dunning date there.

The entire process runs in real-time and fully automated in the background.

Setup

The function is configured in two locations: in the Importer (Backend) and in the Bilendo main application.

1. Importer (Backend)

Note:
This step is performed by your Bilendo Integration Specialist.

On the Fibunet Connection page:

2. Bilendo Main Application (Frontend)

Note:
You can perform this step yourself or implement it with the help of your Bilendo Integration Specialist.