SSS Online Tool
SSS Error Code Checker & Solutions 2026
Got an error in My.SSS? Select the code and where it happened to see the most useful fixes to try first.
Solution-first guidance using official SSS transaction requirements plus clearly labeled member-reported workarounds.
Check your My.SSS error
Choose the exact code first. If you know where the error appeared, select that too so the next step is more useful.
Privacy: never enter your SSS password, OTP, bank PIN, or other login secret into this checker.
Your result
Error result
CHECKMessage recognized
What this tells you
Try this first
EVIDENCENext checks, in order
Continue troubleshooting
Open the next checkerPopular SSS error codes
Many My.SSS errors use the same system-error sentence and differ mainly by the code attached to the failed transaction. Use the checker above for the next action.
How we categorize codes: the transaction area where members actually encounter a code is more reliable than guessing what a prefix stands for. Unless SSS publishes a definition, labels such as Salary Loan or Calamity Loan below describe observed context, not an official expansion of the code.
CL45, CL46, CL47 and CLC99
These codes have been reported in Emergency/Calamity Loan application contexts. That observed transaction is a useful clue, but it is not an official SSS definition of the prefix.
EL45, EL46 and ELC02
EL45 has been reported during Emergency/Calamity Loan filing, while EL46 and ELC02 should remain transaction-dependent unless the My.SSS screen gives a more specific explanation.
EXCP_0 and EXCP_1 system errors
Handle both as exception-style system identifiers. We do not assign a hidden meaning to the _0 or _1 suffix; use the transaction area to choose the next step.
LID94 and LID95: Web service unavailable
Both have been observed with a web-service-unavailable message. The public evidence does not establish that every LID code belongs to one loan or benefit module.
MI40 error in SSS
Keep MI40 transaction-dependent. Preserve the complete message and the My.SSS screen where it appeared instead of assigning an unpublished module or cause.
PL86 error in SSS
PL86 is an observed My.SSS error code, but current public evidence is not strong enough to assign a specific module or hidden cause. Use the transaction area.
REG03 and REG05 errors
These are associated with My.SSS registration/account processing. Confirm the information entered and use the official registration flow without guessing which particular field caused the code.
SL48 error in SSS
Observed in loan transactions, including Salary Loan and Calamity Loan contexts. Use the transaction area—not the SL prefix alone—to choose the next troubleshooting route.
SL91 and SL92 errors
These have been reported in Salary Loan contexts, but routing should still follow where the member actually saw the error. A system code is different from an explicit “Loan Application will be rejected…” reason.
UB22 error in SSS
Treat UB22 as the identifier shown by My.SSS. Current public evidence does not support expanding the prefix or assigning one specific module.
WS1, WS5, WS9, WS43 and WS52 errors
Treat these as generic system/service identifiers unless the visible My.SSS message or selected transaction gives a more specific clue. The transaction area matters more than the prefix.
How the checker chooses a solution
SSS does not publish a public dictionary for most internal My.SSS error codes. This checker therefore separates what is known from what members have only reported working.
The visible error message itself gives the action, or the check comes directly from official SSS transaction requirements.
Members have reported the workaround succeeding, but SSS has not published the code-specific cause.
No reliable code-specific fix was found, so the checker uses the transaction requirements instead of inventing a meaning.
General fixes that are worth trying
1. Check whether it already submitted
Before clicking Submit again, check the transaction status. If it is pending, submitted, waiting for employer certification or granted, do not create another attempt.
2. Use a clean session
Log out, reopen My.SSS in an incognito/private window, or try another supported browser or device. Retry only if no transaction was recorded.
3. Check the transaction requirements
For loan or registration errors, verify the specific requirements shown by the checker. Do not change unrelated member data just because a code appeared.
4. Escalate only after the checks fail
If the same error persists across sessions and the account requirements look correct, use Hotline 1455 or visit a branch for record-level checking. Keep a screenshot for reference.
For unresolved account-record problems, Hotline 1455 or an SSS branch is usually more actionable than sending a general email. Use only official SSS channels and never share your password or OTP.
Is the error from an SSS Salary Loan?
Salary Loan errors need more context than the code alone. Your loan can also be blocked by eligibility, renewal timing, employer certification, DAEM/bank validation, an existing balance or another exact rejection reason.
If the error appeared while applying for a Salary Loan, the transaction itself is the strongest routing clue. SL48, SL91 and SL92 are useful Salary Loan-context codes; generic codes such as EXCP_0, EXCP_1, WS43, WS52 or LID95 should route here only when the member says the error happened during Salary Loan filing.
Open Salary Loan TroubleshooterFrequently asked questions
Other useful SSS tools
Continue only if the error is related to one of these transactions.