{"id":3882,"date":"2026-05-18T11:36:26","date_gmt":"2026-05-18T09:36:26","guid":{"rendered":"http:\/\/tsholo"},"modified":"2026-05-18T11:36:26","modified_gmt":"2026-05-18T09:36:26","password":"","slug":"source-connected-verification-vs-document-collection","status":"publish","type":"docs","link":"https:\/\/j-cred.co.za\/zh\/helpcenter\/source-connected-verification-vs-document-collection\/","title":{"rendered":"Source-Connected Verification vs Document Collection"},"content":{"rendered":"<h2>Overview<\/h2>\n<p>Document collection is when a person uploads or submits a document. Source-connected verification is when the information is checked against a trusted source, custodian, registry, bureau, authority or approved verification process.<\/p>\n<h2>Why it matters<\/h2>\n<p>Documents are useful, but they can be outdated, altered, misread or insufficient on their own. Source-connected verification helps reduce the risk of relying only on what was submitted by the person or intermediary.<\/p>\n<h2>How to think about it<\/h2>\n<ul>\n<li>Use document collection for evidence intake and workflow initiation.<\/li>\n<li>Use source-connected verification where authenticity, current status or risk exposure must be confirmed.<\/li>\n<li>Use manual review when automated results conflict with submitted evidence.<\/li>\n<li>Use a clear audit trail to show which evidence was collected and which source was consulted.<\/li>\n<\/ul>\n<h2>Common examples<\/h2>\n<ul>\n<li>A matric certificate image can be collected, while certificate authenticity may need verification through the relevant education verification channel.<\/li>\n<li>A company registration document can be uploaded, while company status may be checked against a business registry.<\/li>\n<li>A proof of address can be submitted, while contactability and trace indicators may be used to support engagement.<\/li>\n<\/ul>\n<h2>Responsible use reminders<\/h2>\n<ul>\n<li>Do not assume that a clear document image is authentic.<\/li>\n<li>Do not assume that a source result replaces human judgment in every case.<\/li>\n<li>Keep both the document and the verification outcome under appropriate access controls.<\/li>\n<\/ul>\n<hr \/>\n<p><strong>Public knowledge note:<\/strong> This article is intended as general education for verification, compliance, fraud prevention and responsible data-use discussions. It is not legal advice and should not replace your organisation&#8217;s own compliance review, regulator guidance, or contractual obligations.<\/p>","protected":false},"excerpt":{"rendered":"<p>Overview Document collection is when a person uploads or submits a document. Source-connected verification is when the information is checked against a trusted source, custodian, registry, bureau, authority or approved verification process. Why it matters Documents are useful, but they can be outdated, altered, misread or insufficient on their own. Source-connected verification helps reduce the risk of relying only on what was submitted by the person or intermediary. How to think about it Use document collection for evidence intake and workflow initiation. Use source-connected verification where authenticity, current status or risk exposure must be confirmed. Use manual review when automated results conflict with submitted evidence. Use a clear audit trail to show which evidence was collected and which source was consulted. Common examples A matric certificate image can be collected, while certificate authenticity may need verification through the relevant education verification channel. A company registration document can be uploaded, while company status may be checked against a business registry. A proof of address can be submitted, while contactability and trace indicators may be used to support engagement. Responsible use reminders Do not assume that a clear document image is authentic. Do not assume that a source result replaces human judgment in every case. Keep both the document and the verification outcome under appropriate access controls. Public knowledge note: This article is intended as general education for verification, compliance, fraud prevention and responsible data-use discussions. It is not legal advice and should not replace your organisation&#8217;s own compliance review, regulator guidance, or contractual obligations.<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"_eb_attr":"","footnotes":""},"doc_category":[27],"doc_tag":[],"class_list":["post-3882","docs","type-docs","status-publish","hentry","doc_category-public-verification-101"],"blocksy_meta":[],"year_month":"2026-06","word_count":253,"total_views":0,"reactions":{"happy":0,"normal":0,"sad":0},"author_info":{"name":"KTO Digital Admin","author_nicename":"tsholo","author_url":"https:\/\/j-cred.co.za\/zh\/author\/tsholo\/"},"doc_category_info":[{"term_name":"Verification 101","term_url":"https:\/\/j-cred.co.za\/zh\/docs-category\/public-verification-101\/"}],"doc_tag_info":[],"_links":{"self":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs\/3882","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/comments?post=3882"}],"version-history":[{"count":0,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs\/3882\/revisions"}],"wp:attachment":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/media?parent=3882"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_category?post=3882"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_tag?post=3882"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}