> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/reconciliation/amex-sft-config.md).

# Set up the Amex transaction feed

Choose which transactions from your company's daily Amex file come into Reconciliation, and for which dates.

Use the **Manage AMEX SFT Config** page to choose which transactions from your company's daily Amex file come into Reconciliation as statement rows. Open it from **Reconciliation > Amex SFT Config** in the sidebar, which shows it to Owners, Super Admins and Managers.

{% hint style="info" %}
**Amex SFT Config** is in the sidebar only if your company uses Reconciliation with the daily Amex feed turned on. Mappings apply to your whole company, not one production.
{% endhint %}

The table lists each mapping's **Type**, **Identifier**, **Start Date** and **End Date**. Every hour, RollCredits checks for new Amex files and adds matching transactions, skipping rows already in Reconciliation. Each month's rows form one statement, such as "Nov 2026 - AMEX SFT". To match them to transactions, see [Match card statements to transactions](/reconciliation/matching.md).

## Add a mapping

1. Select **Create New**. The **Create AMEX SFT Mapping** window opens.
2. In **Type**, choose what to bring in:
   * **Card Tail Digits**: enter digits from the card number. A transaction matches when its card's last five digits contain them.
   * **Cardholder Name**: type a name. A transaction matches when the cardholder's name in the Amex file contains it, ignoring capital letters.
   * **All Transactions**: every transaction in the file.
3. If you want, choose a **Start Date**. Earlier transactions are left out, and RollCredits goes back through past Amex files to bring in matches from that date on.
4. If you want, choose an **End Date**. Later transactions are left out.
5. Select **Save**.

Without a start date, past files aren't checked.

## Don't mix All Transactions with other types

**All Transactions** mappings can't be combined with **Card Tail Digits** or **Cardholder Name** mappings. If the type you choose would mix them, **Save** or **Update** stays greyed out and a warning appears:

* Choosing **All Transactions** while other mappings use Card Tail Digits or Cardholder Name shows "Cannot use "All Transactions" mapping when filtered mappings (Card Tail Digits or Cardholder Name) already exist. Please delete the filtered mappings first."
* Choosing **Card Tail Digits** or **Cardholder Name** while another mapping uses All Transactions shows "Cannot create filtered mapping when "All Transactions" mapping already exists. Please delete the "All Transactions" mapping first."

## Edit a mapping

1. Select the **...** menu at the end of the mapping's row, then **Edit**.
2. In **Update AMEX SFT Mapping**, change the fields.
3. Select **Update**.

Past files are checked again only when you add a **Start Date** or move it earlier.

## Delete a mapping

1. Select the **...** menu at the end of the mapping's row, then **Delete**.
2. In **Delete AMEX SFT Mapping**, select **Confirm**.

{% hint style="warning" %}
Narrowing or deleting a mapping doesn't remove statement rows it already brought in. To remove them, see [Upload card statements](/reconciliation/matching/upload-statements.md).
{% endhint %}


---

# 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://knowledge.rollcredits.io/reconciliation/amex-sft-config.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.