Should this work have been invoiced?

An intervention finished, a contract still active, an order delivered… and invoicing that never followed. Kohentra tells a normal delay from a genuine miss.

See how it works All use cases

Example situation

What lands in your queue

What you are shown

A reasoned conclusion. Never an automatically generated invoice.

The reasoning, at a glance

Work is done
Invoicing usually follows this kind of work
No linked invoice, no recurrence covering it
The invoicing agent concludes, evidence in hand
You decide

The problem

Work can move ahead while invoicing lags behind. Traditional tools can't tell a normal delay (a recurrence under way, a contract still running, an invoice already generated from a template) from a real miss. The result: too many alerts, or none at all.

What Kohentra looks at

The business object (contract, intervention, order), its invoicing history, linked invoices, provenance notes (an invoice generated from a recurring template, for example) and the events normally expected for this type of object.

What Kohentra does

Kohentra rebuilds the invoicing context before involving anyone. It doesn't trust a raw status field: it checks what is actually demonstrated (a linked invoice, an explicit recurrence, a provenance note).

Expertise involved

The invoicing agent reviews the case with the evidence Kohentra gathered and concludes: invoicing apparently missing, already covered, or not enough data to decide.

What you are shown

A reasoned conclusion. Never an automatically generated invoice.

What you decide

You confirm, dismiss or postpone. This agent writes nothing to Dolibarr.

Why you can check it

Every conclusion cites its facts: invoice reference, recurrence note, contract date. You can check it at a glance.

Every situation comes with its evidence.

See how Kohentra turns your Dolibarr history into a short queue of explained situations.