¶ State-Subsidised FP17 Claim Submission
Status: verified against the live app, 10 September 2026 — the claims list, claim detail and submission were walked through end to end. Claims currently reach Transmitted; acceptance is not yet applied automatically (tracked separately), so the Accepted column can read zero on your dashboard.
¶ What you'll be able to do
After reading this guide you will understand how NHS FP17 claims work in VeriPath Dental — where a claim comes from, what the claims list shows, how to review a claim before sending it, how to submit it to the NHSBSA gateway, and what the statuses mean as it moves through the system.
Who does this? NHS claims belong to the practice manager / admin. Reception collects the patient's band charge; the clinician's charted treatment is what sets the band the claim is priced at.
Where claims come from: you do not create an FP17 claim by hand. Each NHS course of treatment produces one claim at the moment the course is closed and billed — see NHS Contract & FP17 Claims — The Full Journey.
¶ About FP17 claims
FP17 is the NHS form used to claim payment for NHS dental treatment. In VeriPath Dental each claim carries:
| Part of the claim | What it holds |
|---|---|
| Appointment | The visit the claim is anchored to (date, patient, type) |
| Course of treatment | The episode the claim came from (one claim per course) |
| Practice and performer | Where the work happened and which clinician did it |
| Band | Worked out from the treatment actually completed (below) |
| Patient charge — Leg A | The statutory band charge the patient owes (£0 if exempt) |
| NHS fee basis — Leg B | The claim's reference value, frozen once transmitted |
| Exemption | The exemption category, and whether evidence was seen |
| Treatment codes | The codes recorded for the work carried out |
| NHSBSA reference | Filled in once the claim has been transmitted |
The band is derived from the completed treatment, highest band wins — the same table the app uses:
| Band | Content | Patient charge | UDAs |
|---|---|---|---|
| Band 1 | Examination, radiographs, scale & polish, advice | £27.90 | 1 |
| Band 2a | 1–2 fillings/extractions | £76.60 | 3 |
| Band 2b | Three or more restorative teeth, or root canal on a non-molar | £76.60 | 5 |
| Band 2c | Root canal on a permanent molar | £76.60 | 7 |
| Band 3 | Laboratory work — crowns, bridges, dentures | £332.10 | 12 |
| Urgent | Emergency-only care | £27.90 | per contract (1.2 default) |
| Exempt course of treatment | Arrest of bleeding, suture removal, appliance repairs, nurse fluoride varnish | £0 | 0.5–1.2 |
A prescription-only course is logged as activity but produces no claim at all. Charges are England statutory rates as configured for 2026/27; the table is date-effective and maintained by your VeriPath administrator.
Statuses a claim moves through:
| Status | Meaning |
|---|---|
| Draft | Raised by closing the course, not yet submitted |
| Queued for submission | Signed and queued to send |
| Transmitted | Sent, with a gateway reference stored on the claim |
| Accepted | Accepted — the claim's UDAs count towards the contract |
| Partially paid | The gateway has paid part of the claim |
| Rejected | Rejected, with the reason shown; return it to Draft to correct and resend |
¶ Step 1 — Open the FP17 claims list
- Log in to VeriPath Dental.
- Click FP17 in the top navigation.
| Column | What it shows |
|---|---|
| Claim # | The claim's reference number |
| Appointment | The date of the appointment the claim is anchored to |
| Course | The course of treatment the claim came from (CoT #…) |
| Practice | Where the treatment happened |
| Performer | The clinician who did the work |
| Band | The band the claim is priced at, plus an exempt CoT badge where it applies, and an overdue badge if it is past the submission window |
| Patient charge | Leg A — what the patient owes (£0.00 for an exempt patient, N/A if none) |
| Status | The current status badge |
| Invoices | Any invoice raised for the claim, its amount and status, with an ERPNext link; "—" when there is none |
| View | Opens the claim's detail page |
The status badges make it easy to spot what needs action: Draft still needs sending, Queued and Transmitted are in flight, Rejected needs attention.
¶ Step 2 — Review a claim
Click View to open a claim.
- Appointment Details — the date, patient and appointment type.
- Claim Details — practice, performer, band, the course it came from, patient exemption, the NHS fee basis (Leg B) and the patient charge (Leg A). The fee basis is marked frozen — read-only after transmit once the claim has been sent.
- Treatment Codes — the codes recorded for the work carried out.
- Invoices for this claim — the patient-charge invoice raised when the course was closed, with a link to open it in ERPNext.
Two badges appear on the claim when they apply: exempt CoT — no patient charge (an exempt course of treatment, where the claim earns its fee basis but no patient charge) and outside 2-month submission window (see below).
Tip: check the band and the fee basis before sending. The band comes from the treatment completed on the course, so if it looks wrong, look at what was charted before the course was closed.
¶ Step 3 — Submit the claim
- On a Draft claim, click Submit to NHSBSA.
The app queues the claim (building and signing the submission payload) and then transmits it to the NHSBSA gateway in one action. A confirmation message appears — "Claim submitted — status: Transmitted." — the status badge updates, and the NHSBSA Reference is stored on the claim.
The two-month rule. A claim must be submitted within two months of the course being completed, or the UDA credit is lost. The app enforces this: a claim past the window is blocked at submission with an error naming the completion date, and the list and detail page show the overdue / outside 2-month submission window badge.
¶ Step 4 — What happens next
- Transmitted — the claim is with the gateway and carries its NHSBSA reference. Nothing further is needed from you at this point.
- Accepted — the claim's UDAs count towards the contract and the performer's delivery. You will see it on the UDA dashboard and the Contract performance panel on the NHS Ledger home. The patient-charge side is unaffected: that invoice was raised and settled when the course was closed.
- Partially paid — the gateway has paid part of the claim; the balance is picked up in month-end reconciliation.
- Rejected — the reason is shown in a red alert on the claim. Fix the cause and use Return to Draft, then submit again.
Month-end (statement, three-way match, journal and associate pay) is covered in NHS Contract & FP17 Claims — The Full Journey, Part 7.
¶ Useful tips
- One course, one claim. Never try to re-raise a claim for treatment that has already been billed — the app now refuses to open a second course against a billed appointment, and points you at the claim that already covers it.
- Check before you send. Band, fee basis, exemption and treatment codes are all read-only once transmitted.
- Mind the two months. Draft claims sitting past the window lose their UDA credit.
- Keep the reference. The NHSBSA reference on the claim is what you quote in any query.