Changelog

When an enrolling company enters a FEIN that already exists in Check’s system, we will no longer block that FEIN from being entered altogether. Instead, the company will be allowed to use that FEIN and continue enrolling, enabling a more seamless customer experience. The company will still need to terminate with their prior provider before their first payroll, and instructions will be surfaced in Console in these cases.

We have introduced increased validation when a company submits EINs and account numbers. An employer will now be unable to submit a string containing a single repeated alphanumeric character into these fields, such as '11111' and 'aaaaa.' This validation helps to reduce failed tax filings due to invalid EINs and account numbers.

When you confirm and submit in Console, or hit the /start_implementation endpoint, we will now start requiring the company’s start date to be in the future of the current date. Read our docs for more information on validations around submitting to Check.

We have started automatically sending companies through the enrollment process in sandbox. When the /start_implementation endpoint is hit, or you “confirm and submit” in Console, assuming all other validations are complete, the company will automatically have their implementation status set to “complete." This change enables you to build automated testing and QA against our sandbox environment for the Enrollment process.

We have now released deterministic sandbox testing for the bank account API. By sending specific values in the routing number, your system can simulate different bank account verification statuses including validated, disabled_recoverable and disabled_irrecoverable. Testing bank account statuses enables you to build integration testing and QA testing around bank accounts. Learn more in our docs.

We have released the Employee Benefit Component, which enables you to easily embed support for benefits in your product. Employers can configure benefits for a specified employee in this component, as well as view benefits managed by our benefit partners. Read more in our documentation.

Companies with no year to date payroll history can now be submitted to Check for implementation while employees and contractors are in a blocking onboard status. The employees will still need to reach a non-blocking onboard status to be eligible for payroll.

You can now find accepted file types for document requests in the Requirements API. We recommend using these in your in-product guidance for customers uploading documents. Read more about the Requirements API and accepted file formats here.

We have released a new Check Component which enables you to easily embed support for post-tax deductions in your product. Employers can list, create, edit, and delete both child-support and miscellaneous post-tax deductions for a specified employee in this component. Read more in our documentation.

Contractors are now listed in alphabetical order by name and then business name in the contractor lists API, displays in Console and all related components, making it simpler for you to find the information you need.

Console now offers the ability to void paid-in-quarter payrolls! The payroll must have a listed payday in the current quarter and must be in 'paid' or 'partially paid' status. Voiding out-of-quarter and failed payrolls will still require reaching out to Check Support.

Console now offers the ability to create and view a company’s pay schedule. Pay schedules offload the work of calculating period start, period end, and payday for a company to Check. You can also view all future pay dates for the company. To learn more about pay frequency and pay schedules, see our docs here.

Different payment types will now have unique transaction descriptions in employers’ bank statements, giving customers better visibility into their money movement. For example, employers will see the description "[Partner Payroll Name] TAX" as the description on their bank statements for upcoming Q2 variance collection and refund transactions. 

The full range of payment types and the associated descriptions is available in our Glossary. The Glossary will empower your Support teams to promptly address any inquiries from employers regarding payment types; additionally, we recommend sharing the glossary with your employers through another visible product surface for their convenience.

Stay tuned for additional enhancements as we make the payment experience at Check more simple and intuitive!

‍

We have released a new Check Component which allows you to easily embed a Profile UI in your employee payroll experience. Through this Component, employees can view their payroll information including general demographics and details, payment methods and linked bank accounts, and workplaces they have been assigned to. Learn more about this component in our documentation.

You can now view the status of a company’s legal name and Federal EIN verification in Console, as that match is checked against information from the IRS. You can update the company’s legal name and FEIN directly on this feature and trigger a new verification attempt. Please be aware that if there are 3 unsuccessful verification attempts, further attempts will be disabled and the customer will be required to upload documents.

You can now create employee objects with only a last_name; residence, date_of_birth and start_date are no longer required. This change allows employers to send employees onboarding links to fill out their own residences and DOBs, rather than the employer needing to provide this information. Note that while these fields do not block employee creation, they are necessary before paying an employee and will cause a blocking onboard status. Read more about this process in the onboard status guide and the reference to create an employee.

You can now remove the “X” button to close a component from the top-right of components, which can be confusing for components embedded directly in your product. To read more about this ability, check out our guide to customizing components.

