Recover a failed export
Correct an export problem, retry safely, or record an externally completed export.
When an approved invoice cannot reach the ERP, Clerked keeps the failure on the invoice. If AP can act on the problem, it creates a Resolve Task for people with export responsibility and access to that invoice. Problems waiting for a connection to recover or requiring Clerked support do not create AP Tasks. Export failures do not add bell notifications or dismissible notices.
Read the failure
The export-failure disclosure explains the problem, any available remediation, and the current recovery state. The invoice header shows the actions you can actually take. When a Resolve Task is available, everyone with invoice export responsibility and access to the invoice shares that work. A failure waiting on an automatic attempt, connection recovery, or support does not require AP to repeatedly click Retry.
Choose the recovery action
- Retry Export checks that the invoice still matches what was approved and passes the export checks before contacting the ERP. Safe temporary errors retry automatically with increasing delays.
- Retry PDF upload finishes required source-document delivery for a bill that is already in the ERP. It continues delivery to that bill without creating another bill.
- Corrections to fields that require renewed AP review save immediately. When the earlier export is confirmed safe to retry, Return to AP replaces Retry. Enter a reason; Clerked returns the invoice through validation and fresh approval before export. If an earlier attempt might already have created the invoice in the ERP, resolve that uncertainty first.
- Export starts a first export for an approved invoice whose integration was previously not applicable, when the action is available.
- Mark exported externally records that the invoice already exists in the ERP. Confirm it in the ERP first and enter the required reason.
If connection health is bad, Clerked parks the invoice and wakes it automatically after the connection recovers. Do not repeatedly retry it.
If Retry Export reports an export-readiness issue, such as a missing PDF or an attachment over the size limit, resolve that issue first. When Retry remains available, use it again after the repair; you do not need to change an invoice field or reload the page. The readiness message clears when the retry is accepted, and the invoice’s export state shows the outcome of the new attempt.
Prevent duplicate payables
When Clerked cannot prove whether the ERP accepted an earlier attempt, Retry requires a reason and confirmation that you searched the ERP and did not find the invoice. That evidence is retained with the recovery attempt. If Clerked already has evidence that the invoice is in the ERP, follow the recovery action shown for that existing bill. A retry can verify an export that already reached the accounting system instead of creating a second record.
If the connected ERP requires the original PDF, the invoice stays Export Failed until delivery is verified. The disclosure shows the existing ERP record ID when available. Accounting edits, Return to AP, and Mark exported externally cannot bypass required PDF delivery. Use Retry PDF upload when offered; if Clerked cannot determine whether an earlier upload succeeded, follow the recovery guidance or contact support before uploading another copy.
Recover several invoices
The invoice list’s failed-export state supports eligible bulk Retry and Export actions. Each invoice returns its own result; unsafe or unauthorized rows are excluded.