Reconciling EAP Invoices Without Receiving Identifiable Counseling Data

📌 Start with the billing question HR actually needs to answer

For invoice reconciliation, HR usually needs to confirm four things: Was a contracted service delivered? Is the quantity billable under the contract? Was the correct unit price applied? Is the total invoice mathematically and contractually correct? None of those questions automatically requires the employer to know who received counseling or what was discussed.

🔐 Korean EAP confidentiality should shape the finance process

Korea’s Framework Act on Workers’ Welfare provides for Employee Assistance Programs, and Article 55 of its Enforcement Decree requires anonymity so participating workers’ confidentiality is not infringed, except where the worker agrees to the person or content to be disclosed. That makes it risky to design a workflow in which HR, Procurement or Finance routinely receives a named list of counseling users merely to verify charges.

Counseling records may also contain sensitive health or mental-health information under Korea’s Personal Information Protection Act (PIPA). The billing process should therefore be designed around minimum necessary operational data, while individual counseling information remains inside the provider’s clinical or service-delivery environment unless a distinct lawful and necessary disclosure path applies.

🧾 Use a two-layer reconciliation model

The employer layer should let the company verify the invoice without reconstructing an employee’s counseling history. The provider layer can retain the granular evidence it needs under its legal, contractual and professional responsibilities, subject to its own access controls.

📊 Build the invoice schedule around billable units, not people

🚫 Do not use ‘proof of service’ as a reason to request a counseling-user roster

A named roster reveals EAP use even if counseling topics are removed. If the contract requires stronger fraud or duplicate-billing controls, use mechanisms that do not make routine employee-level disclosure the default.

• Aggregate count certification: the provider signs or digitally approves the monthly reconciliation.
• Vendor-side transaction IDs: the provider can trace each billed unit internally without exposing the employee to the employer.
• Restricted exception audit: a material discrepancy triggers a narrow review under an agreed privacy/legal protocol rather than open access to all sessions.
• Eligibility token or verification: the provider confirms eligibility without creating a persistent counseling-user list for the employer.
• Exception reporting: only billing anomalies are escalated, not every counseling event.

🧩 Keep invoice data separate from program-utilization reporting

Utilization reporting and invoice reconciliation serve different purposes. A program report may contain non-identifying aggregate trends such as total use, broad channels or broad topic categories. An invoice should focus on the fields needed to pay the vendor. Combining department, topic, age band, date and exact session count in the same billing file can increase re-identification risk without improving the payment decision.

For small teams or low monthly utilization, even an aggregate-looking report can reveal who used EAP. Unless the commercial model genuinely bills by entity or population segment, department-level detail normally belongs outside the invoice.

🏢 Define the control roles before the first invoice

🔍 When Finance asks, ‘How do we know the sessions were real?’

This separates two controls that are often mistakenly combined: invoice assurance and employee confidentiality. Strong invoice controls do not require weak privacy controls.

⚠️ Review the data-processing structure in the contract

Under PIPA, outsourced personal-information processing requires specified contractual controls and supervision where the relationship is a processing entrustment. An EAP arrangement may involve more than one legal role depending on how the service is designed. Do not assume every provider is simply a processor for every data element.

The contract should separately describe the billing dataset, operational reporting dataset, counseling records, access rights, retention/deletion rules, incident response and any overseas processing or access.

✅ Monthly invoice reconciliation checklist

🔗 Related NudgeEAP guides

❓ FAQ

📚 Official sources and legal note

• Framework Act on Workers’ Welfare, Article 83 — Employee Assistance Programs
• Enforcement Decree of the Framework Act on Workers’ Welfare, Article 55 — anonymity for confidentiality
• PIPA Article 23 — sensitive information
• PIPA Article 26 — outsourced processing

This article provides general operational guidance for EAP billing in Korea. The exact data roles and lawful basis depend on the employer-provider service design, counseling model, contract, eligibility process and any cross-border processing. It does not mean that every EAP vendor holds every data element under the same legal role. Confirm the live billing and privacy architecture with the responsible Korean privacy/legal owner where necessary. Law checked September 30, 2026.