You can now create, view, and edit the active status of employee Earning Rates in Console! This allows Console users to manage employee compensation when necessary. Earning Rate view and configuration can be found in the “Earning Rate” tab on the employee profile page. Learn more about Earning Rates in our API docs.

We have released two new endpoints to the company resource which allow updates to a company’s implementation status: /start_implementation and /cancel_implementation. This change enables you to add Console’s confirm and submit logic directly in your product, as well as giving you the ability to un-submit a company if its implementation status is not yet complete. Read more about these new endpoints in our API docs.

Employers can now view and edit earning descriptions in the Run Payroll Component. These descriptions will appear directly on the employee paystub and are particularly useful for employers and employees to distinguish between earnings of the same type (e.g. hourly).

You can now initiate a company’s termination directly from its Company Details page in Console rather than creating a support ticket, streamlining the termination process for you. Additionally, you will be able to view details about a company’s termination refund in Console.

You can now see tax liabilities and their associated statuses right in Console! Navigate to the Tax Deposits tab for a Company to view the comprehensive list of historical tax deposits. Alternatively, navigate to the particular Payroll Journal to view the breakdown of Tax Deposits for a payroll. Visit our Knowledge Base and API Docs for more information on Tax Deposits.

You can now find details about terminated companies in Console on the Company Info page, including termination date and reason.

Console now shows a payroll’s Payment Method(s) in addition to its Funding Method, giving you better visibility into the ways employees and contractors were paid. For payrolls in which all workers were paid manually, Console now provides additional information to clarify payroll status and tax payment timing.

You can now edit all fields on employees and contractors in Console, except for SSNs and workplaces (coming soon), directly on the employee or contractor detail page. This feature enhances the Console experience, allowing you to modify these fields with the same ease as you would edit a company detail. To update a worker’s information, click the edit icon on the employee or contractor detail page. We will continue to send webhooks when you update information in Console.

We have released four new Check Components aimed at viewing and downloading documents. You can now embed Check Components that allow companies, contractors, and employees to view tax and authorization documents so you don’t have to build these experiences yourself. See our documentation to learn more about our Company Authorization Document, Company Tax Document,  Employee Tax Document, and Contractor Tax Document components.

You can now easily find which employees and contractors have invalid SSNs by generating real-time reports of all employees and contractors with invalid SSNs in Console. We have also added a new field “ssn_validation_status” to the employee object and contractor object in the API. These changes should enable you to save time and streamline the process of fixing these incorrect IDs.

You can now test the Company Review process in Sandbox. You will start to see webhooks when the `company.implementation.kyb_status` field changes through its lifecycle of not_initiated, in_review, and then approved.

Employees are now listed in alphabetical order by default in the employee lists API, employee displays in Console, and all related components, making it simpler for you to find the information you need. The same change for contractors will be coming soon!

We’ve added two new data fields to Check’s reporting functionality including viewing company “Standing” in the Funding Failures report and now you can include a worker’s “Active” status in our Custom Report Builder. Use these new fields to make analyzing funding failures and active workers more seamless for your Operations teams.

We’ve added ACH trace numbers in the Console view of Payment Attempts, so that you can provide them directly to employers who reach out for tracking information to understand where their payments are.

You can now filter Console’s Action Center to only view document requests related to companies you oversee. This feature enables a more tailored Console experience by allowing you to view only outstanding requests relevant to you. To use the filter, simply start typing your email address into the “Account Contact” filter field. You must be sending account contact information via the Enrollment Profile in order to take advantage of this feature.

You can now include contractors in both the Payroll Summary and Payroll Journal reports. When downloading the report, just check “Select to include contractors” and they will be included in the reports.

We’ve added support for two new optional query parameters for the Employee Paystubs API endpoint, enabling users to retrieve paystubs within custom payday date ranges. This enhancement provides more flexibility than the previous restriction of displaying only the most recent paystubs for an employee, starting from today’s date.With the new `start` parameter, users can retrieve paystubs that have payroll paydays starting on or after the specified date. The `end` parameter will retrieve paystubs that have payroll paydays ending on or before the specified date. Together, these two parameters will allow users to filter paystubs based on a specific payroll period.

