Accounts receivable
-
3
 min read

How to measure an embedded collection pilot

Set a fixed pilot window, then count the invoices eligible for the collection button, those for which someone starts the handoff, and the client companies with a confirmed first case created during the pilot. Track connection approval only among companies that need it. These checks show where people stopped and where evidence is missing.

By Lars Holdgaard, Founder & CEO of Debitura

How to measure an embedded collection pilot

Use the same window and keep the counting units visible

Before the pilot, record which customer groups and invoices are eligible, which feature version is active and which events you can verify. Give invoices and companies stable identifiers. Record an event timestamp and a source for each transition. Use invoice counts for eligibility and handoff. Use company counts for connection approval and first cases. Connection approval records the existing client’s consent to connect its account. Record onboarding, signing and case verification separately.

For a Starter Integration, preserve the invoice reference and the returned collection request ID. The request ID tracks progress. Use the case ID, creation time and account history to verify case creation. Count a case only if it was created inside the pilot by the observation cutoff and is the company’s first. Record its current state separately. For example, a submitted request has reached Debitura’s ordinary verification. Collection request reference

Work through a fictional four-week pilot

Check Recorded What the team can say
Eligible invoices 80 invoices across 50 companies 80 distinct invoices met the eligibility rule during the pilot.
Started handoffs 24 invoices across 18 companies 24 of 80 eligible invoices had an observed handoff start. Count repeat clicks against the same invoice once.
Approved connections 5 of 7 starter companies that required existing-account approval Of the 18 companies that started, seven required approval. Five approved, one was pending and one was unresolved at the cutoff.
Verified first cases 6 of the 18 companies that started a handoff Six companies had a case confirmed as their first in the available account history. Two of the six were among the five that approved a connection.

In this example one event delivery was repeated and one expected event never arrived. The team counted repeated delivery of the same event ID once and used the current request read to resolve the missing update. If there is a case ID but earlier history is incomplete, record the first case observed in the pilot and leave first-ever status unresolved. Keep missing evidence in its own count.

Copy this record into your pilot tracker

  • Pilot start, end, observation cutoff and time zone
  • Company key, invoice key and eligibility evidence
  • First handoff timestamp and collection request ID
  • Existing-company approval required, confirmed, pending or unknown
  • Case ID, creation date, verified state and first-case history coverage
  • Missing or duplicated evidence, owner and next review date

Use these counts to choose a follow-up. An eligible invoice with no observed start calls for checking placement and exposure. An account stuck at approval calls for checking the customer’s next action. A start with missing case evidence calls for checking the current request and its related case.

For the integration and release steps, see the Starter quickstart and go-live checklist. If you are evaluating an integration for your platform, review the Debitura referral partner programme.

Subscription

Sign up to our newsletter

Get updated on best practices, tips and tricks about international debt collection and accounts receivable management.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.