Fixed reports and analyses on demand.
The report that looks the same every month, and the question asked for the first time today — both compute with the same figures and the same classes. That is where reporting and the agent belong together.
Due-date report · current month
Report
Queried live
Analytics
Analysis on demand Template · customer analysis
Headline figures
- Overdue share
- 18%
- Median DSO
- 31.4
- Highest reminder level
- 3
Finding
The overdue share is rising for the third month running, carried by two customers with €1.6M between them — both have an open clarification.
Source Figures from the database, classes from your aging ladder
What has to look the same every month.
A report is only a report if it repeats: the same definition, the same classes, the same figure in the same place. That is the half Bilendo has had for years — configured, scheduled, exportable.
Due-date report
The aging breakdown in your classes and your labels — the ladder everything else refers to.
Dashboards
Composed from sections and cards, a home screen per role.
Limit and overdue reports
Utilisation, breaches, risk classes — the reports credit management needs monthly.
Export templates
Fixed fields and formats, so an export still fits the next processing step.
Scheduled exports
On a schedule to the people who need them — without anyone having to remember.
And the question asked for the first time today.
Some analyses do not deserve a report: one customer, one run, one selection, one week. For those the agent writes an analysis — with headline figures, set widgets and a finding in words that points at the figures above it.
- Templates
- Recurring questions have templates — they fix which datasets an analysis always shows.
- Headline figures
- The figures that lead for this object type sit above the prose — declared, not chosen per run.
- Set widgets
- What the template names is always there; what the agent adds comes after it.
- One running analysis per subject
- The same thing does not run twice for one customer. The database enforces that, not the interface.
The same ladder, the same words, the same figure.
This is where the two halves meet: an analysis's aging breakdown uses the classes and the labels of your due-date report — and where no ladder is configured, the breakdown is left out instead of computed against an assumed 30/60/90.
One definition
The words "due today" mean in the analysis what they mean in the report. Otherwise there would be two truths.
Omitted, not guessed
Without a configured ladder the block is missing. That is more honest than a figure nobody can trace.
Figures from the database
Counting, totalling and classifying is SQL's job. The model phrases and selects — it does not compute.
What an analysis explicitly does not do.
A figure without provenance is worthless in a finance department. Which makes these the most important boundaries on the whole platform.
- No figure from the language model. Counting, totalling and classifying is the database's job.
- No totals across currencies. Sums stay separated per currency.
- No invented aging. Without a configured ladder the block is left out.
- No analysis over data without permission. An analysis never sees more than the person it runs for.
- No second running analysis for the same subject. The database prevents it.
- No report that shows something different on export than it did on screen.
What controlling asks first.
From your database, over the same query path as any view — counted and totalled by SQL, with an exact hit count and separated per currency. The language model selects and phrases; it does not compute. Which is why an analysis never contains a figure you cannot find again in a view.
Yes, the ones from your configuration, in the same labels as the due-date report. If no ladder is configured, the analysis leaves the aging breakdown out — it assumes no 30/60/90 and guesses no cut-off.
Yes, and they solve a different problem. A report repeats: the same definition, every month, without asking — which is the basis for comparison over time. An analysis on demand answers today's question. Anyone who reports regularly wants both.
No. It runs with the roles and data scopes of the person it runs for, and returns nothing when in doubt. A customer group that person may not open does not appear in the analysis.
Yes — through export templates with fixed fields and formats, and through scheduled exports that go to the registered recipients on a schedule. What is exported is what was on the screen.