Amicable collection
-
2
 min read

How to pause new embedded collection submissions

Pause new submissions at your own entry points while keeping existing case status available. Reconcile anything still in flight before reopening the button or releasing a queue.

By Lars Holdgaard, Founder & CEO of Debitura

How to pause new embedded collection submissions

Assign an owner to each state

  1. Queued, with no submission attempt. Give each record an internal reference and timestamp. The queue owner confirms it has stayed in your system. Decide whether the customer will be asked to confirm again before it is sent.
  2. Attempted, with acknowledgement pending or recorded. Have the integration owner match the request to a response and case reference where available. If the outcome is uncertain, resolve it using the documented lookup and retry behavior for your chosen integration before submitting again.
  3. Existing active case. Keep the status view and its normal support route available. Assign a support owner to check that a user can still find a case created before the pause.

Test the pause and reopen path

Fictional example. A billing platform is replacing its invoice-to-collection handoff. The release lead closes new submission entry points and asks support to keep existing case links available. The queue owner records three unattempted submissions. The integration owner reconciles a fourth record whose acknowledgement had been delayed. Support checks an older case from the customer’s view.

The release lead uses a test tenant to verify three outcomes: an attempt during the pause produces no outgoing submission, an authorized attempt after reopening yields one acknowledgement and one case reference, and the older case still appears with its expected status. The lead reopens to the first group of users only after all three outcomes match. If any check fails, the lead pauses new submissions again and has the owner reconcile the affected records.

Record the cutover decision

Save the tenant, test time, owner, expected and observed results, queue count and reopen decision. Tell support who owns an unattempted submission, who investigates an uncertain result and where users can see existing cases.

Use Debitura’s case submission guide, case status guide and environment documentation to check the behavior of your integration. Use the pilot measurement guide when you restart measurement. Explore embedded collection for software partners if you are planning a pilot.

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.