Skip to main content
Each Export Item in Pleo carries a bookkeeping.method datapoint, which defines how the expense should be recorded in the Accounting System. The integration must read this value and branch processing accordingly. This step ensures that the expense is recorded in line with the selected bookkeeping method while respecting the default handling rules for non-payable transactions.

Implementation

See the corresponding how-to article for API usage and step-by-step instructions:

Purpose

Before any accounting entries are created, each Export Item must have a resolved bookkeeping method. This resolution step ensures that downstream processes are applied correctly. It determines:
  • How the expense is represented in the Accounting System
  • Which downstream processes apply, including Accounts Mapping, Data Mapping, Invoice/Payment creation, and Posting Behaviour
Resolution ensures consistency with platform rules and supports correct handling of default transaction types.

Resolution Logic

The integration reads the bookkeeping.method datapoint on the Export Item and applies the following logic:
Bookkeeping MethodActionNotes
journalRecord the expense as a Journal EntryStandard double-entry ledger posting
accounts_payableRecord the expense using the Accounts Payable workflowGenerates invoice and payment entries; supports credit notes and split expenses
noneRecord the expense as a Journal EntryRepresents non-payable balance adjustments such as wallet loads, wallet unloads, and balance amendments; does not require Accounts Payable handling
nullSee legacy support

Notes on Default Behaviour

  • Certain transaction types are always recorded as Journal Entries regardless of explicit configuration:
    • Wallet loads
    • Wallet unloads
    • Balance amendments
  • These default rules ensure consistency with Platform Capabilities, where these transactions do not represent vendor liabilities.

Expected Outcome

After resolution:
  • Each Export Item is tagged with a resolved bookkeeping method.
  • Downstream processes rely on this resolution to correctly apply Accounts Mapping, Data Mapping, Invoice/Payment creation, Attachment Handling, Accounting Periods, and Posting Behaviour.

What Comes Next?