Skip to main content

Standalone Flows

Standalone flows are the most basic flows and are used to create a single service order for the following services:

For ordering and API examples, start at Partner products overview.

Certain services (e.g., Foreign Qualification, Registered Agent, State Unemployment Insurance) are fulfilled using a multi-step, API-driven workflow designed to accommodate jurisdiction- and entity-specific requirements.

Flow Overview​

  1. Partner collects baseline business and order information (order placed)
  2. Partner submits order via API
  3. Swyft evaluates filing requirements based on jurisdiction and entity type
  4. Swyft may return additional required inputs via questionnaire or required actions
  5. Partner collects and submits any additional inputs from the questionnaire in Step 4
  6. Swyft completes the filing and returns:
    • status updates
    • filing confirmations
    • registration identifiers

How to Integrate​

Partners should design for a multi-step intake flow, rather than assuming all required inputs are known at initial order creation.

  • Use the order endpoints to create and track orders
  • Use input field / required action endpoints to retrieve additional requirements
  • Continue submitting data until all required inputs are satisfied

Important Notes​

  • Requirements vary by jurisdiction and entity type. Dynamic requirements may be surfaced after order submission through questionnaires or required actions.
  • Additional requirements may be identified during processing, even after questionnaire submission.
  • Swyft ensures completion of filings, including handling of edge cases and exceptions.

The steps below use the EIN application as an example. Other standalone products follow the same pattern (place order, complete intake or questionnaire, processing, completion), with product-specific statuses and notifications.

Successful path​

When the filing proceeds without rejection, the order moves from placement through review and processing to completion.

Step 1 — Order placed and questionnaire opened​

  • (Customer) places the EIN order.
  • (SwyftFilings) completes the new order on our side.
  • (Customer) sees the questionnaire in the account under My Tasks in the iframed customer portal.
  • (SwyftFilings) waits for the questionnaire response.

Step 2 — Questionnaire submitted and order under review​

  • (Customer) submits the questionnaire (EIN Questionnaire = Submitted).
  • (Customer) receives the “under review” notification: We have received your EIN Application, a member of our team is preparing your application.
  • (SwyftFilings) sets order status to Under Review.

Step 3 — Application filed with the IRS​

  • (SwyftFilings) submits the application to the IRS (EIN = Filed).
  • (SwyftFilings) sets order status to Processing.
  • (Customer) receives the processing notification: Your EIN Application is being processed. We will notify you once your EIN is ready.

Step 4 — EIN approved and order complete​

  • (SwyftFilings) receives IRS approval (EIN = Approved).
  • (SwyftFilings) sets order status to Complete.
  • (Customer) receives the completion notification (order type and EIN values come from your CRM), for example: Your [Order Type] is complete! The IRS has issued the following EIN for your company: [EIN]. Your official EIN letter (CP-575) will be mailed to your mailing address from the IRS directly. All documents provided are now uploaded to your account and electronically stored for you to download immediately anytime, 24/7 under the My Documents tab.
  • (Customer) can view the EIN in the account under My Tasks.

Path with additional requirements or government rejection​

If the state or federal government entity rejects the filing, the customer is notified, provides what is needed, and SwyftFilings resubmits. Steps 1–3 match the successful path; the branch below begins after the application is filed.

Steps 1–3 — Same as the successful path​

Follow Step 1 through Step 3 above.

Step 4 — Additional requirements or rejection​

  • (SwyftFilings) identifies additional required information or receives a rejection from the filing authority.
  • (Customer) receives a notification with the specific requirement or reason, for example: There is an issue with your application that requires additional information. [Dynamic reason]. Please respond here.
  • (SwyftFilings) waits for the customer’s response.

Step 5 — Customer responds; application resubmitted​

  • (Customer) provides the requested information or corrections.
  • (SwyftFilings) resumes processing (including re-submission if required).

Step 6 — EIN approved and order complete​

  • (SwyftFilings) receives IRS approval (EIN = Approved).
  • (SwyftFilings) sets order status to Complete.
  • (Customer) receives the same completion notification pattern as in Step 4 of the successful path.
  • (Customer) can view the EIN in the iframe portal account under My Tasks.