The PhilHealth PCU Liveness Check: What It Is and How to Do It Right

The PCU (PhilHealth Check Utility) is an online identity-verification tool that confirms a beneficiary's PhilSys registration and PhilHealth membership using facial recognition, and it must be run at every YAKAP patient encounter — registration, the First Patient Encounter, and every consultation after that. Skip it, and your clinic risks unpaid claims.

What the PCU Actually Verifies

The PCU is not a records lookup — it's a live identity check. Per PhilHealth Circular No. 2025-0017, it is "an online tool accessible via the PhilHealth Member Portal that verifies PhilSys registration and PhilHealth membership using personal details and facial recognition." In practice it does three things in one pass:

Confirms the person in front of you matches their PhilSys (national ID) and PhilHealth records
Performs a liveness check — the facial-recognition step that rules out a static photo or someone else's ID
Tags the beneficiary as verified in PhilHealth's database, which is what later lets their consultation data pass claims validation

The check runs against the PhilSys database first, then cross-references PhilHealth membership. Only individuals who are PhilSys-registered can go through the PCU this way — everyone else has to fall back to manual validation with a valid government ID or alternative documents, per the same circular.

When the PCU Is Required

The PCU runs at every touchpoint where a beneficiary interacts with your clinic — not once a year. PhilHealth Advisory No. 2025-0072 is explicit: "The PCU Liveness Check is required for every patient encounter, including during an FPE." That means:

At registration/selection — before a beneficiary is linked to your clinic
At the [First Patient Encounter](/stories/first-patient-encounter-guide/) — remember the FPE itself is data-gathering, not a medical consultation, but the PCU still applies to it
At every subsequent consultation — PC 2025-0017 requires PC Clinics to run the PCU on beneficiaries before each consultation to confirm identity and only link verified beneficiaries to services

Walk-ins follow the same rule before anything else happens: the circular requires walk-in beneficiaries to undergo PCU identity verification and liveness check first, with staff following a standardized handling matrix based on the person's PhilSys/PhilHealth registration status before proceeding to FPE or consultation.

The check itself can be done two ways: on the beneficiary's own mobile phone, or on a computer terminal your clinic or the Local Health Insurance Office (LHIO) provides.

What to Record After Every PCU Check

A completed PCU check without documentation is functionally the same as no check at all, because PhilHealth validates claims against what you recorded — not against the fact that you ran it. For FPE records specifically, PC 2025-0017 requires "the PCU reference number, verification result, and date/time stamp, and signed [Mutual Care Agreement]." The same fields matter for regular consultations:

PCU transaction/reference number — the unique ID the tool generates per check
Verification result — pass/fail (or verified/not verified)
Date and time stamp — this is what proves the beneficiary was physically present
The linked MCA/YES status, if applicable — see our YAKAP Empanelment Slip guide for when that form is required

Why the transaction number specifically matters: PA 2025-0072 states that effective January 1, 2026, every SAP1 submission must have an attached PCU Transaction Number and MCA, and claims without them "will likely encounter delays in processing or non-payment." This isn't a nice-to-have field — it's a payment gate. The same advisory notes PCU logs automatically timestamp beneficiary interactions, and those entries serve as the basis for capitation payment validation, fraud monitoring, and audit — so your own recorded transaction number needs to match what PhilHealth's system logged.

The June 30, 2026 Deadline for Rolled-Over Members

If your clinic carried over CY2025 beneficiaries into this year, there's a hard compliance date already on the calendar. PA 2025-0072 requires providers to complete MCA and PCU Liveness Check compliance for rolled-over members on or before June 30, 2026. Miss it, and the clinic must return SAP1 payments for every rolled-over beneficiary lacking a signed MCA, subject to PhilHealth's Payment Recovery process. If your clinic still has gaps here, treat it as urgent — this deadline has already passed as of this writing, so any unresolved rolled-over records are already exposed to recovery action.

Interim Documentation Until PCU Integrates With YAKAP

The PCU isn't yet wired directly into the YAKAP system's encoding flow, so PhilHealth requires a manual bridge in the meantime. Per PC 2025-0017, until that integration is complete, facilities must capture a photo of the beneficiary's PCU verification result — via webcam, mobile device, or screen capture — and keep it as temporary documentation for verification and audit. Practically, that means your front desk or nurse needs a habit: run the PCU, screenshot the result screen, and file it alongside the transaction number, result, and timestamp you're already recording. The live tool itself is at pcu.philhealth.gov.ph.

This documentation discipline pairs directly with the rest of your encounter paperwork — the eKAS you print immediately after the encounter and the ePresS for any prescription should reference the same visit the PCU verified, so an auditor can trace one beneficiary's identity check straight through to the services billed.

How RecordKo Handles PCU Capture

RecordKo builds the PCU transaction number, result, and screenshot capture directly into the registration and consultation flow — no separate spreadsheet to remember. The moment a beneficiary is checked, that record ties into the same encounter that generates the eKAS, ePresS, and the encrypted XML claim file, so the PCU Transaction Number is already attached when a SAP1-bound record is built, not bolted on afterward. Because it's built for YAKAP end-to-end, the same encounter also feeds your capitation tracking and PCU compliance history, so rolled-over-member gaps like the June 30 deadline are visible before they become a Payment Recovery problem.

Book a demo ↗