Collect invoices without effort
The accounting software is connected, and invoices and due dates flow in on their own. An AI-assisted import (PDF, image, Excel, CSV) serves as a fallback.
Coperis AI Labs
We build and run our own AI products. They are our testing ground, and the source of what we recommend to our clients.
Product
Relanzy automatically chases unpaid invoices for French freelancers and small businesses, from their own email address. It is in production.
What Relanzy does
The accounting software is connected, and invoices and due dates flow in on their own. An AI-assisted import (PDF, image, Excel, CSV) serves as a fallback.
Reminders go out from your own mailbox (Gmail, Microsoft or SMTP), not from a third-party service. To your customer, it is you writing, with the tone and pace you chose.
Late-payment penalties and the €40 fixed recovery fee are calculated, then a formal notice is generated as a PDF when the amicable route is not enough.
Smart Reply
When a debtor replies, a language model classifies the reply in real time and the case reacts accordingly.
Every classification shows the model’s confidence level. A person decides what happens next whenever the customer relationship is at stake. We do not publish usage figures until the sample is significant.
Field notes
Lessons from our own products, the kind you do not find in the documentation.
Some identifiers exceed the integer size JavaScript can represent without loss. Converted to numbers, they round silently and the sync links the wrong invoice. We store them as text, end to end.
An invoice marked as paid can still show a non-zero amount due in the API response. Trusting the amount would chase a customer who has paid. Reminders stop on status, never on a zero balance.
Before the model classifies anything, safeguards set aside risky cases: no-reply addresses, out-of-office replies, disputes already open. A case in dispute is never downgraded by a later reply.
A test suite pointed at the live database by mistake created ghost accounts there. Since then, the code refuses to start unless the database is explicitly allowed: the safeguard is designed to fail closed.
Our first publisher verification request to Microsoft was rejected: the domain was registered to a person, not to the company. We transferred it before resubmitting. Check this before any platform certification.
For your projects
Identifiers, duplicates, expiring tokens, contradictory statuses: we have hit them before your teams do.
Safeguards, confidence levels, controlled costs, human decisions where they are needed: none of this shows in a demo.
App verification by Google and Microsoft, connector certification by a partner platform: we know what they ask for.
The context, the deadline, what is blocking. We reply within two business days. If we are not the right people for it, we will tell you.