CW-071 · Payslips and a wage receipt on paper
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 54/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authorization, full-stack, localization, testing
Research direction
Start with backend/src/modules/documents/, backend/src/modules/payroll/, and web/src/features/payroll/, then trace the certificate renderer from CW-008 and the date handling in CW-058. Done means tested payslip parity, Thai glyphs and A4 output from Chrome and the NAS PDF, foreign-worker names, and restricted, audited printing.
Written by the indexing model from the issue text.
Description
Priority P0 · Area payroll · documents · Estimate M · Pilot B, November 2026
The pilot pays in cash to staff without smartphones, so a payslip on a screen reaches nobody. The Labour Protection Act also expects the employer to keep a record of wages paid. The PO understands a receipt the employee signs to be the usual way; an accountant should confirm (#36).
Scope
- One printable payslip per employee per run, in Thai, sized so two or four fit on an A4 sheet to be cut. It is built on the certificate renderer from CW-008.
- A wage receipt sheet for the run: one row per employee with net pay and a space to sign. It is printed on A4, and HR files it.
- Dates in พ.ศ. (CW-058).
Acceptance
- Every line on the printed payslip matches the payslip on screen, tested, not inspected.
- Thai renders with no missing glyphs, and the documents print correctly on A4 from Chrome and from the NAS's PDF.
- A foreign worker's slip shows their name as HR entered it.
- Printing is audited, and only people who may see pay can print.
Files backend/src/modules/documents/, backend/src/modules/payroll/, web/src/features/payroll/
Tracked in docs/backlog.md.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SuruchBoss/Cwork
-
documentation good first issue P3 phase-E
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SuruchBoss/Cwork#50 ·
-
good first issue mobile P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SuruchBoss/Cwork#11 ·
-
P0 payroll
Difficulty 4/5 3-5 days Newbie friendliness 55/100
SuruchBoss/Cwork#73 · 1 comment ·
-
P0 payroll
Difficulty 5/5 Over a week Newbie friendliness 38/100
SuruchBoss/Cwork#72 · 1 comment ·
-
P1
Difficulty 4/5 3-5 days Newbie friendliness 45/100
SuruchBoss/Cwork#71 ·
All issues in SuruchBoss/Cwork
Similar issues
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pingdotgg/t3code#14452 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
solana-foundation/program-examples#747 · 1 comment ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
remotion-dev/remotion#11847 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openwatersio/slackwater#355 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melgarafael/DeskcommCRM#1998 · 3 comments ·
Maintainers usually reply within 1 day