Skip to main content

Prerequisites

Before you begin:

Constraints

  • Maximum 100 items per API request
  • Each item must include its accountingEntryId
  • Supports both successful and failed updates

Steps

1. Collect Results

For each processed Export Item, ensure you have:
  • accountingEntryId (get this from /v3/export-items)
  • result: successful or failed (get this from your AS/ERP system)

2. Build Update Payload

For field definitions (externalId, externalUrl, exportedAt), supported failureReasonType values, and common error mappings, see the Integration Design: Update Export Items. Successful item
Failed item

3. Batch Items

Group items into batches of up to 100:

4. Send Request

API Endpoint: PUT v3/export-jobs/{jobId}/items Example parameters:
  • jobId: 8eb648ab-464b-42a0-ba17-eda703657e33
  • accountingEntryId: 59540ed2-0d68-4e36-9e31-58223975d9e9
  • accountingEntryId: 6678bcee-c6a4-4b49-bb1e-8f9fd653d16c
  • accountingEntryId: 9ea2ef81-4d73-460d-bbb4-ccf3da6f6f61
  • accountingEntryId: 0c76ea71-aaaa-4ece-bb68-e1166ccaea04

5. Handle Response

  • Retry on transient failures
  • Do not duplicate already successful updates

Example Response

Pleo Web App

Export Item results are recorded in Pleo but are not fully surfaced to users until the Export Job is completed. Once the Export Job is finalised:
  • Export status becomes visible in the Export queue
  • Failed items and error details are available for review

Result

After completing this step:
  • The job remains in the queue for auditing and compliance purposes
  • In Pleo’s Web App:
    • Export progress is accurately reflected in the Export queue tab
    • Errors are visible to users for review and correction

What Comes Next?


this how-to is part of: