Changelog

We’ve launched Suspensions APIs and Flows to support the programmatic suspension of companies.

Gusto Embedded has partnered with Guideline to provide a seamless and convenient, fully online platform for partners so their end-customers can offer retirement plans. Check out our 401(k) Guide and Flow Types for more information.

Gusto Embedded now supports the reverse_wire_accounts flow type. Some customers routinely process large payrolls that require manual wire transfers, which can be inconvenient and delay payroll processing. The reverse_wire_accounts flow enables customers to authorize Gusto to pull funds via reverse wire. Once set up, no additional manual action is required, ensuring a hands-off and automated way to fund payroll when the ACH limit is reached.

Previously, Gusto utilized the concept of “soft suspends” to encourage customers to provide missing or invalid state tax information. For example: if a filing failed due to a missing state EIN, Gusto would place a pending soft suspension on that state tax field and a customer would have 15 days to fix (edit, update, enter, etc) the invalid information. After 15 days, the customer would be “soft suspended” and blocked from running additional payrolls. If this soft suspension was never resolved, the company would be “hard suspended,” which is effectively a full cancellation of the account.

Gusto Embedded now supports Flow events for pre-built UI components. Previously, you could integrate flows using an iFrame wrapper in your application, but it was unclear when an end-user completed a workflow to trigger navigation or close a containing modal in your application.

Gusto Embedded now supports employee I-9 Verification using APIs and Flows.

The following additional categories have been added to the Embedded Partner Notification System. Details on each notification can be found here:

As numeric IDs were deprecated and sunsetted in a previous API version, we recently removed support for the fields resource_id and entity_id from the webhook event payload that we send to your webhooks endpoint.

The processing_request object is returned by our Get a Single Payroll API endpoint and Prepare API endpoint to provide better visibility into whether a payroll is currently being calculated or submitted. Review our Payroll Processing Request guide for more info.

The following additional categories have been added to the Embedded Partner Notification System. Details on each notification can be found here: