Symptom
- The system requires an expiration date for state-issued ID cards when completing Form I-9 Section 2 (List B), even when the ID is non-expiring.
- Some state IDs display non-expiring indicators that are not valid date entries, for example:
- Tennessee IDs showing
99/99/9999. - Illinois IDs showing
99/99/9999. - Wisconsin IDs showing
NON-EXPIRING.
- Tennessee IDs showing
- Attempting to enter
00/00/0000or99/99/9999is rejected with:"The expected date format is MM/dd/yyyy."
Environment
SAP SuccessFactors Onboarding
Reproducing the Issue
- Open the Form I-9 Section 2 task in Onboarding.
- Go to List B: Identity and select ID card issued by state/territory.
- Choose an issuing authority (for example, Tennessee).
- Observe that the
Expiration Datefield is mandatory and requires a validMM/dd/yyyydate format, preventing entry of non-date values or non-expiring indicators.
Cause
The system enforces a valid expiration date for List B state ID entries by design, and does not accept non-date values or placeholder dates such as 00/00/0000 or 99/99/9999.
Resolution
- Enter a far-future valid date in the
Expiration Datefield (for example,12/31/2099) when the state ID is truly non-expiring. - Do not use placeholder dates (
00/00/0000,99/99/9999) or text values (for example,NON-EXPIRING), as they are not accepted by theExpiration Datefield. - Complete Section 2 after saving the far-future date.
Keywords
I-9, section 2, list b, non-expiring, id, state, ids, expiration, date, required, tennessee, permanent, identification, license, illinois, wisconsin, 00/00/0000, 99/99/9999, expected, dates, format mm/dd/yyyy, onboarding, compliance, validation, far, future, workaround , KBA , LOD-SF-OBX-FRM , Compliance 2.0 Country Forms (except i9&EV) , Problem
Product
SAP SuccessFactors Onboarding 2511
SAP Knowledge Base Article - Public