All systems operational · 99.98% uptime
← All articles
NEMT OPERATIONS12 min · 01.07.2026

Muster 4 fully explained: from prescription to paid invoice

Approval requirements, deadlines, common insurer rejection reasons — and where digital capture saves real money.

If you run patient transport in Germany, your revenue depends on one piece of paper: the Muster 4 form, officially the "Verordnung einer Krankenbeförderung" — the medical transport prescription. It decides whether a ride can be billed at all, to whom, and under which conditions. Yet in many operations the form is treated as an afterthought — until the first wave of insurer rejections lands in the mailbox. This article walks the full path once: from the doctor's office to the paid invoice.

The legal basis: § 60 SGB V

The entitlement to transport cost coverage sits in § 60 of the German Social Code, Book V (SGB V). The statutory health insurer covers transport costs when the ride is connected to an insured treatment and is necessary for compelling medical reasons. What that means in practice is defined by the Krankentransport-Richtlinie, the transport directive issued by the Federal Joint Committee: it specifies which means of transport may be prescribed in which situation, and which rides require prior approval.

For the transport operator, one simple truth follows: without a correctly completed and — where required — approved Muster 4, there is no payment. It does not matter how flawlessly the ride itself was carried out.

What must be on the prescription

Muster 4 is issued by the treating physician under the statutory scheme, and in certain cases by the hospital. The critical fields are:

  • Reason for transport: outpatient or inpatient treatment, high-frequency treatment such as dialysis or oncological therapy, or a permanent mobility impairment.
  • Means of transport: taxi or hire car, ambulance transport vehicle (KTW) with professional attendance, or qualified transport. The doctor must tick the medically necessary option — not the most convenient one.
  • Treatment dates and facility: for recurring prescriptions, the period and frequency.
  • Outbound and return leg: only what is prescribed may be driven — nothing beyond that.

In practice, many claims fail not because of the ride but because of a missing tick box or a forgotten date. Operators who do not check prescriptions for completeness at order intake merely push the problem downstream — to the point where it becomes expensive.

The approval requirement: the decisive fork

This is where payment is won or lost. The ground rules:

  1. Rides to inpatient treatment generally do not require prior approval. The prescription is sufficient.
  2. Rides to outpatient treatment are, as a rule, subject to approval — and that approval must be obtained before the ride starts. Retroactive approval is the exception, never the plan.
  3. The transport directive defines the exceptional cases in which outpatient rides are prescribable at all: high-frequency treatments (typically dialysis, oncological chemotherapy or radiotherapy) and insured persons with a permanent mobility impairment.

Since 2019 there has also been an important simplification: for insured persons holding the disability markers aG, Bl or H, or care grade 4 or 5 (and care grade 3 with a permanent mobility impairment), approval is deemed granted. This approval fiction removes the application — but it does not remove the prescription itself, nor the need to document it.

Rule of thumb for dispatch: no outpatient ride without a clarified approval status. "The insurer always pays for this" is not a legal basis.

Deadlines and the process in practice

The typical sequence: the doctor issues the prescription before the ride. For approval-dependent rides, the insured person — or the operator, with a power of attorney — submits the prescription to the insurer and waits for the decision. Only then does the vehicle roll.

Three deadline topics deserve particular attention:

  • Issuance before the ride: insurers accept retroactively issued prescriptions only in justified exceptional cases. Operators who routinely drive first and chase the paperwork later are building up a receivables risk.
  • Approval before the ride: with recurring series, keep an eye on the approved period. If the approval expires while treatment continues, a gap opens up that nobody will pay for.
  • Billing deadlines: many framework contracts and insurers set submission deadlines. Collecting ride slips in boxes and billing quarterly risks missing them — and quietly ties up three months of liquidity.

Co-payment and exemption

Insured persons pay 10 percent of the transport cost per ride, with a minimum of 5 and a maximum of 10 euros, never more than the actual cost. The co-payment applies per single leg — outbound and return count separately. One peculiarity: unlike most benefits, the transport co-payment also applies to children and adolescents.

Important for the business: the operator usually collects the co-payment and must offset it correctly against the insurer invoice. If an exemption exists (the burden threshold of 2 percent of gross income, 1 percent for the chronically ill), the exemption card must be checked and documented. Co-payments not collected and not backed by a documented exemption are one of the quiet profit killers of daily operations.

The most common insurer rejection reasons

Rejections sort themselves into a stable set of categories:

  1. Missing or late approval on approval-dependent rides — the classic, and usually the most expensive case.
  2. Incomplete prescription: missing means of transport, missing treatment date, missing outbound/return indication, missing signature or practice number.
  3. Deviation between prescription and ride: different vehicle type, different period, more rides than prescribed, different destination.
  4. Missing ride evidence: no confirmed transport slip, no traceable times and kilometres.
  5. Billing formalities: wrong payer data, late submission, incorrect co-payment offsetting.

Notably, almost none of these reasons have anything to do with the driving itself. Claims are rejected at the desk, not on the road.

From ride slip to paid invoice: where money leaks

Between a completed ride and a paid invoice there are typically four stations where revenue evaporates:

  • In the vehicle: the ride slip is filled in incompletely, the prescription stays in the glovebox, the signature is missing.
  • During transfer: slips are retyped, digits get transposed, rides appear twice or not at all.
  • In the filing: prescriptions pile up unsorted, approval status is unclear, series expire unnoticed.
  • In billing: submissions go out late, rejections are not systematically reworked, objection deadlines lapse in a folder.

Each of these stations is manageable on its own. Combined, without a system, they add up to flying blind.

Where digital capture saves real money

The biggest lever is not in billing itself but before it: at capture. If the prescription is recorded digitally at order intake — with mandatory-field validation, a photo of the original and the approval status attached — gaps surface while they can still be fixed. A missing tick box is caught at the next appointment, not six weeks later in an insurer rejection letter.

Add status tracking on top: prescribed, approved, driven, billed, paid. Once every ride carries one of these states, gut feeling ("something must still be open") turns into a work list. Systems like MITA Base map exactly this chain — from the Muster 4 scan at the vehicle to per-payer billing.

Conclusion

Muster 4 is not a bureaucratic monster; it is a process with clear rules: prescription before the ride, approval before departure, complete evidence, timely billing. Operators who organise these four points cleanly lose almost no money to avoidable rejections — and gain, as a side effect, a live picture of which ride is in which state. That is precisely where, in everyday operations, the well-run business parts ways with the paper-chase business.

Enough reading. See it run.

A 30-minute demo with your real workflows — no sales pressure, promised.

🇩🇪 Hosting Frankfurt · DSGVO Art. 9 · AV-Vertrag inkl.