Skip to content

FousSLC HEP Services

Turn SLC's Student Information Service into an API

Read the Attendance Worklist, your CoC statuses and each Tuition fee remittance report from SIS with one API call each. Or have a workflow list the attendances still due before Thursday's cut-off and post each week's remittance to finance.

Works with your own SLC HEP Services account. Fous is an independent product.

What you can build on SIS

  • Get unconfirmed attendances

    Build this

    Searches the Attendance Worklist by course and reads the Unconfirmed Attendances results, with the liability periods still due for each student.

    Takes
    Academic year, liability period, SLC course code (optional)
    Returns
    SSN, name, course name, course year, SLC course code, Tuition Fee Loan, total tuition fee, periods due, attendance code
  • Get a tuition fee remittance report

    Build this

    Opens Financial Reports, then Remittance Report, filters by month and year created and reads each report's payment summary and student table.

    Takes
    Month created, year created, academic year
    Returns
    Payment date, payment type, number of payments, total fee amount, and per student SSN, name, course code, year of course, fee amount, revision indicator
  • Check change of circumstance statuses

    Build this

    Searches View CoC by academic year, status, CoC type or last updated dates and reads each notification's type and status.

    Takes
    Academic year, status (optional), CoC type (optional), last updated between (optional)
    Returns
    SSN, student name, CoC type, status, date created, last updated
  • Submit an attendance confirmation

    Build this

    Runs a Course Search on the Attendance Worklist, finds the student by SSN, picks an attendance code for the liability period due and selects Submit.

    Takes
    Academic year, SLC course code, SSN, liability period, attendance code
    Returns
    SSN, liability period, attendance code, status

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

  • Attendances still due before the Thursday cut-off

    Build this
    Starts
    Every Monday at 8:00, Europe/London
    Step 1
    For each SLC course code you name, get the unconfirmed attendances for the current liability period.
    Step 2
    Keep the students who still have a liability period due.
    Step 3
    Email you the list grouped by course, with SSN, name, course year and any code saved but not submitted.
  • Weekly tuition fee remittance, posted to finance

    Build this
    Starts
    Every Friday at 9:00, Europe/London
    Step 1
    Get the tuition fee remittance reports created this month for the current academic year.
    Step 2
    Keep the reports that were not there on the last run.
    Step 3
    Post each report's payment date, type, total and student lines to your finance system's webhook.
  • Daily CoC status changes, Failed ones first

    Build this
    Starts
    Every weekday at 9:00, Europe/London
    Step 1
    Check change of circumstance statuses for the current academic year, last updated in the past 7 days.
    Step 2
    Keep the CoCs whose status changed since the last run.
    Step 3
    Email you the list, Failed ones first, with SSN, student name, CoC type and status.

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 unconfirmed attendances” 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": "secure.heservices.slc.co.uk/get_unconfirmed_attendances",
    "input": {
      "academic_year": "2026/27",
      "liability_period": 1,
      "slc_course_code": "ACM104"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "students": [
      {
        "ssn": "ACME12345678",
        "full_name": "Jordan Example",
        "course_name": "BSc Computer Science",
        "course_year": 2,
        "slc_course_code": "ACM104",
        "tuition_fee_loan": 9535,
        "total_tuition_fee": 9535,
        "periods_due": [
          1
        ],
        "attendance_code": null
      }
    ]
  }
}

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.

SIS’s own options

The SIS user guide describes no API. Bulk work is done with files: you export a worklist, add your confirmations and import it back, and change of circumstance notifications can be imported as CSV or XML for undergraduates. Remittance reports export as a .dat file.

OptionWhat it coversWhat it takes
Worklist export and importRegistration and attendance confirmations in bulk: export from the worklist, add confirmations, import the file and view the import results.SIS access. Up to 50,000 records per export, and the file does not show which liability period a confirmation is for.
CoC bulk uploadChange of circumstance notifications submitted as an XML or CSV file, shown with the status Submitted (imported).SIS access. Bulk upload by XML or CSV is for undergraduate students only.
Remittance report exportOne file per remittance report, with a header row and a detail record for each student.SIS Report Advisor access. Reports are available each Thursday once generated.
SIS by handWorklists, View CoC, Create CoC and the Financial Reports, on screen through the HE Gateway.An HE Gateway account created by your institution's User Administrator.

Read on November 12, 2026: Attendance worklist export, Withdrawal CoC, Tuition fee remittance report.

Signing in to SIS

SIS is reached through the HE Gateway, which asks for a username and password. A forgotten or first password is reset with a code sent by email, and each account is created by your institution's User Administrator. With Fous you sign in once through the HE Gateway's own sign-in with your own account: the login is sealed with AES-256, and an expired session is signed back in.

Worth knowing

A Thursday cut-off before each payment
Attendance for the October, February and May payments must be confirmed by close of business on the Thursday before. For weekly BACS payments, confirm by the Thursday of the week before.
A submitted positive code is locked
Once a positive attendance code is submitted it cannot be changed on the worklist: you raise a CoC to correct it. A negative code stays editable, and an earlier outstanding period must be submitted before a later one.
Two people for registration
SLC asks for independent validation of registration confirmations by at least two staff members, for example one person checks saved confirmations and another submits them. Saving and submitting are separate steps.
CoCs change status over hours or weeks
A submitted CoC updates within 24 hours, automated ones take 48 hours, and manual processing takes 20 working days, or 30 from August to the end of November.

More in Education, research and nonprofit

Other industries: FirstEnergy online account, PedidosYa Partner Portal, FABeAccess, U.S. Bank Access Online, Coretax DJP, GST Portal.

Frequently asked questions

No public API is documented. SIS offers file exchange instead: worklist export and import for registration and attendance confirmations, a CoC bulk upload by XML or CSV for undergraduates and an export of each remittance report. Everything else is done on screen through the HE Gateway.

By close of business on the Thursday before the main payment dates in October, February and May. For weekly BACS payments, confirm by the Thursday of the week before. Fees are paid in three instalments of 25%, 25% and 50%, each after attendance is confirmed.

A and L release payment. C, F, N, X and S each need a CoC as well. D can only be submitted in the first liability period, and it removes the student's support entitlement.

In the Tuition fee remittance report under Financial Reports. Each report lists the payment date, payment type and total, then every student in it with SSN, course code, year of course and fee amount. Reports are available each Thursday once generated, and you need SIS Report Advisor access.

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

Put SLC HEP 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 nextParchmentUCAS adviser portalBenevity Causes PortalFirstEnergy online accountHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of SLC HEP Services (Student Loans Company). 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.