> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-format-currency-values.md).

# How To: Format Currency Values

Learn how to format currency amounts with symbols, separators, decimals, and related list columns.

You can format currency output directly in merge fields and related list columns.

### Problem

You need to display monetary values with currency symbols, thousands separators, and decimal places.

### Solution

**For US Dollar formatting:**

```
${{!Opportunity.Amount format-number="#,###.##"}}
```

**Result:** `$4,222,300.80`

**For Euro formatting (European style):**

```
€{{!Opportunity.Amount format-number="#.###,##"}}
```

**Result:** `€4.222.300,80`

**For British Pounds:**

```
£{{!Opportunity.Amount format-number="#,###.##"}}
```

**Result:** `£4,222,300.80`

### In Related Lists

Format all prices in a product table:

```
<!--{{!
<lineitems>
<listname>opportunitylineitems</listname>
<column>PricebookEntry.Product2.name</column>
<column prefix="$" format-number="#,###.##">unitprice</column>
<column>quantity</column>
<column prefix="$" format-number="#,###.##">totalprice</column>
</lineitems>
}}-->
```

### Tips

* Add the currency symbol directly before the merge field. It is not part of the attribute.
* Use `#,###.##` for US and UK style.
* Use `#.###,##` for European style.
* The pattern works for numbers of any size.
* Values round when precision exceeds two decimal places.


---

# 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://help.sdocs.com/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-format-currency-values.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.