CW-048 · ประกันสังคม monthly filing (สปส. 1-10)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend
Research direction
No files or entry points are named. Start by tracing the existing payroll export seam and the payslip fields ssoEmployee and ssoEmployer, then read #43 and the Social Security Office specification. Done means producing a compliant file, enforcing the ceiling and missing-number error, and refusing unreconciled periods.
Written by the indexing model from the issue text.
Description
Priority P1 · Area payroll · Estimate M · Phase 3
What to build
A payroll officer picks a month and downloads a สปส. 1-10 file ready to submit to the Social Security Office. Payroll already computes both halves of the contribution under มาตรา 33 and stores them on every payslip as ssoEmployee and ssoEmployer; there is currently no way to get them out.
This runs alongside the withholding-tax chain rather than after it — it shares the export seam and nothing else.
Acceptance criteria
- The export for the seeded demo company matches hand-computed employee and employer totals.
- The layout matches the Social Security Office's published specification.
- The contribution ceiling is applied per employee per month, with tests at the boundary.
- An employee with no social security number is reported as an error naming them, rather than silently omitted or exported blank.
- A period that does not reconcile produces the error from #43, not a file.
Blocked by
- #43 — reconciliation, permission, download and audit come from there.
Not blocked by the ภ.ง.ด.1 chain; these can be worked in parallel. The rules being formatted here have not been reviewed by anyone qualified — see #36.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 37m
- Merged PRs (30d)
- 1
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 ·
-
P1 payroll phase-3
Difficulty 5/5 Over a week Newbie friendliness 30/100
SuruchBoss/Cwork#59 ·
-
P2 phase-3
Difficulty 5/5 Over a week Newbie friendliness 45/100
SuruchBoss/Cwork#58 ·
-
P3 project
Difficulty 3/5 1-2 days Newbie friendliness 76/100
SuruchBoss/Cwork#56 ·
All issues in SuruchBoss/Cwork
Similar issues
-
triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mermaid-js/mermaid-live-editor#2053 ·
Maintainers usually reply within 1 day
-
factory
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jessepollak/home#1455 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
lingdojo/kana-dojo#31227 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
appandflow/stim#1838 ·
Maintainers usually reply within 1 day