Two files can look almost identical on a screen while coming from different places. One may be an electronic document supplied by an issuer. Another may be a scan that a user uploaded to storage. Understanding that difference helps you choose the right file and ask better questions when a recipient requests a digital document.
This guide explains the distinction without deciding whether a particular record is acceptable for your application. The receiving institution's current instructions and the issuer's own service remain the practical authorities for that question. Do not assume that putting a file into an app changes who issued it.
Start with where the document came from
Ask a simple question: did the issuing organisation provide this electronic record through its service, or did somebody create a copy and upload it? The answer describes provenance, the route by which the file reached you. It is separate from whether the image looks sharp or the filename sounds official.
A user-uploaded scan can be useful for personal storage and many practical tasks. It is still a scan of a record. An issuer-provided electronic document has a different source route. You should preserve that distinction when organising files and explaining what you are sending.
Do not rename an uploaded image to make it sound issuer-generated. A clear folder label such as personal-scan helps prevent confusion. If an institution asks for an issued digital record, find out which issuer or verification route it expects rather than assuming any PDF will do.
What DigiLocker calls these categories
The DigiLocker FAQ distinguishes Issued Documents, supplied through integrated issuers, from documents uploaded by the user. It describes issuer document links as URIs. The important practical point is that an uploaded copy and an issued record are different categories in the service.
Look at the section you are using rather than only the thumbnail. A familiar-looking certificate in a personal upload area should not be described as issuer-fetched merely because the same app also supports issued documents. When in doubt, read the service's current help and the issuer information shown with the record.
This distinction does not require you to become a technical specialist. It requires you to keep track of the source. You can record “downloaded from issuer” or “scan of paper original” in your private inventory without copying sensitive fields into the note.
Match the recipient's wording
A recipient might ask for an original, a self-attested copy, an issued digital document or a scan uploaded through a particular form. These phrases can describe different submission routes. Read the whole instruction rather than selecting whichever file is easiest to locate.
If the wording is unclear, ask a specific question: which document type, issuer and submission channel does the institution accept? Keep its answer with the application note. A general claim about paperless services does not settle the requirements of every individual process.
Do not infer acceptance from a previous application. A college, employer or scheme may change its notice or ask for a different issuing level. The certificate directory helps you identify the document topic, while the current receiving notice tells you what this task needs.
Preserve the unchanged file
When you obtain an electronic record, save an unchanged copy before making any working version. If you need a smaller file for a particular upload, keep that output separately. A filename can indicate that it is a submission copy without suggesting that the issuer created a new version.
Avoid editing names, dates, amounts or identifiers inside an official record. A visible error is a reason to contact the issuer or use its correction process. Changing the pixels or text yourself does not update the underlying record and can create a misleading document.
Annotations should stay in a separate note unless the receiving process specifically requests them. Do not place a large handwritten reminder across a QR code or signature. Keeping the received file intact also makes it easier to explain what changed when an authorised replacement later arrives.
Use verification carefully
Some documents include a verification link, code or other mechanism provided by the issuer. Follow the issuer's instructions and check the destination before entering information. A code is not an invitation to upload the record to any website that offers “certificate checking.”
You may be able to inspect whether a verification route exists without publishing the record. Do not post a full certificate in a public forum to ask whether it looks genuine. The image may reveal far more personal information than the question requires.
This reading guide does not authenticate documents. A visually plausible seal, a QR-like pattern or a correct-looking font is not enough to establish authenticity. If acceptance or authenticity is disputed, the responsible issuer and recipient need to resolve it through their authorised channels.
Keep account access separate from document sharing
Giving someone a copy of one requested record is different from giving them access to the account that stores all your records. Do not share a password or OTP so a helper can fetch a single document. Use the service's intended sharing or download process where appropriate.
Review the scope of a sharing action. Does it expose one file, a folder or an account-level connection? Can the recipient edit or reshare? The controls vary by service, so inspect the current interface and help rather than relying on a remembered button from another app.
After the task, review any continuing access you granted. An old sharing link may remain active after the application is complete. Keep the review proportionate: record what you shared, with whom and why, then remove unnecessary access through the service's supported controls.
Make an understandable personal archive
Store issued downloads and personal scans in separate roles, even if they sit inside the same broader task folder. A simple structure prevents you from sending a working scan when the request was for an issuer-provided file.
Use clear, neutral names. Do not include identity numbers merely to make the file feel unique. For multiple records, a private index can tell you which source and date relate to each file. Read file names that stay useful for a small system that works on both phones and computers.
Keep a note of where you can retrieve the record again. That might be the issuer's service or a supported digital-document account. Do not put login credentials in the same note. Retrieval instructions and account secrets should not be mixed into a folder that may later be shared.
When a digital record is not available
A missing record in an app does not by itself tell you whether the underlying paper record is invalid, unregistered or unavailable everywhere. It may mean you are looking in the wrong place or that the issuer's digital route needs a different action. Avoid drawing a broad conclusion from one empty search result.
Check the issuer's official guidance and confirm the information the retrieval form requests. If you still cannot locate the record, use the authorised help route. Keep any error wording and relevant dates privately so your question can be specific without exposing a full identity bundle.
Do not pay an unrelated service that promises to make every record appear in an account. A legitimate retrieval problem is not solved by giving an unknown person unrestricted access. Ask what the issuer can actually provide and which alternative the receiving institution accepts.
A document-sharing check
Before sending, identify the requested record and the source of the file you selected. Open the file, inspect all pages and confirm that it belongs to the correct person. Check the destination and the sharing scope. Save any acknowledgement that the recipient provides.
If you made a smaller copy, retain the unchanged source and label the working version clearly. If you discovered an error, stop and organise a correction query rather than altering the record. Our correction preparation guide gives a structure for that conversation.
The value of a digital archive is not just that files occupy less space. It is that the source, purpose and next action can be understood. A few careful distinctions make the archive more useful without turning it into a complicated technical project.
If a recipient rejects the file, ask which requirement was not met before creating another version. A format issue, a source issue and a mismatch in personal details need different responses. Keep the explanation with your task record.
