Product updates

When loading pay history during Embedded Setup, Check operators often find historical deductions that are not presently configured on  employees. Deductions that are only present historically will now be marked with an external flag set to True on their respective API responses. These deductions will not be editable and will be hidden from list responses by default, unless otherwise specified via the include_external query param. For more information, see our Benefit and Post-tax Deduction API references.  

Check will be updating the logic behind employee and contractor onboard status to more accurately reflect SSN validation in late April. Today, if an employee or contractor has a missing SSN, their onboard status is `blocking`. Through this change, a missing or invalid SSN (as represented by ssn_validation_status = `invalid`) will instead result in a `needs_attention` onboard status. This change will ensure these onboard statuses are more comprehensive, making it simpler for you to surface missing or invalid SSNs to end users along with any other missing payee information. Note that at tax filing, Check will continue to send all-zero SSN values for missing and invalid SSNs in certain outputs from Check’s system, such as W-2 filings, as recommended by the SSA.

We have added Toast-specific instructions to the Previous Provider Access Component (“PPAC”). The PPAC guides employers through providing Check access to their previous provider, in order to give Check the data needed for Embedded Setup. This change enables employers migrating from Toast to more easily provide this access, by providing them step-by-step instructions of how to navigate their Toast platform. To read the Toast instructions and other provider-specific guidance, refer to this guide.

We have launched a change to reduce the number of automatically-generated tickets for Embedded Setup companies, all while continuing to send all of the same information. Historically, while most communications about an Embedded Setup company occurred on one setup ticket, a separate ticket was automatically generated when the company was moved to the final activation step. To simplify managing all information about Embedded Setup companies’ go-lives, we will now send activation-related messages on the existing setup ticket rather than creating a new ticket.