# Claim edit: Monetary amounts with a non-zero digit after the second decimal place

> Stedi now rejects 837P professional claims that contain a monetary amount, such as a line item charge, with a non-zero digit after the second decimal place.

Published Nov 19, 2026

Product: Claim edits

Stedi now rejects [837P professional claims](https://www.stedi.com/docs/healthcare/submit-professional-claims) that contain a monetary amount with a non-zero digit after the second decimal place.

## How the edit works

[X12 standards](https://www.stedi.com/docs/healthcare/intro-to-claim-submission#x12-hipaa-format) limit monetary amounts in a claim to 0, 1, or 2 decimal places. For example, `45.50` is valid. `45.505` isn't. If a monetary amount has more than two decimal places, the payer may reject the claim.

The edit checks monetary amounts at the claim level and on each service line. For example, it checks the claim's [total charge](https://www.stedi.com/docs/healthcare/api-reference/post-create-professional-claim-json#body.billing.totalCharge) and the [charge on each service line](https://www.stedi.com/docs/healthcare/api-reference/post-create-professional-claim-json#body.serviceLines.lineItemChargeAmount).

If a monetary amount has a non-zero digit after the second decimal place, such as `45.505` or `45.5001`, Stedi rejects the claim. This prevents later payer rejections, which take longer to resolve and delay payment for the provider.

Note

The edit doesn't reject zeros after the second decimal place. Instead, a repair removes them before sending the claim to the payer. For example, `45.500` becomes `45.5`.

## Rejection errors

How you get the error depends on how you submit the claim.

**CMS-1500 API**

If you submit a claim using the [Create Professional Claim (CMS-1500) JSON](https://www.stedi.com/docs/healthcare/api-reference/post-create-professional-claim-json) endpoint and the claim fails the edit, you'll get back a `201` response with an `errors` array in real time:

```json
{
  "errors": [
    {
      "description": "Invalid Amount Format. The Total Claim Charge Amount is limited to 0, 1, or 2 decimal positions. The submitted value, 150.555, exceeds the limit. Correct and resubmit."
    }
  ]
}
```

**Claim Submission API**

If you submit a claim using Stedi's other [Claim Submission API endpoints](https://www.stedi.com/docs/healthcare/intro-to-claim-submission#api-claim-submission) and the claim fails the edit, you'll get back an error response in real time. The response includes details in the `errors` array:

```json
{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Amount Format. The Total Claim Charge Amount is limited to 0, 1, or 2 decimal positions. The submitted value, 150.555, exceeds the limit. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}
```

**SFTP**

If you submit a claim using [SFTP](https://www.stedi.com/docs/healthcare/submit-claims-sftp-connection) and the claim fails the edit, Stedi will reject the claim with a [277CA claim acknowledgment](https://www.stedi.com/docs/healthcare/claim-responses-overview#277ca-claim-acknowledgment). The acknowledgment will include a related [claim status category code](https://x12.org/codes/claim-status-category-codes), [claim status code](https://x12.org/codes/claim-status-codes), and error message.

```text
STC*A7>697*[DATE]*U*[AMOUNT]******A7>178**Invalid Amount Format. The Total Claim Charge Amount is limited to 0, 1, or 2 decimal positions. The submitted value, 150.555, exceeds the limit. Correct and resubmit.~
```
