> 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-credit-card-charges.md).

# Sync Credit Card Charges

When a transaction is made using a **Ramp**-issued card, whether physical or virtual, it can be synced into **Rillet** as a payable once it has been properly coded and marked ready. This article explains how to prepare, mark, and sync credit card charges from **Ramp** into **Rillet**.

### Before You Begin

Ensure you have:

* Your Ramp integration active in Rillet.
* The **GL Accounts** and any required custom fields assigned in Ramp.

### Mark Transactions as Ready to Sync

Follow either of these options to mark charges as **Ready to Sync** in Ramp, which is required before they can appear in Rillet:

#### Mark Transactions in Bulk

Use these steps to mark transactions in bulk:

1. Go to **Accounting > Card Transactions** in Ramp.
2. Select the checkbox at the top to **Select all** transactions.

   <figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2Fa2EYTFijD0OYLYOt3gAp%2Fsyn%20credit%20card%20changes%202.png?alt=media&amp;token=230d563d-236f-44bb-a8e5-87a733ceeeec" alt=""><figcaption></figcaption></figure>

With all transactions selected, click **Mark Ready** in the banner at the bottom of the screen to mark them as ready to sync.

#### Mark Individual Transactions

Complete these steps to mark individual transactions:

1. Fill in the required GL Account and classification fields.
2. Click the **Ready to Sync** checkmark on the right side of the transaction row.

   <figure><img src="https://612265232-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNpXFVFZpTQck3vIrjmHB%2Fuploads%2FeGXQ30rI6QfLY0C3QNhG%2Fsyn%20credit%20card%20changes%203.png?alt=media&amp;token=a7a1d971-8ee9-4566-9875-d81a087e900d" alt=""><figcaption></figcaption></figure>

Once marked, the transactions will move to the **Ready to Sync** section. Only transactions in this section will be synced to Rillet automatically.

### Frequently Asked Questions (FAQ)

<details>

<summary>Where do I find synced charges in Rillet?</summary>

Rillet pulls **Ready to Sync** charges from Ramp every hour. Once synced, charges appear in **Accounts Payable > Charges** and the **Vendors** tab updates with the associated vendor. You can click a charge to view more details, including a direct link back to the original Ramp transaction.

</details>

<details>

<summary>How are bank payments matched to synced charges?</summary>

When a payment is made from your bank to cover a Ramp charge, Rillet automatically matches the transaction with your bank feed entry, giving you full visibility into each synced charge without needing to switch back to Ramp to confirm the details.

</details>

<details>

<summary>Does a credit card charge create a journal entry on its own, or only once it's matched to a bank transaction? Which accounts are debited and credited?</summary>

A Ramp charge posts its own journal entry as soon as it syncs into Rillet, once marked Ready to Sync in Ramp, since it's pulled in as a payable within the hour regardless of any bank matching. The entry debits the GL account mapped to that charge's category or vendor and credits the **Ramp Credit Card Account**, the GL liability account configured for your Ramp balance during setup (see [**Connect Ramp to Rillet**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/ramp/connect-ramp-to-rillet.md)). The later bank-transaction match, triggered when your organization pays the Ramp card balance, only reconciles the cash side, since the expense entry itself was already created at sync time.

</details>

### **See Also**

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

* [**Connect Ramp to Rillet**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/ramp/connect-ramp-to-rillet.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)
* [**Transaction Classification & Matching**](/EjmEP4KZ9BVp9j2ho4Mh/cash-reconciliation/transaction-classification-and-matching.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-credit-card-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 `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.