Skip to content

FousPUE ZUS

Get your employees' e-ZLA from eZUS through an API

Read the e-ZLA in Zaświadczenia lekarskie (medical certificates) in your Panel Płatnika (payer panel) with one API call, by period or employee. A workflow can check that list each weekday morning and post the new e-ZLA to payroll.

Works with your own PUE ZUS account. Fous is an independent product.

What you can build on eZUS

  • Get sick-leave certificates (e-ZLA)

    Build this

    Reads the e-ZLA listed in Zaświadczenia lekarskie in the Panel Płatnika for an absence period you set.

    Takes
    Payer NIP, period from, period to
    Returns
    Employee name, identifier type, series and number, status, issue date, leave from and to, hospital stay, medical indication
  • Find corrected, cancelled and retroactive e-ZLA

    Build this

    Reads Zaświadczenia lekarskie and keeps the e-ZLA whose status is Skorygowane (corrected), Anulowane (cancelled) or one of the Wsteczne (retroactive) statuses.

    Takes
    Payer NIP, issued since
    Returns
    Employee name, series and number, status, issue date, leave from and to
  • Get one employee's e-ZLA

    Build this

    Reads every e-ZLA for one employee in Zaświadczenia lekarskie for a period, for checking sick pay before the payroll closes.

    Takes
    Payer NIP, employee PESEL or passport number, period from, period to
    Returns
    Series and number, status, leave from and to, hospital stay, insurance place, care relationship code
  • Request a certificate of no arrears (RWN)

    Build this

    Fills in and sends the RWN request for a zaświadczenie o niezaleganiu (certificate of no arrears) from the payer account.

    Takes
    Payer NIP, electronic or paper delivery
    Returns
    Request type, sent date, confirmation of submission

Automate eZUS 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 e-ZLA handed to payroll each morning

    Build this
    Starts
    Every weekday at 7:00
    Step 1
    Get the sick-leave certificates (e-ZLA) for the current and previous month.
    Step 2
    Keep the certificates that were not there on the last run.
    Step 3
    Post employee, series and number, status, leave from and to to your payroll webhook.
  • Corrected and retroactive e-ZLA to review

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    Find the corrected, cancelled and retroactive e-ZLA issued in the last 30 days.
    Step 2
    Keep those that changed since the last run, and stop the run if there are none.
    Step 3
    Email you the list grouped by status.
  • Monthly sick-leave summary for the payroll close

    Build this
    Starts
    On the 1st of every month at 7:00
    Step 1
    Get the sick-leave certificates (e-ZLA) for the previous month.
    Step 2
    Summarize the days of leave per employee, with hospital stays and cancelled certificates marked.
    Step 3
    Email you the summary.

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 sick-leave certificates (e-ZLA)” 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": "zus.pl/get_sick_leave_certificates",
    "input": {
      "payer_nip": "5250000000",
      "period_from": "2026-11-01",
      "period_to": "2026-11-30"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "payer": "Acme Sp. z o.o.",
    "certificates": [
      {
        "employee": "Marta Lewandowska",
        "identifier_type": "PESEL",
        "series": "ZZ",
        "number": "4820117",
        "status": "Wystawione",
        "issued": "2026-11-09",
        "leave_from": "2026-11-09",
        "leave_to": "2026-11-16",
        "hospital_from": null,
        "hospital_to": null,
        "medical_indication": "may walk"
      }
    ],
    "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.

EZUS’s own options

ZUS offers payers one public web service: it returns the e-ZLA reports you schedule in eZUS, as password-protected ZIP files, for reports generated in the last 30 days. Insurance documents go to ZUS through the Płatnik program or ePłatnik in eZUS. Requests such as RWN and the rest of the payer panel are used in eZUS itself, which is free.

OptionWhat it coversWhat it takes
e-ZLA report service (pobierzRaporty)Collective e-ZLA reports: employee, series and number, status, leave period, hospital stay, medical indication. ZIP files in base64.A cyclic report schedule set in eZUS with its own email login, service password and ZIP password, plus the payer NIP. Open to every payer.
Płatnik and ePłatnikSending settlement and insurance documents to ZUS.The Płatnik desktop program, or the ePłatnik application inside eZUS, which ZUS describes as free of cost.
eZUS by handPanel Płatnika: Zaświadczenia lekarskie with a CSV download, requests such as RWN, and insurance documents sent to ZUS.A free eZUS account, and a power of attorney from the payer when the payer is a company.

Read on November 12, 2026: Usługa do pobierania raportów e-ZLA dla płatników (ZUS BIP), Regulamin korzystania z eZUS, Zaświadczenia o niezaleganiu.

Signing in to eZUS

eZUS signs you in with your eZUS login and password, with a QR code scanned in the ZUS mobile app, or through login.gov.pl (Profil zaufany, banking, mObywatel, e-Dowód or eID). With Fous you sign in once through eZUS's own sign-in with your own login and password: the login is sealed with AES-256, and an expired session is signed back in.

Worth knowing

ZUS's own reports arrive a day later
ZUS generates the cyclic e-ZLA reports at night, and the first data arrives at the earliest the day after you set up the report schedule in eZUS.
The report service has its own login
ZUS's e-ZLA service takes the email and password set in the report schedule, not your eZUS login, plus the payer NIP. It returns only reports generated in the last 30 days.
A company is reached through a person
A company's data is opened by a person with their own confirmed eZUS profile and a power of attorney from the payer. The account you connect sees only the payers it holds that power for.
No-arrears certificates take up to 7 days
ZUS issues the certificate within 7 days of an RWN request, at once in clear cases, and refuses by decision when contributions are overdue. The electronic copy is an XML file with a qualified signature.

More in Government: Southern, Eastern and Nordic Europe, EU

Other industries: Chorus Pro, Texas811 Portal, NatWest Intermediary Solutions, HUD Secure Systems, BidNet Direct, MyDORWAY.

Frequently asked questions

Only for e-ZLA. ZUS's public pobierzRaporty service returns the e-ZLA reports you schedule in eZUS, as password-protected ZIP files from the last 30 days. Insurance documents go through Płatnik or ePłatnik, and the rest of the payer panel is used in eZUS itself.

Yes. ZUS says on its sign-in page that PUE ZUS is changing into eZUS, and its own documentation refers to it as PUE/eZUS.

Skorygowane, Anulowane and the three Wsteczne statuses. ZUS's report lists Wystawione, Anulowane, Skorygowane, Wsteczne - do wyjaśnienia, Wsteczne - uzasadnione and Wsteczne - nie uzasadnione, so a certificate can still change after it is issued.

Send the RWN request from your eZUS account, yourself or through an authorized representative. ZUS answers within 7 days, at once in clear cases, and can issue the certificate as an XML document with a qualified signature.

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

Put PUE ZUS 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 nextSegurança Social DiretaSGK İşveren SistemiSociálna poisťovňa e-SlužbyChorus ProHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of PUE ZUS (Zakład Ubezpieczeń Społecznych (ZUS)). 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.