You can now deactivate and terminate employees in Console, deactivate workplaces for contractor only companies in Console, delete Console users and view Contractor pay statements.

Our payrolls list endpoint will now return results sorted in descending order by payday, in both our API and in the display in Console. In cases where multiple payrolls have the same payday, payrolls that are created more recently will come first.

If a company has specific earning needs that are not covered by default earning types, they can create custom earning codes. For example, a company might want to differentiate earnings from different parts of the day, which they can do by creating “Hourly - Day” and “Hourly - Night” earning codes. To bring Components to parity with the power of our APIs, these custom earning codes can now be selected as earning types in the Run Payroll Component. Learn more about using earning codes and the Run Payroll Component in our documentation.

You can now generate individual component links for customers in Console to send customers specific onboarding steps such as Filing Authorization and Tax Setup. Previously, Console users could only send customers a link to the entire Onboard flow; this change enables you to provide customers a more tailored experience for the onboarding steps they need to complete. When you click the new Generate Component Link button, you’ll see a dropdown of options which still includes the entire onboard flow (“Onboard”), as well as options for individual steps.

We’ve released deeper customizations of Check Components, enabling Components to appear native to your product. When creating Components to embed in your product, you can now specify the font family, monospace font family, and primary color to modify the appearance of Components. Out of the box, you can specify any web-safe font family, but you can also provide a custom font source for Components to use, allowing Components to closely fit your brand.

Employee Paystubs can now be downloaded in Console. If you go to an Employee profile in Console and head to the new Paystubs tab, you can download any paystub for an employee for a payroll they have participated in. They are sorted by most recent payday.

As soon as you “Confirm and Submit” any company that does not have any Year-to-Date payroll history in Console, they will instantly be able to run their first payroll. This change allows for faster go-lives and will also reduce pain in instances of delayed start dates. Check will continue to send a Zendesk ticket when our internal setup processes are complete, but these processes no longer block first payroll approval.

We're changing how we share failed filings for Q1. Instead of placing them in a Google Sheet like in previous quarters, we'll upload them to a new report in Console called Failed Filings. In addition to filings that have failed, you will be able to view the refiles that Check has requested, enabling you to get an up-to-date picture of employers that still have unresolved filing issues.

We will be sending additional webhooks for payrolls. Payroll webhooks are currently sent when any payroll lifecycle event occurs, resulting in a payroll changing statuses. With this enhancement, Check would additionally send webhooks upon payroll creation, update, and deletion. You can use these webhooks to keep your database in sync with Check’s; for example, if a payroll is modified through the Run Payroll Component, you’ll receive an update webhook and be able to store the updated state locally. We’ve enabled these webhooks in the Sandbox environment to enable you to test receiving these webhooks. Once you give us the go-ahead, we’ll enable them for you in your production environment.

Following last week’s release of Action Center, you can now filter document requests in Console to show only Live companies, making it easier for your team to find the relevant companies for them. Live is defined as non-terminated companies that have approved a payroll. Additionally, we have added a link in the Company column to each relevant company to make it faster to complete any task.

Console’s Company page now groups all company statuses and standing conditions at the top of the Company page, so you have to scroll less to get all the information you need.

The Idaho Department of Labor has reactivated its Administrative Reserve Tax Rate effective for 2023. In response, Check will now require employers to provide this rate, and update their SUI and Workforce Development Rate if needed. The agency sent tax rate notices to all Idaho employers in December with their 2023 rates. Employers can provide and update their rates in the Idaho Tax Setup portion of Employer Onboard under the Idaho Special Administrative Reserve Surtax section. Note: This rate is required as soon as possible but will not block the employer from running payroll. Employers must provide this rate to ensure accurate payments.

You can now find the status of all document requests in a new section of Console called ‘Action Center.’ In the Action Center, you’ll see a feed of all document requests sorted by the most recent status updates. You can filter the requests to see only those which require action (“Open” or “Failed”), or view all historical requests, including those in “Pending” or “Resolved” statuses. Learn more about document requests in the knowledge base.

The Connecticut State Unemployment Insurance (SUI) Power of Attorney Company Filing Authorization Form for Connecticut employers is now available in Check. Existing employers in Connecticut will be put into a “Needs Attention” state until they complete this form but will still be able to run payroll. New Connecticut employers will need to sign and submit this form during the onboarding process, before being able to run payroll. This should happen via Employee Onboard or via the Forms API. Learn more about the Onboard Component here.

