Starter Integration approval backlog worksheet
Triage pending and expired connection approvals, then find the next action for each Starter Integration invoice from its current request.
By Lars Holdgaard, Founder & CEO of Debitura

If a Starter Integration invoice is waiting for an existing client to approve a connection, read that invoice’s current request before contacting the submitting user. Keep the approval in a separate queue from the invoices it affects. After consent, refresh each invoice and assign its remaining action separately.
Worked example
Fictional example: Northbank Tools submitted invoices INV-410 and INV-411. Nora is the submitting user. The queue uses short labels R-410 and R-411 for the two stored request IDs. The three rows show alternative snapshots of R-410, each read at 10:15 UTC.
| Current read | Next owner | Next action | Check before restarting |
|---|---|---|---|
| R-410 · awaiting_approval (approval) | Nora, through the hosted approval step | If the current response supplies an approval URL, present it there to Nora. Debitura emails the invitation to the submitting user. | Confirm this is the current request and the submitting user. When the URL is missing, refresh and keep the row waiting. |
| R-410 · expired | Product support, then the submitting user | Explain that the approval expired. Leave the old link closed. If the authorized user still wants to place the invoice, use the integration’s deliberate fresh-submission flow. | Refresh the current request and the related invoice records. Check that a new request is needed and no current submission already represents the invoice. An identical keyed replay returns the earlier response during the idempotency window. |
| R-410 · awaiting_signature (power_of_attorney) after the user approved the connection | Authorized client signatory | Present the current signing action and its returned link, when available. Refresh after signing. | Update R-410 from its own response. Read R-411 separately because it may have a different next action. |
Keep one line per request
Record the external client reference, invoice reference, stored request ID, submitting user, read time, current status, next owner and follow-up. Record whether the current response returned a link. Keep the actual link in the authorized application, outside the shared worksheet.
Read again after a webhook or hosted step
Use the webhook as a prompt to refresh. If a current read returns processing, keep the invoice visible and refresh later. When it returns submitted, show the invoice’s separate case status. Check the case status before describing collection as active.
Copy the worksheet
Select the two tab-separated lines and paste them into a spreadsheet. Replace the example with your own records.
| External client ref | Invoice ref | Request ID | Submitting user | Read time UTC | Reading source | Current status | Solution type | Current link present | Next owner | Next action | Next check |
|---|---|---|---|---|---|---|---|---|---|---|---|
| NT-04 | INV-410 | R-410 | Nora | 10:15 | Current request GET | awaiting_approval | approval | Yes | Nora | Open current approval action | Refresh after hosted step |
Next step
Build the Starter Integration flow
References
-min.webp)
Sign up to our newsletter
Get updated on best practices, tips and tricks about international debt collection and accounts receivable management.

.webp)