Retrieve an expense

The ID of the expense.

Indicates the state of the expense. Possible values:

• missing_info: The expense is missing some required information.

  This is the initial state of the expense when it's first created. Once the missing information is provided, the expense is ready to be submitted.

• awaiting_review: The expense is awaiting approval before it can be completed.

  The approver can approve, reject, or request refund for the expense. It is also possible for the submitter to undo the submission at this stage.

• rejected: The expense has been rejected by the approver.

  The expense submitter (typically, the payer) should fix the issue that was the reason for the rejection and resubmit the expense.

• refund_requested: The expense has been rejected and refund has been requested.*

  This state is possible for card transactions. It indicates that following the review, the approver rejected the expense and requested that it be refunded back to the business account. This can happen, for example, if an employee accidentally makes a personal purchase with their business card. Once refunded, the admin can mark this expense as refunded.

• refunded: The expense has been refunded.*

  This state indicates that the admin has marked the expense as refunded.

• approved: The expense has been approved and is now completed.*

• reverted: The expense has been reverted.

  This status indicates that the transaction related to the expense has been reverted. In such a case, the expense status is automatically set to reverted, and the expense is completed. This can happen, for example, when the transaction has been reverted by the merchant.

*Additionally, if an admin has previously approved the expense, marked it as refunded, or requested a refund, they can revert their decision. In such a case, the expense goes back to the initial missing_info state.

For more information, see the guides: Retrieve expenses and receipts.

The type of the transaction related to the expense.

The description of the expense.

The date and time the expense was submitted in ISO 8601 format.

The date and time the expense was completed in ISO 8601 format.

The name of the team member who made the transaction, refund request, or ATM withdrawal, or the name of the business if the related transaction is of type fee.

The name of the merchant.

The ID of the transaction related to the expense. Not available for transactions of type external.

The expense data depends on the type of the expense and whether it has been completed.

Typically, it's the date and time of the expense transaction in ISO 8601 format.

• If the transaction related to the expense is completed, it is the date and time of its completion (completed_at).
• Otherwise, it is the date and time of its creation (created_at).

For reimbursements, it's the payment date provided in the reimbursement request.

The labels added to the expense, organised in groups.

You can have up to five label groups, with unlimited number of labels in each group.

The labels are provided as an object, where each key is a name of a label group, and the values corresponding to the keys are arrays of labels from those groups.

The splits of the expense.

A single expense can be divided into multiple parts (splits), for example, to allocate different portions of the expense to different categories.

The IDs of the receipts related to the expense.

The expense amount in billed currency.