You can now see all bank verification document requests in Console within minutes of an Employer linking their Plaid account. This release drastically reduces instances of bank verification document requests coming through Zendesk later in the company enrollment lifecycle. This change comes as part of a broader effort to both make document requests predictable and available upfront during the Company Review process and to strengthen Check’s ability to detect fraudulent companies. Outstanding bank verification document requests will still block payroll, but these document requests will be surfaced much earlier in the enrollment process. Document requests will continue to be displayed in both the API and in Console (in the Company Actions view). Learn more about the bank verification process in our API docs.

You can now modify the payment method of payroll items and contractor payments when creating and editing payrolls in Check Console. This can be useful for uploading any remaining payrolls before the end of the year, as you can now mark them as all-manual with a payday in 2022.

The Arizona Department of Revenue (DOR) has updated Form A-4, Employee’s Arizona Withholding Election. Starting this Friday, December 23rd, please prompt all employees with workplaces in Arizona to submit a new 2023 Arizona A-4 Form in Employee Onboard. The 2023 form comes with a new set of withholding rates and a new default rate available for Arizona employees. Check will not block an employee if they do not fill this form by January 1, 2023, but we will default them to a withholding rate of 2%, per state guidance. For more information on this new form, see the Arizona DOR FAQ.

In Oregon, per the 2023 state requirement, Check will withhold the Paid Family and Medical Leave Insurance tax (PFML) for all employees and for employers with 25+ employees. Please prompt all employers with workplaces in Oregon to answer additional OR PFML questions in Employer Onboard or in your product via API. Check will put the employer in a `needs attention` Onboarding state until the employer answers these questions. Employers will not be blocked from running payroll due to this change. 

If you have current employers affected by this change, you will receive a follow-up from Check with proposed communication to these employers alongside a list of impacted employers. For more information on this new PFML, see the Oregon agency website.

In Colorado, per the 2023 state requirement, Check will withhold the Paid Family and Medical Leave Insurance tax (PFML) for all employees and for employers with 10+ employees. Please prompt all employers with workplaces in Colorado to answer additional CO PFML questions in Employer Onboard or in your product via API. Check will put the employer in a `needs attention` Onboarding state until the employer answers these questions. Employers will not be blocked from running payroll due to this change.

If you have current employers affected by this change, you will receive a follow-up from Check with proposed communication to these employers alongside a list of impacted employers. For more information on this new PFML, see the Colorado agency website.

You now generate company-specific corrections templates in Console. When an employer needs to make a payroll correction, navigate to the company page, click the reports tab, and click the blue “Download Payroll Template” button. After completing all required information, submit the payroll correction template to Check Support via the support portal (ticket category “Correct Payroll”). Please download this template each time you need to make a correction, as the template may change over time with new taxes and earning codes. See a demo and learn more about Making a Payroll Correction in the Knowledge Base.

To reward businesses that consistently fund their payrolls and mitigate the impact of failed fundings, we've rolled out two new policies related to Company Processing Period, effective Monday, December 12, 2022. This includes a “Graduation” process and a “Downgrade & Exit” one for changing a business’ payroll processing period. To learn more, visit the Company Graduation, Downgrade & Exit Processes Guide in the Knowledge Base.

You can now report 2% Shareholder Benefits and HSAs using the Run Payroll Component in Console. To do so, you’ll need to run an off-cycle payroll on behalf of your employers. This feature will allow you to handle reporting these benefits and HSAs without integrating with our 2% shareholder earnings via API. Please note, 2% Shareholder Group Term Life must still be reported by an employer on a payroll with regular or supplemental pay using the regular `group_term_life` earning. To learn more, see our 2% Shareholder Reporting Guide in the Knowledge Base. See a demo of the process here. 

After submitting one file to satisfy a requirement in Console, you will now see the ability to upload another file for the same requirement. You may choose the same type of file or different types of files for that requirement. See how it works in this demo.

