Skip to main content
This how-to explains the trigger event for the rest of Vendor Creation: a bookkeeper adding a new Vendor directly in Pleo, before it exists anywhere in the Accounting System. This is not an integration step. Your integration does not build or call anything here, a bookkeeper performs this action in the Pleo Web App. It matters to your integration because it produces the DRAFT Vendor that How to Detect Draft Vendors picks up next.

​
Scenario

This how-to uses a consistent example, carried through the rest of Vendor Creation: a bookkeeper adds “Greenfield Logistics” as a new Vendor while tagging an expense, before it exists yet in the Accounting System.

​
Steps

​
1. Verify that the Vendor doesn’t already exist

  1. Select Accounting from the main left-hand navigation.
  2. Select Export from the sub-menu.
  3. Click on a row to open the details panel for that expense.
  4. Select the Vendor drop-down menu and type “Greenfield Logistics” to search.
  5. The Vendor field returns no search results, confirming the Vendor doesn’t already exist.
Vendor drop-down field with no matches for Greenfield Logistics, only the option to create a new Vendor

​
2. Create the new Vendor

  1. Click the + Create a new vendor option inside the drop-down field, or click the + New vendor button above the Vendor field.
  2. The Create a new vendor modal opens.
  3. Fill in the Vendor’s details, such as name, country, currency, and optionally a tax number and registration number.
  4. Click Create.
Create a new Vendor form filled in with Greenfield Logistics details

A notification confirms the vendor is being created in the Accounting System:
Notification confirming Greenfield Logistics is being created in Custom API Integration

“Greenfield Logistics” is now selected on the expense, with a note below the Vendor field confirming the vendor is still being created:
Vendor field on an expense showing newly created Greenfield Logistics, not yet linked to the Accounting System

​
Result

After this action:
  • A new Vendor exists in Pleo with state: DRAFT
  • Its name, country, defaultCurrency, registrationNumber, and taxRegistrationNumber are set from what the bookkeeper entered
  • It has no code or externalId yet, those are assigned once your integration creates the record in the Accounting System and activates it
  • A v1.vendor.created webhook event has been emitted for it

​
What Comes Next?

this how-to is part of:
Vendor Creation Workflow Guide