Ask for the original, not another guess.

Zoom in on a clipped invoice total. If the last digit is outside the frame, zooming makes the missing space larger. It does not bring the digit back. That is a useful place to stop guessing.

I would ask for the original supplier PDF first, where one exists. Otherwise ask for a complete rescan or a new photograph. The request should identify the problem so the supplier does not resend the same damaged copy at a higher file size.

Name the missing information

Distinguish an unclear digit from a missing region. A faint GSTIN may benefit from a better scan. A GSTIN cut off by the camera frame requires a complete photograph. A tax amount covered by a stamp needs another source or appropriate clarification.

“Send clearer invoice” is a weak request. “Please send the full invoice with the right-hand tax column visible” tells the supplier what to fix. Keep the invoice number and date in the request so the response cannot be confused with another bill.

Ask for the full page even when only one field is unclear. A crop may omit the heading needed to interpret the amount, or the party label needed to assign a GSTIN. Reading a sharp number without its role can still produce the wrong entry.

If the bill continues, ask for all pages in sequence. The multi-page completeness check is separate from image sharpness. A crisp first page cannot replace the missing continuation.

Choose the source that adds information

For a digitally issued invoice, request the original exported PDF rather than a screenshot of a print preview or a photograph of the printed page. Preserve the file you receive. A screenshot can cut margins or reduce small text.

A digital file is not automatically a legally valid invoice, and its text layer is not automatically complete. It is simply a potentially better reading source. The tax and identity checks still apply.

For a paper invoice, place the page flat, include every edge and avoid shadows over the table. Use enough detail for the smallest relevant figures. This is a practical capture habit, not a promise that a particular camera setting will deliver a measured accuracy rate.

Glare is another source problem. If a reflection covers the tax summary, changing the angle or lighting can add information that sharpening cannot recover. Keep the original full-page view as well as any clearer supporting close-up.

Do not photograph several loose bills in one frame if their identities or edges become ambiguous. Separate complete pages and preserve the order for each invoice. A larger image can still be a worse source if the relevant text occupies very little of it.

Where a supplier can send a replacement scan without a stamp obscuring the printed values, request it. Do not ask the clerk to infer the tax from the total just because the supplier's stamp makes the bill look official.

Don't replace a missing field with a convenient proxy

A vendor master can help you check a supplier identity, but it is not evidence of every number on the current invoice. A previous bill can explain a familiar layout; it cannot prove today's quantity or date.

Similarly, taxable value multiplied by a familiar rate does not establish that the invoice printed that line tax. The validation contract keeps required evidence and arithmetic separate from a general permission to fill gaps.

A GSTIN that looks one character away from the master may still be ambiguous. The checksum-limit article explains why plausible repairs cannot establish the intended counterparty in every case.

Keep your review note honest. “Unclear on supplied scan; clearer original requested” is useful. “Confirmed” is not useful if the person only accepted the most likely number because the queue was long.

If a new source contradicts the earlier extraction, preserve the earlier observation and resolve the difference explicitly. A revised PDF may be a clearer copy, or it may be a corrected document. Ask which it is before silently replacing the old source.

Another model sees the pixels you give it

EntryLedger uses local text/OCR rules where they can resolve a page and a vision-model fallback for uncertainty. A fallback can read difficult images, but it cannot guarantee recovery of information that is absent or obscured.

Some digital PDFs with source-bound checksum disqualifiers go straight to review instead of buying a model re-read. Their source preview may be rendered locally for display. Missing fields or lines can still need manual entry, and preview rendering can fail.

Do not generalise that route to all invalid GSTINs or to every scan. The workflow description distinguishes the narrow direct-review case from model fallback. A preview image is not proof that a model filled the whole invoice.

Older missing previews are not automatically backfilled. If a review lacks useful source information, follow the available re-ingest or source-review process rather than assuming a later release repaired every historic row.

Use a request the supplier can act on

Write the invoice identity, the specific unreadable area and the requested replacement. For example: “Please send the original PDF for invoice X; the right edge of the supplied photo clips the tax figures. Include all continuation pages.” This is a suggested message, not a report of a real customer exchange.

Record who requested it and keep the response attached to the same review. The next shift should know that evidence is pending, not restart the same guessing exercise.

Once the replacement arrives, read the disputed field and the surrounding labels again. Do not confirm merely because the new file is larger. Better source means the missing information is now usable.

The bill can then return to the ordinary checks and explicit review decision. Capture quality does not waive checksum or arithmetic validation, and a confirmed entry still prepares an export rather than completing a Tally import.

When the last digit is outside the frame, send the request. The cheapest next step may be a better page, not a more confident answer to an unreadable one.