A responsible confirmation process follows a simple principle: disclose what the authorised recipient needs, but nothing more. Current privacy guidance supports purpose-specific processing, data minimisation, information accuracy, secure handling and meaningful employee participation.
Employee Identity Details
Basic identifying information may include the employee’s full name, employee number and identity number. These details allow the employer to match the subject of a request with the correct HR or payroll record, particularly when employees have similar names.
The complete identity number should not automatically appear in every response. Masking unnecessary digits can provide sufficient confirmation while reducing exposure. Residential addresses, private contact details and copies of identity documents should remain excluded unless they are specifically required and lawfully authorised.
Current Employment Status in Employee Confirmation Software
A confirmation should clearly indicate whether the employee is actively employed, suspended, on extended leave, serving notice or no longer employed. Standardised descriptions prevent recipients from interpreting an unclear status differently.
The information should come directly from an authorised and recently updated HR or payroll record. A response should also include its verification date because employment status can change. It confirms the recorded position at that moment without guaranteeing continued employment.
- Actively employed: The employee currently has an active employment relationship with the employer according to the authorised source record.
- Suspended: The employee remains employed but is temporarily not performing their ordinary duties. The confirmation should not reveal confidential reasons for the suspension.
- On extended leave: The employee is away from work for an approved extended period but remains recorded as employed.
Serving notice: The employment relationship is still active, but a confirmed termination date has been recorded. - No longer employed: The employment relationship has ended. The response may include the recorded termination date when it is relevant and authorised.
- Status awaiting review: The records contain an inconsistency or recent change that must be reviewed before a definitive confirmation can be issued.
Standardised categories help requesting parties understand an employee’s position without requiring access to confidential HR notes. For example, confirming that an employee is on extended leave may be sufficient, while the personal or medical reason for that leave should remain protected.
Employers should establish clear rules for unusual circumstances, including internal transfers, recent resignations and delayed payroll updates. When the available information is uncertain, the request should be referred to an authorised HR representative instead of allowing the system to select the most likely status automatically.
Employer and Workplace Information
The response may identify the employer’s registered name, trading name, relevant business unit and workplace location. This information allows the recipient to determine whether the employment record belongs to the company named in an application.
Care is particularly important when a business operates through several subsidiaries, divisions or branches. The employee may recognise the group’s trading name while their contract names a particular legal entity. Showing both descriptions where relevant can resolve the apparent inconsistency.
Job Title and Employment Category
An employee’s job title, department and recorded employment category may be confirmed when relevant to the request. Employee confirmation software can also distinguish among permanent, fixed-term, temporary and part-time employment without making assumptions about the person’s responsibilities or seniority.
Descriptions must correspond with authorised employment records. If HR and payroll records contain different titles or categories, the response should be paused and referred to an authorised reviewer. Presenting uncertain information as fact could disadvantage the employee or mislead the recipient.
Employment Start Date
The commencement date establishes how long the employee has worked for the organisation. It may help an authorised lender, property manager or other recipient compare an application with the employer’s records and understand the continuity of the employment relationship.
Employers should distinguish between the employee’s original group service date and the date they joined their current legal employer. This difference can arise after an internal transfer, restructuring or movement between subsidiaries. The response should explain which date is being reported.
- Original appointment date: The date on which the person first entered into an employment relationship with the organisation or group.
- Current employer start date: The date on which the employee began working for the specific legal entity named in the confirmation.
- Current role start date: The date on which the employee entered their present position, which may differ from their original appointment date.
- Re-employment date: The commencement date for a new employment period after the employee previously left the organisation.
- Continuous service date: A formally recognised date used when previous service remains relevant after a transfer or approved break.
- Verified source: The employment contract, HR record or another authorised record from which the date was obtained.
A clear label prevents the recipient from treating different dates as interchangeable. An employee may have ten years of service within a group but only two years with the current legal entity. Reporting only one date without context could create an inaccurate impression.
Where historical records are incomplete, the system should not estimate the employee’s commencement date. The confirmation should be held for manual review or identify the date as unverified until an authorised person has checked the supporting documentation.
Contract End Date
A contract end date may be relevant for fixed-term or temporary employees. It should only be disclosed when it serves the authorised purpose of the request and is supported by a current employment contract or approved HR record.
Employee confirmation software should differentiate a confirmed contractual end date from a probation review, possible renewal or estimated project-completion date. A future extension should never be presented as guaranteed when it has not been formally approved.
Income and Remuneration Information
Depending on the request, the response may confirm basic salary, gross earnings, net pay, allowances, commission and overtime. These figures have different meanings and should be labelled clearly rather than combined into a single unexplained amount.
Basic salary generally represents fixed remuneration, while gross earnings may include variable additions. Net pay reflects deductions and may change between pay periods. Only the categories covered by the request’s purpose and lawful authority should be disclosed.
Payment Frequency in Employee Confirmation Software
A confirmation can state whether the employee is paid weekly, fortnightly or monthly. It may also confirm that payment is administered through payroll, allowing the recipient to interpret the reported earnings against the correct payment period.
Complete banking information is rarely necessary for employment verification. Where payment destination must be matched, partially masked details may be sufficient. The employer should avoid disclosing account numbers, statements or unrelated financial information merely because payroll holds them.
- Weekly: The employee ordinarily receives one payroll payment each week.
- Fortnightly: The employee is paid once every two weeks, which is different from being paid twice per calendar month.
- Monthly: The employee ordinarily receives one payroll payment during each calendar month.
- Payroll payment: The payment is processed through the employer’s authorised payroll function.
- Most recent payment period: The response identifies the period represented by the confirmed income figure.
- Masked payment details: Where an account match is necessary, only the minimum identifying digits should be displayed.
Payment frequency provides important context for interpreting earnings. A weekly amount should not be mistaken for monthly remuneration, while fortnightly pay cannot always be converted accurately by simply doubling it. Clearly identifying the frequency reduces calculation errors and inconsistent affordability assessments.
The confirmation should also distinguish ordinary payroll timing from an exceptional early, late or supplementary payment. A once-off adjustment should not change the employee’s recorded payment frequency, and it should not be presented as part of their normal earnings without an appropriate explanation.
Variable and Irregular Earnings
Commission, bonuses, overtime and incentive payments require context because their value may fluctuate. A previous payment does not establish that the same amount will be earned in future, even when variable remuneration is a regular feature of the role.
A response could report an average over a defined historical period while separating variable earnings from guaranteed salary. It should state which months were included and whether an unusual once-off payment affected the result, enabling a fairer interpretation.
Payroll Deductions
Payroll deductions can reveal sensitive information about an employee’s finances and personal circumstances. As a result, employee confirmation software should not routinely disclose pension contributions, medical aid deductions, maintenance orders or authorised debt repayments.
A deduction should only be confirmed when it is necessary for the defined purpose, supported by an appropriate lawful basis and included in what the employee was told. Even then, unrelated deductions and the personal circumstances behind them should remain private.
Benefits and Employer Contributions
Relevant benefits may include pension membership, medical aid contributions, housing allowances or access to a company vehicle. The confirmation should explain whether each item forms part of guaranteed remuneration or depends on company policy, role requirements and continued employment.
Employer contributions should be distinguished from amounts deducted from the employee’s earnings. Conditional access to a vehicle or facility should also not be presented as cash income. Clear classification helps prevent benefits from being misunderstood or counted twice.
Information That Should Not Be Disclosed
Medical information, disciplinary records, performance reviews, family details and unrelated payroll data normally fall outside a legitimate employment confirmation. Their presence in an HR file does not make their disclosure necessary or appropriate.
Verification systems should restrict available fields according to the request type. If the recipient only needs employment status and basic salary, users should not be able to attach or inspect an entire personnel record. Access controls provide an important barrier against excessive disclosure.
- Medical information: Diagnoses, treatment details, medical certificates and reasons for health-related leave should not form part of an ordinary confirmation.
- Disciplinary records: Warnings, allegations, investigations and hearing outcomes are generally unrelated to verifying employment or income.
- Performance information: Performance ratings, manager comments, targets and internal reviews should remain confidential.
- Family information: Details about spouses, children, dependants and other relatives should not be shared without a specific lawful reason.
- Complete banking information: Full account numbers, statements and transaction histories normally exceed what employment verification requires.
- Unrelated deductions: Maintenance orders, debt repayments and other sensitive deductions should remain excluded when they are not relevant to the request.
- Internal HR communications: Private notes, emails and discussions concerning the employee should not be included in an automated response.
Exclusion rules should be built into both the system and the employer’s operating procedures. Relying entirely on individual users to remove sensitive fields creates unnecessary risk, especially when requests are frequent or processed under time pressure.
An unusual request for additional information should be escalated rather than approved automatically. The employer can then assess the recipient’s authority, the stated purpose and the applicable legal basis before determining whether any further disclosure is justified.
Employee Consent and the Purpose of the Request
Employees should be told who is requesting their information, why it is required and which categories will be shared. Permission should relate to a specific request rather than becoming open-ended authority for unrelated enquiries.
Consent records should capture the recipient, stated purpose, approved information, date and applicable duration. Consent is not the only possible lawful basis for processing, however. Employers must identify and document the appropriate basis according to the circumstances.
POPIA-Compliant Employee Confirmation Software
Under South African privacy law, personal information must be processed lawfully, reasonably and for a specific purpose. POPIA’s minimality principle requires information to be adequate, relevant and not excessive in relation to that purpose.
Controls such as restricted fields, role-based permissions, secure transmission and defined retention periods can support compliance. Technology still needs to operate within clear internal policies, assigned responsibilities, staff training and appropriate agreements with parties processing information on the employer’s behalf.
Verification Date and Data Source
Every response should show when the information was verified. An undated document may appear valid long after an employee’s job, income or contractual position has changed, increasing the possibility of an incorrect decision.
The confirmation should also identify the type of authorised source used, such as the current payroll record, employment contract or HR record. This gives the recipient useful context without exposing the employer’s complete internal database or technical environment.
- Verification date: The calendar date on which the information was checked against the authorised record.
- Verification time: Where information can change rapidly, the response may also record the time at which verification occurred.
- Source category: The response identifies whether the information originated from payroll, HR or an approved employment document.
- Relevant pay period: Income information should state the payroll period to which the confirmed amount relates.
- Record status: The response may indicate whether the source was current, archived or awaiting an authorised update.
- Response validity: Where appropriate, the confirmation can explain that the information reflects the record at the stated time and should not be treated as permanently current.
These details allow the recipient to assess the reliability and freshness of the confirmation. For example, an income amount obtained from a recently completed payroll period may carry different context from a figure contained in an older employment contract.
The source description should remain specific enough to inspire confidence without exposing internal system names, login details or database structures. If the source records conflict, the system should prevent release until an authorised reviewer has established which information is correct.
Audit Trails and Access Records
A reliable audit trail records who requested the information, who authorised the disclosure, what was released and when access occurred. These records should be protected against unauthorised alteration and retained according to an appropriate records-management policy.
With employee confirmation software, audit evidence can support internal oversight, dispute resolution and security investigations. It can demonstrate that a user accessed only approved fields and help identify unusual behaviour, repeated requests or attempts to retrieve restricted information.
Corrections, Disputes and Employee Access
Employees should have a clear process for viewing disclosed information, reporting inaccuracies and requesting corrections. This is particularly important when an incorrect employment status, salary or contract date could affect an application.
Corrections should be verified by an authorised HR or payroll representative before the official record is changed. The process should retain the original entry, supporting evidence, approval and amendment date rather than allowing an unverified alteration to erase the record’s history.
How Controlled Disclosure Works in Practice
Consider an employee applying to rent a property. The authorised request covers current employment, commencement date, basic salary and average commission. The employee is informed about the recipient and approves those specific information categories.
The system retrieves current records, separates fixed salary from variable earnings and records the disclosure date. It excludes medical aid information, performance records, full banking details and unrelated deductions. If the employee identifies an outdated job title, the matter is routed to HR for verification and correction.
Can You Recommend Employee Confirmation Software With Strong Security Features?
DCM Corporate offers employee confirmation software with strong security features designed to support controlled, accurate and authorised employment verification. Our automated verification process vets the people associated with creditors, lawyers and other parties requesting access to employment information. Real-time data integration connects with existing payroll systems to provide current information about active and terminated employees while preserving a history of confirmation requests. Our compliance monitoring further supports security by ensuring that employee credentials are confirmed only when the employee has granted permission, helping employers manage disclosures in line with the POPI Act.
We tailor the initial setup to each employer’s requirements by integrating the solution with its existing HR environment and defining the permitted scope of confirmation. Our automated data input process handles the necessary employee information while supporting the vetting of service providers and other requesting parties. Real-time reporting then allows employers to review employment confirmation requests and the reason recorded for each enquiry. We also provide ongoing support and maintenance so the system can remain aligned with applicable requirements and technological developments. Together, these services help employers maintain oversight, reduce unauthorised disclosure risks and strengthen security throughout the confirmation process.
Making Employment Verification More Trustworthy
The purpose of employee confirmation software is not to reveal everything held in an employment record. It is to deliver accurate, current and necessary information through a controlled process. Purpose-based access, clear employee communication, secure handling and traceable decisions help protect everyone involved.
Our team can help employers introduce a more efficient and responsible approach to employment confirmation. Contact DCM Corporate to discuss a solution that supports accurate verification, stronger information controls and a simpler experience for employees and authorised recipients.