Get your PSW reports and deferral changes through an API

What you can build on PSW

• Get deferral changes

  Build this

  Runs the Deferrals Report from Run Reports for one plan and a date range, and reads each participant's deferral changes.

  Takes

  Plan number, from date, to date

  Returns

  Employee ID, participant name, source, previous deferral, new deferral, change date

• Get contributions received per batch file

  Build this

  Runs the Detailed Contribution and Adjustment History report: the contributions and loan repayments Fidelity received on each batch file submitted.

  Takes

  Plan number, report type, from date, to date

  Returns

  Batch, received date, participant, source, contribution amount, loan repayment amount

• Get participants with loan balances

  Build this

  Runs the Annual Loan Balance report from Run Reports: participants with an outstanding loan balance above 0 on the first or last date chosen.

  Takes

  Plan number, from date, to date, division (optional)

  Returns

  Employee ID, participant name, loan ID, outstanding balance on each date

• Enter one participant's contribution

  Build this

  Under Manage Data, creates a DC: Contributions file with Enter data manually, fills the amounts by source for one participant and submits it to check for errors.

  Takes

  Plan number, file name, employee ID, amount per source

  Returns

  Tracking number, file name, participant, source, amount, errors

Automate PSW 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.

• Deferral changes to payroll before each payroll run

  Build this

  Starts

  When your payroll system calls the workflow's webhook with the pay period dates

  Step 1

  Get the deferral changes from the Deferrals Report for the pay period dates.

  Step 2

  Keep the changes that were not there on the last run.

  Step 3

  Post employee ID, source, new deferral and change date to your payroll system's webhook.

• Contributions received each week, totalled by batch

  Build this

  Starts

  Every Monday at 8:00

  Step 1

  Get the contributions and loan repayments received per batch file over the last 7 days.

  Step 2

  Have an AI step total them by batch and source.

  Step 3

  Post the totals to your accounting webhook and email you the summary.

• New participant loans for payroll deductions

  Build this

  Starts

  Every weekday at 7:00

  Step 1

  Get the participants with loan balances from the Annual Loan Balance report up to today.

  Step 2

  Keep the loan IDs that were not there on the last run.

  Step 3

  Post employee ID, name, loan ID and balance to your payroll 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 deferral changes” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "sponsor.fidelity.com/get_deferral_changes",
    "input": {
      "plan_number": "12345",
      "from": "2026-11-01",
      "to": "2026-11-11"
    }
  }'

{
  "status": "completed",
  "data": {
    "plan_number": "12345",
    "plan_name": "Acme 401(k) Plan",
    "changes": [
      {
        "employee_id": "A10482",
        "participant_name": "Jordan Example",
        "source": "01-EMPLOYEE PRE-TAX",
        "previous_deferral": "4%",
        "new_deferral": "6%",
        "change_date": "2026-11-03"
      }
    ],
    "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.

PSW’s own options

The PSW guides Fidelity publishes describe three ways to move data: sending files under Manage Data, running reports in Run Reports that export to Excel or CSV, and asking Fidelity for reports through a service request. None of these guides describes an API for plan sponsors.

Read on November 12, 2026: Plan Sponsor's Guide to Annual Audit Support Templates, Auditor's Guide: 2025 Plan Year Reporting Package, Steps for adding a Roth source and entering data manually.

Signing in to PSW

PSW signs you in with a user ID and password. New users get their user ID and a one-time password by email, three failed attempts lock the password, and a sign-in from an unrecognized computer may ask for security questions or a security code. With Fous you sign in through PSW's own sign-in with your own account, and the login is sealed with AES-256 and never shown to your code or AI agents.

Worth knowing

Reports are not kept in PSW

Reports from Run Reports do not save or post anywhere in PSW. You export each one to Excel, or to CSV when it is larger than about 24 MB, and keep it yourself.

Fidelity keeps the deferral percentages

Deferral elections live at Fidelity, so payroll has to pick up changes. The Deferrals Report returns the last two calendar years of changes when no date range is chosen.

Submitting is not funding

A contribution file is first submitted to check for errors. Only a file without errors is ready for funding, which you apply as a separate step.

Signed out after 30 minutes idle

PSW signs you out after 30 minutes of inactivity. Changes to a user's access go through your Fidelity representative, who completes a form to change security attributes.

More in Finance: wealth and retirement

• LPL ClientWorks
• NetX360+
• Empower Plan Service Center
• Fidelity Wealthscape
• Schwab Advisor Center
• Nest employer account

Other industries: Georgia Ports WebAccess, TQL Carrier Dashboard, Net-Inspect, Satair Market, CRMLS, KinderConnect.