Product updates
All updates
03
/
01
/
22
February 2022 Changelog
February has been a very exciting month at Check! Even with only 28 days to work with, our engineering team was able to make several key additions to Onboard, Console, and our API. This month we released improved payment visibility, failed payment retries, and bank account validation. With the recent announcement of our series C, we are excited for a supercharged year of building to make paying people even simpler!Get visibility into money movementFor the first time, partners have visibility into the status of money movement within Check. With the new ‘payment’ and ‘payment_attempts’ objects, you can observe payments and their corresponding attempts for completion initiated by Check on behalf of a company directly from the API. For more information, please view the updated documentation hereRetry failed paymentsAlong with viewing the status and reason for why a payment failed, you are now able to programmatically retry any failed payment with a simple API call or with the click of a button on Console. We will also support programmatic refunds and wires:Refunds: In the event the Company doesn’t want to retry a failed payment and wants to pay the Employee or Contractor manually via a paper check, you’ll have the ability to send the Company a ‘refund’ via Console or our API.Wires: Companies who see a failed ACH debit often prefer sending a wire in time for payday. If your Company would like to do this, you’ll be able to create an expected wire, view the wire details programmatically via our API and Console, and show the status of the wire to your users.For more information, see our Payments Recovery guide hereValidate bank accountsFailed payments are a pain for all of us — they result in significant delays and manual operations. To help avoid failed payments, Check now proactively validates all bank accounts added by your employers, employees, and contractors. If validation fails, we’ll automatically notify you so that you can request your users to update their banking details in time for payday. To ensure account validation does not get in the way of running payroll, bank accounts may be used while validation is in progress. See our Bank Account Validation guide here
3/1/22
February 2022 Changelog
February has been a very exciting month at Check! Even with only 28 days to work with, our engineering team was able to make several key additions to Onboard, Console, and our API. This month we released improved payment visibility, failed payment retries, and bank account validation. With the recent announcement of our series C, we are excited for a supercharged year of building to make paying people even simpler!
Get visibility into money movement
For the first time, partners have visibility into the status of money movement within Check. With the new ‘payment’ and ‘payment_attempts’ objects, you can observe payments and their corresponding attempts for completion initiated by Check on behalf of a company directly from the API. For more information, please view the updated documentation here.
Retry failed payments
Along with viewing the status and reason for why a payment failed, you are now able to programmatically retry any failed payment with a simple API call or with the click of a button on Console. We will also support programmatic refunds and wires:
- Refunds: In the event the Company doesn’t want to retry a failed payment and wants to pay the Employee or Contractor manually via a paper check, you’ll have the ability to send the Company a ‘refund’ via Console or our API.
- Wires: Companies who see a failed ACH debit often prefer sending a wire in time for payday. If your Company would like to do this, you’ll be able to create an expected wire, view the wire details programmatically via our API and Console, and show the status of the wire to your users.
For more information, see our Payments Recovery guide here.
Validate bank accounts
Failed payments are a pain for all of us — they result in significant delays and manual operations. To help avoid failed payments, Check now proactively validates all bank accounts added by your employers, employees, and contractors. If validation fails, we’ll automatically notify you so that you can request your users to update their banking details in time for payday. To ensure account validation does not get in the way of running payroll, bank accounts may be used while validation is in progress. See our Bank Account Validation guide here.
02
/
01
/
22
January 2022 Changelog
January was a rush at Check! Our teams made improvements to our API and core products, Onboard and Console, while also supporting the ongoing effort of year-start and year-end. This month, we’ve released employee pay splits, SSN duplication checks, and company Start Date validation. In addition to those features, we’ve also hit embedded payroll support for all 50 states (that’s 50 states, 1267 jurisdictions, and 6829 taxes)! To learn more about this feat, check out our blog post, The Road to 50Split employee pay into multiple bank accounts Check now allows employees to split their pay into multiple bank accounts! This feature is available in Onboard, Console, and the Check API. Employees can split net pay amounts across up to 7 accounts. Here is an example of how a net pay split will work: An employee configures their net pay splits as follows: Priority 1: Wells Fargo checking account ending 4431 Amount: $500Priority 2: PNC savings account ending 2982Amount: $300Priority 3: Capital One savings account ending 6720Amount: RemainderIf the employee receives a net pay of $1000, they’ll receive:Wells Fargo checking (4431)Amount: $500PNC savings (2982)Amount: $300Capital One savings (6720)Amount: $200See our ‘Net Pay Split’ guide to learn more about employee pay splits.Prevent employee and contractor SSN duplicates We've rolled out SSN Duplicate validation to better support customer tax filings. We've also updated our API docs to note the duplicate restrictions now in place. At a high level, the duplicate check prohibits:Any single company from having multiple employees with the same SSN.Any single company from having multiple contractors with the same SSN/ITIN.Please note that a single company can have a contractor and an employee with the same SSN, as a company may pay one person as both a contractor and an employee throughout a tax filing period.We've added further validation to company Start Dates To ensure that all selected company Start Dates are valid banking days, we’ve added validation to only allow users to select valid banking days. Users will see this change in both our API and Console. If a banking holiday is selected, the following error will occur: "Start date {start_date} must be a valid bank date."
2/1/22
January 2022 Changelog
January was a rush at Check! Our teams made improvements to our API and core products, Onboard and Console, while also supporting the ongoing effort of year-start and year-end. This month, we’ve released employee pay splits, SSN duplication checks, and company Start Date validation.
In addition to those features, we’ve also hit embedded payroll support for all 50 states (that’s 50 states, 1267 jurisdictions, and 6829 taxes)! To learn more about this feat, check out our blog post, The Road to 50.
Split employee pay into multiple bank accounts
Check now allows employees to split their pay into multiple bank accounts! This feature is available in Onboard, Console, and the Check API. Employees can split net pay amounts across up to 7 accounts. Here is an example of how a net pay split will work:
An employee configures their net pay splits as follows:
- Priority 1: Wells Fargo checking account ending 4431
- Amount: $500
- Priority 2: PNC savings account ending 2982
- Amount: $300
- Priority 3: Capital One savings account ending 6720
- Amount: Remainder
If the employee receives a net pay of $1000, they’ll receive:
- Wells Fargo checking (4431)
- Amount: $500
- PNC savings (2982)
- Amount: $300
- Capital One savings (6720)
- Amount: $200
See our ‘Net Pay Split’ guide to learn more about employee pay splits.
Prevent employee and contractor SSN duplicates
We've rolled out SSN Duplicate validation to better support customer tax filings. We've also updated our API docs to note the duplicate restrictions now in place. At a high level, the duplicate check prohibits:
- Any single company from having multiple employees with the same SSN.
- Any single company from having multiple contractors with the same SSN/ITIN.
Please note that a single company can have a contractor and an employee with the same SSN, as a company may pay one person as both a contractor and an employee throughout a tax filing period.
We've added further validation to company Start Dates
To ensure that all selected company Start Dates are valid banking days, we’ve added validation to only allow users to select valid banking days. Users will see this change in both our API and Console. If a banking holiday is selected, the following error will occur: "Start date {start_date} must be a valid bank date."
Changelog
12
/
29
/
21
December 2021 Changelog
December is always a busy time of year in the payroll world, but that didn’t stop our team from releasing key features like the Run Payroll Component and support for ‘Applied for’ parameters in Onboard and Console. We're very excited to head into the new year strong, with even more features coming down the pipeline to help you build faster and more elegantly on top of Check.Happy holidays from the Check team! A quick recap of DecemberLaunch of the Run Payroll ComponentSupport for ‘Applied For’ status in Onboard and ConsoleEdit support for child support remittancesCreate new hire contractor reportsAdd workplaces to contractor paymentsRun and preview payrolls using the Run Payroll ComponentYou can now use the Run Payroll Component to create, edit, preview, and run payroll. This component offers your users an easy way to set up employee pay rates, add earnings, and preview payrolls all in one embeddable flow. We’re committed to helping you build a world-class payroll experience. With the use of the Run Payroll Component, you will be able to embed a preview and run payroll flow that is compliant, well-tested, and user-friendly.To learn more about the Run Payroll Component, and all other Check Components, see our documentation here. If you would like to see how Check Components can help speed up your payroll product build, please reach outMark Console and Onboard parameters as 'Applied For'We have updated Console and Onboard to allow employers to indicate that certain company parameters are not yet available but have been applied for by the company. This may be useful for a new business that hasn't received its state-specific employer identification number from the state agency.When marking parameters as “Applied For,” certain state forms may be deferred for signature in Check Onboard and Check Components — this is normal and won't block implementation or payroll.Edit Child Support RemittanceYou can now PATCH the `managed` field on a Post-Tax deduction to `false`, and Check will not include the funds in the `cash_requirement` (found in the Totals object) or attempt to make payment on behalf of the company.This is for employers who prefer to keep their current process for remitting deductions and not have it paid through Check.Create new hire contractor reportsCheck has added optional fields `dob` and `start_date` to the contractor object and `workplace` to the contractor payments object to facilitate new-hire reporting for contractors.Add a workplace to a contractor paymentYou can now associate a workplace with a contractor payment. This allows Check to complete the appropriate state filing of 1099s for Year-End.
Changelog
12/29/21
December 2021 Changelog
December is always a busy time of year in the payroll world, but that didn’t stop our team from releasing key features like the Run Payroll Component and support for ‘Applied for’ parameters in Onboard and Console. We're very excited to head into the new year strong, with even more features coming down the pipeline to help you build faster and more elegantly on top of Check.
Happy holidays from the Check team!
A quick recap of December
- Launch of the Run Payroll Component
- Support for ‘Applied For’ status in Onboard and Console
- Edit support for child support remittances
- Create new hire contractor reports
- Add workplaces to contractor payments
Run and preview payrolls using the Run Payroll Component
You can now use the Run Payroll Component to create, edit, preview, and run payroll. This component offers your users an easy way to set up employee pay rates, add earnings, and preview payrolls all in one embeddable flow.
We’re committed to helping you build a world-class payroll experience. With the use of the Run Payroll Component, you will be able to embed a preview and run payroll flow that is compliant, well-tested, and user-friendly.
To learn more about the Run Payroll Component, and all other Check Components, see our documentation here. If you would like to see how Check Components can help speed up your payroll product build, please reach out.
Mark Console and Onboard parameters as 'Applied For'
We have updated Console and Onboard to allow employers to indicate that certain company parameters are not yet available but have been applied for by the company. This may be useful for a new business that hasn't received its state-specific employer identification number from the state agency.
When marking parameters as “Applied For,” certain state forms may be deferred for signature in Check Onboard and Check Components — this is normal and won't block implementation or payroll.
Edit Child Support Remittance
You can now PATCH the `managed` field on a Post-Tax deduction to `false`, and Check will not include the funds in the `cash_requirement` (found in the Totals object) or attempt to make payment on behalf of the company.
This is for employers who prefer to keep their current process for remitting deductions and not have it paid through Check.
Create new hire contractor reports
Check has added optional fields `dob` and `start_date` to the contractor object and `workplace` to the contractor payments object to facilitate new-hire reporting for contractors.
Add a workplace to a contractor payment
You can now associate a workplace with a contractor payment. This allows Check to complete the appropriate state filing of 1099s for Year-End.
Changelog
12
/
01
/
21
November 2021 Changelog
We’ve been hard at work this month and are excited to share some of the latest features that shipped at Check! Our team has made many improvements across our platform, specifically around bank account verifications, FEIN validations, benefits support, and Console features. Below is a recap of our November launches.Launched bank account verificationsTo ensure the highest payment success rates, Check now verifies all bank accounts. You can view the status of these verifications via the `status` and `disabled_reason` fields in the bank account object and bank account webhooksTo learn more, check out our guide on bank account verificationsReleased company W-4 exemptions endpointYou can now get federal and state withholding exemption status for all employees at a company via this endpoint. With a Form W-4, you are able to determine the amount to withhold from an employee’s paycheck for federal tax purposes. This form needs to be updated annually for employees marked as exempt, so this new report can help you understand which employees to notify.Please see our reference documentation for more information, and feel free to reach out with any questions.Released support for effective dated tax withholding settings in ConsoleThis feature provides more visibility and granularity on when settings are effective. For example, tax rates may go into effect only on January 1 of next year. Prior to this launch, users could only define settings once, and needed to make changes to those values on the day they went into effect. Now, users can update current and past setting values as well as create new ones in the future.As always, you can visit our Console guide for a product overview and can also request an API key to gain full access to Console and its guides.Added validation for FEIN inputsWe now enforce all FEIN input values to be in the following format: ##-#######. This validation occurs in Console, Check Components, and Check Onboard to ensure consistent and compliant FEIN inputs from your employers.Added ability to define multiple benefits of the same type for an employeeYou can now define multiple benefits of the same type for an employee with non-overlapping effective dates. In addition, you can now define concurrent benefits of the same type for the same employee for Section 125 benefits. For these benefits, a maximum of 10 can exist at the same time for an employee.For all other benefits, only one benefit of a given type can be effective for a given employee.
Changelog
12/1/21
November 2021 Changelog
We’ve been hard at work this month and are excited to share some of the latest features that shipped at Check! Our team has made many improvements across our platform, specifically around bank account verifications, FEIN validations, benefits support, and Console features. Below is a recap of our November launches.
Launched bank account verifications
To ensure the highest payment success rates, Check now verifies all bank accounts. You can view the status of these verifications via the `status` and `disabled_reason` fields in the bank account object and bank account webhooks.
To learn more, check out our guide on bank account verifications.
Released company W-4 exemptions endpoint
You can now get federal and state withholding exemption status for all employees at a company via this endpoint. With a Form W-4, you are able to determine the amount to withhold from an employee’s paycheck for federal tax purposes. This form needs to be updated annually for employees marked as exempt, so this new report can help you understand which employees to notify.
Please see our reference documentation for more information, and feel free to reach out with any questions.
Released support for effective dated tax withholding settings in Console
This feature provides more visibility and granularity on when settings are effective. For example, tax rates may go into effect only on January 1 of next year. Prior to this launch, users could only define settings once, and needed to make changes to those values on the day they went into effect. Now, users can update current and past setting values as well as create new ones in the future.
As always, you can visit our Console guide for a product overview and can also request an API key to gain full access to Console and its guides.
Added validation for FEIN inputs
We now enforce all FEIN input values to be in the following format: ##-#######. This validation occurs in Console, Check Components, and Check Onboard to ensure consistent and compliant FEIN inputs from your employers.
Added ability to define multiple benefits of the same type for an employee
You can now define multiple benefits of the same type for an employee with non-overlapping effective dates. In addition, you can now define concurrent benefits of the same type for the same employee for Section 125 benefits. For these benefits, a maximum of 10 can exist at the same time for an employee.
For all other benefits, only one benefit of a given type can be effective for a given employee.
No Results Found
It looks like the combination of filters you've applied didn't return any results. Try adjusting your filters or clearing some selections to see more entries.