Skip to main content
Question

Marital Status Validity Period for Payroll

  • September 16, 2026
  • 4 replies
  • 39 views
Do Gooder (Customer)
Forum|alt.badge.img+4

The current design stores Marital Status only as a current value, without an effective-from/to date.

This creates a payroll gap in countries where a change in marital status affects tax treatment.

Example - Switzerland:
An employee is Single and gets married on 15 May. For Swiss withholding tax, a change in civil status can change the applicable tax tariff.

If IFS only stores Marital Status = Married, it cannot determine when the employee became married or which status applied to a particular payroll period.

Proposed Design Change:

Marital Status should have validity period. 

Effective dating supports payroll calculations in countries where marital-status changes have statutory payroll/tax consequences.

    4 replies

    Hero (Partner)
    Forum|alt.badge.img+11
    • vickyrohilya
    • Hero (Partner)
    • September 17, 2026

    ​@Iveta Aldana : System will always store current Marital Status o employee, as such there is no validity period. You can create a property code/ free field for Marital status, in case you need to maintain the validity period and that can be used for payroll/tax calculation.

    Vikas Jain
    Do Gooder (Customer)
    Forum|alt.badge.img+4
    • Iveta Aldana
    • Author
    • Do Gooder (Customer)
    • September 17, 2026

    Hello ​@vickyrohilya,

    Thank you for your answer. However, as marital status is sensitive information protected by GDPR. FADP and other local laws, we cannot store it in property fields, which are not included in protected information. Hence this solution is not viable.

    Validity period of marital status affects income tax and thus important for payroll in several countries, hence the idea for IFS to include it in their standard design.

    Thank you.

    Iveta

    Hero (Partner)
    Forum|alt.badge.img+11
    • R Lum Wai
    • Hero (Partner)
    • September 21, 2026

    Hi ​@Iveta Aldana 

     

    When an employee is active properties can be restricted from view of everyone but HR it is all about how and where you build the data using free fields/properties and multi fields.

    I would recommend if you have not done thinking about only using one of these to store  confidential data which only a small part of the business should see. Confidential data should not be split across all three options as then it becomes hard to restrict the visibility.

    Using permission sets and projections you can only assign visibility of the confidential data.

    You can add properties to the data processing rules which the should be used to make sure when someone leaves the business this data is then either deleted of anonymized as per GDPR rules  this was in an update to Cloud.

    Protected information was not aimed at being the only option for protecting data - this was not originally what it was built for.

     

    kind Regards

    rachel 

    Do Gooder (Customer)
    Forum|alt.badge.img+4
    • Iveta Aldana
    • Author
    • Do Gooder (Customer)
    • September 21, 2026

    Hello ​@R Lum Wai,

     

    Thank you. Permissions is how we protect the properties now.

    We also have different users HR, Global Mobility, Finance, etc needing access to different property fields and not others. The access attributes in HCM are there but I could not make them work for particular property fields. Moreover, there is no IFS documentation that I know of that would describe this. If you have insights I would be very grateful.

    Also, if marital status already exists as a field and more countries might need the validity period for income tax , I think my idea request is justified.  Storing the same information twice for the lack of IFS design is not optimal.

    Thank you.

    Iveta

    Terms & ConditionsAccessibility statement