{"id":3895,"date":"2026-05-18T11:36:27","date_gmt":"2026-05-18T09:36:27","guid":{"rendered":"http:\/\/tsholo"},"modified":"2026-05-18T11:36:27","modified_gmt":"2026-05-18T09:36:27","password":"","slug":"why-source-availability-and-turnaround-times-can-vary","status":"publish","type":"docs","link":"https:\/\/j-cred.co.za\/zh\/helpcenter\/why-source-availability-and-turnaround-times-can-vary\/","title":{"rendered":"Why Source Availability and Turnaround Times Can Vary"},"content":{"rendered":"<h2>Overview<\/h2>\n<p>Verification is dependent on source availability, channel performance, manual processing, data quality, integration rules, maintenance windows, regulatory limits and the completeness of the submitted request.<\/p>\n<h2>Why it matters<\/h2>\n<p>Clear expectations reduce frustration. Not every check that appears simple to the requester is simple at the source or legally available in real time.<\/p>\n<h2>How to think about it<\/h2>\n<ul>\n<li>Automated checks may fail if a source is unavailable or if input data is incomplete.<\/li>\n<li>Manual checks may require documents, fingerprints, payment confirmations, agency review or official processing.<\/li>\n<li>Batch checks may return dashboards and reports rather than individual instant responses.<\/li>\n<li>Some sources have scope limits: they verify only certain record types or dates.<\/li>\n<\/ul>\n<h2>Common examples<\/h2>\n<ul>\n<li>A certificate issued recently may not yet be available through a verification channel.<\/li>\n<li>A criminal record-related check may require official processing time.<\/li>\n<li>A company search may need disambiguation where many names are similar.<\/li>\n<li>A credit bureau result may depend on the bureau&#8217;s latest contributor updates.<\/li>\n<\/ul>\n<h2>Responsible use reminders<\/h2>\n<ul>\n<li>Publish realistic turnaround expectations.<\/li>\n<li>Use statuses such as submitted, pending, completed, failed, disputed and escalated.<\/li>\n<li>Do not blame the user before checking data quality and source status.<\/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 Verification is dependent on source availability, channel performance, manual processing, data quality, integration rules, maintenance windows, regulatory limits and the completeness of the submitted request. Why it matters Clear expectations reduce frustration. Not every check that appears simple to the requester is simple at the source or legally available in real time. How to think about it Automated checks may fail if a source is unavailable or if input data is incomplete. Manual checks may require documents, fingerprints, payment confirmations, agency review or official processing. Batch checks may return dashboards and reports rather than individual instant responses. Some sources have scope limits: they verify only certain record types or dates. Common examples A certificate issued recently may not yet be available through a verification channel. A criminal record-related check may require official processing time. A company search may need disambiguation where many names are similar. A credit bureau result may depend on the bureau&#8217;s latest contributor updates. Responsible use reminders Publish realistic turnaround expectations. Use statuses such as submitted, pending, completed, failed, disputed and escalated. Do not blame the user before checking data quality and source status. 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":[28],"doc_tag":[],"class_list":["post-3895","docs","type-docs","status-publish","hentry","doc_category-public-data-custodians-official-sources"],"blocksy_meta":[],"year_month":"2026-06","word_count":226,"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":"Data Custodians &amp; Official Sources","term_url":"https:\/\/j-cred.co.za\/zh\/docs-category\/public-data-custodians-official-sources\/"}],"doc_tag_info":[],"_links":{"self":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs\/3895","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=3895"}],"version-history":[{"count":0,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs\/3895\/revisions"}],"wp:attachment":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/media?parent=3895"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_category?post=3895"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_tag?post=3895"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}