How to Hide Reports Until Payees Sign Their Plan Document in Varicent
WorkCentive || November 19, 2025
Have you ever wondered if you could hide compensation reports until your payees sign their plan documents? If so, this guide is for you.
Many organizations want to ensure plan documents are signed before reports become visible to payees for compliance purposes. Fortunately, Varicent provides a way to configure this. Below is a high-level overview of the steps required.
Create a table named spWorkflowPeriodMapping with the primary key columns WorkflowID and PeriodName. This ensures each workflow is accurately tied to the correct reporting period.

Create a datastore with the below data sources (which are: Payee, spWorkflowPeriodMapping, Workflow History, sysYesNo). The source “Workflow History” is a system table that stores the information regarding workflow actions.
The restrictions below will be added to join these sources together. Notice the sysYesNo restrictions, it is structured so that it will be “Yes” if the payee has signed the workflow document, and “No” if the payee has not signed the document.
For the display columns, select:
Configure the stored value as shown below. The stored value “v PlanDocAccepted” stores a Boolean value of either 0 or 1 (Signed = 1, Not Signed = 0), giving us a single indicator that shows whether a specific payee has signed the plan document for a specific period.
To retrieve the Boolean value, PayeeID and PeriodName need to be included in the datastore display columns so they can join to the stored value restrictions.
Add the restriction shown below so that an object will be visible only if the stored value v_PlanDocAccepted = 1 (signed). If the value is 0 (not signed), the object will remain hidden.
This visibility restriction must be added to all objects in each report.
Note: If multiple reports need to be hidden, Steps 3 and 4 must be repeated for each report.
The setup described above provides a high-level overview of how to hide reports for payees who have not signed their plan document. This allows compensation teams to ensure that all payees complete the acknowledgement process before gaining visibility into their compensation information.
The datastore configuration may vary by model depending on report structure and metadata.
At WorkCentive, we specialize in tailoring Varicent solutions like this for our clients. If you’d like support setting up plan document signature-based report visibility for your organization, reach out to our team. We’d be happy to help you get started.
Many organizations want to ensure plan documents are signed before reports become visible to payees for compliance purposes. Fortunately, Varicent provides a way to configure this. Below is a high-level overview of the steps required.
Step 1: Create a Support Table
First, create a support table that aligns the workflow ID of the plan document to the period in which the workflow is executed.Create a table named spWorkflowPeriodMapping with the primary key columns WorkflowID and PeriodName. This ensures each workflow is accurately tied to the correct reporting period.

Step 2: Build a Datastore to Track Signatures
Next, create a datastore that identifies whether a plan document has been signed by a payee.Create a datastore with the below data sources (which are: Payee, spWorkflowPeriodMapping, Workflow History, sysYesNo). The source “Workflow History” is a system table that stores the information regarding workflow actions.
The restrictions below will be added to join these sources together. Notice the sysYesNo restrictions, it is structured so that it will be “Yes” if the payee has signed the workflow document, and “No” if the payee has not signed the document.
For the display columns, select:
- PayeeID
- Boolean value (The Boolean Value can either be 0 or 1, where 0 represents “No” and 1 represents “Yes”. We get this “Yes” and “No” from the restriction logic in the calculation and then convert it to either 0 or 1)
- PeriodName
Step 3: Create a Stored Value
Next, bring this signature status information into a stored value.Configure the stored value as shown below. The stored value “v PlanDocAccepted” stores a Boolean value of either 0 or 1 (Signed = 1, Not Signed = 0), giving us a single indicator that shows whether a specific payee has signed the plan document for a specific period.
To retrieve the Boolean value, PayeeID and PeriodName need to be included in the datastore display columns so they can join to the stored value restrictions.
Step 4: Add Visibility Restrictions
Now that we have a value confirming whether a payee has signed their plan document for the selected period, we can use it as a visibility restriction in the report.Add the restriction shown below so that an object will be visible only if the stored value v_PlanDocAccepted = 1 (signed). If the value is 0 (not signed), the object will remain hidden.
This visibility restriction must be added to all objects in each report.
Note: If multiple reports need to be hidden, Steps 3 and 4 must be repeated for each report.
The setup described above provides a high-level overview of how to hide reports for payees who have not signed their plan document. This allows compensation teams to ensure that all payees complete the acknowledgement process before gaining visibility into their compensation information.The datastore configuration may vary by model depending on report structure and metadata.
At WorkCentive, we specialize in tailoring Varicent solutions like this for our clients. If you’d like support setting up plan document signature-based report visibility for your organization, reach out to our team. We’d be happy to help you get started.
