# PutPaymentInformationSepaSeparatePaymentByPaymentInformationSepaSeparatePaymentId Edit the details of a payment information separate payment record __Activity name :__ PutPaymentInformationSepaSeparatePaymentByPaymentInformationSepaSeparatePaymentId Edit an existing separate payment-record (for an employment). For each unique payroll component there can only be one payment record per employment. __Metadata :__ Not applicable for this resource. Select loket.nl (REST) API URL: /providers/employers/employees/employments/paymentinformationsepaseparatepayments/{paymentInformationSepaSeparatePaymentId} Insert loket.nl (REST) API URL: /providers/employers/employees/employments/paymentinformationsepaseparatepayments/{paymentInformationSepaSeparatePaymentId} Update loket.nl (REST) API URL: /providers/employers/employees/employments/paymentinformationsepaseparatepayments/{paymentInformationSepaSeparatePaymentId} Delete loket.nl (REST) API URL: /providers/employers/employees/employments/paymentinformationsepaseparatepayments/{paymentInformationSepaSeparatePaymentId} Select loket.nl (REST) API Operation: put /providers/employers/employees/employments/paymentinformationsepaseparatepayments/{paymentInformationSepaSeparatePaymentId} - Catalog: `LoketNlRest` - Schema: `PaymentInformationSeparatePayments` - Field Selection Method: NotRequired - Base Path: `content` 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. ## Parameters of Table Function | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `body` | `string` | ☑ | | | | `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). | | `paymentInformationSepaSeparatePaymentId` | `guid` | ☑ | | The unique identifier of the SEPA payment record | ## Columns of Table Function The columns of the table function `PutPaymentInformationSepaSeparatePaymentByPaymentInformationSepaSeparatePaymentId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `amount` | `double` | | ☐ | The amount to be split from the net salary | | `cityBeneficiary` | `string(24)` | | ☐ | City name of beneficiary | | `description1` | `string(32)` | | ☐ | Description 1. Both description field values will be a line in the (unstructured) description of the SEPA file. | | `description2` | `string(32)` | | ☐ | Description 2. Both description field values will be a line in the (unstructured) description of the SEPA file. | | `endDate` | `datetime` | | ☐ | The end date of the record | | `iban` | `string(35)` | | ☐ | International Bank Account Number (IBAN). Only IBAN without spaces are accepted. | | `id` | `guid` | | ☐ | The unique identifier of an object (GUID/UUID) | | `nameBeneficiary` | `string(70)` | | ☐ | Name of beneficiary | | `startDate` | `datetime` | | ☐ | Start date of this record __NOTE :__ at the moment of performing a payroll run it will be checked what record is applicable for splitting from net salary at that date (based on the start- and enddate). |