- 07 Aug 2024
- 6 Minutes to read
- Print
- DarkLight
Update an supplier
- Updated on 07 Aug 2024
- 6 Minutes to read
- Print
- DarkLight
Update an existing supplier. This will fully overwrite the supplier with the data from the request.
Description
Update an existing supplier. This will fully overwrite the supplier with the data from the request. Both the 'reference' and the 'externalIdentifier' can be used to identify the supplier which needs to be overwritten. Preferably only the reference is used. If this is not available, the externalIdentifier can be used. If both properties are used it is important that both are correct and match with the same entity (supplier). If this is not the case, the request will return with an error code and the supplier will not be overwritten. A supplier encompasses all entities from which you receive invoices. For example, the tax authorities or a cleaning company. Also, for instance, the company from which you purchase office supplies.
Use Case
The Bloxs user has added a supplier with several incorrect properties. Therefore the user wants to change multiple properties at the same time rather than making several requests and changing one property at a time.
Field | Description |
---|---|
externalIdentifier | The unique identifier within the system of the requesting party. This identifier is not generated by the Bloxs system. |
phoneNumber | Phone number of the supplier. |
mobileNumber | Mobile phone number of the supplier. |
cocNumber | Chamber of Commerce number. |
cocDescription | Additional information about the Chamber of Commerce number. Termed as KVK description in the Bloxs system. Extra information can be entered here regarding the Chamber of Commerce number. |
vatNumber | VAT (BTW) number of the supplier. |
correspondenceMethod | The default method of correspondence. This field is an integer with 2 options: 1 = Email 2 = Post If the correspondenceMethod is set to Email, then the primaryEmailAddresses field is mandatory. If the CorrespondenceMethod is set to Post, then the Address field is mandatory. |
remarks | General comments. Please note: Avoid including sensitive information here, such as passwords or sensitive personal data. |
languageISOCode | ISO language code. Use the 2-letter code from the ISO 639-1 Code list. |
address | The address of the supplier. |
street | The street of the supplier. |
houseNumber | The house number of the supplier. |
postalCode | The postal code of the supplier. |
city | The place of residence of the supplier. |
countryISOCode | ISO country code. Use the 2-letter code from the ISO 639-1 Code list. |
invoiceAddress | The billing address of the supplier. In case this field is empty, the data from 'address' will be used. This is mainly relevant for certain templates. |
postalAddress | The postal address of the relation. In case this field is empty, the data from 'address' will be used. This is mainly relevant for certain templates. |
primaryEmailAddresses | Primary email address used by the relation. If other email addresses are left empty, this email address will be used for correspondence. |
invoicesEmailAddresses | The email address used to send invoices. |
paymentRemindersEmailAddresses | The email address used to send reminders regarding payments. |
indexationsEmailAddresses | The email address to which the annual rent increase (indexation) is sent. |
serviceTicketsEmailAddresses | The email address to which all maintenance notifications are sent. This may differ from the general email address. For instance, in the case of a shared office space where all communication is centralized through one central desk instead of being handled separately by individual tenants. |
purchaseOrdersEmailAddresses | All communication specifically related to procurement is conducted through this email address. This is primarily applicable to large parties where procurement processes are managed through separate email accounts. |
portalsEmailAddresses | Within Bloxs, a portal account for customers or tenants can be opened. Through this field, you can provide multiple email addresses that need to be granted access. |
otherEmailAddresses | Other email addresses. |
supplierTypeName | Supplier type. The enumeration can be set by the user in the admin module. In the administration, there is already a default list created by Bloxs, which can be modified by the user. To retrieve the list of available options the following endpoint can be used: GET SupplierTypes. |
name | Name of the supplier. |
website | Website of the supplier. |
defaultPurchaseInvoiceSubject | This is a text field for the preferred subject of the invoice. For example, if the supplier is a cleaner, you could enter 'cleaning services' as the default text here. |
paymentMethod | 1 = DirectDebit 2 = BankTransfer 3 = Withdrawal 4 = Cash 5 = iDeal If this option is selected, it will appear on the invoice as the default preferred payment method. The user cannot modify this enumeration. |
defaultPaymentTermName | Preferred payment term. The enumeration can be set by the user in the admin module. There exists a default list created by Bloxs, which can be modified by the user. |
defaultLedgerAccountCode | Preferred general ledger account. The enumeration can be set by the user in the admin module. There exists a default list created by Bloxs, which can be modified by the user. |
reference | The relationship number within Bloxs. This is unique (per client specific environment) for all relationships (EstateAgents, Organisations, Owners, Persons, Suppliers). The relationship number is generated by the Bloxs system. |
Please enter a valid token
1 = Email
2 = Post
1 = DirectDebit
2 = BankTransfer
3 = Withdrawal
4 = Cash
5 = iDEAL
The supplier was updated
1 = Email
2 = Post
1 = DirectDebit
2 = BankTransfer
3 = Withdrawal
4 = Cash
5 = iDEAL
The supplier data has validation issues