You can now view the company signatories, and create new signatories, on the company detail page in Console. Companies going through enrollment use signatories to sign forms and initiate company review. With signatories, the enrollment profile, and tax setup information in Console, you can now enter all information to initiate company review for a business via Console. Learn more about signatories here and their use in the company enrollment process here.

You can now create, edit, and view payrolls in Console. To create a new payroll, you can navigate to the list payrolls view for a company. To edit a payroll, navigate to that payroll and click the Edit button. This enables integrating partners to create, edit, and approve payrolls more quickly, removing the need to integrate with Check’s flows for running payroll. This release also helps ensure a successful year-end, as you may need to handle support cases that you may not have support for in your product, like 2% shareholder payouts. In these cases, you can create a payroll in Check in Console with the appropriate earnings. See how it works in this demo.

Check now offers a variety of new CSV reports for download in a new Tax Inputs report page in Console (see below). Reports include

1. Companies with outstanding Applied For IDs by state jurisdiction
2. Companies with outstanding Applied For IDs by individual ID
3. Outstanding company and employee tax inputs needed for successful Year-End filings, such as MD NAICS codes, WA SOC codes, and IN residency and employment county codes.

You can now edit the company enrollment profile on the company detail page in Console. Learn more about Check company enrollment here.

Check now offers new earning types for 2% shareholders via the API, including `2_percent_shareholder_benefits` and `2_percent_shareholder_hsa`. These earning types are only available to employees that are 1) identified as a 2% shareholder in the company-defined employee attribute field and 2) employed by an S-Corp or LLC company. See our docs for more information on Group Term Life earning types for 2% shareholders. 

Please note that all S-Corp and LLC employees will be placed in a ‘needs attention’ state until the company-defined attribute has been updated, but this will not block payroll. You are able to set this status in Console or using the API, and employers will be able to set this status using Employer Onboard. You can update the 2% shareholder earning types today via API integration or wait for support in Console later this month. Learn more about 2% shareholder earning types here.

You can now edit company legal name, trade name, website, business type, and industry type on the company details page in Console. 

The state of Indiana has released a new version of the withholding form (WH-4), which allows employees to claim additional exemption for each adopted qualifying dependent during calculation of the state and county income taxes.

Going forward, Check will surface a new parameter during Indiana employee onboarding, which is used to collect the number of adopted qualifying dependents each employee has. Should employees who previously onboarded wish to take advantage of the new exemption, they can do so by signing and submitting the WH-4 form again.

You can now view and take action on document requests for company review in Console. Use the new Company Actions tab in Console to submit and monitor the status of outstanding document requests. Check will continue to use Zendesk to communicate company review outcomes and manage requested documents in order to minimize disruption to our partners’ current processes. However, we encourage all partners to migrate this workflow to Console for faster document verifications and a more seamless experience. For a walkthrough of the Company Actions workflow, see this loom video.

The Requirements API now provides the ability to identify payroll funding failures for a given company as well as track the funding recovery process for failed payrolls. Leveraging this API, you can now identify outstanding funding failures for a given company and receive funding status updates. Companies that fail to fund payroll will be blocked from running additional payrolls until the funds are recovered. Learn more about identifying and resolving funding failures here.

Employees can now opt into paperless delivery of W-2 statements using a checkbox in the Employee Onboarding component. Similarly, the Contractor Onboarding component will also provide a checkbox where contractors can opt into paperless delivery for 1099s.

You can also manage consent for paperless delivery of annual tax statements in Console, using the Employee or Contractor Info pages. This enables you to reflect any changes in the worker’s delivery preferences that are collected outside of your product. To learn more about managing delivery methods for W-2 and 1099 statements, check out our knowledge base.

The state of Washington now requires all companies to provide a Standard Occupational Classification (SOC) code for each employee. As such, when onboarding new employees in Washington going forward, Check will prompt each employer to provide an appropriate SOC code on each employee’s behalf. There is no integration work required on your end. 

If an employee is missing a SOC code, their Onboard Status will remain in ‘needs_attention’ state. While the ‘needs_attention’ state does not interfere with running payroll, Check will need this information by the year-end in order successfully file taxes. 

Check will provide separate guidance by November 1 on how to backfill this information for existing employees in Washington.

