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 help you with.
Why We Built a YAKAP Module
If you use SeriousMD for private practice and have never touched YAKAP, this one may look like a detour from the features you actually pay for, so let me explain.
We did not go looking for government work. Many of our own SeriousMD doctors were already part of accredited facilities and needed a new system since the old government system was being retired.
So we built YAKAP EMR and it lives in its own module beside the core EMR rather than in place of it.
Private practice is still home for us, which our core team handles day to day. The grind never stops.
Now that’s out of the way, let’s continue.
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, from what we’ve seen so far. Our current assumption is that those cases are not necessarily rejected and that they go into a slower manual verification queue, so they do not appear in SAP 1 yet. We’re still waiting to get an official response on this one.
Worth clearing up while we are here: the Digital YES on its own is enough. The physical YES is optional, so if your staff are still doing both, that is work you can drop.
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 goes through whenever a facility raises a short payout. Most short payouts trace back to one of these, and two are fixable on your side today.
One caveat before we get into it. This is what we are seeing as of 29 July 2026. The process has changed more than once this year and not every office moves at the same time, so treat this as our current read rather than a permanent rule.
If your PRO tells you something different from what is below, we would genuinely like to know. That is how we keep this page honest.
- 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 what we need to chase. Screenshot it.
- PCU liveness check. Confirm it was completed, and note how, through our PCU checker or directly on the PhilHealth portal.
- Two PCUs, not one. This is the one catching facilities right now. Some PhilHealth offices have been telling clinics that a single PCU is enough and the rest is handled on the HCI portal. It is two. The second PCU is what serves as the patient’s signature on the Digital YES, so if only one was captured, the empanelment is not finished.
- Digital YES, or a manual MCA. In practice it is one or the other, and this is where most short months come from. If the empanelment went the manual route, the case is not lost. It sits in the slower queue and will not show up in this month’s SAP 1.
- 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, then it is not something you can fix on your end.
What We Can Help You With
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 being upfront about this, because it changes what to send 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. Share the month and a screenshot of the SAP ledger.
With those two things we can usually tell 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.