Expense data model
View field support, webhooks, and list parameters for each integration on the Supported Integrations page.
| Field | Type | Required | Description |
|---|---|---|---|
id | string | No | unique identifier for the expense |
created_at | string (date-time) | No | when the expense was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
updated_at | string (date-time) | No | when the expense was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
matter_id | string | No | pointer to the Legal Matter this expense is recorded against |
user_id | string | No | HR Employee who incurred or recorded the expense (reference to HrisEmployee) |
description | string | No | free-text description of the expense |
incurred_at | string (date-time) | No | date the expense was incurred (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
quantity | number | No | number of units |
price_amount | number | No | unit price |
total_amount | number | No | total amount of the expense |
currency | string | No | ISO 4217 currency code |
type | enum | No | hard cost, soft cost or other Values: HARD_COST, SOFT_COST, OTHER |
category | string | No | the vendor's expense category name |
is_billable | boolean | No | whether the expense is billable |
is_billed | boolean | No | whether the expense has been billed |
invoice_id | string | No | pointer to the Accounting Invoice this expense was billed on (reference to AccountingInvoice) |
expense_code | string | No | UTBMS/LEDES expense code |
metadata | LegalMetadata[] | No | custom field values |
metadata[].id | string | No | the custom field identifier |
metadata[].slug | string | No | the custom field key |
metadata[].value | object | No | the custom field value |
metadata[].namespace | string | No | the scope or origin of the custom field |
metadata[].format | enum | No | the data type of the value Values: TEXT, NUMBER, DATE, BOOLEAN, FILE, TEXTAREA, SINGLE_SELECT, MULTIPLE_SELECT, MEASUREMENT, PRICE, YES_NO, CURRENCY, URL |
metadata[].extra_data | object | No | additional data about the custom field |
Are we missing anything? Let us know
Was this page helpful?