Product updates
All updates
Product Announcement
03
/
14
/
24
Upcoming Warnings for Potential for Late Tax Payments for All Manual 4-Day Payrolls
Normally payrolls on a four-day processing period must be approved by 8pm ET four business days prior to payday. However, we make an exception for payrolls that contain only payroll items with a manual payment method. For example, if an employer forgets to run payroll, they can set the payment method for each item on the payroll to manual, approve it all the way up to and including on payday, and then pay employees with cash or paper checks.While useful to employers, it’s important to note that in these situations Check cannot guarantee that all tax payments will be made on time if the payroll is funded via ACH. We must wait three business days after payday before making any tax payments triggered by these payrolls, regardless of when the tax payments are due, to ensure we are not taking on ACH credit risk. To avoid late tax payments, we recommend that employers on four-day processing periods minimize the use of all-manual payrolls, and when they are necessary fund them via wire.In the coming weeks we will be adding a `warnings` attribute to the Payroll object, which will be populated on four-day all-manual payrolls where there is a possibility of late tax payments. By watching this field you can determine when this case has occurred, and surface guidance to Employers on your platform accordingly.
Product Announcement
03
/
14
/
24
Upcoming Warnings for Potential for Late Tax Payments for All Manual 4-Day Payrolls
Normally payrolls on a four-day processing period must be approved by 8pm ET four business days prior to payday. However, we make an exception for payrolls that contain only payroll items with a manual payment method. For example, if an employer forgets to run payroll, they can set the payment method for each item on the payroll to manual, approve it all the way up to and including on payday, and then pay employees with cash or paper checks.
While useful to employers, it’s important to note that in these situations Check cannot guarantee that all tax payments will be made on time if the payroll is funded via ACH. We must wait three business days after payday before making any tax payments triggered by these payrolls, regardless of when the tax payments are due, to ensure we are not taking on ACH credit risk. To avoid late tax payments, we recommend that employers on four-day processing periods minimize the use of all-manual payrolls, and when they are necessary fund them via wire.
In the coming weeks we will be adding a `warnings` attribute to the Payroll object, which will be populated on four-day all-manual payrolls where there is a possibility of late tax payments. By watching this field you can determine when this case has occurred, and surface guidance to Employers on your platform accordingly.
Changelog
03
/
07
/
24
Payday/Processing Period Configurations and Alphabetical Worker Sorting in the Run Payroll Component
To reduce support burdens for running payroll, the Run Payroll Component now allows your customers to edit a payroll’s payday and processing period via the “Settings” button in the top left corner of the “Payroll Edit” screen. Payday configuration changes are allowed by default, and if you want to allow employers to edit processing periods as well, you can toggle this via the Component SDK settingsFinally, when a payroll is saved, payroll items, contractor payments and dropdowns are now automatically sorted alphabetically. Learn more about using the Run Payroll Component here
Changelog
03
/
07
/
24
Payday/Processing Period Configurations and Alphabetical Worker Sorting in the Run Payroll Component
To reduce support burdens for running payroll, the Run Payroll Component now allows your customers to edit a payroll’s payday and processing period via the “Settings” button in the top left corner of the “Payroll Edit” screen. Payday configuration changes are allowed by default, and if you want to allow employers to edit processing periods as well, you can toggle this via the Component SDK settings.
Finally, when a payroll is saved, payroll items, contractor payments and dropdowns are now automatically sorted alphabetically. Learn more about using the Run Payroll Component here.
Changelog
02
/
29
/
24
API Throttle Limits Update
Starting March 4th, Check will update our default throttle policy in the live production environment from 10,000 requests/hour to 25 requests/second. This rate limit update to the throttle durations is aimed at reducing the severity in hitting rate limits and aims to improve Check API performance overall. The new throttle policy is already active and successfully running without issue across all partners in Sandbox. We have backtested your API usage over the past two months and do not expect this change to impact access. However we recommend you review your own API usage metrics to confirm. Learn more about how to handle rate limits and best practices.
Changelog
02
/
29
/
24
API Throttle Limits Update
Starting March 4th, Check will update our default throttle policy in the live production environment from 10,000 requests/hour to 25 requests/second. This rate limit update to the throttle durations is aimed at reducing the severity in hitting rate limits and aims to improve Check API performance overall. The new throttle policy is already active and successfully running without issue across all partners in Sandbox. We have backtested your API usage over the past two months and do not expect this change to impact access. However we recommend you review your own API usage metrics to confirm. Learn more about how to handle rate limits and best practices.
Changelog
02
/
29
/
24
Usability Improvements to the Previous Provider Access Component
We’ve shipped two improvements to the Previous Provider Access Component, which directs employers participating in Embedded Setup on how to grant access to their prior payroll provider account. Previously, the component included a required step asking for the employer’s prior payroll provider. This step will now be skipped if the `previous_payroll_provider` field on the Enrollment Profile has been provided. This will make for a smoother experience in situations where prior provider information may have already been collected in a previous step.The UI has been simplified to prioritize guided instructions upfront, and now includes a double confirmation for the employer to attest that they have both granted access and set the appropriate permissions level for the new account. For more details, see the Guide to the Previous Provider Access Component
Changelog
02
/
29
/
24
Usability Improvements to the Previous Provider Access Component
We’ve shipped two improvements to the Previous Provider Access Component, which directs employers participating in Embedded Setup on how to grant access to their prior payroll provider account.
- Previously, the component included a required step asking for the employer’s prior payroll provider. This step will now be skipped if the `previous_payroll_provider` field on the Enrollment Profile has been provided. This will make for a smoother experience in situations where prior provider information may have already been collected in a previous step.
- The UI has been simplified to prioritize guided instructions upfront, and now includes a double confirmation for the employer to attest that they have both granted access and set the appropriate permissions level for the new account.
For more details, see the Guide to the Previous Provider Access Component.
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.