Implementation
See the corresponding how-to article for API usage and step-by-step instructions:Purpose
- Finalise Export Job processing.
- Reflect the aggregated outcome of all Export Items.
- Enable auditing, visibility, and downstream workflows.
Export Job Status Events
Post an Export Job Event using one of the following outcomes:| Condition | Event | Additional Fields |
|---|---|---|
| All Export Items successful | completed | — |
| Some items failed | completed_with_errors | failureReason, failureReasonType |
| All items failed | failed | failureReason, failureReasonType |
failureReasonType Guidance
- Default value:
accounting_system_validation_failure - Use specialised values when defined in Integration Specifications.
Implementation Guidance
- Send the Export Job Event only once processing is fully complete.
- Ensure all Export Item statuses are final before completing the job.
- Do not complete jobs prematurely.
- Processing has finished.
- Results can be surfaced to users.
- Follow-up workflows may begin.
Expected Outcome
At the end of this step:- The Export Job reflects the true batch outcome.
- Users can review results in Pleo.
- The export lifecycle is complete.
Upstream Dependencies
- Export Job has been claimed (status = in_progress)
- Fetch Export Item Data (data layer)
- Bookkeeping method resolved
- Accounts Mapping – determines which GL accounts are debited and credited
- Data Mapping – ensures amounts, dates, dimensions, identifiers, and VAT/tax information are recorded correctly
- Attachment Handling – links receipts and supporting documentation
- Accounting Periods – assigns entries to the correct accounting period
- Posting Behaviour – determines whether entries are created as drafts or finalised
- Export Item status update – updates outcome of Export Item (
successfulorfailed)
What Comes Next?
Related Reading
- How to Update & Complete the Export Job
- Export Integration Workflow Guide
- AS/ERP Processing Workflow Guide