> For the complete documentation index, see [llms.txt](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/set-up-expensify-integration.md).
# Set Up Expensify Integration
**Expensify** integrates with **Rillet** to automatically create credit card charges and reimbursements in your accounting records, keeping your expense data synchronized and reducing manual entry. Setting up the integration requires configuration in both **Expensify** and **Rillet** so your categories, fields, and mappings align correctly across both systems.
### Create Categories in Expensify
Follow these steps to create categories in Expensify:
{% stepper %}
{% step %}
Go to **Settings > Workspaces**, then select the policy.
{% endstep %}
{% step %}
Go to **Categories**.
{% endstep %}
{% step %}
Create or modify categories as needed.
{% endstep %}
{% endstepper %}
Categories act as GL Accounts in Expensify.
### Create Fields in Expensify
Complete these steps to create fields in Expensify:
{% stepper %}
{% step %}
Go to **Settings > Workspaces**, then select the related policy.
{% endstep %}
{% step %}
Go to **Reports > Add New Field**.
{% endstep %}
{% step %}
Enter a field name.
{% endstep %}
{% step %}
Set the field **Type** to **Dropdown**, since this is required for compatibility with Rillet.
{% endstep %}
{% endstepper %}
Once created, your fields are ready to sync into Rillet, though some field types, such as Text and Date, do not sync, and new fields can only be created after Expensify is disconnected from previous ERP integrations.
### Connect Expensify in Rillet
Open the Expensify integration from the **Browse Integration** section of the **Launchpad**, or open the **Integrations** page as described in [**Access Your Integrations Management Page**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/access-your-integrations-management-page.md). Then continue with the steps in [**Complete the Expensify Connection**](#complete-the-expensify-connection) below.
### Complete the Expensify Connection
Follow these steps once you reach the **Integrations** page:
{% stepper %}
{% step %}
Click **Connect** on the **Expensify** card in the **Available** list, which you can narrow with the **Accounts payable** filter.
{% endstep %}
{% step %}
Enter the integration keys and setup details:
* **User ID:** Unique identifier for your Expensify account (found in the Integration Server page).
* **User Secret:** Authentication key used with the User ID.
* **Start From:** Date from which expenses should begin syncing into Rillet.
* **Charges Liability Account:** Account where credit card charges are temporarily recorded (e.g., Expensify Clearing or Credit Card Payable).
* **Reimbursement Payable Account:** Account used to track unpaid reimbursements owed to employees.
* **Reimbursement Date:** Date reference for reimbursement (e.g., expense date).
{% endstep %}
{% step %}
Click **Connect** to complete the setup once the fields are filled in.
{% endstep %}
{% step %}
Start with the **General** step once connected, and fill in the following fields:
* **Sync data from:** Select the date when expenses should begin syncing into Rillet.
* **Charges Liability Account:** Typically an Expensify Clearing Account or a Credit Card Payable Account. Charges remain here until matched with credit card bank feeds.
* **Reimbursement Liability Account:** Typically an Employee Reimbursement Payable Account to track unpaid reimbursements.
{% endstep %}
{% step %}
Select **Next Step** to continue.
{% endstep %}
{% step %}
**(Optional):** Map departments from Expensify to departments in Rillet, completing this mapping for each policy since policies have separate field sets:
* **Expensify Policies and Fields (left):** Values pulled from Expensify.
* **Rillet Field Mapping (right):** Select a corresponding Rillet field for each Expensify value.
{% endstep %}
{% step %}
Select **Next Step** to proceed.
{% endstep %}
{% step %}
Map categories from Expensify to Rillet GL accounts:
* **Expensify Categories (left):** Categories pulled from Expensify.
* **Rillet GL Accounts (right):** Select a default account per policy, and override only for accounts that should differ.
{% endstep %}
{% step %}
Select **Next Step** to proceed.
{% endstep %}
{% step %}
**(Optional):** Map additional fields, such as project codes, event expenses, or tags. Leave this step blank if you do not want to use this option.
{% endstep %}
{% step %}
Click **Finish Setup** after completing all mappings.
{% endstep %}
{% endstepper %}
The Expensify integration is now set up and ready to sync, automatically creating credit card charges and reimbursements in Rillet based on the mappings you configured.
### See Also
To learn more about the Expensify integration in **Rillet**, review these articles:
* [**Expensify Reimbursements & Charges**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/expensify-reimbursements-and-charges.md)
* [**Access Your Integrations Management Page**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/access-your-integrations-management-page.md)
* [**Brex Integration**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/brex-integration.md)
* [**Connect Ramp to Rillet**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/ramp/connect-ramp-to-rillet.md)
---
# 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.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/set-up-expensify-integration.md?ask=&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.
