E-invoicing: inbound-reception obligation in France from September 1, 2026 Your Backlane invoices are already compliant →
The agents · Collections

The collection delay, divided by 3.

The Collections agent sweeps unpaid invoices every morning, drafts the chasers, tracks payment promises and collects through the portal. On the first fleet under management: from ~14 days to under 5.

Quantify my fleet in 48 hours Book a demo
÷3 on the average collection delay10,000+ paid invoices measured, H1 2026day before every chaser announced before it goes
Does alone
✓Sweeps all unpaid invoices every morning at 8:00
✓Drafts chasers by email, SMS or WhatsApp, with a payment link
✓Tracks payment promises and reacts when they slip
✓Ties every collection to its invoice, balance by balance
Asks you
Approve sensitive chasers before sending (large balances, fragile customers): an editable draft, not a frozen template
A volume circuit breaker: an unusual mass send freezes itself and waits for your go
A typical morning
8:00 am, the morning queue.
The agent has swept the outstanding balance: standard chasers are ready and announced, three sensitive files await your approval with the draft already written. You reread, adjust one sentence, send. The customer pays on the portal, the invoice settles itself.
The circuit breaker

The guardrail nobody talks about, and the one that matters most.

An agent that chases is an agent that can chase too much. The real risk of an automated back office is not that it forgets: it is that it sends eight hundred messages because a rule was written badly. So there is a fuse, upstream of the send.

What it does
  • Counts sends per customer and per time window, before the first message leaves.
  • Freezes every send as soon as the volume leaves what is ordinary for that fleet.
  • Raises a critical card once, naming the count and the window at fault.
  • Stays frozen until a human explicitly releases it: no timer unlocks it.
  • Refuses to resolve the affected cards while the freeze holds, so the fuse cannot be bypassed by approving by hand.
What it does not do
  • Reopen itself after a few minutes.
  • Let "just the urgent ones" through during the freeze.
  • Trigger on a fixed threshold identical for every fleet.
  • Send part of the batch before closing.

This fuse exists because a real incident demanded it: a mass send from a demonstration environment reached real recipients. Every send path now goes through this control, and a demonstration environment redirects its sends instead of delivering them.

Frequently asked questions

Who writes the chasers? In what tone?

Your rules, your tone: every chaser is an editable draft, sent from your domain once verified. Never a frozen template, never an unverified domain.

Will it spam my customers?

No: the agent announces its work the day before, respects your caps, and a circuit breaker freezes any unusual mass send until you approve. A customer with a live payment promise is not chased.

How does the customer pay?

Every chaser carries a link to the payment portal: the customer signs in with a one-time code, sees all their invoices, pays by card or transfer. The payment settles the invoice automatically.

The team: Billing · Collections · Sales · Intake · ContractsThe whole team →
The rest of the team
Billingissues, chases, collectsIntakefrom order to roadSalesqualified inboundContractsterms before the term
How much are you losing today?
No theoretical number: we measure it with you. In 30 minutes on your real fleet, or quantified from 6 months of history, delivered within 48 hours.
Quantify my fleet in 48 hours Book a demo

No commitment. Nothing changes with your current tools or insurer.