Loket.nl REST API Data Model
PutFiscalCompanyCarByFiscalCompanyCarId |
Edit the details of a fiscal company car record__Activity name:__ PutFiscalCompanyCarByFiscalCompanyCarIdEdit the details for a fiscal company car record.Please note this resource is related for the registration of the company car for tax purposes.This is NOT directly related to the registration of the company car(s) related to the HRM-module Verstrekking__Metadata :__ Possible options for fields of the type 'metadata' can be acquired (GET) by adding `/metadata` to the PUT URL.
Catalog: LoketNlRest
Schema: FiscalCompanyCar
This is a read-only table function. The loket.nl (REST) API may not support changing the data or the Invantive SQL driver for loket.nl (REST) does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the loket.nl (REST) API.
Select loket.nl (REST) API URL: /providers/employers/employees/employments/fiscalcompanycars/{fiscalCompanyCarId}
Insert loket.nl (REST) API URL: /providers/employers/employees/employments/fiscalcompanycars/{fiscalCompanyCarId}
Update loket.nl (REST) API URL: /providers/employers/employees/employments/fiscalcompanycars/{fiscalCompanyCarId}
Delete loket.nl (REST) API URL: /providers/employers/employees/employments/fiscalcompanycars/{fiscalCompanyCarId}
Field Selection Method: NotRequired
Base Path: content
Select loket.nl (REST) API Operation: put /providers/employers/employees/employments/fiscalcompanycars/{fiscalCompanyCarId}
Table Function Parameters
The following parameters can be used to control the behaviour of the table function PutFiscalCompanyCarByFiscalCompanyCarId. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be treated using their default values.
Value specification by position is done by listing all values from the first to the last needed value. For example with `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.
Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.
Name |
Data Type |
Required |
Default Value |
Documentation |
|---|---|---|---|---|
fiscalCompanyCarId |
guid |
☑ |
|
The unique identifier of the fiscal company car |
If-Match |
string |
☐ |
|
Input the value acquired in the ETag header for concurrency control. Please note this is optional (and not recommended for most types of integrations). |
Table Function Columns
The columns of the table function PutFiscalCompanyCarByFiscalCompanyCarId are shown below. Each column has an SQL data type.
Name |
Data Type |
Label |
Required |
Documentation |
|---|---|---|---|---|
additionalTaxLiabilityGroup_key |
int32 |
|
☐ |
|
additionalTaxLiabilityGroup_value |
string(100) |
|
☐ |
|
dateOfFirstAdmission |
datetime |
|
☐ |
First day of admission for the vehicle (datum eerste toelating). It is possible to acquire a value for this field based on the RDW-registration by calling that supplementary endpoint. |
deviatingAdditionalTaxLiability |
double |
|
☐ |
Normally Loket will calculate the applicable tax liability based on the value and tax liability group of the car. However this field may OVERRIDE any other values, and in that case this amount will be applied as the applicable tax liability amount. |
endDate |
datetime |
|
☐ |
The end date of the entity. The date is up to and including. |
id |
guid |
|
☐ |
The unique identifier of an object (GUID/UUID) |
licensePlateNumber |
string(15) |
|
☐ |
Vehicle registration number (license plate) of the fiscal company car. The number should be provided with or without any hyphens (-). |
reasonForNoAdditionalTaxLiability_key |
int32 |
|
☐ |
|
reasonForNoAdditionalTaxLiability_value |
string(50) |
|
☐ |
|
startDate |
datetime |
|
☐ |
The start date of the entity.A (broken chain)[./#section/Data/Date-chains] is maintained within this resource. |
taxableBenefitForPrivateUse |
double |
|
☐ |
Taxable benefit for private use (eigen bijdrage van de werknemer) may be entered here, this will lower the tax liability to be paid in the payrolling process. |
valueForTaxPurposes |
double |
|
☐ |
The value of the car for tax purposes. This field may only be NULL if a reason for no additional tax liability (reden voor geen bijtelling) is provided.It is possible to acquire a value for this field based on the RDW-registration by calling that supplementary endpoint. |
25-05-2022 14:15 Version 22.1.46-BETA+3385
