# PATIENT_BILLING_NOT_ALLOWED

Canonical page: https://docs.ovok.com/errors/patient-billing-not-allowed

**HTTP 403.** Problem type: [`https://docs.ovok.com/errors/patient-billing-not-allowed`](https://docs.ovok.com/errors/patient-billing-not-allowed).

## What this means [#what-this-means]

Your access policy does not allow this patient billing action. Coverages need a `patient_billing_coverages` row with the interaction (`read`, `create`, `update` or `delete`) and, to change them, a Patient row that lets you update the patient. Plans, accounts and invoices are read with a `patient_billing_invoices` row with `read`. Charges need a `patient_billing_charges` row (`read`, `create` or `update`), and issuing an invoice from them a `patient_billing_invoices` row with `create`. Claims, eligibility checks and insurers' payments need a `patient_billing_claims` row (`read`, `create` or `update`). Plans, recorded invoices and prices are written only by a project admin or an admin ClientApplication.

## Troubleshooting [#troubleshooting]

1. Ask a project admin to add the capability row to your access policy (`PUT /v1/access-policies/<id>`).
2. To change a patient's coverages, check that your Patient rows let you update that patient.
3. Write plans, recorded invoices and prices from your app's server, with an admin ClientApplication of the project.

## Retry safely [#retry-safely]

Retrying changes nothing until the policy changes. Once it does, the same request succeeds.

## If the problem persists [#if-the-problem-persists]

Share the HTTP status, problem `type`, request path, response timestamp and `traceId` with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
