{"id":3940,"date":"2026-05-18T11:36:32","date_gmt":"2026-05-18T09:36:32","guid":{"rendered":"http:\/\/tsholo"},"modified":"2026-05-18T11:36:32","modified_gmt":"2026-05-18T09:36:32","password":"","slug":"glossary-verification-and-compliance-terms","status":"publish","type":"docs","link":"https:\/\/j-cred.co.za\/zh\/helpcenter\/glossary-verification-and-compliance-terms\/","title":{"rendered":"Glossary: Verification and Compliance Terms"},"content":{"rendered":"

Purpose of this glossary<\/h2>\n

This glossary explains common verification, compliance, fraud prevention and evidence terms in plain language. It is written for public education and onboarding, not for legal interpretation.<\/p>\n

Verification terms<\/h2>\n
\n
Verification<\/strong><\/dt>\n
A process used to check whether supplied information is supported by a source, evidence or authorised process.<\/dd>\n
Match<\/strong><\/dt>\n
A result indicating that submitted information aligns with the reference data or matching rule used.<\/dd>\n
No match<\/strong><\/dt>\n
A result indicating that submitted information does not align with the reference data under the applicable matching rule.<\/dd>\n
Partial match<\/strong><\/dt>\n
A result where some fields align and others do not, usually requiring review.<\/dd>\n
Unable to verify<\/strong><\/dt>\n
A result indicating that the check could not be completed or did not return enough evidence to support a conclusion.<\/dd>\n
Evidence pack<\/strong><\/dt>\n
A structured set of request, source, result, document, timestamp, user and decision records supporting a verification process.<\/dd>\n<\/dl>\n

Compliance terms<\/h2>\n
\n
Purpose<\/strong><\/dt>\n
The reason personal information is collected, checked or processed.<\/dd>\n
Consent<\/strong><\/dt>\n
Permission from a person for a specific processing activity where consent is the appropriate basis.<\/dd>\n
Lawful basis<\/strong><\/dt>\n
The recognised legal or permitted ground relied on to process information.<\/dd>\n
Data minimisation<\/strong><\/dt>\n
Using only the personal information that is necessary for the defined purpose.<\/dd>\n
Audit trail<\/strong><\/dt>\n
A record of actions, users, dates, requests and results that shows what happened in a process.<\/dd>\n<\/dl>\n
\n

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’s own compliance review, regulator guidance, or contractual obligations.<\/p>","protected":false},"excerpt":{"rendered":"

Purpose of this glossary This glossary explains common verification, compliance, fraud prevention and evidence terms in plain language. It is written for public education and onboarding, not for legal interpretation. Verification terms Verification A process used to check whether supplied information is supported by a source, evidence or authorised process. Match A result indicating that submitted information aligns with the reference data or matching rule used. No match A result indicating that submitted information does not align with the reference data under the applicable matching rule. Partial match A result where some fields align and others do not, usually requiring review. Unable to verify A result indicating that the check could not be completed or did not return enough evidence to support a conclusion. Evidence pack A structured set of request, source, result, document, timestamp, user and decision records supporting a verification process. Compliance terms Purpose The reason personal information is collected, checked or processed. Consent Permission from a person for a specific processing activity where consent is the appropriate basis. Lawful basis The recognised legal or permitted ground relied on to process information. Data minimisation Using only the personal information that is necessary for the defined purpose. Audit trail A record of actions, users, dates, requests and results that shows what happened in a process. 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’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":[34],"doc_tag":[],"class_list":["post-3940","docs","type-docs","status-publish","hentry","doc_category-public-glossary"],"blocksy_meta":[],"year_month":"2026-06","word_count":242,"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":"Public Glossary","term_url":"https:\/\/j-cred.co.za\/zh\/docs-category\/public-glossary\/"}],"doc_tag_info":[],"_links":{"self":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs\/3940","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=3940"}],"version-history":[{"count":0,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/docs\/3940\/revisions"}],"wp:attachment":[{"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/media?parent=3940"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_category?post=3940"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/j-cred.co.za\/zh\/wp-json\/wp\/v2\/doc_tag?post=3940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}