> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/integrations/coupa-integration/setup-in-coupa/custom-fields-in-coupa.md).

# Custom fields in Coupa

Coupa supports custom fields on most objects, and Fairmarkit can take advantage of these custom fields to present a better user experience between the two systems. While these fields are not required, they are recommended to improve your integration experience.

### Fairmarkit Savings Amount <a href="#fairmarkitsavingsamount" id="fairmarkitsavingsamount"></a>

Fairmarkit is aware of benchmark pricing and can calculate the savings on a purchase requisition based on awarded data. Because this is useful to know in both Fairmarkit and Coupa, Fairmarkit supports a field that includes the savings value when data is exported back to Coupa

#### Setup

1. In Coupa, navigate to /custom\_fields.
2. On the **Requisitions** -> **Requisitions** object, add a new Money type field.
3. Enter the following information:
   * **Prompt**: We suggest selecting Savings (Fairmarkit).
   * **Field Name**: Enter fmkt\_savings\_amount.\
     This field is used for integration and you cannot customize the name.
   * **Active**: Select the Active check box.
4. Click **Done**.

### Fairmarkit Line Kind <a href="#fairmarkitlinekind" id="fairmarkitlinekind"></a>

With Fairmarkit line items, there is a distinction between items (physical products) and services (work to do). Because Coupa does not have this distinction, the Line Kind field tells Fairmarkit what type of line item is being imported.

Note: If a custom field isn't defined or the line item type cannot be determined, line items default to item type.

#### Setup

{% stepper %}
{% step %}
In Coupa, navigate to /custom\_fields.
{% endstep %}

{% step %}
On the **Requisitions** -> **Requisitions** object, add a new Drop Down type field.
{% endstep %}

{% step %}
Enter the following information:

* **Field Name**: Enter fmkt\_line\_kind.\
  This field is used for integration and you cannot customize the name.
* **Choices**: Select item and service.
* **Active**: Select the **Active** check box.
  {% endstep %}

{% step %}
Click **Done**.
{% endstep %}
{% endstepper %}


---

# 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.fairmarkit.com/buyers/integrations/coupa-integration/setup-in-coupa/custom-fields-in-coupa.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.