> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/cash-rounding/configuring-cash-rounding/changing-cash-rounding-settings.md).

# Changing Cash Rounding Settings

**Always refresh configuration after changing rounding settings.**

If you change any cash rounding setting (`cash.rounding.enabled`, `cash.rounding.strategy`, or `cash.rounding.adjustment`), you must manually refresh the configuration on Commander right away — go to **Configuration Client > Tools > Refresh Configuration**. Don't wait for the next scheduled Day Close to apply it.

**Why this matters:**

The POS starts using the new rounding settings as soon as a cashier logs in. But the FCC (the fuel/forecourt controller) doesn't update automatically — it keeps using the old settings until you either run a Refresh Configuration or a Day Close (which includes a refresh).

**What happens if you skip this:**

Some prepay transactions may not round correctly, potentially showing an incorrect "due inside" balance even after the customer has paid in full.

**Steps to follow after changing rounding settings:**

1. Update the setting(s) in **Configuration Client > Initial Setup > System Properties**.
2. Save the changes.
3. Refresh the configuration via **Configuration Client > Tools > Refresh Configuration**.
4. Test a prepay transaction that should round up, and confirm it settles correctly with no false "due inside" balance.


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/cash-rounding/configuring-cash-rounding/changing-cash-rounding-settings.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.
