> For the complete documentation index, see [llms.txt](https://docs.fieldmotion.com/fieldmotion-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fieldmotion.com/fieldmotion-api-docs/invoice/_setdiscount.md).

# \_setDiscount

Sets the Discount value in an Invoice

### Parameters

#### id

The ID of the Invoice being modified

#### val

The value of the discount, 1 is considered a euro (e.g 1.2 => €1.20)

### Example

```
FM_api('Invoice_setDiscount',[
  'id'=>'30151',
  'val'=>'15'
]);
```

### Result

#### On Success

```
{"ok":1}
```

#### On Failure

If the "id" parameter is missing or has a value less than 1:

```
{"error":"missing or invalid parameter: id"}
```

If the "val" parameter is missing:

```
{"error":"missing or invalid parameter: val"}
```

If the Invoice being modified has its Status set as Paid:

```
{"error":"cannot edit invoices that are marked Paid"}
```

If the "val" parameter value contains non-numeric characters (e.g a-z):

```
{"error":"invalid discount"}
```


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fieldmotion.com/fieldmotion-api-docs/invoice/_setdiscount.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.