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 present non-expiring formats that cannot be entered as dates, for example:
- Tennessee IDs showing 00/00/0000.
- Illinois IDs showing 99/99/9999.
- Wisconsin IDs showing NON-EXPIRING.
- Attempting to enter 00/00/0000 or 99/99/9999 is 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 Date field is mandatory and requires a valid MM/dd/yyyy date format, preventing entry of non-date values or non-expiring placeholders.
Cause
The current system design enforces a valid expiration date for List B state ID entries and does not accept non-date values or placeholder dates like 00/00/0000 or 99/99/9999.
Resolution
- Enter a far-future valid date in the Expiration Date field (for example, 12/31/2099) when the presented state ID is truly non-expiring.
- Do not use non-date placeholders (for example, 00/00/0000, 99/99/9999) or text (for example, NON-EXPIRING) as they are not accepted by the date field.
- Proceed to complete Section 2 after saving the valid far-future date.
Keywords
i-9, section 2, list b, non-expiring id, state id, expiration date required, tennessee permanent identification license, illinois non-expiring id, wisconsin non-expiring, 00/00/0000, 99/99/9999, expected date format mm/dd/yyyy, onboarding compliance, date validation, far future date 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