tsholo
FAQ: What Information Should Support Requests Include?
Last Updated: 18 May 2026Answer A good support request includes enough information to reproduce, locate and understand the issue without exposing unnecessary personal data. Vague messages such as ‘it is not working’ slow down support and may require avoidable back-and-forth. Key points Include the search ID or request reference where available. Include the date, time, user email, client name and check type. Describe what you expected and what actually happened. Attach a screenshot only if it does not expose unnecessary personal information. What to do next Do not send full identity documents through ordinary support email unless requested through a secure channel. Mask sensitive fields where possible. Tell support whether the issue is urgent and why. Keep internal case references aligned to the platform reference. 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.
FAQ: Why Do Criminal Record Checks Need Fingerprints or Authorised Processes?
Last Updated: 18 May 2026Answer Criminal record-related checks are sensitive and may require official identity confirmation, fingerprints, authorised submission channels and formal processing. This is because the information can seriously affect a person’s rights, reputation and opportunities. Key points A police clearance process is not the same as a casual name search. Fingerprint or official process requirements help reduce mistaken identity risk. Turnaround may depend on official processing. Role relevance and lawful authority should be documented. What to do next Use the approved process for the required check. Obtain clear consent and role context where required. Store results securely and limit access. Escalate ambiguous outcomes for review. 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.
FAQ: How Do Organisations Avoid Over-Checking?
Last Updated: 18 May 2026Answer Organisations avoid over-checking by mapping each check to a specific decision, risk, law, contract or operational need. If a check does not answer a necessary question, it should not be included by default. Key points Use role-based or risk-based check bundles. Review whether each field collected is necessary. Apply deeper checks only where risk or value justifies it. Remove duplicated checks across departments. Monitor user behaviour to detect unnecessary searches. What to do next Create a verification matrix by use case. Get compliance approval for sensitive checks. Train users on permitted purposes. Review reports for unusual or excessive usage. 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.
Glossary: Verification and Compliance Terms
Last Updated: 18 May 2026Purpose 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.
Glossary: Data Sources and Custodians
Last Updated: 18 May 2026Purpose 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. Source and custodian terms Data custodian An organisation or authority responsible for maintaining a particular record set or source system. Source-connected verification Verification that checks information against a recognised source or authorised channel rather than relying only on a submitted document. Home Affairs The South African public authority associated with civic and identity records such as identity documents, births, deaths and related services. Credit bureau An organisation that maintains consumer or business credit information and provides reports under applicable credit-information rules. Umalusi The quality council responsible for specified general and further education and training qualifications and certificate verification functions. CIPC The Companies and Intellectual Property Commission, associated with company registration and enterprise information. SAQA The South African Qualifications Authority, associated with the National Qualifications Framework and foreign qualification evaluation. Record quality terms Stale data Information that may have been correct before but has not yet reflected a recent change. Contributor update A record update submitted by an organisation that contributes information to a bureau or shared database. Source correction A correction made by the custodian or contributor that owns the record. 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.
Glossary: Risk, Fraud and Evidence Terms
Last Updated: 18 May 2026Purpose 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. Risk and fraud terms Risk signal An indicator that may suggest higher risk and may require review, but is not proof of wrongdoing. False positive A result or signal that appears risky but is later found not to be a true problem. Identity fraud Misuse or misrepresentation of identity information to gain access, money, employment, services or other value. Synthetic identity An identity constructed from a mixture of real and false information. Ghost employee A person or record incorrectly receiving payroll or workforce benefits without legitimate employment status. Credential fraud Misrepresentation of qualifications, licences, memberships, work history or professional status. Evidence and decision terms Manual review Human assessment of an exception, conflict, partial result or high-risk case. Exception A case that does not follow the normal workflow and requires approval, escalation or review. Decision note A written explanation of how the verification result informed the final action taken. Dispute A challenge raised by a person or organisation about the accuracy or interpretation of a result. 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.
FAQ: Why Do Results Differ Between Sources?
Last Updated: 18 May 2026Answer Different sources may hold different data because they collect information for different purposes, update at different times, receive data from different contributors and apply different matching rules. A difference between sources should be reviewed before being treated as an error or fraud indicator. Key points One source may be more authoritative for a specific field than another. A source can be current for one attribute and incomplete for another. Timing delays can occur after a person changes details or after a contributor updates records. Matching rules affect whether a result appears as match, partial match or no match. What to do next Identify which source is authoritative for the disputed field. Review the original input data and supporting documents. Use the relevant dispute or correction process. Document the source used for any decision. 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.
FAQ: Can J-Cred Correct Government Records?
Last Updated: 18 May 2026Answer No platform should claim to correct government or custodian records unless it has the authority and process to do so. In most cases, the source custodian must correct its own records, while the platform can help identify the mismatch and route the user to the appropriate next step. Key points The platform can record the dispute or support ticket. The custodian normally controls changes to its own official record. Internal client data can sometimes be corrected separately from source data. A verified mismatch should be handled through an approved escalation path. What to do next Give the affected person clear information on which record appears inconsistent. Avoid exposing unnecessary personal details in support channels. Direct the person to the relevant custodian where the source record is the issue. Record follow-up evidence when the source correction is completed. 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.
FAQ: Does a Verification Equal Approval?
Last Updated: 18 May 2026Answer No. Verification provides evidence. Approval is a decision made by the organisation according to its policy, law, contract, risk appetite and human review process. A verification result can support approval, rejection, escalation or further evidence requests, but it is not the decision itself. Key points A match can confirm a fact but may not satisfy all policy requirements. A no match may require review rather than automatic rejection. A risk flag should be interpreted in context. The organisation remains responsible for its decision. What to do next Define decision rules separately from verification results. Create escalation paths for exceptions. Keep decision notes with the evidence pack. Explain adverse decisions in a fair and lawful way. 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.
FAQ: What If a Person Disputes a Result?
Last Updated: 18 May 2026Answer A disputed result should be logged, reviewed and routed to the correct correction path. The organisation should identify whether the issue is input error, source data, outdated information, matching logic, mistaken identity or a misunderstanding of what the result means. Key points Disputes are part of responsible data use. Do not delete the audit trail simply because a result is disputed. Some disputes can be fixed internally; others require the source custodian. High-impact decisions may need to be paused or qualified pending review. What to do next Capture the dispute details and supporting evidence. Check the original request data. Identify the source responsible for the disputed field. Communicate the next step and expected process clearly. 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.
FAQ: How Often Is Master Data Updated?
Last Updated: 18 May 2026Answer Master data update frequency depends on the source, contributor, bureau, custodian, integration, record type and update cycle. Some sources update frequently, others depend on official submissions, manual processing, batch schedules or event-based changes. Key points There is no single universal update frequency across all sources. A recently changed record may not appear immediately everywhere. Contributor-based data, such as some credit data, may depend on when contributors submit updates. Official custodian data may depend on the custodian’s own processing rules. What to do next Check the specific source or product documentation for the check being used. Use result dates and search IDs when asking support questions. Do not assume that stale-looking data is wrong without source review. Design operational processes with realistic update expectations. 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.
FAQ: What Is Needed to Verify a Qualification?
Last Updated: 18 May 2026Answer Qualification verification usually needs enough information to identify the person, qualification and issuing or quality-assurance context. This may include names, ID or passport number, certificate type, year, institution or assessment body, certificate number where available, and a copy of the certificate if required by the process. Key points Different qualification types have different verification sources. School certificates, NATED certificates, university degrees, foreign qualifications and professional designations may follow different routes. A clear certificate copy helps but does not replace source verification. Some checks require manual turnaround. What to do next Identify the qualification type before choosing a verification route. Capture the certificate details accurately. Use the correct source or verification agency path. Keep the applicant informed where the process is not instant. 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.
FAQ: Why Is Consent Requested?
Last Updated: 18 May 2026Answer Consent is requested where the verification process requires the person’s permission or where transparency and fair processing require the person to understand what will be checked and why. Consent also creates evidence that the person was informed of the purpose and scope of the check. Key points Consent should be specific enough to understand. Consent should be linked to the purpose and the check type. Consent is not a licence to use the data for unrelated purposes. Some checks may rely on other lawful bases, but transparency and purpose still matter. What to do next Read consent wording before accepting it. Store consent records with the verification request. Refresh consent if the purpose changes materially. Provide a contact route for questions or withdrawal where applicable. 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.
FAQ: Can Mobile or Dynamic IP Users Access the Platform?
Last Updated: 18 May 2026Answer Yes, a public-facing platform can support users on mobile or dynamic networks when access control is designed at the application and identity layer. Instead of blocking the whole environment behind one infrastructure IP allowlist, the application can apply client-specific access policies using user, client, role, IP range, MFA, device trust and exception rules. Key points Some clients require fixed-IP access policies. Other users legitimately work from mobile, 3G, LTE, fibre or changing networks. Application-level policy can apply different rules to different clients. Infrastructure controls such as WAF and access restrictions remain useful for broad perimeter protection. What to do next Define the client’s access policy during onboarding. Use MFA and role-based access for higher-risk users. Log source IP and session context. Create approved exception workflows for users who cannot operate from fixed IPs. Important: This is a design principle; implementation should be confirmed with the platform security team. 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.
Higher Education and Student Funding Verification 101
Last Updated: 18 May 2026Overview Higher education and student funding environments often need to verify identity, enrolment, qualifications, household or sponsor details, contactability, banking information, institution records and programme eligibility. Why it matters Funding and support programmes are vulnerable to duplication, incorrect records, ineligible claims, delayed confirmations and poor evidence management. Verification can improve speed and accountability when designed around the student journey. How to think about it Map the student lifecycle: application, eligibility, onboarding, disbursement, attendance, completion and audit. Verify only what is needed at each stage. Connect evidence to the programme rule being tested. Use dashboards for exceptions, duplicates and unresolved cases. Preserve dignity and access while resolving mismatches. Common examples Confirming identity before bursary or stipend processing. Checking qualification or enrolment status where relevant. Flagging duplicate beneficiaries across programmes. Creating evidence packs for funder reporting. Responsible use reminders Do not allow verification delays to become silent exclusion. Do not over-collect information from students without clear purpose. Use exception support for people with legitimate data anomalies. 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.
SETA and Skills Programme Evidence 101
Last Updated: 18 May 2026Overview SETA and skills programme environments require credible evidence of learners, employers, training participation, attendance, completion, qualifications, stipends, workplace placement and outcome reporting. Why it matters Programme value is often lost when evidence is scattered across spreadsheets, emails, attendance registers and manual files. Verification and evidence packs help make programme outcomes auditable and easier to trust. How to think about it Define evidence requirements before programme launch. Verify learner and employer identities where appropriate. Connect attendance, assessment, completion and placement evidence to each learner. Use dashboards to show active, inactive, completed and at-risk participants. Keep funder reporting aligned to evidence rather than narrative only. Common examples Learner identity verification at onboarding. Employer or host-company verification before placement. Attendance and engagement tracking for stipend governance. Completion evidence linked to qualification or certificate records. Responsible use reminders Do not create evidence only at close-out; capture it during delivery. Do not confuse activity counts with verified outcomes. Protect learner information throughout the programme. 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.
Recruitment and Employee Screening 101
Last Updated: 18 May 2026Overview Recruitment and employee screening checks whether candidate claims and role-critical risk indicators are supported by appropriate evidence. It may include identity, qualifications, employment history, professional registrations, criminal record-related checks, credit-related checks for specific roles and reference checks. Why it matters Screening should protect the employer, clients and public while treating candidates fairly. A good screening process is role-relevant, consent-based where required, transparent and auditable. How to think about it Define checks by role risk, not by habit. Use candidate consent and clear notices where required. Verify the claims that matter to the role. Escalate inconsistencies before making final adverse decisions. Keep results confidential and access controlled. Common examples Qualification verification for a technical position. Professional registration confirmation for a regulated role. Criminal record-related process for a high-trust position where lawful and relevant. Credit information only where role relevance and legal basis are clear. Responsible use reminders Do not over-screen junior or low-risk roles unnecessarily. Do not use irrelevant checks to exclude people unfairly. Document the reason for every screening category. 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.
Legal and Financial Services Verification 101
Last Updated: 18 May 2026Overview Legal and financial services organisations often require identity verification, customer due diligence, beneficial ownership awareness, sanctions screening, source-of-funds context, credit information, fraud indicators and recordkeeping. Why it matters These sectors face regulatory, reputational and financial crime risk. Verification supports trust, but it must sit inside a broader compliance and risk-management framework. How to think about it Know whether the client is an individual, company, trust or other entity. Identify beneficial owners and authorised representatives where required. Use risk-based customer due diligence rather than a one-size-fits-all approach. Keep evidence of checks and approvals. Monitor for changes or suspicious indicators during the relationship. Common examples Identity verification for a new client. Company and director verification for a business account. Sanctions or adverse media screening for higher-risk relationships. Credit or affordability checks in appropriate credit contexts. Responsible use reminders Do not treat onboarding as the only compliance event. Do not ignore ongoing monitoring obligations. Escalate suspicious activity through internal compliance channels. 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.
Insurance Claims and Fraud Screening 101
Last Updated: 18 May 2026Overview Insurance verification supports underwriting, claims validation, identity confirmation, vehicle or asset checks, policyholder contactability, death or beneficiary checks and fraud-risk review. Why it matters Fraudulent or exaggerated claims raise costs for insurers and policyholders. At the same time, valid claims should not be delayed by unnecessary or unclear verification steps. How to think about it Match the check to the claim type and risk level. Use identity and beneficiary verification where claim proceeds are being paid. Verify vehicle, asset or incident details through appropriate sources where relevant. Keep claim evidence and decision notes together. Use manual review for conflicting results. Common examples Confirming the identity of a claimant. Checking vehicle details for a motor claim. Reviewing deceased-status evidence for a life policy claim. Flagging repeated contact or bank-detail patterns across unrelated claims. Responsible use reminders Do not use verification to delay legitimate claims unfairly. Do not expose claim details beyond authorised claim handlers. Keep fraud suspicion separate from confirmed fraud. 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.
Debt Collection and Tracing 101
Last Updated: 18 May 2026Overview Debt collection and tracing use contactability, identity, credit and account information to support lawful engagement with debtors and improve recovery outcomes. Why it matters Good tracing should improve fairness and efficiency. It should help organisations contact the right person, understand ability to pay, route disputes and avoid costly action where recovery is unlikely. How to think about it Verify that the debt, account and person are correctly linked. Use trace results to improve contact strategy, not to harass. Segment accounts by value, age, dispute status, contactability and propensity. Keep collection evidence and communication logs. Respect applicable debt-collection and consumer-protection rules. Common examples Locating updated contact details for an account holder. Removing deceased or disputed accounts from normal collection queues. Identifying accounts suitable for payment arrangements. Escalating high-value, contactable, non-paying accounts through legal review. Responsible use reminders Do not contact third parties inappropriately. Do not ignore vulnerability or affordability indicators. Do not lose the audit trail between trace data and collection action. 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.
Procurement and Beneficial Ownership Awareness
Last Updated: 18 May 2026Overview Procurement verification helps organisations know who they are buying from, who controls or represents a supplier, whether company details are consistent and whether conflict, duplication or misrepresentation risks need review. Why it matters Beneficial ownership awareness matters because the visible supplier name may not show who ultimately controls or benefits from the entity. This is important for fraud prevention, conflicts of interest and public-sector governance. How to think about it Verify the legal entity and registration number. Review directors, representatives and authority to act. Compare supplier details to procurement records, bank confirmations and tax documents where relevant. Look for related-party or duplicate-bidder indicators. Keep evidence for audit and bid review. Common examples Two bidders share directors, addresses or contact numbers. A supplier changes bank details before payment. An entity is recently registered but claims long trading history. A representative cannot show authority to act for the company. Responsible use reminders Do not equate verification with automatic disqualification. Use conflict review and procurement rules before acting. Protect director and ownership data from unnecessary exposure. 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.
NPO, CSI and Programme Beneficiary Verification
Last Updated: 18 May 2026Overview NPO, CSI and programme beneficiary verification helps funders and implementing partners confirm who is being supported, whether eligibility rules are met, whether duplication exists and whether evidence is strong enough for impact reporting. Why it matters Programme trust depends on credible evidence. Donors, boards and public partners need to know that funds reached the intended people or communities without creating unnecessary barriers for vulnerable participants. How to think about it Define eligibility criteria clearly before collecting information. Verify identity and participation only to the extent needed. Capture attendance, delivery, outcomes and follow-up evidence during the programme. Use dashboards to show progress, exceptions and evidence gaps. Use sensitive escalation pathways for vulnerable beneficiaries. Common examples Avoiding duplicate beneficiary claims across sites. Confirming youth or student participation in a funded programme. Supporting stipend payment controls. Creating impact evidence packs for donors. Responsible use reminders Do not overburden vulnerable people with excessive documentation. Do not use verification as a barrier where support and correction are possible. Protect beneficiary dignity in reporting. 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.
FAQ: Why Did an ID Check Fail?
Last Updated: 18 May 2026Answer An ID check can fail for several reasons. It may be a true mismatch, but it may also be caused by spelling differences, old names, recently changed personal details, incorrect data capture, incomplete input, a source issue, a deceased-status conflict, or a record that needs correction at the custodian. Key points A failed result does not automatically prove fraud. Check the exact fields submitted, including names, ID number and date of birth. Ask whether the person recently changed name, document type or civic details. Escalate sensitive conflicts for review. What to do next Correct obvious input errors and retry where permitted. Request supporting documents through secure channels if needed. Where the source record appears wrong, advise the person to approach the relevant custodian or authority. Record the outcome and any manual decision. Important: Never publish or send full identity numbers through unsecured support messages. 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.
Why One Check Is Not Always Enough
Last Updated: 18 May 2026Overview One check answers one question. Strong risk management often requires a layered view: identity, contactability, source authenticity, financial risk, role relevance, behaviour, document evidence and manual review may each answer different questions. Why it matters Fraud often exploits gaps between systems. A person may pass one check but fail another. A company may exist but still be risky. A document may look valid but not be source-confirmed. How to think about it Use the least intrusive set of checks that reasonably addresses the risk. Layer checks according to transaction value and sensitivity. Use risk scoring or routing to avoid unnecessary checks on low-risk cases. Combine automated screening with human review for exceptions. Review outcomes to improve the check design. Common examples Identity match plus qualification verification for a regulated role. Company registration plus director and bank-account review for supplier onboarding. Credit information plus affordability context for credit decisions. Contactability plus propensity indicators for collections prioritisation. Responsible use reminders Layering should be proportionate, not excessive. Do not use unrelated checks simply because they are available. Document why each check is part of the 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.
Credit Bureau Report 101
Last Updated: 18 May 2026Overview A credit bureau report is a structured view of consumer or business credit-related information held by a bureau. It may include identifying information, account history, payment behaviour, adverse information, enquiries, judgments or other data depending on the report type and applicable rules. Why it matters Credit bureau information helps with credit risk, affordability context, collections, tracing and fraud prevention, but it must be used only for authorised and documented purposes. How to think about it Know which report type you are requesting and why. Check whether the requester has the correct permission or purpose. Interpret scores and profiles together rather than relying on one number. Treat outdated, disputed or partial information carefully. Record the search reference and decision context. Common examples Assessing a credit application. Reviewing collections strategy for an existing account. Finding updated contact indicators for a debtor. Checking possible identity inconsistencies. Responsible use reminders Do not share reports with unauthorised parties. Do not use bureau information for informal curiosity checks. Support consumer dispute rights where information appears incorrect. 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.
Credit Score vs Credit Profile
Last Updated: 18 May 2026Overview A credit score is a summary indicator produced by a scoring model. A credit profile is the underlying body of credit information, behaviour and records that may explain risk more fully than the score alone. Why it matters Decision-makers sometimes over-rely on the score because it is simple. The profile can reveal context: thin-file consumers, disputed records, recent distress, improved behaviour, fraud warnings or data quality issues. How to think about it Use the score as one input, not the whole decision. Review account-level behaviour where the decision is significant. Consider affordability and policy rules separately from the bureau score. Watch for thin files, stale records or disputed data. Keep reasons for adverse decisions explainable. Common examples A low score caused by old adverse data may need policy review. A high score does not prove income or affordability. A thin file may lack enough history for confident scoring. Recent enquiries may indicate credit-seeking behaviour but need context. Responsible use reminders Do not present scores as moral judgments. Do not confuse credit risk with character. Do not ignore dispute and correction mechanisms. 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.
Consumer Trace and Contact Data 101
Last Updated: 18 May 2026Overview Consumer trace and contact data helps an authorised organisation find or update contactability information for a person connected to a lawful account, debt, service, fraud investigation or administrative process. Why it matters Trace data can improve engagement and reduce waste, but it must not become intrusive surveillance. The purpose, contact rules and privacy obligations must be clear. How to think about it Use trace data only for the account, case or lawful purpose involved. Prioritise verified or higher-confidence contact channels. Record contact outcomes to improve future segmentation. Respect opt-outs, disputes and communication rules where applicable. Avoid excessive contact attempts. Common examples Updating contact details for a municipal account holder. Locating a debtor for lawful collections communication. Finding alternative contactability indicators after returned mail. Separating untraceable accounts from those with viable engagement paths. Responsible use reminders Do not use trace data to contact unrelated relatives or employers inappropriately. Do not publish or export trace information unnecessarily. Keep contact strategies fair and respectful. 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.
Affordability, Income Estimation and Propensity Concepts
Last Updated: 18 May 2026Overview Affordability, income estimation and propensity concepts help organisations understand whether a person or account may be able to pay, how to segment engagement and which strategy may be most appropriate. Why it matters These concepts are useful for credit, collections and public-sector revenue work, but they are estimates or indicators. They should not be treated as exact facts about a person’s income or willingness. How to think about it Affordability looks at ability to pay in relation to obligations and income indicators. Income estimation uses available data signals to approximate income bands or earning likelihood. Propensity to pay estimates the likelihood of payment or engagement under certain conditions. Segmentation helps choose different actions for different risk and ability groups. Human review remains important for exceptions and vulnerability. Common examples Prioritising high-value accounts with good contactability and higher payment propensity. Separating indigent or vulnerable households from strategic non-payers in municipal contexts. Designing payment arrangements that reflect likely affordability. Identifying accounts that need data correction before collection. Responsible use reminders Do not treat estimates as guaranteed income facts. Do not use propensity to justify unfair treatment. Build appeal or review channels for affected consumers. 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.
Disputes and Corrections in Credit Information
Last Updated: 18 May 2026Overview Credit information can be disputed when a consumer believes information is inaccurate, outdated, incomplete or incorrectly linked. Corrections may need to happen through the relevant bureau, credit provider or source that contributed the record. Why it matters Dispute processes protect consumers and improve data quality. Ignoring disputes can lead to poor decisions, complaints and regulatory exposure. How to think about it Record the disputed item clearly. Identify the source or contributor responsible for the information. Pause or qualify decisions where the disputed information is material. Keep communication clear and documented. Update internal records when the bureau or source confirms a correction. Common examples An account appears as unpaid after settlement. A record belongs to a different person with similar details. A judgment or adverse listing is outdated. A contact detail is incorrectly linked to the consumer. Responsible use reminders Do not dismiss consumers without checking the disputed record. Do not try to correct bureau data only inside your internal system if the source remains wrong. Maintain evidence of the dispute and outcome. 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.
Credit Data for Collections and Debtors Books
Last Updated: 18 May 2026Overview Credit and trace data can help organisations understand a debtors book more clearly. Rather than treating every account the same, the book can be segmented by contactability, risk, affordability indicators, account age, balance, dispute status and likely recovery path. Why it matters Better segmentation can improve collections performance while reducing unnecessary pressure on vulnerable or uncontactable accounts. It also gives management a clearer view of recoverable value versus administratively difficult or toxic debt. How to think about it Clean the debtors book before enrichment. Enrich with only necessary fields. Create dashboards that separate operational, risk and compliance views. Use evidence packs for high-value or disputed accounts. Update strategies as new contact or payment outcomes come in. Common examples High-balance, contactable accounts with higher payment propensity. Accounts linked to deceased indicators requiring sensitive handling. Accounts with property or address mismatches requiring data correction. Low-value or older accounts that may not justify expensive action. Responsible use reminders Do not use bureau data outside the permitted collections purpose. Do not automate harsh action without governance review. Track outcomes to prove value and responsible treatment. 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.
Responsible Use in Public Sector Revenue Recovery
Last Updated: 18 May 2026Overview Public-sector revenue recovery uses data and evidence to improve collection of lawful debts such as municipal accounts while preserving fairness, administrative justice and public trust. Why it matters The goal should not only be to collect more, but to understand the debtors book better: who can be contacted, who may be vulnerable, where records are wrong, where legal escalation is justified and where policy interventions are needed. How to think about it Separate indigent, vulnerable, disputed, deceased, untraceable, high-propensity and strategic non-payment segments. Use trace and affordability indicators to guide engagement strategy. Create management dashboards that show value, risk, action and evidence. Keep councillor, finance, legal and customer-care needs distinct. Document the purpose and governance of all enrichment. Common examples Identifying accounts with valid contact details but no recent engagement. Producing ward-level or portfolio-level views without exposing unnecessary personal information. Routing disputes to customer care before enforcement. Prioritising high-yield, compliant collection actions. Responsible use reminders Do not create public shaming lists. Do not ignore vulnerable-consumer policies. Make reports explainable enough for CFO, revenue, legal and oversight users. 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.
Municipal Verification and Revenue Intelligence 101
Last Updated: 18 May 2026Overview Municipal verification and revenue intelligence uses data enrichment, trace, affordability, contactability and evidence reporting to help municipalities understand their debtor records, supplier risks, employee records and service-delivery data more clearly. Why it matters Many municipal problems are hidden in plain sight: duplicate records, wrong addresses, poor contactability, deceased account holders, inactive collection segments, supplier inconsistencies and debt books that are not segmented for action. How to think about it Ingest structured records such as debtors books, supplier lists or employee records. Clean and standardise the data before enrichment. Run appropriate verification and risk checks according to purpose. Produce dashboards and evidence packs for management and audit. Translate findings into practical action lists. Common examples Debtor-book contactability and propensity segmentation. Supplier verification and director-risk awareness. Employee identity and payroll integrity checks. Ward or portfolio dashboards that show operational bottlenecks. Responsible use reminders Do not centralise more personal data than is necessary. Use role-based reporting for finance, legal, customer care and executive oversight. Build correction workflows for bad municipal master data. 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.
Retention, Access and Correction of Personal Information
Last Updated: 18 May 2026Overview Retention, access and correction controls answer three practical questions: how long information is kept, who may see it, and how inaccurate or outdated information can be challenged or corrected. Why it matters Verification records should remain available long enough to support audits, disputes, contractual obligations and operational needs, but not forever by default. Access should be limited, and correction should be routed to the correct source or internal process. How to think about it Set retention periods by record type and purpose. Use role-based access controls and audit logs. Separate source correction from platform correction: some records can only be amended by the data custodian. Record disputes, evidence supplied and outcome decisions. Do not silently overwrite disputed results without a trace. Common examples A user can view a recent report but older reports may require re-running or authorised retrieval. A disputed identity result may require the person to approach the relevant civic authority. An incorrect internal reference can be corrected in the client’s own case record. A credit bureau dispute follows bureau and regulatory dispute channels. Responsible use reminders Do not keep high-risk personal data indefinitely without a reason. Do not give broad access to everyone in an organisation. Explain correction pathways clearly to users and affected people. 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.
Working with Special Personal Information
Last Updated: 18 May 2026Overview Special personal information is information that requires heightened care. In verification contexts this may include criminal behaviour information, biometric information, health information, children’s information and other sensitive categories depending on the use case. Why it matters Special personal information can create significant harm if misused or leaked. It should be requested only when clearly necessary, legally permitted and protected by stronger controls. How to think about it Confirm that the check is necessary for the role, service, law or risk being managed. Use explicit workflows and stronger approvals for sensitive checks. Limit who can view the result and for how long. Use secure capture methods for biometrics or fingerprints where applicable. Provide dispute or escalation channels for affected people. Common examples Fingerprint-based police clearance processes. Biometric liveness checks during high-risk onboarding. Checks involving children or vulnerable beneficiaries. Health-related information used only where the programme or service lawfully requires it. Responsible use reminders Do not request sensitive checks simply to appear thorough. Do not send biometric, criminal or health information through informal channels. Train users before giving access to sensitive search types. 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.
Public Sector Responsible Use of Verification Data
Last Updated: 18 May 2026Overview Public-sector verification supports service delivery, revenue management, eligibility assessment, programme oversight, fraud prevention, procurement governance and audit readiness. Because public bodies serve citizens, responsible use and public trust are essential. Why it matters The public sector must balance efficiency with fairness, transparency and accountability. A verification result should help clarify a case, not become an unexplained black-box decision. How to think about it Connect every verification to a mandate, programme, debt, service, procurement process or lawful administrative purpose. Use evidence packs to support audit and oversight. Avoid unnecessary centralisation of sensitive information where local authority or programme context is needed. Design review steps for adverse or ambiguous outcomes. Communicate what information is required and why. Common examples Municipal debtor data enrichment for revenue recovery and contactability. SETA learner or employer verification for programme evidence. Supplier due diligence for procurement integrity. Beneficiary verification for grant, bursary or development programme administration. Responsible use reminders Do not use verification to create hidden exclusion lists. Do not share results outside authorised officials and service providers. Keep decision-making human-readable and auditable. 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.
Fraud Prevention 101
Last Updated: 18 May 2026Overview Fraud prevention is the disciplined use of controls, verification, monitoring, evidence and review to reduce deception, misrepresentation, false documentation, identity abuse, account manipulation and financial loss. Why it matters Fraud prevention works best when it is built into normal processes instead of being treated as an emergency response after money, access or benefits have already been released. How to think about it Identify the point where value is being released: money, credit, employment, access, benefits, contracts or data. Place the right verification controls before that point. Use risk signals to route cases, not to make unfair assumptions. Review exceptions and overrides. Learn from confirmed fraud cases to improve controls. Common examples Checking identity before creating a high-value account. Verifying qualifications before appointment. Screening suppliers before purchase orders are issued. Monitoring debtor-book changes for unusual patterns. Flagging repeated use of the same contact details across unrelated identities. Responsible use reminders Do not over-check low-risk interactions unnecessarily. Do not accuse people based on a weak signal. Document confirmed fraud separately from suspicion or risk flags. 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.
Identity Fraud Warning Signs
Last Updated: 18 May 2026Overview Identity fraud warning signs are indicators that the person, document, contact details or behavioural pattern may not align with a genuine identity. A warning sign is not proof of fraud; it is a reason to review. Why it matters Identity fraud can lead to credit losses, false employment, duplicate beneficiaries, fraudulent SIM or account use, fake suppliers, ghost employees and reputational damage. How to think about it Check whether names, ID number, date of birth and document details align. Watch for recently changed contact details used across unrelated records. Look for inconsistencies between document image, source data and behaviour. Use step-up checks where risk is high. Record the reason for escalation. Common examples ID number and date of birth do not align. Multiple people use the same phone number, email or bank account in suspicious contexts. A document image appears altered or inconsistent. A person cannot provide basic supporting evidence for the claimed identity. The record appears linked to a deceased-status conflict. Responsible use reminders False positives happen; review before acting. Avoid discriminatory assumptions based on name, location or appearance. Protect the person’s data even when fraud is suspected. 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.
Synthetic Identity and False Documentation 101
Last Updated: 18 May 2026Overview Synthetic identity fraud usually involves combining real and false information to create an identity that appears plausible. False documentation involves documents that are forged, altered, expired, misused or not issued by the claimed authority. Why it matters These risks are difficult because individual fields may look correct while the overall identity story is false. Strong verification uses multiple signals rather than relying on a single document or field. How to think about it Validate identity structure and source records where possible. Check document authenticity indicators and data consistency. Compare contact, address, device, bureau and behavioural signals where permitted. Use manual review for high-value or high-risk cases. Keep evidence of the inconsistency and the review decision. Common examples A real ID number is paired with a different person’s name or photo. A certificate copy appears genuine but is not supported by source verification. A company document is old while the registry status has changed. Contact details are reused across many unrelated applications. Responsible use reminders Do not publish fraud patterns that teach people how to bypass controls. Do not rely only on visual inspection. Use proportionate checks based on the risk of the transaction. 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.
Ghost Employees and Payroll Integrity 101
Last Updated: 18 May 2026Overview A ghost employee is a person recorded on a payroll or workforce system who should not be receiving payment. This may involve fictitious employees, terminated employees, duplicated identities, unauthorised bank-detail changes or collusion. Why it matters Payroll fraud directly affects organisational finances and can continue for long periods if HR, payroll, access control and bank-payment records are not reconciled. How to think about it Compare payroll records to HR master data, identity records, employment contracts and termination records. Check duplicate identity numbers, bank accounts, phone numbers or addresses where lawful. Review dormant employees with active payments. Monitor changes to bank details and approvals. Use evidence packs for audit and disciplinary processes. Common examples A terminated employee remains active on payroll. Two employee records share the same bank account unexpectedly. A person appears on payroll but has no access-control, attendance or manager confirmation. Bank details are changed shortly before payment without proper approval. Responsible use reminders Handle employee investigations confidentially. Separate anomaly detection from proven misconduct. Use HR, payroll and audit teams together rather than a single-person review. 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.
Debtor Tracing and Contactability 101
Last Updated: 18 May 2026Overview Debtor tracing and contactability work aims to improve the quality of contact, location and engagement information for people or entities with outstanding accounts, while respecting lawful collection, privacy and fairness requirements. Why it matters Poor debtor information weakens collections, increases write-offs, wastes call-centre effort and hides recoverable value. Better data helps segment accounts, prioritise engagement and avoid unnecessary escalation. How to think about it Start with clean debtor-book data: account number, ID or registration number, address, contact details and balance. Enrich only the fields needed for lawful account management. Segment by contactability, affordability indicators, risk, age of debt and service history. Use dashboards to identify hidden patterns in the book. Keep evidence of purpose and data source. Common examples Finding accounts with valid contact numbers but no recent engagement. Separating deceased, untraceable, high-propensity and disputed accounts. Flagging duplicate accounts linked to the same person or property. Estimating the difference between recoverable and toxic debt. Responsible use reminders Do not harass consumers or bypass debt-collection rules. Do not expose debtor details to unauthorised staff. Treat tracing as a governance and engagement process, not only as a search. 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.
Supplier and Vendor Risk 101
Last Updated: 18 May 2026Overview Supplier and vendor risk refers to the possibility that a supplier may be misrepresented, conflicted, non-compliant, financially unstable, fraudulent, sanctioned, linked to related-party risks or unable to deliver. Why it matters Supplier risk can affect procurement value, service continuity, public trust, audit outcomes and legal exposure. Verification provides structured evidence before onboarding and during ongoing monitoring. How to think about it Verify company existence and registration details. Check directors, representatives and authority to act where appropriate. Confirm bank, tax, address and contact details through approved channels where required. Screen conflicts of interest and related parties in public-sector contexts. Monitor changes during the supplier lifecycle. Common examples A supplier name differs from the registered entity name. A director appears linked to multiple bidders in the same process. Bank details change just before payment. A company is newly registered but claims long operational history. A supplier uses unverifiable contact details. Responsible use reminders Do not treat registration as proof of capability. Do not rely only on submitted documents. Keep procurement evidence packs complete and reviewable. 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.
Credential Fraud in Recruitment 101
Last Updated: 18 May 2026Overview Credential fraud occurs when a person misrepresents qualifications, licences, professional memberships, work history, references or experience. It can range from exaggeration to forged certificates and fabricated institutions. Why it matters Recruitment decisions create risk for employers, customers, learners, patients, communities and public funds. Verification helps ensure that claims relevant to the role are supported by source evidence. How to think about it Decide which credentials are essential for the role. Verify qualifications, professional memberships or licences through the relevant source. Check employment history and references using controlled processes. Escalate inconsistencies for candidate explanation. Keep the process fair and role-relevant. Common examples A qualification is claimed but not supported by the source. An institution name is similar to a recognised institution but is not the same. A professional designation has expired or was never held. Employment dates conflict with references or payroll records. Responsible use reminders Do not verify unnecessary personal history unrelated to the role. Do not reject a candidate on an ambiguous result without review. Make consent language clear and specific. 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.
Umalusi Qualification Verification 101
Last Updated: 18 May 2026Overview Umalusi is the quality council responsible for standards in general and further education and training in South Africa. Qualification verification in this context is used to establish the authenticity of specified qualifications or certificates. Why it matters Qualification fraud can affect recruitment, admissions, professional eligibility, supplier vetting and public-sector appointment processes. Verification helps organisations avoid relying only on copies of certificates or statements of results. How to think about it Umalusi-related verification focuses on specified certificates and qualifications under its mandate. Umalusi’s public FAQ states that individuals do not apply directly to Umalusi for ordinary verification services; they should use a verification agency. Umalusi’s public FAQ indicates that N4-N6 certificates must be verified by the Department of Higher Education and Training. Older certificates and foreign qualifications may require different channels. Common examples Verifying a National Senior Certificate for recruitment. Checking whether a certificate copy aligns with recognised qualification records. Routing foreign qualification questions to SAQA rather than treating them as local school certificates. Identifying when a certificate type falls outside a specific source’s verification scope. Responsible use reminders Do not treat an uploaded certificate as verified until the relevant verification process has confirmed it. Do not assume one education source verifies every qualification type. Keep the applicant informed where manual turnaround is required. Public reference points Umalusi public Certification & Verification FAQ and service information. 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.
SAQA and Foreign Qualification Evaluation 101
Last Updated: 18 May 2026Overview The South African Qualifications Authority, commonly referred to as SAQA, is associated with the National Qualifications Framework and the evaluation of foreign qualifications for South African equivalence. Why it matters Foreign qualification questions are often different from local certificate authenticity checks. A foreign qualification may need evaluation for comparability, while a local certificate may need verification against the issuing or quality-assurance body’s records. How to think about it Ask whether the issue is authenticity, local equivalence, admission, employment eligibility or professional registration. Foreign qualification evaluation is not the same as verifying a South African matric certificate. Professional bodies may have additional designation or membership requirements. Some education records require the institution, assessment body or quality council rather than a single universal source. Common examples A foreign degree submitted for employment may need SAQA evaluation. A South African school certificate may need Umalusi-related verification. A professional designation may need confirmation with the relevant professional body. A skills programme certificate may need source-specific evidence. Responsible use reminders Do not collapse all education checks into one process. Record the qualification type, country, institution and purpose before choosing the route. For high-impact decisions, allow applicants to supply additional evidence or official evaluation documents. Public reference points SAQA public information on the National Qualifications Framework and foreign qualification evaluation. 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.
SAPS Criminal Record and Police Clearance Concepts
Last Updated: 18 May 2026Overview Criminal record and police clearance-related processes are sensitive and often require authorised channels, fingerprints, identity information and specific procedural requirements. They should not be treated as ordinary database lookups. Why it matters Criminal history information can affect employment, licensing, volunteering, travel, trust positions and public safety decisions. Because of the potential impact, organisations must use appropriate authority, consent, purpose and secure handling. How to think about it A police clearance certificate process is different from a general background screening statement. Fingerprint capture or authorised submission may be required for certain official processes. Results can take time because they may depend on official processing. A result should be interpreted in line with the role, legal requirements and fairness principles. Common examples Screening for roles involving vulnerable people or high-trust access. Supporting travel, immigration or permit applications where a police clearance certificate is required. Checking whether a candidate must provide additional official evidence. Escalating inconclusive results for authorised follow-up. Responsible use reminders Do not request criminal record-related information without a lawful and role-relevant reason. Do not store sensitive results in unsecured shared drives or emails. Do not automatically reject a person without applying the correct legal, fairness and relevance tests. Public reference points SAPS public service information on applying for police clearance certificates. 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.
CIPC Company and Director Information 101
Last Updated: 18 May 2026Overview CIPC is the Companies and Intellectual Property Commission. Company verification may involve checking registration status, company name, registration number, director information, enterprise history and other public or authorised registry details. Why it matters Company and director checks help organisations reduce supplier fraud, identify shell entities, support due diligence, verify trading counterparties and improve procurement governance. How to think about it Start with the registration number wherever possible, because company names can be similar or changed. Separate company existence from operational legitimacy: a registered entity can still present other risks. Director information should be handled responsibly and used only for the due diligence purpose. Procurement decisions may require additional checks such as tax, banking, sanctions, beneficial ownership awareness or conflict-of-interest review. Common examples Checking that a supplier exists before onboarding. Comparing invoice details to registered enterprise details. Flagging recently registered or dormant-looking entities for review. Supporting public-sector procurement evidence packs. Responsible use reminders Do not assume that registration equals endorsement or financial strength. Maintain an audit trail for supplier due diligence. Review changes in directors, addresses or status as part of ongoing monitoring where appropriate. Public reference points CIPC public information and business registry services. 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.
Credit Bureaus as Data Custodians
Last Updated: 18 May 2026Overview Credit bureaus collect, maintain and report consumer and business credit information within the rules that apply to credit information, consumer rights, disputes and correction processes. Why it matters Credit information is powerful because it can inform affordability, collection strategy, traceability, credit risk, fraud indicators and account management. It is also highly regulated because misuse can harm consumers. How to think about it Use credit information only where the purpose is permitted and documented. Distinguish credit score, credit profile, account behaviour, adverse information, contact information and trace indicators. Give consumers appropriate dispute and correction pathways where information appears incorrect. Keep access limited to authorised users who understand the rules. Common examples Assessing credit-related risk before entering into a credit agreement. Supporting responsible collections on a debtors book. Checking contactability indicators for lawful tracing. Detecting inconsistent identity or account information. Responsible use reminders Do not use credit data for curiosity, informal profiling or unrelated decisions. Do not share bureau results outside the permitted user group. Keep bureau access logs and purpose references. 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.
Why Source Availability and Turnaround Times Can Vary
Last Updated: 18 May 2026Overview 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’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’s own compliance review, regulator guidance, or contractual obligations.
POPIA 101 for Verification Users
Last Updated: 18 May 2026Overview POPIA is South Africa’s Protection of Personal Information Act. For verification users, the practical message is simple: personal information must be processed lawfully, reasonably, securely, for a defined purpose and with appropriate respect for the person whose information is being processed. Why it matters Verification work often involves identity numbers, contact details, employment, education, credit, criminal history, biometric or financial indicators. These can be sensitive and should be protected by design rather than after a problem occurs. How to think about it Define the purpose before collecting or checking data. Collect only what is necessary for that purpose. Make sure there is a lawful basis, such as consent, legal obligation, contract, legitimate interest or another permitted ground depending on context. Protect access, storage, sharing and retention. Keep evidence of requests, results and user activity. Common examples A recruitment check should be linked to a role and candidate consent where required. A debtor trace should be connected to a lawful collection or account-management purpose. A programme beneficiary check should be tied to eligibility, reporting or fraud-prevention requirements. A support ticket should not expose more personal information than is needed to resolve the issue. Responsible use reminders Do not assume consent is always the only basis, but do not bypass consent where it is required. Do not collect more because it is convenient. Make correction and dispute routes clear. Public reference points Information Regulator public POPIA and PAIA resources. 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.
National Credit Act 101 for Credit Information Use
Last Updated: 18 May 2026Overview The National Credit Act regulates the consumer credit environment in South Africa, including roles and obligations that affect credit providers, credit bureaus and users of credit information. Why it matters Credit information can influence access to credit, collections, risk assessment and consumer treatment. Because of that impact, organisations should treat credit data as regulated information requiring purpose discipline, access control, audit trails and dispute handling. How to think about it Know whether the use case is credit granting, account management, collections, tracing, fraud prevention or another permitted activity. Keep records of the requester, purpose, consumer reference and result. Train users on what they may and may not do with bureau data. Support disputes and corrections rather than treating credit data as unquestionable. Common examples Using bureau information to assess credit-related affordability or risk. Using trace information to contact a debtor through lawful channels. Reviewing adverse indicators during collections strategy design. Separating consumer credit checks from non-credit background checks. Responsible use reminders Do not use credit data for unrelated employment, social or informal decisions unless there is a proper lawful basis and role relevance. Do not expose bureau reports in unprotected emails or shared folders. Do not ignore correction requests. 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.
FIC Act and Customer Due Diligence 101
Last Updated: 18 May 2026Overview The Financial Intelligence Centre Act environment is concerned with identifying and combating money laundering, terrorist financing and proliferation-financing risks. Many accountable institutions must understand their customers, monitor risk and report where required. Why it matters Verification supports customer due diligence by helping organisations know who they are dealing with, confirm identity, understand business relationships, screen relevant risk indicators and keep evidence of compliance activity. How to think about it Customer due diligence is not a single ID check; it is a risk-based process. Identity, beneficial ownership, source of funds, sanctions exposure and transactional behaviour may all matter depending on the institution and risk level. Records should show what was checked, when, by whom and why. Higher-risk relationships may need enhanced due diligence. Common examples Confirming customer identity during onboarding. Checking company and director information for a business customer. Supporting sanctions and risk-screening workflows. Keeping a clear evidence pack for compliance review. Responsible use reminders Do not treat a verification result as a complete AML programme. Follow your accountable institution’s risk management and compliance programme. Escalate suspicious indicators through approved internal reporting channels. Public reference points Financial Intelligence Centre public information on its mandate and compliance guidance. 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.
Consent vs Lawful Purpose: What Is the Difference?
Last Updated: 18 May 2026Overview Consent and lawful purpose are related but not identical. Consent is one possible basis for processing personal information. Lawful purpose explains why the information is being processed and must be clear even where consent is not the basis. Why it matters Confusing consent with purpose can create risk. A person may consent to one type of check, but that does not automatically allow the information to be reused for another purpose. Similarly, some legally required checks may rely on law or contract rather than ordinary consent, but they still need transparency and control. How to think about it Purpose answers: why do we need this information? Consent answers: has the person agreed to this specific use where consent is required? Lawful basis answers: which recognised ground allows the processing? Audit trail answers: can we prove what happened later? Common examples A candidate consents to qualification verification for a specific role. A financial institution performs customer due diligence because it has compliance obligations. A municipality processes debtor records for revenue management and lawful account administration. A programme manager verifies beneficiaries against eligibility criteria disclosed to participants. Responsible use reminders Do not use vague blanket consent for unrelated checks. Do not treat consent as a shortcut around fairness, necessity or security. Store consent records with the related request. 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.
Data Minimisation in Verification
Last Updated: 18 May 2026Overview Data minimisation means collecting and using only the information reasonably necessary for a defined verification purpose. It is one of the most practical ways to reduce risk while still achieving operational outcomes. Why it matters More data does not always create better decisions. Excessive data increases breach impact, support complexity, user risk, public concern and compliance burden. How to think about it Define the decision first, then decide the data required. Avoid requesting full documents where a specific attribute is enough. Mask, redact or limit display of sensitive identifiers where possible. Use role-based access so users see only what they need. Review old workflows to remove unnecessary fields. Common examples Using the last four digits of an ID number in a support conversation instead of the full number. Collecting qualification details relevant to the role rather than every certificate a person has ever obtained. Showing a risk category to a manager while limiting access to the full source report. Separating operational dashboards from raw personal records. Responsible use reminders Minimisation does not mean weak verification; it means proportionate verification. Document why a sensitive field is necessary. Delete or archive records according to an approved retention rule. 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.
Identity Verification 101
Last Updated: 18 May 2026Overview Identity verification checks whether a person is who they claim to be. It may include checking identity numbers, names, date of birth, citizenship or permanent-residence status indicators, deceased status, biometric signals, document authenticity, contact details, and related risk indicators. Why it matters Identity is foundational. If identity is weak, later checks such as credit, criminal record, qualification, employment, beneficiary, account or supplier checks can be misdirected to the wrong person. How to think about it Identity verification should combine data quality, source reliability and context. A correct identity number is not always enough; names, date of birth and other attributes should be considered. The purpose determines the depth of the check: onboarding, employment, credit, programme participation and investigation may require different evidence. Identity checks should not be used to exclude people unfairly where data quality issues can be resolved. Common examples Confirming that an applicant’s ID number format is valid before deeper checks are requested. Comparing supplied names and date of birth against identity records. Flagging possible deceased-status conflicts for manual review. Requesting additional evidence when a record cannot be confidently matched. Responsible use reminders Use identity data only for the purpose communicated or legally permitted. Protect identity documents and images as sensitive personal information. Document exceptions and manual overrides. Public reference points Department of Home Affairs public information on identity documents and civic services. 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.
Understanding Match, No Match, Partial Match and Unable to Verify
Last Updated: 18 May 2026Overview 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’s own compliance review, regulator guidance, or contractual obligations.
Source-Connected Verification vs Document Collection
Last Updated: 18 May 2026Overview 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’s own compliance review, regulator guidance, or contractual obligations.
Why Consent, Purpose and Audit Trails Matter
Last Updated: 18 May 2026Overview Consent, purpose and audit trails are the control points that make verification accountable. They help show why a check was performed, who requested it, what the person understood, which data was used and what result was returned. Why it matters Verification can affect people’s opportunities, finances, reputation and access to services. A weak audit trail can turn a useful check into a compliance, reputational or contractual risk. How to think about it Purpose explains why the data is needed. Consent records the person’s permission where consent is the appropriate basis. Audit trails show what happened, when it happened, who did it and which result was returned. Exceptions explain why a process departed from the normal workflow. Common examples A recruitment check should show the role, applicant, consent record, checks requested and result date. A credit-related check should be tied to the permitted purpose and the requester’s authorisation. A public-sector verification should show programme, case, user and approval context. Responsible use reminders Do not hide broad permissions inside unclear language. Do not reuse a verification result for a new purpose without checking whether that use is permitted. Keep evidence long enough to support disputes, audits and regulatory obligations, but not longer than necessary. Public reference points Information Regulator public guidance and POPIA resources. 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.
What Is an Evidence Pack?
Last Updated: 18 May 2026Overview An evidence pack is a structured record that brings together the request, lawful purpose, submitted data, source result, timestamps, user actions, supporting documents, exceptions and decision notes related to a verification or risk process. Why it matters Evidence packs help organisations explain decisions, support internal governance, handle disputes, respond to audits and improve operational consistency. How to think about it The request record explains who asked for the check and why. The input record shows what data was submitted. The result record shows what was returned and when. The decision note explains how the result was interpreted. The exception log records any override, escalation or manual review. Common examples A debtor tracing evidence pack for a municipal book. A qualification verification evidence pack for a recruitment process. A beneficiary eligibility evidence pack for a programme audit. A supplier due diligence pack for procurement review. Responsible use reminders An evidence pack should not contain unnecessary personal information. Access should be limited to authorised users. A clear evidence pack should be readable by compliance, operations and management, not only by technical users. 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.
Understanding Real-Time and Manual Verification
Last Updated: 18 May 2026Overview Some verification checks can return quickly through automated channels, while others require manual handling, source processing, document review, biometric capture, fingerprint submission, third-party confirmation or custodian turnaround. Why it matters Real-time checks improve speed, but not every reliable check is real-time. Organisations should design processes that distinguish urgent automation from checks that require more time and evidence. How to think about it Real-time checks are useful for fast screening and workflow routing. Manual checks are useful where the source process requires human review or certified documentation. Hybrid workflows use quick checks first, then escalate unclear or high-risk cases. Turnaround time should be communicated clearly to users and applicants. Common examples An ID format check may be instant. A qualification verification may depend on source availability or agency process. A criminal record-related process may require authorised fingerprint or police clearance processes. A debtor book enrichment may run as a batch and produce a dashboard or report. Responsible use reminders Do not promise instant results where the source process is not instant. Track pending, completed, failed and escalated statuses separately. Use service-level expectations that reflect real source constraints. 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.
What Information Is Usually Needed for a Verification Request
Last Updated: 18 May 2026Overview The information needed depends on the check. Common fields include full names, identity number, date of birth, contact details, document images, qualification details, employer details, company registration number, case reference, consent record and purpose of request. Why it matters Good input quality improves matching accuracy, reduces failed requests and avoids unnecessary escalations. Poor input quality can cause false non-matches, duplicated work and delayed decisions. How to think about it Collect the minimum information needed for the check. Validate obvious formatting errors before submitting the request. Capture the purpose and reference number at the start of the process. Separate applicant-supplied data from source-returned data. Record who submitted the request and when. Common examples For a qualification check: certificate type, year, institution or assessment body where relevant, names and ID/passport number. For a company check: registration number, company name and director or representative context. For a trace check: identity details, last known contacts and lawful collection purpose. For support: search ID, request date, user, client and screenshot if appropriate. Responsible use reminders Avoid collecting documents because they are convenient if they are not necessary. Protect high-risk identifiers such as ID numbers, biometric data and criminal history information. Use standard input templates to improve data quality. 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.
What Is a Data Custodian?
Last Updated: 18 May 2026Overview A data custodian is an organisation or authority that maintains a record set or source system for a particular type of information. Custodians may include public authorities, regulators, statutory bodies, credit bureaus, education bodies, business registries, professional bodies and authorised third-party data providers. Why it matters Knowing the custodian matters because the custodian usually determines what can be verified, which fields are available, what consent or purpose is required, how often records are updated and whether a result can be corrected directly or only at the source. How to think about it The custodian is not always the same as the platform that displays the result. A verification platform may connect to, request from or process data sourced from a custodian. Some custodians provide direct public services; others work through authorised channels or verification agencies. Corrections usually need to happen at the source that owns the record. Common examples Home Affairs for identity and civic-status-related records. Umalusi for specified school and further education certificates. CIPC for company-registration information. Credit bureaus for consumer credit information. SAPS-related processes for police clearance and criminal record-related procedures. Responsible use reminders Always distinguish source ownership from platform delivery. Check whether the requester has lawful authority to use the source. Do not promise correction of a record that only the custodian can amend. 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.
Home Affairs Checks 101
Last Updated: 18 May 2026Overview Home Affairs is central to identity and civic-record context in South Africa. Identity verification may involve ID number structure, names, date of birth, citizenship or permanent-residence indicators, deceased-status indicators and document-related information depending on the authorised service and use case. Why it matters Identity information is high-impact personal information. A mismatch can delay employment, onboarding, public services, credit processes or benefit access, so the result should be handled carefully and reviewed where necessary. How to think about it Identity checks should use accurate input fields, especially full names and ID number. A Home Affairs-related result may confirm, conflict with, or be unable to verify the supplied data. Name changes, spelling differences, old documents, data capture issues and record updates may affect the result. Where the record itself is wrong, the person may need to resolve it through Home Affairs channels. Common examples Checking whether a South African ID number appears consistent with supplied personal details. Flagging a deceased-status conflict for review. Supporting onboarding where proof of identity is required. Identifying cases where additional documentation is needed. Responsible use reminders Do not use identity information for unrelated purposes. Do not publish identity numbers or documents in unsecured support channels. Escalate sensitive mismatches rather than making assumptions. Public reference points Department of Home Affairs public identity-document information explains that identity documents are issued to eligible persons from age 16 to prove identity. 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.
RTMC and Motor Vehicle-Related Verification 101
Last Updated: 18 May 2026Overview Road traffic and motor vehicle-related verification may involve vehicle identifiers, licensing context, ownership-related indicators, driver or operator information, traffic contraventions, and other information governed through road traffic systems and authorised channels. Why it matters Vehicle and driver information can support asset finance, insurance, logistics, fleet management, public-sector enforcement, investigations and fraud prevention. It must be used carefully because inaccurate vehicle or driver assumptions can affect people and organisations unfairly. How to think about it Vehicle checks should use accurate registration, VIN, engine or other relevant identifiers where required. Different checks answer different questions: vehicle existence, status, ownership context, licensing or contravention risk are not the same thing. Data access may depend on legislation, contract, permitted purpose and the source channel. Results should be interpreted with operational context, especially where vehicles change ownership or records are pending update. Common examples Checking a vehicle identifier before asset recovery or insurance assessment. Supporting fleet integrity by comparing internal records to verified vehicle attributes. Flagging suspicious mismatches in ownership or vehicle details. Improving debtor, supplier or asset records with structured evidence. Responsible use reminders Avoid using vehicle checks as a proxy for unrelated personal profiling. Keep vehicle and driver data under appropriate access controls. Escalate disputed or unclear results to the relevant authority or internal review process. Public reference points Road Traffic Management Corporation and NaTIS/eNaTIS public information channels for road-traffic context. 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.
What Verification Means in a Trust Environment
Last Updated: 18 May 2026Overview Verification is the process of checking whether information supplied by a person, organisation, applicant, debtor, employee, supplier or beneficiary can be supported by a trusted source or by appropriate evidence. Why it matters In a trust environment, verification is not only about finding data. It is about making a decision more reliable, reducing preventable fraud, improving auditability, and ensuring that decisions are made for a lawful and clearly understood purpose. How to think about it Start with the question you need to answer, not with the check you want to run. Use the least intrusive check that can reasonably support that question. Separate raw data from interpretation: a result may inform a decision, but it does not automatically make the decision. Keep evidence of the request, purpose, consent or lawful basis, result, user, date and follow-up action. Responsible use reminders Do not run checks because they are available; run them because they are necessary for a defined purpose. Treat every result as part of a governed process, especially where it affects a person’s access to work, credit, services or benefits. Allow for correction or dispute where the result appears inaccurate or incomplete. Helpful questions to ask What decision are we trying to support? Which source is most appropriate for this type of information? What evidence must be retained if the decision is challenged later? Is the person aware of the verification and its purpose where consent is 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’s own compliance review, regulator guidance, or contractual obligations.
J-Cred Terms You Should Know
Last Updated: 31 March 2026A few key terms appear again and again in J-Cred. Understanding them makes the platform easier to use correctly. Core terms Search ID: the unique identifier for a search. Reference / Case Number: your organisation’s internal reason or case label for the activity. Prescribed Purpose: the reason the search is being performed. Real-time search: a search that returns immediately after submission. Manual or document request: a request that requires manual processing or external confirmation. e-Consent: a digital workflow that allows a candidate to review and sign consent. Dispute / challenged information: information a consumer believes is incorrect and that should not be treated as confirmed while under review. Tip: Teaching these terms to new users early reduces avoidable confusion later. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Client Admin Handover Checklist
Last Updated: 31 March 2026When a new client administrator takes over responsibility for J-Cred, a short handover checklist can prevent a lot of confusion. Recommended handover points Which users currently have access Which services are approved for the organisation What internal reference rules the team uses Which workflows the team uses most often How support requests are usually escalated What recurring issues or delays the team has already encountered Who the internal decision-maker is for disputes and complaints Best practice: Do not hand over only credentials. Hand over working context. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
A Manager’s Guide to Responsible J-Cred Use
Last Updated: 31 March 2026Managers do not need to perform every search themselves, but they do need to create the conditions for responsible platform use. What managers should reinforce Only the right users should have access. Searches must be tied to a valid business purpose. Internal references and Search IDs must be retained properly. Consent requirements must be treated seriously where applicable. Support, disputes, and complaints should be raised through the correct route. Teams should not use speed as an excuse for careless process. Outcome: Strong management habits reduce support pressure and improve confidence across the organisation. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Why Search IDs Matter Even When a Report Looks Fine
Last Updated: 31 March 2026A report may look fine today and still need to be traced later. Search IDs matter even when nothing appears to be wrong because they support follow-up, audits, support, and dispute handling. Keep the Search ID because Older reports may not remain visible in the portal. Support can often trace an issue faster with the Search ID. Your internal team may need to explain why the search was done later. It forms part of a stronger audit trail when paired with the internal reference. Tip: Treat the Search ID as a normal record, not as something to remember only when there is a problem. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Use Search History for Internal Follow-Up
Last Updated: 31 March 2026The Search History page is more than a log. It can be used as a working record for reviewing recent activity, finding results, and tracing what has already been done. Useful habits Review recent searches before creating duplicates. Use filters to narrow down by date, type, or other visible fields. Use the action column to open current reports where still viewable. Export filtered views when you need offline or internal reporting support. Tip: A quick check in Search History can save unnecessary repeat work. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Explain J-Cred to a New Team Member
Last Updated: 31 March 2026A useful introduction to J-Cred is simple: it is a working environment for approved users who need to run searches, manage requests, handle consent-led activity, and keep better traceability around sensitive workflows. A simple explanation to give Some workflows are real time and some are manual or tracked. Every search should have a valid purpose and internal reference. Search IDs should be retained for traceability. Consent matters where required. Support, complaints, and disputes each have a proper route. Tip: New team members do not need every detail on day one. They need the right principles and the few workflows they will use first. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
When to Contact Your Client Administrator First
Last Updated: 31 March 2026Not every issue needs to go straight to J-Cred support. In many organisations, the fastest first step is your own client administrator or internal responsible person. Start with your client administrator when You are unsure whether you should have access to a workflow. You need help understanding how your organisation uses references or case numbers. You are not sure whether a request type is appropriate for your process. You need an internal decision before support can act. Escalate externally when: The issue is platform-related, needs supplier follow-up, or requires formal support, complaint, or dispute handling. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Reduce Rejected Requests in Your Team
Last Updated: 31 March 2026Rejected searches and requests are often a process issue before they become a system issue. Teams can reduce them with a few simple disciplines. What helps most Use the correct workflow for the business need. Enter accurate subject information. Use meaningful internal references. Confirm consent requirements before submitting. Review common rejection reasons and teach them back to the team. Tip: A short internal checklist before submission usually prevents more problems than reactive support after rejection. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Prepare for Busy Periods in J-Cred
Last Updated: 31 March 2026When request volumes increase, self-service discipline becomes more important. A busy team needs clear patterns, not more confusion. Prepare by Using the help centre before logging repetitive support requests. Making sure all users know the main workflows and status meanings. Keeping references and Search IDs properly. Escalating only the issues that truly need support or dispute handling. Having a client admin or manager coordinate common internal questions. Outcome: The better your team uses the knowledge base, the less support pressure you create during peak periods. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
What a Prescribed Purpose Means in Practice
Last Updated: 31 March 2026A prescribed purpose is the reason you are performing a check. In practice, this means the purpose selected in the system should match the real business reason for the search. Why this matters It supports lawful and responsible use of information. It helps prevent misuse of sensitive results. It creates a stronger audit trail for your organisation. It helps support and review teams understand the context of the search. Rule: If the purpose changes, run a new search with the correct purpose instead of reusing the old result. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Why You Must Not Reuse Results for a Different Purpose
Last Updated: 31 March 2026A result returned for one purpose should not be reused for another purpose just because it is convenient. Why reuse is a problem The original context no longer matches the new use case. The search may not have been lawful or appropriate for the second purpose. It weakens traceability and undermines internal controls. It can create unnecessary compliance risk for your organisation. Example: An employment-related result should not automatically be reused for credit decisioning. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Keep Better Records with Search ID and Reference
Last Updated: 31 March 2026The combination of Search ID and internal reference is one of the simplest ways to improve your organisation’s control and follow-up capability in J-Cred. Better record-keeping habits Capture the internal reference before you submit the search. Retain the Search ID once the search is created. Store both together in your internal system or case file. Use the same identifiers when contacting support or raising a dispute. Do not rely only on portal visibility if the record may be needed later. Tip: These two details often make the difference between a fast support interaction and a slow one. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Protect Your J-Cred Account
Last Updated: 31 March 2026Your J-Cred account is part of your organisation’s security and compliance posture. Protecting it is a basic responsibility, not only a technical preference. Protect your account by Keeping your password private Using your own account only Logging out when you finish, especially on shared devices Avoiding public or unsecured computers where possible Reporting suspected unauthorised access quickly Do not: Share your login details with colleagues or use shared accounts. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
What to Do If You Suspect Unauthorised Access
Last Updated: 31 March 2026If you suspect that someone else has accessed your J-Cred account or that your account activity does not look right, act quickly. Recommended response Stop using the session if something looks suspicious. Reset your password if that is available to you and safe to do. Notify your client administrator or internal responsible person. Contact J-Cred support immediately. Be ready to provide your user details and a short explanation of what you observed. Important: Do not ignore suspicious account behaviour and hope it resolves itself. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
What Information to Include When Contacting Support
Last Updated: 31 March 2026Support works best when the request is clear and traceable. A vague message such as “it is not working” often slows the process down. Include these details Your organisation name Your primary contact details Your user email address Search ID where applicable Internal reference or case number The selected purpose where relevant A short description of the issue Screenshots where useful Tip: The more specific your request, the easier it is for support to assist quickly. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Understanding Response Times and Updates
Last Updated: 31 March 2026J-Cred aims to acknowledge requests promptly and provide updates, but actual turnaround time can vary depending on what type of help or request is involved. What affects timing Whether the request involves a real-time workflow or a manual/document process Whether the issue depends on a third-party confirmation How complete and clear the original support request was What your contract or service agreement provides for that request type Important: Where a third-party confirmation is required, expected timelines may be advised separately. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
What External Dependencies Mean for Your Request
Last Updated: 31 March 2026Some J-Cred workflows depend on systems or institutions outside J-Cred’s direct control. This is important when managing expectations with your team or your client. Examples of external dependencies Upstream system outages or maintenance Institutional closures or peak periods Reference contact availability Incomplete or incorrect information slowing external processing Good to know: Where needed, J-Cred can provide proof of submission and processing traceability to show that a request is active and awaiting external response. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Support Request vs Complaint vs Dispute
Last Updated: 31 March 2026These three routes are related but not identical, and choosing the right one helps move the issue to the correct path more quickly. How they differ A support request is for help, clarification, technical issues, or operational follow-up. A complaint is for dissatisfaction with service delivery. A dispute is for information you believe is inaccurate or that a consumer has challenged. Tip: If you are not sure which route applies, start by explaining the issue clearly and include the Search ID and internal reference where relevant. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
What Challenged Information Means
Last Updated: 31 March 2026Challenged information refers to information that a consumer disputes as incorrect. In these cases, the information should not simply be treated as settled or confirmed. What this means in practice Do not treat the disputed information as final. Log a dispute or support request properly. Include the Search ID and internal reference. Be ready to provide supporting documentation if requested. Wait for the review process rather than trying to force certainty yourself. Important: Disputed items may be treated as under investigation while they are being resolved. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Why You Should Not Work Around a Dispute by Re-Running a Search
Last Updated: 31 March 2026If information is under dispute, re-running the same search is not an acceptable shortcut around the review process. Why this matters It does not resolve the underlying dispute. It can create the false impression that repeated searching equals confirmation. It weakens the proper handling of challenged information. It may create unnecessary compliance and support problems. Correct approach: Use the dispute and support path, not repeated re-searching, when accuracy is being challenged. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
What Bank Account Verification Can and Cannot Confirm
Last Updated: 31 March 2026Bank account verification is useful, but it should be understood properly. It helps confirm details about the account and whether the supplied information aligns with the verification process. What it can help with Confirming whether the account details appear to align with the person or entity being checked. Supporting onboarding or verification workflows that need bank detail confirmation. Reducing avoidable errors before downstream processing. What it does not replace Your organisation’s own review of the broader transaction or onboarding context. The need for correct inputs and supporting records. Any other legal, compliance, or business checks required for your process. Tip: Enter all required details carefully, especially branch code, surname, and account number. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Before You Submit a Document Request
Last Updated: 31 March 2026Document requests work best when they are prepared properly before submission. Incomplete or unclear requests often create delays or rejections. Prepare these first The correct request type Accurate subject details such as full name, ID number, or document information A clear internal reference Any supporting details required for the specific manual request An understanding that the request may need external or manual processing Tip: The better your initial submission, the less time you lose later in follow-up. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Why a Document Request May Be Rejected
Last Updated: 31 March 2026A rejected document request usually means the information supplied was not sufficient, valid, or aligned to the request type. Common reasons Incorrect or incomplete subject details Wrong request type selected Missing information needed to process the request Consent-related requirements not being met where applicable The information supplied not matching the intended verification route What to do next: Read the rejection reason carefully, correct the issue, and submit again only when the information is ready. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
What to Do If a Document Request Stays Open or In Progress
Last Updated: 31 March 2026Some document requests take longer because they depend on manual handling or third-party response times. A request remaining Open or In Progress for a time does not always mean it has been ignored. A sensible response Check that the request type and subject details were entered correctly. Review whether the request depends on an institution, external party, or manual process. Keep your internal reference and any request identifiers ready. Contact support if the delay appears unusual or if you need a progress update. Tip: Support can often assist faster when you provide the request context clearly rather than saying only that it is delayed. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How Client Admins Can Use the Document Tracker Better
Last Updated: 31 March 2026Client administrators often have wider visibility than standard users, which makes the Document Tracker a useful coordination tool. How admins can use it well Monitor all requests across the organisation, not only individual submissions. Spot requests that remain Open or In Progress for longer than expected. Help users improve how they label references and submit details. Reduce duplicate requests by checking the tracker before a team member resubmits. Use tracker visibility to support internal reporting and follow-up. Best practice: A strong client admin uses the tracker to improve coordination, not only to check status. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
When to Use Multi-Search and When Not To
Last Updated: 31 March 2026Multi-Search is powerful when several checks belong together for the same subject and the same business purpose. It is less suitable when different purposes are being mixed together. Use Multi-Search when You need several checks on the same person or subject. The checks belong to the same case and business reason. You want a more streamlined submission and visibility path. Do not use it when The checks serve different purposes. Different internal references should apply. You are trying to force unrelated workflows into one batch for convenience. Important: If purposes differ, run separate searches. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Common Reasons a Multi-Search May Fail or Be Rejected
Last Updated: 31 March 2026A Multi-Search can fail in full or in part for the same kinds of reasons that affect individual searches: incorrect data, invalid combinations, or incomplete information. Common reasons Incorrect ID number or identity details A selected search within the batch requiring information that was not provided A manual or downstream search not completing successfully A consent or purpose issue affecting one of the checks A search-specific rejection inside the overall batch Tip: If several items fail, review the common subject details first before retrying one by one. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Read a Combined Multi-Search Report
Last Updated: 31 March 2026A combined Multi-Search report brings together successful results from the batch into one holistic view. This can make records and review easier, but you should still understand the status of each individual search inside the batch. What to look for Which searches completed successfully Which searches are still pending Which searches failed or were rejected Whether any individual item needs to be retried separately Whether the combined report is sufficient for the use case or whether more follow-up is needed Tip: The combined report is useful, but it does not remove the need to understand the detail behind each included search. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Before You Send an e-Consent Request
Last Updated: 31 March 2026Before sending e-Consent, make sure the candidate details and selected checks are correct. A rushed consent request creates avoidable follow-up later. Check before sending Correct first name and surname Correct ID number or passport number Correct mobile number and email address The right set of checks requiring consent Internal records showing why the consent request is being sent Tip: Only send the consent request once you are satisfied that the candidate details and intended checks are correct. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
What the Candidate Needs Before Opening e-Consent
Last Updated: 31 March 2026Candidates respond better to e-Consent when they already understand what it is for and what information they will need. Helpful preparation Tell the candidate to look out for the e-Consent email or link. Ask them to keep their ID number or passport number ready. Explain that they may be asked to review and accept or reject listed searches. If qualifications are part of the checks, advise them to prepare those details too. Remind them that they will need to sign the consent using one of the available signature methods. Tip: Good candidate preparation can reduce delays and unnecessary rejection of valid consent requests. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Why a Candidate May Reject e-Consent
Last Updated: 31 March 2026A rejected e-Consent does not always mean the process has failed permanently. It often means the candidate is unsure, disagrees with the listed checks, or needs clarification. Common reasons for rejection The candidate does not understand why the checks are being requested. The candidate believes the details are incorrect. The candidate is not ready to proceed yet. The candidate does not agree with one or more of the listed checks. What to do next: Review the reason if one was provided, clarify the process with the candidate, and only resend when the issue has been addressed. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How the Qualification Step Works in e-Consent
Last Updated: 31 March 2026If qualification checking is part of the consent workflow, the candidate may need to add qualification details before signing the form. What the candidate does Open the qualification section when prompted. Add the qualification name. Add the institution name and city. Add the student number where available. Add the year completed. Save the entry and repeat the process if more than one qualification must be added. Tip: If no qualifications need to be captured, the candidate can continue to the signing step. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Understanding Signature Options in e-Consent
Last Updated: 31 March 2026J-Cred supports more than one signature method in the e-Consent workflow so that candidates can complete the process in the way that works best for them. Possible signature methods Typing a signature Drawing a signature Uploading a signature Using a default signature option where available Important: The candidate still needs to accept the terms and conditions before the consent can be submitted. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
When Consent Records Must Be Kept
Last Updated: 31 March 2026Where consent is required for a check or purpose, the consent record must not be treated as a temporary formality. It should be retained and linked properly to the relevant record. What good practice looks like Consent is obtained before the relevant search proceeds. Consent is linkable to the Search ID and internal reference. Consent details are clear enough to support audit and compliance review. Teams know which checks require consent and which do not. Important: Searches that need consent should not be treated as if consent were optional or implied. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Prepare Your Team Before They Use J-Cred
Last Updated: 31 March 2026A good rollout starts before people begin clicking through the platform. Teams work better when access, purpose, and support expectations are already clear. What to prepare Identify which users need access and what they are expected to do. Decide who in your team will act as the first internal point of contact for questions. Agree on how internal references or case numbers will be captured consistently. Remind users that consent must be obtained where required and linked to the relevant record. Explain that older reports may not remain viewable in the portal, so Search IDs and references should be kept properly. Best practice: The stronger your internal readiness, the fewer support issues you create for yourself later. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Common Login Problems and How to Fix Them
Last Updated: 31 March 2026Most login problems are simple and can be resolved quickly with a few checks. Check these first Make sure you are using the email address that was registered during onboarding. Check that Caps Lock is off before entering your password. Use the password reset flow if you are not sure that your password is correct. Try signing in again in a fresh browser tab or incognito window. Clear browser cache and cookies if the page is not behaving normally. Security: Use your own account only and never share login details with another user. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
I Did Not Receive My Onboarding Email
Last Updated: 31 March 2026If you did not receive your onboarding email, it does not always mean that something is wrong with your account. Sometimes the email is delayed, filtered, or sent to the wrong folder. What to do Check your spam, junk, and promotions folders. Search your inbox for J-Cred or onboarding-related subjects. Confirm with your organisation that the correct email address was submitted for onboarding. Ask your client administrator whether your profile has already been approved. Request that the onboarding email be resent if needed. Important: Registration is only for already approved and onboarded users. It is not a public sign-up process. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
What to Do If You See Invalid Credentials
Last Updated: 31 March 2026The “invalid credentials” message usually means the email or password does not match the active account details on record. How to respond Re-enter your email address carefully and remove any extra spaces. Check that you are using the correct password and not an older one. Use the Forgot Password option if you are unsure. Confirm that you are using the correct email address for this account. Contact support if the problem continues after a password reset. Do not: Keep trying random passwords repeatedly. It wastes time and can create unnecessary account confusion. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Browser Tips for a Better J-Cred Experience
Last Updated: 31 March 2026A stable browser environment makes a real difference when you are working with multi-step workflows, downloads, and support screenshots. Recommended habits Use a modern browser such as Chrome, Firefox, or Edge. Keep your browser updated. Avoid opening many duplicate tabs for the same process if you can help it. Allow downloads and pop-ups where your organisation’s policy permits and where the platform needs them for reports. Use a secure and stable internet connection. Good practice: If a page does not load properly, try a refresh first, then clear cache or use an incognito window. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Understanding the Side Navigation Menu
Last Updated: 31 March 2026The side navigation menu is where you move between the main working areas of J-Cred. It groups related workflows so you can find the correct type of search or request quickly. What you will usually find Person-related searches Company-related searches Assets and property-related searches Credit-related searches Compliance searches Document requests Multi-Search e-Consent Tip: If the sidebar is collapsed, use the arrow toggle to expand it and make navigation easier. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Open, Switch, and Close Working Tabs
Last Updated: 31 March 2026J-Cred can open internal working tabs as you move through searches, reports, and modules. This helps you return to recently used pages without starting again. How to use tabs well Click a tab to switch back to an open page. Close tabs you no longer need if the bar becomes crowded. Keep your Search History tab open so you can return to your main working dashboard easily. Avoid opening too many duplicate tabs for the same item. Tip: Internal tabs are there to support flow, not clutter. Close what you are finished with. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Why Your Internal Reference Matters
Last Updated: 31 March 2026Your internal reference or case number is one of the most important pieces of information you enter into J-Cred. It explains why the search or request was performed and helps your organisation trace it later. Why it matters It supports audit and compliance requirements. It helps support trace your issue more quickly. It allows your organisation to connect platform activity to internal cases or files. It becomes even more useful when kept together with the Search ID. Best practice: Use meaningful references, not vague notes. A clear reference will help months later when someone asks why a search was run. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Which Search Should I Use? A Quick Decision Guide
Last Updated: 31 March 2026One of the most common questions in J-Cred is not how to search, but which search to use. The best choice depends on what you are trying to confirm. A simple guide Use person-related searches when you need to verify or trace an individual. Use company or CIPC-related searches when you need company registration, status, or director information. Use assets-related searches when you need property or vehicle ownership information. Use credit-related searches when you need consumer or business credit information or bank account verification. Use compliance searches when you need fraud, PEP, or sanctions-related checking. Use a document request when the work requires manual processing or external confirmation. Tip: If you are unsure, start by clarifying the business purpose. The purpose usually points you to the right search family. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Choose the Right Search Criteria
Last Updated: 31 March 2026Many search types allow more than one input method, such as ID number, name, date of birth, passport number, telephone number, or registration number. The right search criteria improves accuracy and reduces unnecessary retries. General guidance Use the most reliable identifier you have. Use ID or registration numbers where available for more exact matching. Use name-based searching more carefully because it may return broader or multiple matches. Complete required fields fully and accurately. Add a clear reference every time. Important: If you receive no result or an unexpected result, first review the details you entered before assuming the platform is wrong. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
What to Do When a Search Returns No Results
Last Updated: 31 March 2026A no-result outcome does not always mean the search failed. In some cases, it means the search completed successfully but did not find a matching record based on the information provided. What to check next Review spelling, number formatting, and the selected search criteria. Confirm you used the correct search type for the information you have. Check whether you can search by a stronger identifier, such as ID number instead of name. Try a different but valid criteria path if the workflow supports it. Log a support request if the result still looks wrong. Tip: Do not guess wildly with repeated searches. Start by reviewing the business case and the details you entered. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Re-Run an Older Search Correctly
Last Updated: 31 March 2026Older reports may no longer remain viewable in the portal after a period of time. When that happens, the right approach is to re-run the search using the same correct criteria and internal reference discipline. How to do it well Go to the relevant search type in the side navigation. Use the correct search criteria again. Enter an internal reference that clearly reflects the current business case. Retain the new Search ID for the new search event. Do not re-run a search casually if the original information is under dispute or requires review. Important: Re-running is for valid business need and traceability, not to work around dispute or consent rules. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Understanding Exact Match, Contains, and Starts With in Company Search
Last Updated: 31 March 2026When searching for a company by name, the match type you choose affects how broad or narrow the results may be. How each option works Exact Match looks for the company name exactly as entered and is usually the most precise. Contains looks for records where the phrase appears anywhere within the company name. Starts With looks for records where the company name begins with the phrase entered. Tip: Use the narrowest option that still matches the quality of information you have. This helps reduce unnecessary result clutter. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
When to Search by ID and When to Search by Name
Last Updated: 31 March 2026Where a search offers both ID-based and name-based options, use the stronger identifier where possible. General rule of thumb Use ID number when you need a more exact individual match. Use company registration number when you have it and want a more exact company result. Use name-based searching when a stronger identifier is not available or when you are looking for possible matches. Use full and accurate names where name-based searching is necessary. Tip: Name-based searching can be useful, but it may also produce broader results that need closer review. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Before You Submit a Credit Search
Last Updated: 31 March 2026Credit-related searches should be approached carefully because they are tied to prescribed purpose rules and can materially affect individuals. Before you submit Make sure you have selected the correct prescribed purpose. Use the correct internal reference or case number. Confirm that any required consent is in place where applicable. Double-check the identity details before submission. Understand whether your workflow is for consumer credit, business credit, bank account verification, or another bureau-specific outcome. Important: If the purpose changes, do not reuse the original result. Run a new search with the correct purpose. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Why Employment Screening May Need a Job Description
Last Updated: 31 March 2026The guide notes that if Employment is selected as the reason in certain credit-related searches, a job description may also be required. This supports the lawful and purpose-specific use of the search. Why this matters It helps show that the search is tied to a real employment-related use case. It supports the correct application of purpose in line with responsible usage. It reduces the risk of treating employment and other purposes as interchangeable when they are not. Tip: Prepare the job description in advance if employment-related screening forms part of your workflow. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
Your First Day in J-Cred: A Simple Checklist
Last Updated: 31 March 2026If this is your first day in J-Cred, do not try to learn everything at once. Start with access, navigation, and the workflows your team uses most often. What to do first Complete your registration and sign in with your own account. Confirm that your access matches the services your organisation expects you to use. Open the Search History page and get familiar with the layout, filters, and action buttons. Ask your manager or client administrator which searches or requests you are expected to perform most often. Keep a clear internal reference for every search or request you submit. Make sure you understand when consent is required and when a Search ID should be retained. Tip: A calm and focused start reduces mistakes. Begin with one or two common workflows and build confidence from there. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
What Approved and Onboarded Means
Last Updated: 31 March 2026J-Cred is not a public sign-up platform. Users are added through an approval and onboarding process before they can register and sign in. What this usually means Your organisation has been approved to use specific services. Your user profile has been created with a role and permitted access level. You should receive onboarding communication with instructions for registration or password setup. Some search types may only become available after administrator approval or training. Important: If you believe you should have access but you have not received onboarding communication, contact your client administrator or support. Need help? Email support@kto.co.za or support@j-cred.co.za, call +27 10 224 0589 during 9AM to 5PM CAT, or log a clear support request with your Search ID and internal reference where applicable.
How to Submit a Document Request
Last Updated: 31 March 2026Submitting a request Log in to J-Cred. Open the Documents section. Select the Document Tracker area or related request entry point. Choose the type of request you need. Complete the required fields, such as name, ID number, reference, and supporting details. Submit the request. Before you submit Check that the information entered is accurate Use a clear internal reference Include enough detail to help the request be processed correctly Important: Incomplete or incorrect information can delay a request or lead to rejection. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
Understanding Document Tracker Statuses
Last Updated: 31 March 2026What the Document Tracker shows The Document Tracker helps you view and manage manual requests submitted through the platform. Typical statuses Open – the request has been submitted and is waiting to be processed In Progress – the request is actively being worked on Completed – the report is ready for viewing or download Rejected – the request could not be completed as submitted What to do with each status Open: check that the request was submitted correctly and allow normal processing time In Progress: monitor for completion and avoid duplicate submissions Completed: open or download the report Rejected: read the reason and correct the issue before resubmitting Important: Client Admin users may have broader visibility across requests submitted by users in their organisation. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to View or Download a Completed Document Request
Last Updated: 31 March 2026Accessing a completed request Open the Document Tracker. Locate the request with a Completed status. Use the action menu for that request. Choose View to open it or Download to save it. Why this matters Document Request reports are treated differently from many normal search reports. Once uploaded, they can remain available after completion. Important: Use a meaningful internal reference when submitting requests so completed items are easier to find later. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
When to Use Multi-Search
Last Updated: 31 March 2026What Multi-Search is Multi-Search allows you to run several checks at the same time on the same person or subject in a single submission. When it is useful When several checks belong to the same onboarding case When due diligence requires multiple related checks When you want one grouped workflow instead of running each search separately Important rule Only bundle checks together if they are being performed for the same purpose and the same internal case or reference. If the purpose is different, run separate searches. Important: Multi-Search improves efficiency, but it must still follow proper purpose and reference discipline. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Run a Multi-Search
Last Updated: 31 March 2026Running a Multi-Search Open the Multi-Search section from the side menu. Select the searches you want to include in the batch. Enter the common details for the subject, such as full name and ID or passport number. Add your internal reference. Submit the Multi-Search. After submission The system processes the selected checks together in the background, and you can track progress through the Multi-Search history area. Important: Use a clear reference every time. It makes grouped work much easier to find and support later. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
Understanding Multi-Search Statuses, Reports, and Re-Try
Last Updated: 31 March 2026What the history page shows The Multi-Search history page gives you a high-level view of each grouped submission and lets you drill down into the individual checks inside it. Common statuses Completed – all searches in the batch have completed successfully Partially Completed – some searches are complete while others are still pending or failed Pending – the grouped workflow is still processing Failed – an individual search did not complete successfully Rejected – an individual search could not proceed as submitted Available actions View a single report View a combined grouped report where available Use Re-Try for individual failed or rejected searches where appropriate Important: If several searches fail or are rejected, first check the accuracy of the information entered before trying again. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
What e-Consent Is and How to Send It
Last Updated: 31 March 2026What e-Consent is e-Consent is a digital consent workflow that allows a candidate to review and sign consent before selected searches are performed using their personal details. How to send an e-Consent request Open the E-Consent section. Choose New E-Consent. Enter the candidate’s first name and surname. Enter the candidate’s ID number or passport number. Enter the candidate’s mobile number and email address. Select the checks that require consent. Send the request. Why it matters Where consent is required, it must be properly captured and linkable to the relevant Search ID and reference. e-Consent helps make that process clearer. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
What the Candidate Does in e-Consent
Last Updated: 31 March 2026Candidate journey Once the request is sent, the candidate receives the e-Consent link and completes the consent process. Open the e-Consent link received by email. Authenticate using the required identifying detail. Review the searches listed in the request. Accept or reject the request. Complete any qualification information if that check is part of the request. Choose a signature method and sign the form. Submit the completed consent. If the candidate rejects The candidate can reject the request and may be prompted to give a reason. A rejection can then be seen in the history area. Important: Where qualification checks are included, the candidate may need to list the qualifications they are consenting to before signing. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
Understanding e-Consent Statuses and Reminders
Last Updated: 31 March 2026Where to view status Use the e-Consent History page to monitor the current status of consent requests that have been sent. Common statuses Pending – the request has been sent and is awaiting candidate action Signed – the candidate accepted, signed, and submitted the consent Rejected – the candidate rejected the consent request Helpful actions Send a reminder when a request stays pending Download the signed copy when the status is Signed Review the result and next step when the status is Rejected Important: Do not proceed with consent-required activity unless consent has been properly obtained. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
Responsible Use: Purpose, Consent, Reference, and Search ID
Last Updated: 31 March 2026The core compliance habits The strongest day-to-day discipline in J-Cred comes down to four things: correct purpose, proper consent where required, clear internal references, and keeping the Search ID. What this means in practice Choose the correct purpose every time Do not use one result for a different purpose later Capture consent where required and keep it linkable to the search Always add your internal reference or case number Keep the Search ID as part of your audit trail Why it matters These habits support lawful access, stronger auditability, faster support resolution, and better operational discipline. Important: If your purpose changes, run a new search using the correct purpose rather than reusing the old result. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
Employment Screening and the Job Description Requirement
Last Updated: 31 March 2026When Employment is the reason In the credit workflow, if Employment is selected as the reason for the search, the guide notes that the Job Description must also be uploaded. Why this matters This is part of prescribed-purpose discipline. The reason selected for the search must match the actual business reason, and the related supporting requirements must be followed. Good practice Check that Employment is genuinely the correct reason Upload the Job Description when required Do not reuse employment-related outputs for a different purpose Keep your internal reference and Search ID for the case Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
Support, Service Continuity, and Turnaround Times
Last Updated: 31 March 2026Understanding turnaround times Some workflows are real time, while others depend on manual processing or third-party institutions. Turnaround times can therefore vary by request type and operating conditions. When timelines may extend Upstream system outages or maintenance Institutional closures or peak periods Reference contact availability Incomplete or incorrect submission information Proof of submission Where delays occur, J-Cred can provide proof of submission and processing traceability, such as request identifiers, timestamps, and status logs, to show that a request was submitted and is awaiting an external response. Support contact details Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT. When contacting support, include your organisation name, user email address, Search ID where applicable, internal reference or case number, the selected purpose where relevant, and a short description of the issue. Screenshots can also help. Important: Formal service commitments remain governed by your signed service agreement or SLA.
How to Handle Complaints, Disputes, and Challenged Information
Last Updated: 31 March 2026If a result looks wrong If you believe a result is incorrect, or if a consumer disputes the accuracy of information, do not treat the information as confirmed. What to do Log a support request or dispute. Include the Search ID. Include your internal reference or case number. Provide a clear description of the concern. Attach supporting documentation where available. Complaints If you are unhappy with service delivery, you can lodge a complaint using the complaints contact provided by J-Cred and include your ticket or Search ID together with a clear description of the concern. Complaints email: complaints@kto.co.za Important: Do not attempt to work around dispute handling by re-running searches to obtain the same information without proper review. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
Client Administrator Quick Start Guide
Last Updated: 31 March 2026Your role as a client administrator Client administrators help set the tone for good usage inside the organisation. During rollout and day-to-day operations, strong admin discipline reduces confusion and makes support faster. Your first five actions Confirm who should have access. Check that users are aligned to the correct services and workflows. Make sure your team understands purpose, reference, consent, and Search ID discipline. Guide users on where to get help. Encourage clean internal records from the start. What to watch Repeated rejected requests Searches being run without clear references Questions about purpose or consent Requests staying open for longer than expected Users sharing access or using weak security habits Important: Client Admin users may have broader visibility across certain request types, including document requests submitted by users in the same organisation. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Log In to J-Cred
Last Updated: 31 March 2026Logging in Open the J-Cred login page in your browser. Enter the email address linked to your J-Cred account. Enter your password. Click Log in. On successful login, you will be taken to the main J-Cred dashboard, where the Search History page usually loads first. Good practice Use your own account only Do not share login details Log out when you finish, especially on shared devices Avoid signing in on public or unsecured computers Important: If you suspect unauthorised access, contact support immediately. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Reset Your Password
Last Updated: 31 March 2026If you forgot your password Open the Forgot Password page from the J-Cred login screen. Enter the email address linked to your J-Cred account. Click Send. Check your inbox and spam or junk folder. Open the reset email and follow the link. Create and confirm your new password. Common issues Make sure you are using the exact email registered on your account Check that Caps Lock is off Check spam or junk mail if the reset email does not appear Clear browser cache or try an incognito window if the page does not load Important: Use a strong password and do not reuse passwords across shared or public systems. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
Understanding the Search History Page
Last Updated: 31 March 2026What the Search History page is After login, the Search History page acts as your working dashboard. It shows a real-time log of the searches you have performed and helps you navigate back to recent activity. What you will usually find there A table of previous searches Search IDs, dates, search types, references, and related metadata A View More action for recent reports Search filtering and advanced search tools Export options for your filtered list What to remember Reports older than the portal’s normal viewability period may no longer open directly. If you need an older result again, you may need to re-run the same search. Important: Always keep your Search ID and internal reference in your own records. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Use Filters, Tabs, and Exports in J-Cred
Last Updated: 31 March 2026Use the platform more efficiently J-Cred includes several navigation and filtering tools that make it easier to work with recent searches and requests. Useful tools on the page Search box for quick filtering Advanced search for more precise filtering Active tabs to move between open items Export options for offline tracking or reporting Sidebar navigation to switch between search types Helpful habits Use the search box to find a case faster Use exports to help with internal reconciliation and audit preparation Use active tabs if you need to compare work without losing your place Refresh the page to view the latest recent activity Important: If an older report is no longer viewable, keep the original details and re-run the search where appropriate. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
Reports, Viewability, and Why Search IDs Matter
Last Updated: 31 March 2026Why Search IDs matter Every search generates a Search ID. This should be retained together with your internal reference or case number. Why this is important It supports audit readiness It helps with support follow-up It makes it easier to trace what was done and why It helps when a report is no longer directly viewable in the portal Viewability reminder Standard search reports may not remain viewable in the portal indefinitely. In the user guide, older reports are highlighted as subject to viewability limits, with 72-hour viewability noted as an important rule for recent report access. Document Request reports are treated differently and can remain available after upload. Important: Use export options where needed and keep your own clean internal records. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Run a Person Trace
Last Updated: 31 March 2026What a Person Trace is for A Person Trace helps you locate consumer trace details for an individual, which may include address, contact, or employment history depending on the result returned. How to run it Log in to J-Cred. Open the left-side menu and expand it if needed. Go to the person-related search area. Select Person Trace. Choose the search criteria shown on the page. Complete the required fields. Add your internal reference if prompted. Submit the search. Before you submit Make sure the selected purpose matches the reason for the search Check that names, ID number, date of birth, or other identifiers are correct Add a meaningful internal reference Important: If no results appear, double-check the spelling or identifier used before trying again. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Run Person Verification and ID Photo Verification
Last Updated: 31 March 2026When to use these searches Person Verification is used to verify the existence and legitimacy of an identity number or locate the closest match to an individual. ID Photo Verification extends this by including a Home Affairs photo where available. How to run the search Log in to J-Cred. Open the person-related search area. Select Person Verification or ID Photo Verification. Choose the available search criteria. Complete the required fields. Add your internal reference where relevant. Submit the search. Tips Use accurate identifying information Make sure the selected purpose is correct Keep the Search ID once the result is created Use support if the result appears incorrect or inconsistent Important: Where consent is required for your use case, make sure it is properly in place before proceeding. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Search a Deceased Estate
Last Updated: 31 March 2026What this search is for The Deceased Estate search helps you retrieve estate-related information using either name-based details or an ID number, depending on the workflow available to your organisation. How to run it Open the Deceased or CSI search area. Choose whether you are searching by name or by ID. Enter the required details. Add your internal reference. Submit the search. What you may receive Results may include estate details, executor information, status, and related report outputs depending on the search and response returned. Important: Always use a clear internal reference so the search can be traced later if follow-up is needed. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Search a Company or Director
Last Updated: 31 March 2026Company and director searching J-Cred supports company-related workflows such as CIPC company searches and director searches. Search by director Open the company search area. Choose the director search option. Enter the director’s first name and surname, or the identifier required by the page. Add your internal reference. Submit the search. Search by company name or registration Choose the company name or registration option. Select the matching mode available on the page, such as exact match, contains, or starts with where applicable. Enter the company name or registration number. Add your internal reference. Submit the search. Important: Use the search route that best fits the information you already have. Stronger identifiers usually lead to cleaner results. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Run a Trust Search
Last Updated: 31 March 2026What a Trust Search is for A Trust Search helps you retrieve trust-related information using the search type and criteria available in the platform. How to run it Open the Trust search section. Choose the search type shown, such as trustee ID number or trust number and trust name. Complete the required details for the selected route. Add your internal reference. Submit the search. Helpful advice Use the most reliable identifier available Check spelling and numbering carefully Use a meaningful reference so the search can be found again later Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Search Deeds Office and Vehicle Ownership
Last Updated: 31 March 2026Deeds Office Search The Deeds Office search helps trace property ownership and related deeds information. Open the Assets section. Select Deeds Office. Choose the relevant office, province, or city shown in the form. Select the search criteria, such as ID number, business registration number, business name, bond account number, ERF number, or title deed number. Enter the relevant details. Add your internal reference. Submit the search. Vehicle Ownership Search Vehicle Ownership searches help check vehicle ownership details linked to a specific person. Select Vehicle Ownership. Enter the required details shown on the page, such as ID number, initials, and surname. Add your internal reference. Submit the search. Important: Use accurate identifiers and keep your Search ID after submission. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Run Credit Checks and Bank Account Verification
Last Updated: 31 March 2026Credit workflows in J-Cred The Credit category supports credit checks on individuals and businesses, as well as bank account verification, depending on the bureau and products enabled for your organisation. General steps Open the Credit section. Choose the bureau available to you, such as XDS, VeriCred, TransUnion, or CPB. Select the sub-search type you need. Complete the required details. Select the correct prescribed purpose. Submit the search. Important compliance reminders Always select the correct prescribed purpose If Employment is selected as the reason, upload the Job Description where required Keep the Search ID together with your internal reference Do not reuse a result for a different purpose Bank account verification Bank account verification helps confirm that an account belongs to the person or company in question, where that workflow is enabled. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Run a Fraud Check
Last Updated: 31 March 2026What the Fraud Check does The Fraud Check helps determine whether an individual has fraud-related incidents or compliance flags recorded against the relevant fraud prevention dataset. How to run it Open the Compliance section. Select Fraud Check. Enter the required details, including the person’s ID number and your internal reference. Submit the search. Good practice Use a clear internal reference Confirm that the selected purpose is correct Treat suspicious or challenged information carefully and use the support path if needed Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Run a PEP and Sanctions Check
Last Updated: 31 March 2026What this search does PEP and Sanctions Checks help determine whether an individual or business is identified as a politically exposed person or appears against relevant sanctions information. How to run it Open the Compliance section. Select PEP and Sanction Check. Choose the entity type: Individual or Business. Enter the name and any required details. Add your internal reference. Submit the search. Helpful tip Use the correct entity type and check spelling carefully. Name-based searches are sensitive to the quality of information entered. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
What Counts as a Document Request
Last Updated: 31 March 2026When to use a Document Request A Document Request is used when a verification cannot be completed automatically in real time and needs manual processing or external confirmation. Examples of Document Requests Qualifications Employment references Criminal checks Psychometric assessments Driver’s licence verification Citizenship verification SARS tax clearance verification Vehicle reports Public servant checks Work or asylum permits You submit the request in the platform, it is picked up for processing, and the verified report is returned once complete. Important: Provide accurate details and a meaningful reference to reduce delays or rejection. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.
How to Set Up Your J-Cred Account
Last Updated: 31 March 2026Who can register J-Cred registration is only for users who have already been approved and onboarded. It is not a public sign-up form. How to complete registration Open the registration link sent in your welcome or onboarding email. Enter the email address that was used on your onboarding form. Create a password that meets the system requirements. Click the button to complete registration. Wait for the success confirmation, then return to the main login page. Password requirements At least 8 characters At least one digit At least one uppercase letter At least one lowercase letter At least one special character Important: If the registration link has expired, ask your J-Cred administrator to resend the onboarding email. Need help? Email support@kto.co.za or support@j-cred.co.za, or call +27 10 224 0589 during 9AM to 5PM CAT.