镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

20.0 hr doc belgium yti - #20878

Open
tivisse wants to merge 13 commits into
20.0from
20.0-hr-doc-belgium-yti
Open

tivisse wants to merge 13 commits into
20.0from
20.0-hr-doc-belgium-yti

Conversation

@tivisse

@tivisse tivisse commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

The Belgian payroll page had grown to ~3200 lines covering 25+ unrelated
topics. Split it by theme (payslip, annual payments, time off, departure,
social security declarations, tax declarations, social reporting), with
belgium.rst becoming the index. Content is moved as is; images follow their
section into a folder named after the new page. Labels are kept so existing
:ref: links still resolve.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Document the setup of the Belgian payroll localization in 20.0: modules,
Belgian settings, company data, reference data (joint committees, salary
scales, employer categories, worker codes, NACE codes, work locations),
employee types, Belgian employee information, structures, benefits,
premium pay and the Belgian salary configurator.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Rewrite the Belgian payslip explanation for 20.0 (versions instead of
contracts, current rule layout) and document the company car benefit in
kind, meal vouchers, mobility and insurances. Representation fees are now
lump sum allowances configured per benefit: the old single threshold is
gone. Screenshots regenerated.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Update December pay, double holiday pay, end of year bonus and eco
vouchers for 20.0: the December holiday pay balance is computed on the
December payslip (no more dedicated button), eco vouchers amounts for
part-time workers fixed, withholding tax tables replaced by a reference to
the rule parameters. Screenshots regenerated.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Rewrite the social security declarations for 20.0. The page becomes an
overview of the common ONSS flow (ONSS certificate, environments, batch
files, XSD validation, ONSS Declarations and ONSS Files menus) with one
subpage per declaration. Dimona now relies on declarations, periods and
relations; the DmfA documentation covers the new web and batch declarations,
contribution reductions and reorganisation measures. Screenshots
regenerated.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Document the DRS (WECH/ZIMA scenarios) generated from the payroll data:
automatic creation from the employee situation, content of each scenario
and follow-up of the declarations.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Document the Flexi@Work declarations of flexi-job workers: configuration,
generation from the validated payslips and submission.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Update the individual accounts (populate, generate and post reports), the
social balance sheet (PDF, XLSX, validation, integration in the annual
accounts XBRL export) and the social security certificate for 20.0.
Screenshots regenerated.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Rewrite the Belgian time off documentation for 20.0: Belgian time types,
carried-over, youth and senior holidays, small leaves, public holiday
compensation, temporary unemployment, legal time off entitlement and
allocation, sick leave split and relapse rules, holiday pay recovery based
on holiday attests, working schedule changes creating versions and the
standard time entries export (the payroll secretariat export modules no
longer exist). Screenshots regenerated.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Document the 20.0 departure flow through the End of Collaboration wizard
(notice period and holiday attests tabs), the Belgian departure reasons,
notice period rules (including hirings from 2026-08-01), termination fees,
departure holiday pay and end of year bonus on departure, and the
termination documents. Screenshots regenerated.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Move the tax declarations to subpages and rewrite the author's rights
documentation for 20.0: 273S and 273 Part sheets (populate, generate,
correct), 2026 intellectual property rules, employee and payslip fields.
The outdated legal explanation is removed. Screenshots regenerated.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Rewrite the withholding tax declaration for 20.0: monthly or quarterly
declarations, modifications, PDF/XML/XLSX generation, tabs content,
researchers exemption and its caps, journal entries. Screenshots
regenerated.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
Document the 281.10, 281.13, 281.18, 281.20, 281.30 and 281.45 forms in
20.0 (single declaration per year, compute, file creation, PDF and
Documents integration, corrections, withholding taxes check, fiscal
mapping) and the Belcotax-on-web 2.0 export (XML up to 2025 incomes, JSON
Lines from 2026). The tax declarations page becomes an overview with
the common rules. Screenshots regenerated.

How this was verified:
- The content was written with an AI assistant (Claude), then checked
  against Odoo 20.0 (odoo 15847649b67e, enterprise 0d2a8594a038) on a
  local database with demo data and ~270 modules (all HR apps, Fleet,
  Maintenance, Sign, Email and SMS Marketing, Events, Planning,
  Timesheets, Purchase, Documents, Belgian payroll).
- Every added or changed UI instruction was followed as written on that
  database, as in the documentation team's UI verification prompt;
  mismatches were fixed in the text.
- Icons use the data-icon value and the tooltip of the element, read on
  the screen (filled variants as _f).
- Examples and screenshots use the demo data only; screenshots taken at
  a 992 px viewport.
- Not verified in the UI, checked in the 20.0 source code instead: the
  ONSS / FPS Finance web services (Dimona, DmfA, DRS, Belcotax),
  scheduled actions, emails, validated or paid payslips; the Belgian
  payroll computations themselves were not recomputed.
@robodoo

robodoo commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator

Pull request status dashboard

🤖 Open bundle on Runbot

@C3POdoo
C3POdoo requested a review from a team November 5, 2026 13:02

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants