{"id":3881,"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":"understanding-match-no-match-partial-match-and-unable-to-verify","status":"publish","type":"docs","link":"https:\/\/j-cred.co.za\/zh\/helpcenter\/understanding-match-no-match-partial-match-and-unable-to-verify\/","title":{"rendered":"Understanding Match, No Match, Partial Match and Unable to Verify"},"content":{"rendered":"<h2>Overview<\/h2>\n<p>Verification results are often misunderstood. A result is usually a comparison between supplied information and available source information. The outcome may be a clear match, a clear no match, a partial match, or an unable-to-verify outcome.<\/p>\n<h2>Why it matters<\/h2>\n<p>Decision-makers should avoid treating every non-match as fraud. Errors, old records, spelling differences, maiden names, data capture mistakes, timing delays and source availability can all affect the result.<\/p>\n<h2>How to think about it<\/h2>\n<ul>\n<li>A match means the supplied data aligns with the reference data used for that check.<\/li>\n<li>A no match means the supplied data does not align with the reference data under the matching rules applied.<\/li>\n<li>A partial match means some attributes align and others do not; this usually needs review.<\/li>\n<li>Unable to verify means the check could not be completed or the source did not return enough information to support a result.<\/li>\n<\/ul>\n<h2>Common examples<\/h2>\n<ul>\n<li>A person changed surname after marriage but the source still carries the previous name.<\/li>\n<li>A qualification was recently issued but not yet reflected in the relevant verification process.<\/li>\n<li>A document image is unreadable, causing data extraction errors.<\/li>\n<li>A source is temporarily unavailable or a manual turnaround is required.<\/li>\n<\/ul>\n<h2>Responsible use reminders<\/h2>\n<ul>\n<li>Do not make high-impact decisions on ambiguous results without a review step.<\/li>\n<li>Keep a record of the matching rule and the data submitted.<\/li>\n<li>Give affected people a reasonable opportunity to correct inaccurate information where required.<\/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 results are often misunderstood. A result is usually a comparison between supplied information and available source information. The outcome may be a clear match, a clear no match, a partial match, or an unable-to-verify outcome. Why it matters Decision-makers should avoid treating every non-match as fraud. Errors, old records, spelling differences, maiden names, data capture mistakes, timing delays and source availability can all affect the result. How to think about it A match means the supplied data aligns with the reference data used for that check. A no match means the supplied data does not align with the reference data under the matching rules applied. A partial match means some attributes align and others do not; this usually needs review. Unable to verify means the check could not be completed or the source did not return enough information to support a result. Common examples A person changed surname after marriage but the source still carries the previous name. A qualification was recently issued but not yet reflected in the relevant verification process. A document image is unreadable, causing data extraction errors. A source is temporarily unavailable or a manual turnaround is required. Responsible use reminders Do not make high-impact decisions on ambiguous results without a review step. Keep a record of the matching rule and the data submitted. Give affected people a reasonable opportunity to correct inaccurate information where required. 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-3881","docs","type-docs","status-publish","hentry","doc_category-public-verification-101"],"blocksy_meta":[],"year_month":"2026-06","word_count":270,"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\/3881","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=3881"}],"version-history":[{"count":0,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs\/3881\/revisions"}],"wp:attachment":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/media?parent=3881"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_category?post=3881"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_tag?post=3881"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}