The state of Maryland now requires every company to provide a North American Industry Classification System (NAICS) code on the state’s annual reconciliation statement. As such, when onboarding new employers in Maryland going forward, Check will prompt each employer to provide an appropriate NAICS code. There is no integration work required on your end. 

If the employer does not provide a NAICS code, their Onboard Status will remain in ‘needs_attention’ state. While the ‘needs_attention’ state does not interfere with running payroll, Check will need this information by the year-end in order to successfully file taxes. 

Check will provide separate guidance by November 1 on how to backfill this information for existing employers in Maryland.

You can now use an options array to company-defined attributes of type boolean. This will enable presenting more user-friendly options when surfacing boolean company-defined attributes. Instead of presenting True and False, you can now present Yes and No. Learn more about retrieving and updating company-defined attributes here.

We have updated some language in Check Onboard to increase clarity for users. Previously, where contractors were asked to provide a TIN, they will now be asked to provide an Identification Number. This term is used to encompass a Social Security Number (SSN), Employee Identification Numbers (EIN), or an Individual Taxpayer Identification Number (TIN). Learn about managing contractors in Check Onboard here.

You can now change the processing period of a company or individual payroll in Console. This change can be made on the company’s page in Console, or for draft payrolls in the payroll journal. If a company has not been approved for 2-day processing, this option will be greyed out. If you would like to upgrade a company to 2-day processing, reach out to Check Support.

You can now change the processing period of a company via the Check API. This will affect all new, nonexistent payrolls. If a company has not been approved for 2-day processing, you will receive an error message. If you would like to upgrade a company to 2-day processing, reach out to Check Support. Learn more about updating the company object here.

You can now use the Custom Report Builder in Console to generate reports that include information about custom earning codes and earning rates. This enables the creation of reports that detail earning information and aggregate gross pay amounts earned at different rates and codes. Learn more about the Custom Report Builder here.

You can now view the payment method of a payroll in both Console and in the payroll journal downloadable report. This allows you to differentiate between direct deposit and manual payrolls to employees. Learn more about payment methods in the payroll item here.

You can now create more than one benefit or post-tax deduction object at once in Console. With this new company-level, bulk upload workflow, you can upload all relevant information via CSV. Learn more about creating employee benefits and post-tax deductions in Console here.

When uploading a quarter of payroll history, Check will now smartly detect if the quarterly payroll starts and ends on a quarter start and quarter end. If it does, we will audit the uploaded payroll using a quarterly pay frequency. As a result, you will start to see less variances when uploading quarterly payrolls.

We have released a new component that allows employers to input all of the necessary enrollment details required to kick-off company review. Partners can use this component to facilitate getting important company review decisions earlier in onboarding, such as company eligibility and processing period. Learn more about the Early Enrollment Component here.

You can now serve employees that live in Missouri and work in another state, work in Missouri and live in another state, or who split their time working in Missouri and other states. Now, any new multi-state employees onboarded will be automatically prompted to provide the percent of time worked in Missouri while filling out the form MO-W4A surfaced via the Tax Setup API or Onboard. Please refer to the employees’ MO-W4A and MO-W4C Forms if you have multi-state employees that are switching from another payroll provider.

You can now query the Requirements API to surface what information is required to unblock payroll. For example, you can use the Requirements API to build an in-product experience to upload documents to Check during company review. Today, this includes document requests during company review, document requests for bank account verification, and required tax IDs that are in an “applied for” state. Additional use cases coming soon. Learn more about the Requirements API here.

You can now generate a report of the tax IDs that are marked “applied for” for a given company. The report is available as a CSV or as a paginated list. Learn more about the “applied for” IDs report here.

You can now see whether an employee was paid as `direct_deposit` or `manual` in the JSON body for the paystubs endpoint. This added granularity allows you to inspect paystubs by payment method to provide more flexibility in how you choose to leverage this endpoint. Learn more about paystubs here.

You can now request specific API resources in bulk. When the `id` query parameter is used in requests to resource list endpoints such as `/employees` and `/workplaces`, only the specified resources will be returned. Fewer API requests can help improve performance and simplify many use cases. Learn more about bulk requests here.

You can now use the `/company_provided_documents` endpoint to upload documents directly from employers to Check. The current supported document types are geared towards helping with follow-up documentation requests during company review. Additional document types and corresponding Console functionality coming soon. Learn more about uploading company provided documents here.

