Final outputs

Outputs are the fixed reports per payrun period that Ason generates automatically. They arrive in two waves:

• Closing a period doesn't send anything to Swissdec until the payroll is switched to "live" - see Go live
• Concrete list of what's generated, per regulation: see Outputs under your assigned country regulation
• The payment file itself (pain.001) comes from triggering a Payout, not from closing a period
• Outputs vs. documents you upload yourself: Outputs are generated by Ason; files attached to a case value are yours to upload - see Company Data / Employee Data
• Accounting document generation failing? Usually the wage type-to-account mapping isn't complete - see WageType-Accounting-Allocation
• Format: Word, Excel, Pdf, Xml, XmlRaw or Csv, whichever the assigned accountingDocument regulation produces - Xml/XmlRaw is the closest to structured data; get in touch for JSON
• Layout is fixed per regulation, not customizable - get in touch if you need something different
• Year-end declarations arrive as part of finalization for the relevant year-end period

Subscribing to webhooks

Subscribe a webhook to PayrunPeriodClosed and PayrunPeriodFinalized - see Webhooks for setup, payload shape and signature verification. Payloads are thin (that something happened, not the documents themselves), so fetch the documents separately once notified - no polling needed either way, same as a payout's payment file.

Retrieval

Same document endpoints as Results - list a period's documents, or fetch one by id. Fine for a one-off; for full automation once finalized, the payrun period summary below gives you status plus every document's category and URL in one call.

Payrun period summary

Use the ExecuteQuery endpoint to get a payrun period summary:

Code
curl -X 'POST' \
'https://sandbox-api.asonpayroll.com/api/tenants/<TENANTID>/query' \
-H 'accept: application/json' \
-H 'Authorization: Bearer <TOKEN>' \
-H 'Content-Type: application/json' \
-d '{
  "$type": "PayrunPeriodSummaryRequest",
  "payrunPeriodId": <PAYRUNPERIODID>
}'

The response will have this schema:

Code
{
  "status": "Open" | "Closed" | "Finalized",
  "billedEmployeeCount": number,
  "documents": Array<{
    "id": uuid,
    "name": string,
    "contentType": string,
    "url": string,
    "type":
      "AccountingDocument" |
      "CumulativeJournal" |
      "Payslip" |
      "PaymentFile" |
      "Switzerland_SalaryCertificate" |
      "Switzerland_OASI" |
      "Switzerland_FAF" |
      "Switzerland_AccidentInsurance" |
      "Switzerland_SupplementaryAccidentInsurance" |
      "Switzerland_SicknessDailyAllowance" |
      "Switzerland_WithholdingTax",
    "employeeId": uuid | null, // if null this is a payroll-wide document,
    "employeeAttributes": Record<string, any>
  }>
}

Use the document's url with a GET request (plus your Authorization header - it's not a temporary link) to download it.

• All payslips at once: no single page for that in the standard product UI, but the documents endpoint returns every payslip document if you want to build one yourself
• ELM submission log: no dedicated log exists - the closest is the period's documents after finalization
• Emailing payslips to employees: not a built-in Ason feature - Ason delivers the documents to you (webhook + documents endpoint); actually emailing them is something you'd build on your platform, or check with support if you need this natively

Testing

In the sandbox, finalization is faked - shortly after closing, a finalized event fires with a document per category.

API Endpoints

Webhook management endpoints (create/list/update/delete a subscription) are on the Webhooks page.

to Feature Map