> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/expensify.md).

# Expensify

Expensify is an expense management platform for receipt capture, expense reports, corporate cards, and reimbursement. Connect to work with policies, reports, and expenses.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Expensify | Credentials    |

#### Expensify

Connect to Expensify with a partner user ID and secret generated at <https://www.expensify.com/tools/integrations/>. The pair inherits the access of the Expensify account that generated it.

**Set up in Expensify**

1. Prepare the Expensify account or service that the workflow will access. Grant access to the required resources and operations.
2. **Partner User ID:** The partnerUserID half of an Expensify credential pair. Generate a pair at <https://www.expensify.com/tools/integrations/> while signed in as the account whose access the integration should inherit.
3. **Partner User Secret:** The partnerUserSecret half of the same pair. Expensify shows it once, when the pair is generated; generate a new pair if it was not saved.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Expensify**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field       | Required | What to enter                                                                                                                                                                                                                                                                  |
| ------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Partner User ID     | Yes      | The partnerUserID half of an Expensify credential pair. Generate a pair at <https://www.expensify.com/tools/integrations/> while signed in as the account whose access the integration should inherit. [Provider instructions](https://www.expensify.com/tools/integrations/). |
| Partner User Secret | Yes      | The partnerUserSecret half of the same pair. Expensify shows it once, when the pair is generated; generate a new pair if it was not saved. [Provider instructions](https://www.expensify.com/tools/integrations/).                                                             |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Expensify** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Create Expense Report

Create an expense report in Expensify with its expenses attached, so receipt data captured earlier in a workflow becomes a filed report.

**Inputs**

| Field                | Type            | Required | Description                                                                                                                                                                                                    |
| -------------------- | --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Policy               | select (string) | Yes      | The workspace the report is filed under. Options load from the selected connection.                                                                                                                            |
| Employee email       | string          | Yes      | The account the report is created in. Use the email of the account that generated the connection's credentials unless it has advanced permissions.                                                             |
| Report title         | string          | Yes      | Name shown on the report in Expensify.                                                                                                                                                                         |
| Expenses             | object\_array   | Yes      | The expenses to put on the report. Each needs a date, merchant, amount, and currency.                                                                                                                          |
| Custom report fields | object          | No       | Values for the workspace's custom report fields. Each key is the field name with every non-alphanumeric character replaced by an underscore, so a field shown as "Reason of trip" is keyed "Reason\_of\_trip". |

**Outputs**

| Field              | Type    | Description                                  |
| ------------------ | ------- | -------------------------------------------- |
| Report ID          | string  | Unique ID of the report Expensify created.   |
| Report name        | string  | Name Expensify stored for the report.        |
| Number of expenses | integer | How many expenses were sent onto the report. |
| Policy ID          | string  | The workspace the report was filed under.    |

#### Export Report

Export Expensify reports and their expenses, filtered by state, workspace, date, or ID. Returns the reports as structured data and as a file, so an approved batch can be handed to accounting.

**Inputs**

| Field                            | Type                      | Required | Description                                                                                                                                                                                                                                                           |
| -------------------------------- | ------------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Report states                    | multiple\_select (string) | No       | Which report states to include. Leave empty for every state. For an accounting export, this is usually Approved and Reimbursed. Available values: Open (OPEN), Processing (SUBMITTED), Approved (APPROVED), Reimbursed (REIMBURSED), Closed (ARCHIVED). Default: \[]. |
| Report IDs                       | string                    | No       | Export only these reports, comma-separated.                                                                                                                                                                                                                           |
| Policy IDs                       | string                    | No       | Restrict the export to these workspaces, comma-separated.                                                                                                                                                                                                             |
| Start date                       | string                    | No       | Only reports submitted or created on or after this date, as yyyy-mm-dd. This does not filter by expense date, and the range cannot exceed one year.                                                                                                                   |
| End date                         | string                    | No       | Only reports submitted or created on or before this date, as yyyy-mm-dd. This does not filter by expense date.                                                                                                                                                        |
| Approved after                   | string                    | No       | Only reports approved after this date. Filters on approval date, not on expense date.                                                                                                                                                                                 |
| Skip reports already labelled    | string                    | No       | Leave out reports already marked with this export label, so a repeated run does not export the same report twice.                                                                                                                                                     |
| Mark exported reports with label | string                    | No       | Tag every report this run exports with the given label. This changes the reports in Expensify.                                                                                                                                                                        |
| Maximum reports                  | integer                   | No       | Cap on how many reports to export.                                                                                                                                                                                                                                    |
| Format                           | select (string)           | No       | File format of the export. JSON also gives you the reports as structured output; the others are file-only. Available values: JSON, CSV, XML, Text. Default: json.                                                                                                     |
| Custom Freemarker template       | textarea                  | No       | Advanced: your own Freemarker template controlling the file's contents. Leave empty to use the built-in JSON template.                                                                                                                                                |

**Outputs**

| Field             | Type          | Description                                                 |
| ----------------- | ------------- | ----------------------------------------------------------- |
| Reports           | object\_array | The exported reports, each with its expenses.               |
| Number of reports | integer       | How many reports the export matched.                        |
| Export file       | file          | The exported file, ready to attach or hand to another step. |
| File name         | string        | Name Expensify gave the generated export.                   |

#### Get Policy

Read an Expensify workspace's setup: its expense categories, tag lists, custom report fields, tax rates, and members with their approval routing.

**Inputs**

| Field    | Type                      | Required | Description                                                                                                                                                                                                |
| -------- | ------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Policies | multiple\_select (string) | Yes      | The workspaces to read. Options load from the selected connection.                                                                                                                                         |
| Sections | multiple\_select (string) | No       | Which parts of the policy to return. Defaults to all of them. Available values: Categories, Tags, Report fields, Tax rates, Members. Default: \["categories", "tags", "reportFields", "tax", "employees"]. |

**Outputs**

| Field              | Type          | Description                                       |
| ------------------ | ------------- | ------------------------------------------------- |
| Policies           | object\_array | The requested workspaces and their configuration. |
| Number of policies | integer       | How many policies were returned.                  |

#### Create Policy

Create a new Expensify workspace owned by the connected account. The workspace starts with Expensify's default expense categories and no members. Note that workspaces cannot be deleted through the API and that Expensify bills per active member per workspace.

**Inputs**

| Field          | Type            | Required | Description                                                                                                                                                                     |
| -------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Workspace name | string          | Yes      | Name for the new workspace.                                                                                                                                                     |
| Plan           | select (string) | No       | Which Expensify plan the workspace runs on. Team is the default; corporate adds approval workflows and costs more per member. Available values: Team, Corporate. Default: team. |

**Outputs**

| Field          | Type   | Description                                   |
| -------------- | ------ | --------------------------------------------- |
| Policy ID      | string | Unique ID of the workspace Expensify created. |
| Workspace name | string | Name Expensify stored for the workspace.      |
| Plan           | string | Plan the workspace was created on.            |

#### Update Employees

Add or update people on an Expensify workspace: who they submit reports to, their role, and their approval limit. Marking someone terminated removes them from the workspace. Use the preview option to see what a sync would change before it runs.

**Inputs**

| Field        | Type          | Required | Description                                                                                                                     |
| ------------ | ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Employees    | object\_array | Yes      | The employees to add or update. Each needs an email, a manager's email, your own employee ID, and the workspace to add them to. |
| Preview only | boolean       | No       | Ask Expensify what it would change without changing anything. Useful to check a sync before letting it run. Default: false.     |

**Outputs**

| Field                    | Type          | Description                                               |
| ------------------------ | ------------- | --------------------------------------------------------- |
| Employees updated        | integer       | How many employee records Expensify processed.            |
| Added to a workspace     | array         | Employees newly added to a workspace by this sync.        |
| Removed from a workspace | array         | Employees this sync took off a workspace.                 |
| Skipped                  | object\_array | Employees Expensify declined to process, with its reason. |
| Was a preview            | boolean       | Whether this run only previewed the changes.              |
| Request ID               | string        | Expensify's identifier for this sync.                     |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/expensify.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
