Skip to content

FousMinnesota e-Services

Turn Minnesota e-Services into an API

Read your client list, bulk file summaries and demand letters for missing withholding returns from Minnesota e-Services with one API call each. A workflow can check for new demand letters each weekday morning and email you which clients have missing returns.

Works with your own Minnesota e-Services account. Fous is an independent product.

What you can build on e-Services

  • Get the client list

    Build this

    Reads Manage Client List under Manage clients in your Withholding Tax account: every client you file and pay for as a bulk filer.

    Takes
    Nothing
    Returns
    Client name, Minnesota Tax ID, count
  • Get demand letters and missing returns

    Build this

    Reads the demand letters sent for your clients and the list of missing withholding returns that e-Services shows with them.

    Takes
    Client Minnesota Tax ID (optional)
    Returns
    Client name, Minnesota Tax ID, letter name, letter date, missing return period
  • Check a bulk file's summary

    Build this

    Reads the summary for an uploaded bulk file of returns or payments: whether it appears error-free, or which errors to correct and resubmit.

    Takes
    Confirmation number
    Returns
    Confirmation number, file type, result, errors to correct
  • Make a payment for one client

    Build this

    Uses Make a payment for another account to pay one client's withholding tax and reads back the confirmation number.

    Takes
    Client Minnesota Tax ID, period, amount, payment date
    Returns
    Confirmation number, client, period, amount, payment date

Automate e-Services with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • New demand letters for missing withholding returns

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    Get the demand letters and missing returns for all your clients.
    Step 2
    Keep the letters that were not there on the last run.
    Step 3
    Email you the list, one line per client with the missing periods.
  • Errors in a bulk file, sent back to your payroll system

    Build this
    Starts
    When your system calls the workflow's webhook with a confirmation number
    Step 1
    Check the bulk file's summary for that confirmation number.
    Step 2
    Stop when the file appears error-free.
    Step 3
    Post each error to correct, with the confirmation number, to your payroll system's webhook.
  • Monthly client list check

    Build this
    Starts
    Monthly on the 1st at 7:00
    Step 1
    Get the client list from Manage Client List.
    Step 2
    Compare it with the last run and keep the clients added or removed.
    Step 3
    Email you the changes so you can match them against the clients you serve.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get the client list” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "www.mndor.state.mn.us/get_client_list",
    "input": {}
  }'
Example response
{
  "status": "completed",
  "data": {
    "clients": [
      {
        "client_name": "Acme Fabrication LLC",
        "minnesota_tax_id": "9000412"
      },
      {
        "client_name": "Northwind Dental PA",
        "minnesota_tax_id": "9000587"
      },
      {
        "client_name": "Globex Logistics Inc",
        "minnesota_tax_id": "9000633"
      }
    ],
    "count": 3
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

E-Services’s own options

The Department of Revenue documents file uploads for bulk filers, not an API. Registered third-party bulk filers upload a spreadsheet file of returns or a file of payments in e-Services and get a confirmation number and a summary of errors. Deposits can also go by ACH credit from your bank. Client lists and demand letters are reviewed in e-Services.

OptionWhat it coversWhat it takes
Upload a bulk file of returnsWithholding returns for many clients in one spreadsheet-format file, with a confirmation number and an error summary.Registration as a third-party bulk filer, and clients added to your client list.
Upload a bulk file of paymentsWithholding deposits for many clients in one file, with a confirmation number and an error summary.Registration as a third-party bulk filer, and clients added to your client list.
ACH creditWithholding deposits sent from your own bank instead of through e-Services.Arranged with your bank, which may charge a fee. Your 7-digit Minnesota Tax ID and payment data in CCD+ format with the correct addendum.
e-Services by handManage Client List, File a return and Make a payment for another account one client at a time, plus demand letters and missing returns.An e-Services login with a verification code at each sign-in.

Read on November 12, 2026: Third-Party Bulk Filers (Withholding Fact Sheet 5), Verification Codes.

Signing in to e-Services

e-Services asks for your username, password and a verification code, sent by text message or email, or taken from an authenticator app. With Fous you sign in once through e-Services' own sign-in with your own account: the login is sealed with AES-256, codes sent by email are handled, and an expired session is signed back in.

Worth knowing

Register as a bulk filer first
With a Minnesota Tax ID, you call 651-282-9999 or 800-657-3594 and say you are registering as a third-party bulk filer. Without one, you apply online and indicate that you are a bulk filer.
Clients bring their own Tax ID
A client needs a Minnesota Tax ID and a withholding account before you add them. Bulk filers cannot set up Tax IDs or update client addresses, and must update the client list monthly.
Demand letters arrive in two rounds
The first demand letter goes out about 5 days after the due date and a second about 16 days after. The letters and the list of missing returns are generally in e-Services about 5 days after the first letter.
Every file gets a confirmation number
Each uploaded file of returns or payments gets a confirmation number and a summary that says it appears error-free or lists errors to correct and resubmit.

More in Government: US state and local tax

Other industries: NCSUITS, VWR (Avantor), Bullhorn, McKesson Connect, NIPR, Collaborati.

Frequently asked questions

Not one the Department of Revenue documents for bulk filers. Its fact sheet describes uploading a spreadsheet file of returns or a file of payments in e-Services, each with a confirmation number and an error summary, and ACH credit deposits in CCD+ format from your bank.

In your Withholding Tax account, select Manage clients, then Add a Client under Manage Client List. The client must already have a Minnesota Tax ID and a withholding account, and should give you their confirmation letter.

Generally about 5 days after the first demand letter, which goes out about 5 days after the due date. Letters go to both you and your client, and a second letter follows about 16 days after the due date.

Yes. Use Upload a bulk file of payments in e-Services, or send an ACH credit through your bank with the payment data in CCD+ format. For one client, use Make a payment for another account.

No. Fous is an independent product. You use it with your own e-Services login, and a method reads and does only what that login can.

Put Minnesota e-Services behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextMy DORmyconneCTMyDORWAYNCSUITSHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Minnesota e-Services (Minnesota Department of Revenue). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.