Document rejected as unreadable: what to fix before resubmitting
A readability rejection calls for a readable capture of the correct document. Repeating the same upload or editing its contents does not answer the underlying problem.
Read the rejection as a specific question
First separate “cannot read the image” from “this document is not acceptable”. The latter may concern a category, date or mismatch, and requires clarification of that requirement. An unreadable image concerns whether the recipient can assess the details that were supplied.
OLG’s withdrawal FAQ identifies unreadable images and unsupported file types among rejection reasons. 888 Ontario separately asks for relevant document details to be visible and legible. These are operator-specific examples; follow the actual recipient’s instructions.
Inspect the saved file, not just the camera preview
- Open the exact file you intend to upload and confirm the requested pages or sides are present.
- Check whether glare, shadow or blur obscures the particular field mentioned in the rejection.
- Check the frame against the recipient’s instructions; do not assume a cropped detail is sufficient.
- Read dates and names at a practical viewing size. A larger file alone does not establish readability.
- If the error concerns type or size, check those requirements separately before taking another photograph.
Worked example: a reflection over one date
A fictional rejection says the expiry date cannot be read. Your saved image includes both sides of the requested card, but a bright reflection crosses that date. A fresh photograph under even lighting addresses that stated defect. Increasing sharpness on the original does not recover information hidden by the reflection.
Before resubmitting, check the new image for the same issue and preserve the rejection notice. Record that the replacement addresses readability of the date. Do not claim that the operator has accepted the document merely because the upload succeeded.
Correct the capture without changing the evidence
Retake or rescan the document when that is the appropriate fix. Do not paint over fields, reconstruct letters with image-generation software or change a date. Ask the recipient before applying redactions, combining pages or converting formats when its instructions do not cover the change.
If the new upload produces the same generic rejection, ask which field is still unreadable and whether the latest version was assessed. Repeatedly submitting more records can obscure which file the response concerns.
What to retain privately
Keep the case reference, submission time, file version and receipt. A short log such as “replacement image, expiry date clearer, uploaded Tuesday” can explain the change without placing the document in a public complaint.
This is a practical capture checklist, not forensic validation. Northline cannot inspect your identity document, approve it or promise that a corrected image will resolve a separate eligibility issue.
Sources & reading
Primary references support the factual context below. Explanations, worked examples and calculations are original Northline analysis. Read how we handle evidence.
- 888 Ontario — document types
Operator-specific guidance. Requests are conditional on the reason for verification. This is not a universal document list. Accessed .
- OLG — withdrawal questions and processing stages
OLG-specific FAQ. Processing aim, subsequent bank transfer and document issues are separate. No private-operator timing or guaranteed arrival is inferred. Accessed .
An editorial review date is not a new policy effective date. Always check the current source for operator-specific conditions.
Suggest a correction