Expose employee fixed additions/deductions ("Faste tillegg/trekk") through the API
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- api, backend-api-design
Research direction
Start by reviewing the existing employee and employment endpoints and the API documentation to confirm whether fixed additions or deductions are already exposed elsewhere. Compare the requested employee/employment reference, salary type, dates, and amount or percentage with current API patterns. Done means the availability is clarified or a scoped API addition is specified.
Written by the indexing model from the issue text.
Description
Hi!
It doesn't seem to be possible to retrieve the fixed additions/deductions configured for an employee ("Faste tillegg/trekk") through the API.
Our use case is payroll calculation. We would like to calculate the expected salary for an employee before the payroll transaction is created in Tripletex. Currently, we can retrieve employment details such as salary and employment percentage through the employee/employment endpoints, but we cannot retrieve the fixed additions/deductions that will later be included when payroll is generated.
It would therefore be useful to have API access to these entries, for example like:
GET /employee/employment/fixedAddition
Ideally, the API would expose something in the line of:
- Employee/employment reference
- Salary type
- Start date
- End date
- Fixed amount / percentage
Is this functionality currently available through another endpoint that I have missed?
If not, would it be possible to expose it through the API?
- Dominant language
- No language data
- Stars
- 49
- Forks
- 47
- Avg merge
- 1h 1m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 Tripletex/tripletex-api2
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Tripletex/tripletex-api2#133 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Tripletex/tripletex-api2#130 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Tripletex/tripletex-api2#127 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Tripletex/tripletex-api2#126 · 1 reaction ·
-
faktura( 1500 konto)Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Tripletex/tripletex-api2#114 ·
All issues in Tripletex/tripletex-api2
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Qiskit/qiskit-ibm-runtime#3431 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
edi-adapter-client enhancement helsemelding-edi-adapter
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
navikt/helsemelding-edi-adapter#102 ·
Maintainers usually reply within 1 day
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
callstackincubator/simlock#350 ·
Maintainers usually reply within 1 day
-
Booking email verification fails for plus aliases with impersonation protection enabledPossibly taken @kankadev claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
calcom/cal.diy#30293 · 1 comment ·
Maintainers usually reply within 5 days