Document template · be.communications.yearend_letter
Year-End Letter
- Render-verified
- Informational
- Version 1.0.0
Employee communication templates: welcome letters, benefits summaries, salary indexation notifications, and year-end letters.
JSON Schema
Fields in this template
Data sent to the API is validated against the template’s JSON Schema before anything is rendered. This template defines 53 fields:
| Field | Required | Type | Description |
|---|---|---|---|
| letter | Required | object | |
| letter.place | Required | string | |
| letter.date | Required | date | |
| letter.reference_year | Required | integer | |
| letter.language | Required | enum | |
| letter.reference | Optional | string | |
| employer | Required | object | |
| employer.name | Required | string | |
| employer.address | Optional | string | |
| employer.bce_number | Required | string | |
| employer.vat_number | Optional | string | |
| employer.onss_number | Required | string | |
| employer.joint_committee | Required | string | |
| employer.social_secretariat | Optional | string | |
| employer.represented_by | Optional | string | |
| employee | Required | object | |
| employee.given_name | Required | string | |
| employee.surname | Required | string | |
| employee.address | Optional | string | |
| employee.function_title | Required | string | |
| employee.department | Optional | string | |
| employee.start_date | Required | date | Date of entry into service (for prorata calculation). |
| employee.employee_number | Optional | string | |
| employee.statut | Optional | enum | |
| yearend_premium | Required | object | Year-end premium or 13th month details. |
| yearend_premium.premium_type | Required | enum | Legal type of the year-end payment. |
| yearend_premium.gross_amount_eur | Required | number | |
| yearend_premium.onss_employee_eur | Required | number | Employee ONSS/RSZ deduction (standard 13.07% or special CCT 90 rate). |
| yearend_premium.withholding_tax_eur | Optional | number | Withholding tax (précompte professionnel) deducted at source. |
| yearend_premium.net_amount_eur | Required | number |
+23 more fields — the full JSON Schema is available in the dashboard and via the API.
POST /render
Generate it
One POST /render call: send your JSON, get the finished PDF back. Or skip the JSON entirely and describe the document in plain language on chut.app.
curl -X POST https://api.papii.eu/render \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "be.communications.yearend_letter",
"data": { ... },
"options": {"language": "en"}
}' -o yearend-letter.pdf Frequently asked questions
What is “Year-End Letter”?
Employee communication templates: welcome letters, benefits summaries, salary indexation notifications, and year-end letters. On papii this document is available as template be.communications.yearend_letter: a JSON Schema plus a deterministic PDF renderer, so the same data always produces the same document.
Can I generate a Year-End Letter with AI?
Yes. chut.app — the AI back office papii powers — fills this template from a plain-language description: you describe the document in one sentence, the AI structures the data, papii validates it against the schema and renders the PDF. Developers can also call the papii API directly with structured JSON.
Is the Year-End Letter template legally compliant?
This template is render-verified: its schema, sample data and PDF output are automatically tested on every release. It is published with status “ready”, meaning it has not yet been through papii’s final legal review. Where it references specific legislation, that is stated in the template description — always have a professional check documents with legal effect before relying on them.