Invoicing
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.
Use cases
Invoicing, interventions, tickets, relations, collections: each case starts from a real business question and shows what Kohentra looks at, the expertise it calls in and what it leaves for you to decide.
Invoicing
An intervention finished, a contract still active, an order delivered… and invoicing that never followed. Kohentra tells a normal delay from a genuine miss.
Interventions
Close too early and you lose a follow-up still due. Close too late and it buries the ones that matter. Kohentra tells you when every condition is met.
Expected events
Your tools see what happened. Kohentra also sees what should have happened, and didn’t.
Support
Between spam, requests already dealt with and real customers left waiting, Kohentra sorts things out, and tells you why a ticket stands out.
Relations
Customer, contract, intervention, equipment: Kohentra measures what really links your records, and never passes off a correlation as a certainty.
Add-on modules
Asset management, connectors, in-house modules: Kohentra discovers the objects your add-ons bring and links them to the rest of your business, without custom code.
Memory
Nothing wears people down like a settled alert that comes back every morning. Kohentra remembers what you decided, and what its agents concluded.
Collections
An overdue invoice is not necessarily a problem. Kohentra lets the grace period you set run its course before it bothers you.
Each case describes a capability available today. It only switches on in your workspace if your data allows it: Kohentra first checks that it has the resources and history it needs, and tells you what is missing if not.
See how Kohentra turns your Dolibarr history into a short queue of explained situations.