If your YAKAP SAP 1 came back smaller than you expected, you are not alone. We have seen the same gap across a number of facilities this year, and in most cases it traces back to one process change.
Here is what changed, what to check on your end, and what we can chase for you.
Why SAP 1 Payments Are Coming Up Short
PhilHealth moved empanelment to the Digital YES on the HCI Portal. Empaneling a patient, the step that ties them to your clinic, is now a digital process tied to a second PCU liveness check.
It sounds like a small process change. In practice it decides whether a patient counts toward your SAP 1.
Facilities that kept submitting empanelments on paper or by email are the ones seeing short payouts. Those cases are not rejected. They go into a slower manual verification queue, so they do not appear in SAP 1 yet.
One more wrinkle worth knowing: it has not been applied identically everywhere. Some facilities doing it the old way were still paid, while others in a different region were not. If your experience does not match a neighbouring clinic’s, that is why.
Six Things to Check When Your SAP 1 Is Short
This is the list our support team now walks through on every call. Most short payouts trace back to one of these, and two are fixable on your side today.
- Which month is short. Pull up the SAP ledger and note the exact period. A general “we were not paid” is the hardest thing to chase.
- Counted versus expected. The ledger shows a beneficiary count. If it says 9 and you submitted 200, that gap is the whole conversation. Screenshot it.
- PCU liveness check. Confirm it was completed, and note how, through our PCU checker or directly on the PhilHealth portal.
- Second PCU, or a physical MCA. This is the big one. The second PCU now serves as the patient’s signature on the Digital YES. If paper was emailed instead, the case sits in the manual queue.
- PCU transaction number on the HCI portal. We have seen clinics capture both PCUs correctly and then never enter the number where it counts.
- Records marked complete. One facility spent weeks certain their yearly reports were broken. The records had never been marked complete. Once they were, the reports updated.
If you get through all six and the numbers still do not add up, the issue is upstream of you.
What We Can Chase for You
When a payout is short, what helps is evidence, not sympathy.
We can compile the transmittal IDs and counts for the affected month, so you can go to your PRO with exactly what was sent and when, and request that the manual cases be verified and counted rather than treated as negative.
If patients have disappeared from your roster entirely, that is usually a central cleanup on PhilHealth’s side rather than anything you did. Those patients need to re-select your clinic through the eGov app, the PhilHealth Member Portal, or your LHIO.
And where the confusion is ours, we fix it. A status inside our own system that reads as unclear is on us, and we are working on it.
What We Cannot See
Worth setting expectations on, because it shapes what to bring us.
We do not have access to your PhilHealth portal. We cannot see which of your cases were rejected, and we cannot see what you were actually paid. What we can see is what left our system and when.
That is why we ask you for the ledger screenshot rather than pulling it ourselves, and why the transmittal IDs are the piece we can put in your hands.
If Your Numbers Look Wrong This Month
Run the six checks above, then talk to us. Bring the month and a screenshot of the SAP ledger.
With those two things we can usually tell within one call whether it is something we can fix, something you can fix, or something we need to raise together.
If you want the longer version of what this year has looked like from our side of the software, I wrote that one on my own blog.