How to Update Vendors

This how-to covers updating a Pleo Vendor’s details to match its corresponding active AS vendor. Run this after How to Fetch and Match Vendors found a matching Pleo Vendor whose details differ from the AS.

Prerequisites

Before you begin:

You have completed How to Fetch and Match Vendors and found a matching Pleo Vendor whose details differ from the AS
Your integration is authenticated using one of the supported authentication methods
Your integration can call Pleo’s Vendors API endpoints

Scenario

This how-to continues from the How to Fetch and Match Vendors scenario: “Kaffehuset AS” (EXT-004) is active in both systems, but its country and currency differ (Pleo has SE/SEK, the AS has DK/DKK).

Steps

1. Update the Vendor

API Endpoint: PUT /v1/vendors/{id} The “Kaffehuset AS” Vendor’s country and currency are updated from SE/SEK to match the AS values of DK/DKK in this example. Example Pseudo:

if detailsDiffer(matchedVendor, vendor):
    if isValidCurrency(vendor.defaultCurrency):
        currency = vendor.defaultCurrency
    else:
        logDataQualityIssue(vendor, field = "defaultCurrency")
        currency = matchedVendor.defaultCurrency  # or a preconfigured fallback currency
        # or: skip updating this vendor, log it, and continue with the next one

    updatePayload.companyId               = matchedVendor.companyId
    updatePayload.externalId              = vendor.externalId
    updatePayload.code                    = vendor.code
    updatePayload.name                    = vendor.name
    if isValidCountry(vendor.country):
        updatePayload.country             = vendor.country
    else:
        logDataQualityIssue(vendor, field = "country")
    updatePayload.defaultCurrency          = currency
    updatePayload.registrationNumber      = vendor.registrationNumber
    updatePayload.taxRegistrationNumber   = vendor.taxRegistrationNumber
    updatePayload.state                   = "ACTIVE"
    PUT updatePayload to Pleo /v1/vendors/{matchedVendor.id}

OAuth 2.0
API Key

curl -X PUT "https://external.staging.pleo.io/v1/vendors/b2c3d4e5-f678-901f-2345-bcd67f89aabc" \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json;charset=UTF-8" \
  -d '{
        "companyId": "12abc3d4-e567-890e-1234-abc56e78fabc",
        "externalId": "EXT-004",
        "code": "1004",
        "name": "Kaffehuset AS",
        "country": "DK",
        "defaultCurrency": "DKK",
        "registrationNumber": "556677-8899",
        "taxRegistrationNumber": "SE556677889901",
        "state": "ACTIVE"
      }'

curl --request PUT \
  -u "pls_1ab2cd3e4f5g6h7a89b012c34de56f78_gabc90:" \
  -H "Accept: application/json;charset=UTF-8" \
  -H "Content-Type: application/json;charset=UTF-8" \
  "https://external.staging.pleo.io/v1/vendors/b2c3d4e5-f678-901f-2345-bcd67f89aabc" \
  -d '{
        "companyId": "12abc3d4-e567-890e-1234-abc56e78fabc",
        "externalId": "EXT-004",
        "code": "1004",
        "name": "Kaffehuset AS",
        "country": "DK",
        "defaultCurrency": "DKK",
        "registrationNumber": "556677-8899",
        "taxRegistrationNumber": "SE556677889901",
        "state": "ACTIVE"
      }' \
| jq

Example Response

{
  "data": {
    "id": "b2c3d4e5-f678-901f-2345-bcd67f89aabc",
    "companyId": "12abc3d4-e567-890e-1234-abc56e78fabc",
    "externalId": "EXT-004",
    "code": "1004",
    "name": "Kaffehuset AS",
    "country": "DK",
    "defaultCurrency": "DKK",
    "registrationNumber": "556677-8899",
    "taxRegistrationNumber": "SE556677889901",
    "state": "ACTIVE",
    "accountingSystem": "custom_api_integration",
    "createdAt": "2026-06-01T08:48:52.799351Z",
    "updatedAt": "2026-07-08T09:20:10.215202Z"
  }
}

What it looks like in Pleo Web App

Select Accounting from the main left-hand navigation.
Select Export from the sub-menu.
Click on a row to open the details panel for that expense.
Select the Vendor drop-down menu and type “Kaffehuset” to search.

“Kaffehuset AS” now shows Denmark, confirming the country/currency update was applied.

Vendor dropdown on an expense showing Kaffehuset AS updated to Denmark

Handling Edge Cases

See Handling Edge Cases on How to Create Vendors for partial-failure and unknown-outcome handling, which applies to this write too.

Result

Vendor	AS Status	Pleo State Before	Action	Final Pleo State
Kaffehuset AS (EXT-004)	Active	Active, country differed	Updated	Active

What Comes Next?

this how-to is part of:

Vendor Sync Workflow Guide

Get Started

Integration Design

Workflow Guides

How-to's

How to Update Vendors

Prerequisites

Scenario

Steps

1. Update the Vendor

Example Response

What it looks like in Pleo Web App

Handling Edge Cases

Result

What Comes Next?

​Prerequisites

​Scenario

​Steps

​1. Update the Vendor

​Example Response

​What it looks like in Pleo Web App

​Handling Edge Cases

​Result

​What Comes Next?

​Related Reading

Prerequisites

Scenario

Steps

1. Update the Vendor

Example Response

What it looks like in Pleo Web App

Handling Edge Cases

Result

What Comes Next?

Related Reading