Skip to content

FousWorkday supplier portal

Turn the Workday supplier portal into an API

Read purchase orders, invoice statuses and payments from each customer's Workday supplier portal with one API call each. Or have a workflow check every customer's Most Recent Invoices each weekday and post status changes to your ERP.

Works with your own Workday supplier portal account. Fous is an independent product.

What you can build on the Supplier Portal

  • Get purchase orders

    Build this

    Reads Most Recent Purchase Orders on the POs and Catalogs dashboard for one customer, searched by document date or purchase order number.

    Takes
    Customer, document date from (optional), PO number (optional)
    Returns
    PO number, document date, status, buyer, total, uninvoiced amount, currency
  • Check invoice statuses

    Build this

    Reads Most Recent Invoices on the Invoices and Payments dashboard for one customer, searched by due date, invoice number, invoice status or payment status.

    Takes
    Customer, invoice status (optional), due date from (optional)
    Returns
    Invoice number, supplier's invoice number, invoice date, due date, invoice status, payment status, total
  • Get payments

    Build this

    Reads Most Recent Payments on the Invoices and Payments dashboard for one customer: what was paid, by which payment type and with which reference.

    Takes
    Customer, payment date from (optional)
    Returns
    Payment date, payment type, payment status, currency, amount, supplier reference number, transaction reference
  • Create an invoice from a purchase order

    Build this

    Runs Create Invoice from Purchase Order: picks a PO with an uninvoiced amount, fills in the invoice, attaches the PDF on the Attachments tab and submits it.

    Takes
    Customer, PO number, supplier's invoice number, invoice date, control total amount, invoice PDF
    Returns
    Invoice number, status, PO number, control total amount

Automate the Supplier Portal 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 purchase orders from every customer

    Build this
    Starts
    Every weekday at 7:00
    Step 1
    For each customer you name, get the purchase orders dated in the last 7 days and keep those in Issued status.
    Step 2
    Keep the POs that were not there on the last run.
    Step 3
    Email you the list, one section per customer.
  • Invoice status changes, posted to your ERP

    Build this
    Starts
    Every weekday at 9:00
    Step 1
    For each customer, check Most Recent Invoices with their invoice status and payment status.
    Step 2
    Keep the invoices whose invoice status or payment status changed since the last run.
    Step 3
    Post each one, with its supplier's invoice number and total, to your ERP or Slack webhook.
  • Payments received, handed to accounting

    Build this
    Starts
    Every day at 18:00
    Step 1
    For each customer, get Most Recent Payments from the last 2 days.
    Step 2
    Keep the payments that were not there on the last run, and stop when there are none.
    Step 3
    Post date, payment type, amount, currency and references to your accounting webhook.

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 purchase orders” 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": "myworkday.com/get_purchase_orders",
    "input": {
      "customer": "Acme",
      "document_date_from": "2026-11-01"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "customer": "Acme",
    "purchase_orders": [
      {
        "po_number": "PO-0031842",
        "document_date": "2026-11-10",
        "status": "Issued",
        "buyer": "Procurement Services",
        "total": 4260,
        "uninvoiced_amount": 4260,
        "currency": "USD"
      }
    ],
    "count": 1
  }
}

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.

The Supplier Portal’s own options

Each customer sets up the Supplier Portal in its own Workday: it creates your account and chooses which dashboards and worklets you see. Workday's supplier documentation describes the portal in the browser and no API for supplier accounts. With the Unified Supplier Portal, one Workday Central Login account reaches every customer that grants you access.

OptionWhat it coversWhat it takes
Unified Supplier PortalPurchase Orders, Invoices, Payments, Catalog, Contact and Banking for each customer, opened from the Customer Directory.A Workday Central Login account, and access granted by each customer. Not every customer turns it on or enables every app.
Catalog Load Request for SupplierLoads catalog items to the customer's catalog in Workday.The POs and Catalogs app, where the customer has enabled it.
The Supplier Portal by handThe POs and Catalogs and Invoices and Payments dashboards, one customer at a time, with a printable PDF of each PO.A supplier contact account that each customer creates for you.

Read on November 12, 2026: Concept: Unified Supplier Portal for Suppliers, Set Up the Supplier Portal, Concept: Supplier Portal.

Signing in to the Supplier Portal

Suppliers sign in through Workday Central Login with an email address, a password and multifactor authentication by authenticator app or SMS, which is required even where SSO is set up. A customer can add an emailed six-digit passcode before its Procurement Portal. With Fous you sign in through Workday's own sign-in with your own account, and the login is sealed with AES-256.

Worth knowing

One customer at a time
You open each customer's Procurement Portal from its profile in the Customer Directory. Customers that have not taken up the Unified Supplier Portal keep their own Supplier Portal, outside the USP.
Your customer decides what you see
Each customer adds or removes worklets on your dashboards, and not every customer enables every app in the USP. A method reads what that customer shows your account.
Uninvoiced amounts count paid invoices only
In one customer's guide, the uninvoiced amount on Uninvoiced POs ignores invoices that are in progress or approved but not yet paid. Read invoice statuses alongside it before invoicing again.
A submitted invoice cannot be edited
After you submit, the invoice shows In Progress and can no longer be edited. You cannot invoice more than the PO's remaining balance.

More in Procurement

Other industries: Sage Intacct, 微信公众平台, Auto Integrate, ACV Auctions, The Work Number, BuildingConnected.

Frequently asked questions

Not for supplier accounts in Workday's supplier documentation. It describes the portal in the browser, set up by each customer in its own Workday, and the Unified Supplier Portal, where one Workday Central Login account reaches every customer that grants you access.

Partly. The Unified Supplier Portal lists your customers in the Customer Directory, but only those that grant you access, and you open each one's Procurement Portal in turn. With Fous, a workflow can loop over your customers, call the same method for each and email you the result.

Open the Invoices and Payments dashboard for that customer. Most Recent Invoices shows each invoice's status and payment status, and View More Details searches by invoice number, supplier reference number, invoice status or payment status. Most Recent Payments lists the payments themselves.

You cannot invoice more than the balance left on the purchase order, and the line extended amounts must equal the Control Total Amount.

No. Fous is an independent product. You use it with your own Workday supplier account, and a method reads and does only what that account can.

Put Workday supplier portal 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 nextNalandaAvettaISNetworldSage IntacctHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Workday supplier portal (Workday). 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.