How to Create a Vendor in the AS

This how-to covers creating the vendor record in the Accounting System from a detected DRAFT Pleo Vendor. Run this after How to Detect Draft Vendors, which covers detecting the DRAFT Vendor in Pleo.

Prerequisites

Before you begin:

You have completed How to Detect Draft Vendors and have the DRAFT Vendor’s details and Pleo id
Your integration can call the target Accounting System’s own API to create a vendor record

Scenario

This how-to continues from the How to Detect Draft Vendors scenario: a DRAFT Vendor “Greenfield Logistics” was detected in Pleo with id: c27ed4d6-3d3d-458e-8f3f-735fdf32a3bc.

Steps

1. Create the Vendor in the AS

Using the DRAFT Vendor’s name, country, defaultCurrency, registrationNumber, and taxRegistrationNumber, create the corresponding vendor record in the Accounting System. Example Pseudo:

asVendor = createVendorInAS({
    name:                  draftVendor.name,
    country:               draftVendor.country,
    defaultCurrency:       draftVendor.defaultCurrency,
    registrationNumber:    draftVendor.registrationNumber,
    taxRegistrationNumber: draftVendor.taxRegistrationNumber,
    // If the AS supports a custom reference/memo field, store draftVendor.id
    // (and draftVendor.companyId, for multi-company integrations) here now.
    // Handling Edge Cases below needs this for exact retry lookups, not name matching.
    referenceField:        draftVendor.id
})

// asVendor now has an AS-assigned identifier, used as externalId,
// and optionally an AS-assigned account code, used as code

Example Result

Field	Value
AS-assigned identifier (→ `externalId`)	`AS-VENDOR-7841`
AS-assigned account code (→ `code`)	`2041`

Handling Edge Cases

AS creation fails: do not call activate. Leave the Vendor as DRAFT in Pleo and retry on the next detection cycle.

try:
    asVendor = createVendorInAS(draftVendor)
    activateVendor(draftVendor.id, asVendor.externalId, asVendor.code)
catch ASCreationError:
    log("Failed to create vendor in AS, will retry")
    // leave vendor as DRAFT, do not call activate

Result

The table below recaps the outcome for this Vendor so far.

Vendor	Pleo State Before	Action	Pleo State After
Greenfield Logistics	DRAFT	Created in AS	DRAFT (unchanged)

The vendor now exists in the Accounting System, with an AS-assigned externalId and, optionally, a code. It remains DRAFT in Pleo until you report these identifiers back via activation.

What Comes Next?

this how-to is part of:

Vendor Creation Workflow Guide

Get Started

Integration Design

Workflow Guides

How-to's

How to Create a Vendor in the AS

Prerequisites

Scenario

Steps

1. Create the Vendor in the AS

Example Result

Handling Edge Cases

Result

What Comes Next?

​Prerequisites

​Scenario

​Steps

​1. Create the Vendor in the AS

​Example Result

​Handling Edge Cases

​Result

​What Comes Next?

​Related Reading

Prerequisites

Scenario

Steps

1. Create the Vendor in the AS

Example Result

Handling Edge Cases

Result

What Comes Next?

Related Reading