Companies can now update company legal name, legal address, and phone number in Company Onboard, and administrators can update the company phone number in Console. Legal name and legal address can only be updated before company review is initiated. As always, ensure your system stays in sync with these updates by listening to company update webhooks. Learn more about the company object here.

You can now include an employee’s ID as an additional column in our Payroll Journal Report.  When the new query parameter ‘include_employee_id’ is set to true or the ‘Select to include employee ID’ checkbox is selected in Console, we’ll include the new column. Learn more about accessing the payroll journal via API here or visit our Payroll Journal Reports page in Console.

You can now configure any child support garnishment to have payments remitted by Check, regardless of the garnishment’s state agency. This week we’ve added support for Alaska, DC, Hawaii, Iowa, Kentucky, Minnesota, New Jersey, North Dakota, Pennsylvania, Rhode Island, South Dakota, and Wyoming. To enable remittance by Check via the API include `managed = true` when creating or updating thepost-tax deduction object. To enable it via Console, check the “Managed (Payment Remitted by Check)" box on the Child Support object. Learn more about Child Support Garnishment Remittance here.

You can now create a company object in Check without any of the fields that were previously required (legal name, phone number, address). This update offers more flexibility for custom onboarding flows, making it simpler to create companies and any associated entities with fewer required fields. When a legal name is not provided at creation time, it must subsequently be updated via API using the company ID. Please note that in order for a company to be visible in Console, or to generate links for onboarding, a company legal name and address are required. Learn more about the company object here.

You can now create a company with the company object using only the legal name. This improvement allows you to create company objects earlier and adds flexibility to when you collect address and phone number data in your onboarding flow. While no longer required at company object creation, company address and phone number are still required to initiate enrollment with Check. Learn more about the company object here.

Check is exposing two new API resources, the Enrollment Profile and the Signatory. These APIs enable smooth enrollment processes for your clients. You can read more about them in the Guide to Company Enrollment.

‍

Check will now remit payments to the child support agencies in Vermont and West Virginia. For Check to remit the payment, you will need to add the garnishment via the post-tax deduction object and mark ‘managed = true’. See which states Check supports for child support garnishments remittance here. 

We have released a new and improved version of our Tax Setup Onboarding Component that will streamline the tax setup workflow for employers. This new experience includes SUI rate validation (in both the Tax Setup UI and API), SUI rate guidance for new employers, detailed tax parameter labels and descriptions, support links, and more. Learn more about the Tax Setup Component here.

You can now determine the status of company tax deposits with the new List Tax Deposits endpoint. A ‘tax deposit’ refers to a payment that a company owes to a tax agency for any payrolls run on Check. Learn more about tax deposits here.

You can now create multiple items for a payroll concurrently. To create items in bulk, pass in a JSON array of payroll items when making a `POST` request to the `payroll_items` endpoint. Learn more about creating payroll items here.

You can now add contractor payments to payrolls using the Run Payroll Component. Without any additional engineering work or configuration, you can now set payment and reimbursement amounts for both individual and business contractors. Learn more about the Run Payroll Component here.

A new, optional question asking employers to enter the number of W-2 employees they expect to pay has been added to Company Onboard. This will help Check's risk team more accurately assign payroll processing decisions during the enrollment process. Learn more about Check Onboard components here.

Check will now remit payments to the child support agencies in Alabama, Delaware, Idaho, Maine, and New Mexico. For Check to remit the payment, you will need to add the garnishment via the post-tax deduction object and mark ‘managed = true’. See which states Check supports for child support garnishments remittance here.

Check will now remit payments to the child support agencies in South Carolina. For Check to remit the payment, you will need to add the garnishment via the post-tax deduction object and mark ‘managed = true’. See which states Check supports for child support garnishments remittance here.

Check will now dynamically verify a Company’s Federal EIN submitted via Check Console or the Tax Setup API. Normally this verification will take less than 10 seconds. Learn more about Automatic Federal EIN Verifications here.

Check will now remit payments to the child support agencies in Nebraska, Maryland, Ohio, and Missouri. For Check to remit the payment, you will need to add the garnishment via the post-tax deduction object and mark ‘managed = true’. See which states Check supports for child support garnishments remittance here.