Expenses

Choose between dynamic Fields and direct JSON payloads when creating, updating, and submitting expenses and expense reports. Create, update, and submit expenses and expense reports using either dynamic Fields or direct ASM/JSON payloads.

Overview

The Expense API supports two formats for creating and updating expenses and expense reports:

Format	Recommended for	Description
Dynamic Fields	User-facing applications	Fetch server-driven field definitions, render the returned form, and submit the completed fields payload. This is the recommended approach because the form automatically stays up to date with Findity’s latest expense rules, validations, and organization-specific configuration.
ASM / JSON format	Controlled backend-to-backend integrations	Build the expense or report object directly and submit it as JSON. Use this only when your integration owns the data model and can stay aligned with Findity’s API schema and business rules.

We strongly recommend using Dynamic Fields for user-facing expense creation. Findity controls which fields are shown, which values are required, and when fields need recalculation — so your UI stays current without hardcoding expense rules.

Use this page as a starting point, then continue to the detailed guide for the format you want to implement:

Supported expense types

The Expense API supports these expense types:

Expense type	Description	`type` value
Receipt expense	Standard purchases with receipts	`ReceiptVerification`
Mileage	Distance-based travel claims	`CarSpecification`
Per diem / Subsistence	Daily allowances for business travel	`SubsistenceAllowance`
Food benefits	Meal benefit reporting	`FoodBenefitsSpecification`

Last modified on August 31, 2026

⌘I

Home

MCP Server

API Basics

Guides

Overview

Supported expense types

​Overview

​Supported expense types

Overview

Supported expense types