Authorization screens for embedded debt collection
Design the customer journey from invoice preview through account setup, connection approval, invoice correction and confirmed submission.
By Lars Holdgaard, Founder & CEO of Debitura

Keep the invoice and its next action visible in your software. When the customer needs to complete a step in Debitura, explain where the next action opens and what will happen when they return. Show a submission confirmation once a fresh request read confirms submission and returns a case reference.
Storyboard for one overdue invoice
Fictional example for an invoicing platform: North Quay Studio’s invoice INV-2048 has €2,400 outstanding. Each screen shows a possible state for that invoice. The next screen depends on the result for the customer and invoice.
Review invoice for collection
“Review the outstanding balance of €2,400 on INV-2048 before sending the invoice details to Debitura.”
Button in your software · Continue with Debitura
Use the invoice data already in your software for this preview. The collection request starts when the customer continues. The preview has no case reference.
Set up your Debitura account
“Finish setting up your Debitura account to continue with INV-2048.”
Button in your software · Continue setup in Debitura
On awaiting_onboarding, open the returned action link. The customer completes setup in Debitura. Refresh the request on return and keep the invoice visible while setup is pending.
Approve the connection in Debitura
“Sign in to Debitura and review the connection request for your company.”
Button in your software · Review connection in Debitura
On awaiting_approval, use the returned approval link. Account selection and approval happen in Debitura. A case can be created once required connection approval is granted and the request advances.
Sign the required agreement
“INV-2048 needs your signature before it can proceed. Review the agreement in Debitura.”
Button in your software · Review agreement in Debitura
On awaiting_signature, use the returned agreement type to name the document and the returned link to open it. A case may already exist while signing is pending. Use the returned case reference and current case status to tell the customer where it stands.
Correct invoice details
“Add the debtor’s missing street address in Debitura, then submit INV-2048 from the review screen.”
Button in your software · Correct invoice in Debitura
On needs_fixing, use the returned issue and action link. The customer corrects and explicitly submits the draft in Debitura. Saving the draft leaves it awaiting submission.
Invoice submitted to Debitura
“INV-2048 was submitted. Debitura is verifying the case.”
Button in your software · View case in Debitura
Use this example when the current request is submitted, the invoice has a caseId and its caseStatus shows verification. Use the returned case status for other outcomes. Offer the case link when the response supplies it.
Acceptance checks
- Return from setup or signing and refresh the existing request even when no update notification arrived. Keep the customer on the same invoice.
- For
awaiting_kyc, show “Complete identity details in Debitura” and open the returned link. Refresh afterward. - Show “Checking submission” while the request is
processing. If an action link is absent, offer a refresh of the same request. Use a current read for an unfamiliar state. - If approval expires, explain that the connection request expired. If the invoice is rejected, explain the returned reason when available.
- In a five-invoice selection, show the outcome on each invoice row. Confirm only the invoices whose current request and case reference show a submission.
Plan the integration
Use the Starter Integration guide for the flow and the collection request reference for states, case fields and action links.
-min.webp)
Sign up to our newsletter
Get updated on best practices, tips and tricks about international debt collection and accounts receivable management.

.webp)