Reconcile a saved Registry row with a missing receipt log
Master Beneficiary Registry · Reconcile a saved Registry row with a missing receipt log · all · Published version 7
Public task guidance
Provisional guidance
The Registry saved the row and recorded that save in the same transaction. The normal receipt log is still missing for the indicated row.
What to do
- Open Reconcile records and check Registry saved, receipt log missing. Use Download audit report and keep the original batch and Registry references.
- Field Agent: Report the missing receipt log to the Registry Administrator. Keep the saved row out of follow-up corrections.
- First Reviewer: Keep the existing approval and use the original and alternate batch references to follow the reconciliation.
- Registry Administrator: Compare the saved-row evidence with the native job and receipt log. If both retries have ended and the log is still missing, keep the failed attempts with the incident evidence. Coordinate with Registry integration support to retry the existing native job once the log error is resolved. Refresh the original receipt to verify the restored log.
What you need
A saved row continues to block alternate transfers for its source key. Native retries reuse the same saved row and share the same receipt, even if they overlap. If another worker is still retrying when a worker fails, keep the alternate blocked and refresh the original receipt when the retry settles.
Next step
Resolve the missing log against the original transfer. After both retries fail, ask Registry integration support to retry that same job once the log error is resolved. Keep the saved row out of alternate batches throughout.
Source · Native Registry import save journal and receipt reconciliation