> 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/ramp/sync-employee-reimbursements.md).
# Sync Employee Reimbursements
Employee reimbursements submitted through **Ramp** sync into **Rillet** automatically once they are approved and marked as **Ready to Sync**, keeping your accounts payable records accurate without manual entry. This article explains how to prepare reimbursements in **Ramp** and how to review them once they appear in **Rillet**.
### Before You Begin
Ensure you have in Ramp:
* A **GL Account** and any required custom fields (e.g., Department) assigned.
* The reimbursement marked as **Ready to Sync** under the **Actions** column.
### Mark Reimbursements as Ready to Sync
Follow these steps to prepare reimbursements for sync:
1. Go to **Accounting > Reimbursements** in Ramp.
2. Select the appropriate **GL Account** and custom fields.
3. Click **Ready to Sync** in the **Actions** column.
Once marked, the reimbursements will move to Ramp's **Ready to Sync** section and will be pulled into Rillet automatically every hour.
### Find Synced Reimbursements in Rillet
Use these steps to find reimbursements in Rillet:
1. Click **Accounts Payable** in the left-side menu of the dashboard.
2. Select **Vendors** from the **Accounts Payable** dropdown.
3. Open the vendor's record to review the synced reimbursement.
Each synced reimbursement includes a **Ramp label** to help you identify its origin and a **direct link** to view the reimbursement in Ramp.
### Frequently Asked Questions (FAQ)
When are reimbursements marked as paid in Rillet?
Reimbursements remain unpaid in Rillet until they are matched with the corresponding bank payment. Once matched, each reimbursement gives you a complete, traceable record from the original Ramp submission through to final payment in Rillet. To learn more about payment matching, see [**Matching and Unmatching Transactions with Rillet**](/EjmEP4KZ9BVp9j2ho4Mh/cash-reconciliation/transaction-classification-and-matching/matching-and-unmatching-transactions-with-rillet.md).
### **See Also**
To learn more about the Ramp integration in **Rillet**, review these articles:
* [**Expensify Reimbursements & Charges**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/expensify-reimbursements-and-charges.md)
* [**Sync Vendor Bills**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/ramp/sync-vendor-bills.md)
* [**Sync Ramp Card Payments**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/ramp/sync-ramp-card-payments.md)
* [**Prepaid Expenses**](/EjmEP4KZ9BVp9j2ho4Mh/accounts-payable/prepaid-expenses.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 dynamically 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/ramp/sync-employee-reimbursements.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 `build a script that syncs our docs to a CMS` 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.
