> 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/expensify-reimbursements-and-charges.md).

# Expensify Reimbursements & Charges

With your **Expensify** integration set up, charges and reimbursements sync directly into **Rillet** as soon as their reports reach the required status. Charges appear in **Accounts Payable** as credit card expenses, while reimbursements are created as payable items you can match in the bank feed. If you have not yet configured the integration, see [**Set Up Expensify Integration**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/set-up-expensify-integration.md) to get started.

### Understand Expensify Sync Behavior

Rillet automatically syncs a credit card charge as a **Charge** once it has been added to a report and the report is in an **Approved** state. To review a synced charge, see [**Review a Synced Charge**](#review-a-synced-charge) below.

<figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FpLVZU2X488uiJFmGTxBC%2Fimage.png?alt=media&amp;token=317b67f9-40e2-4fd1-a80d-80e2d0dbd9c8" alt=""><figcaption></figcaption></figure>

Rillet automatically syncs a reimbursement as a **Reimbursement** once it has been added to a report and the report is in an **Approved** or **Reimbursed** state. To review a synced reimbursement, see [**Review a Synced Reimbursement**](#review-a-synced-reimbursement) below.

<figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FlcWCfjyxirM2UWM0iTvD%2Fimage.png?alt=media&amp;token=aa9775fc-6b70-4737-a705-f46069612ce6" alt=""><figcaption></figcaption></figure>

### Review a Synced Charge

Follow these steps to review a synced charge:

1. Go to **Accounts Payable > Charges** in Rillet.

   <figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FhEi9Y21vYENHnrj1DdN9%2Fimage.png?alt=media&amp;token=72036129-bf39-432a-a33c-5209bd7cf150" alt=""><figcaption></figcaption></figure>
2. Review the charge, which is imported as **Unpaid** by default.

   <figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FzWqgDCohMVSmYQ1JH67M%2Fimage.png?alt=media&amp;token=474d97d0-84f4-4edb-8b1c-1f3223237280" alt=""><figcaption></figcaption></figure>

Match this charge to its corresponding credit card transaction once it appears in your **Rillet Bank Feed**. This updates the charge's status from **Unpaid** and completes the reconciliation.

### Review a Synced Reimbursement

Complete these steps to review a synced reimbursement:

1. Go to **Accounts Payable > Reimbursements** in Rillet.

   <figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FBpUvjZF3WIzolVrV9PRf%2Fimage.png?alt=media&amp;token=2479f5c1-1c92-40df-9d85-f867e755cebd" alt=""><figcaption></figcaption></figure>
2. Review the reimbursement, which is imported as **Unpaid** by default.

   <figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FJg3NBhYRBIRrejDuO8kg%2Fimage.png?alt=media&amp;token=cfa62575-fbee-46ee-9c9b-31824fbea6a0" alt=""><figcaption></figcaption></figure>

Match this reimbursement to its corresponding payor transaction once it appears in your **Rillet Bank Feed**. This updates the reimbursement's status from **Unpaid** and completes the reconciliation.

### Frequently Asked Questions (FAQ) <a href="#undefined" id="undefined"></a>

<details>

<summary>What if the vendor does not already exist in Rillet?</summary>

Rillet will automatically create a new vendor if the Expensify vendor does not already exist.

</details>

<details>

<summary>How can I see what expenses have been synced?</summary>

You can view which reports have been exported in the Reviews listing view in Expensify.

<figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2Ff2VNyu393NyCRI5b4PIf%2Fimage.png?alt=media&amp;token=cab3ecc1-0001-48c8-a3a2-2ffd5561067d" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary>When are transactions synced? </summary>

Transactions sync only when they are included in a report with status Approved or Reimbursed.

</details>

<details>

<summary>How often do transactions sync?</summary>

Rillet syncs new approved or reimbursed reports every 1 hour.

</details>

### See Also

To learn more about the Expensify integration in **Rillet**, review these articles:

* [**Set Up Expensify Integration**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/set-up-expensify-integration.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/expensify-reimbursements-and-charges.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.