Reporting reasons and lifecycle
Understand Meldegründe 10–13 and 20/30 in the German student health-insurance Meldeverfahren — how study timelines drive automatic notices, what insurers send back, and how Fuxam surfaces the cycle.
Reporting reasons (Meldegründe) are the coded “why” on every electronic notice between a Hochschule and a Krankenkasse. This chapter explains the Meldegrund vocabulary used in the Studenten-Meldeverfahren under § 199a SGB V, how student status timelines drive Hochschule outbound notices, and how insurer responses typically close the loop — so Fuxam’s Insurance notices and Sent notices make sense to non-technical staff.
Fuxam does not invent these codes. They come from the Gemeinsame Grundsätze agreed between the GKV-Spitzenverband and the Hochschulrektorenkonferenz. Fuxam’s role is to carry Meldegrund 20 and 30 outbound through Dakota when study timelines and configuration allow, and to surface inbound insurer notices on the per-user Krankenkasse tab.
Why it matters
Without a shared Meldegrund vocabulary, teams misread the Krankenkasse tab: a Meldegrund 12 (contribution arrears) looks like a technical error; Meldegrund 30 is confused with a leave of absence; fund changes (11) never trigger the expected follow-up start-of-study notice. Clear codes reduce enrollment delays, incorrect outbound traffic, and audit friction.
Understanding the lifecycle also clarifies why study dates matter in Fuxam: Meldegrund selection is driven by academic status on the study timeline, not by clicking export buttons in Statistics Center.
How it fits
| Related Fuxam page | Role in the lifecycle |
|---|---|
| Configure GKV integration | Absendernummer, ITSG, and insurance start date must be live before notices exchange reliably. |
| Manage insurance data | Where staff read Insurance notices (inbound) and Sent notices (outbound). |
| Export exmatriculations | Automated Meldegrund 30 path for end of study. |
| Study programs and cohorts | Source of immatriculation, leave, and exmatriculation facts on the study timeline. |
Key terms
| Term | Meaning |
|---|---|
| Meldegrund | Reason code identifying the type of notice in the electronic Meldeverfahren. |
| Krankenkasse Meldegründe | Codes 10, 11, 12, 13 — insurer → Hochschule. |
| Hochschule Meldegründe | Codes 20, 30 — Hochschule → insurer. |
| KV number | Krankenversichertennummer — student insurance number used to identify the person across notices. |
| Absendernummer | Hochschule or Dienstleister sender ID required for addressing and trust in the procedure. |
| Study timeline | Fuxam study-plan dates that determine when start-of-study and end-of-study reporting become relevant. |
Meldegründe reference
Notices from the Krankenkasse
| Code | Name (plain language) | Typical purpose |
|---|---|---|
| 10 | Insurance status | Confirms whether insurance exists (or that the person is free / exempt / not liable). Usually requested by the student so enrollment can proceed. |
| 11 | Start of insurance after fund change | New Krankenkasse reports that coverage has begun with them. |
| 12 | Contribution arrears | Student is behind on contributions — can block enrollment or re-enrollment under statutory rules. |
| 13 | Arrears settled | Contributions caught up after a 12. |
Notices from the Hochschule
| Code | Name (plain language) | Typical purpose |
|---|---|---|
| 20 | Start of study | Reports beginning of study / immatriculation — commonly semester start and day of enrollment. Also used after a fund change (11) and after re-enrollment following arrears clearance. |
| 30 | End of study | Reports end of study / exmatriculation — commonly semester end, and exmatriculation day when that day is earlier than semester end. |
Who initiates what
| Situation | Typical first notice | Follow-up |
|---|---|---|
| First enrollment | Student asks fund → Meldegrund 10 | Hochschule Meldegrund 20 |
| Krankenkasse change during study | New fund Meldegrund 11 | Hochschule Meldegrund 20 to the new fund |
| Exmatriculation / end of membership | Hochschule Meldegrund 30 | Insurer adjusts membership; no Hochschule “receipt” Meldegrund required for routine cases |
| Arrears blocking re-enrollment | Meldegrund 12 | After 13 (and often a fresh 10), Hochschule Meldegrund 20 on re-admission; Meldegrund 30 may have been sent when re-enrollment was refused |
The reporting lifecycle
1. Before enrollment
Students (or applicants) ask their Krankenkasse to report insurance status to the Hochschule. In Fuxam, the student-facing checklist on Dashboard → Management → Krankenkasse captures KV number entry and confirmation that the provider was notified — so staff can see progress without collecting paper certificates.
2. Insurer confirms status
The Krankenkasse sends Meldegrund 10. In Fuxam this appears under Insurance notices on the user’s Krankenkasse tab once the health-insurance integration is live and inbound processing has run.
3. Study begins
After enrollment, the Hochschule reports Meldegrund 20 (start of study). Domain content typically includes semester begin and day of enrollment. In Fuxam, outbound M20 history is visible under Sent notices when transmitted for that user.
4. Status changes during study
| Change | What happens in the Meldeverfahren |
|---|---|
| Fund change | New Krankenkasse sends 11; Hochschule answers with 20 to the new fund. |
| Contribution arrears | Krankenkasse sends 12; institution may have to refuse enrollment or re-enrollment until settled. |
| Arrears settled | Krankenkasse sends 13; student often requests a fresh 10 before re-admission; Hochschule then sends 20. |
| Leave of absence | Academic leave is not automatically Meldegrund 30. Keep leave and exmatriculation distinct on the study timeline. |
5. Study ends
The Hochschule reports Meldegrund 30. Domain rules commonly tie this to the end of the semester in which (or with effect to which) the student was exmatriculated. If exmatriculation is earlier than semester end, the day of exmatriculation is also part of the reporting picture.
In Fuxam, eligible Meldegrund 30 traffic is produced by the exmatriculation export from study-timeline dates, then recorded under Sent notices.
How student status timelines drive automatic notices
Fuxam connects Meldeverfahren obligations to the same academic lifecycle used elsewhere in OrgHub:
| Study timeline fact | Meldeverfahren relevance |
|---|---|
| Immatriculation / start dates | Support Meldegrund 20 timing and audit of start-of-study reporting. |
| Leave | Must not be confused with end of study; wrong status can suppress or invent Meldegrund 30. |
| Exmatriculation / end dates | Primary eligibility for automated Meldegrund 30 export. |
| Insurance start date (institution setting) | Limits how far back Fuxam considers notifications after go-live. |
How insurers respond (what staff should expect)
| After this… | You typically see… | Staff action |
|---|---|---|
| Student completes provider request | Meldegrund 10 under Insurance notices | Proceed with enrollment checks per policy. |
| Fund change | Meldegrund 11 inbound | Expect / verify Hochschule Meldegrund 20 to the new fund. |
| Arrears | Meldegrund 12 inbound | Involve enrollment / re-enrollment owners; may block progression. |
| Settlement | Meldegrund 13 inbound | Often wait for a fresh 10, then Meldegrund 20 on re-admission. |
| Meldegrund 30 sent | Entry under Sent notices | Confirm dates; use correction workflows if the timeline was wrong. |
Inbound Meldegründe are not Statistics Center rows. They are per-student statutory messages next to identity data in User Management.
Worked scenarios
Scenario A — Clean first enrollment
- Student completes Krankenkasse checklist and KV number.
- Meldegrund 10 arrives (insured).
- Study timeline shows immatriculation.
- Meldegrund 20 is transmitted; appears under Sent notices.
- Years later, exmatriculation is set on the study plan; nightly export sends Meldegrund 30.
Scenario B — Mid-study fund change
- Meldegrund 11 arrives from the new Krankenkasse.
- Staff verify identity and KV number on the Krankenkasse tab.
- Hochschule Meldegrund 20 goes to the new fund with original study-begin / enrollment facts as required by the procedure.
- Later Meldegrund 30 still closes the study with the (then current) insurer relationship.
Scenario C — Arrears block re-enrollment
- Meldegrund 12 arrives; re-enrollment is refused per policy.
- Depending on process, Meldegrund 30 may already have closed study membership for the prior period.
- Meldegrund 13 (and typically a new 10) clears the path.
- On re-admission, Meldegrund 20 reports start of study again with the original begin / enrollment dates as required in arrears-recovery cases.
Best practices
- Train front-line staff on 10–13 before go-live. Most operational confusion is inbound, not outbound Meldegrund 30.
- Never treat leave as exmatriculation. Wrong timeline status is the fastest way to send an incorrect Meldegrund 30.
- Keep Absendernummer ownership clear when a Dienstleister is involved — addressing errors look like “missing” Meldegrund 10s.
- Use one vocabulary across registrar and IT. Prefer Meldegrund names in tickets (“arrears 12”) over internal job names.
- Document corrections. When you fix a timeline and re-send or correct a notice, note why — auditors care about Meldeverfahren trails.
Common pitfalls
| Pitfall | Why it hurts | Better approach |
|---|---|---|
| Ignoring Meldegrund 12 | Student may remain blocked while staff chase “bugs” | Route arrears notices to enrollment policy owners. |
| Expecting Meldegrund 30 the morning of exmatriculation | Export is a daily job | Check Sent notices after the nightly run or request an operator trigger. |
| Confusing Statistics leavers lists with Meldeverfahren | Different schemas and audiences | Use export exmatriculations and the Krankenkasse tab for GKV. |
| Marking Hochschuldatei complete too early | Inbound/outbound routing fails silently | Wait for real ITSG confirmation — see Configure GKV integration. |
FAQ
Which Meldegründe does the Hochschule send?
Primarily 20 (start of study) and 30 (end of study). Insurers send 10, 11, 12, and 13.
Where do I see these codes in Fuxam?
On OrgHub → User Management → [User] → Krankenkasse: inbound under Insurance notices, outbound Hochschule notices under Sent notices.
Is Meldegrund 30 the same as deleting a user?
No. Meldegrund 30 is a statutory end-of-study notice to the Krankenkasse. User records, cohorts, and study plans remain separate OrgHub concerns.
Does a leave of absence require Meldegrund 30?
Not by default. Leave is an academic status. Meldegrund 30 is end of study / exmatriculation reporting. Keep the study timeline precise.
Where is Meldegrund 30 automated in Fuxam?
Via the exmatriculation export daily job, driven by study-timeline eligibility.
Related pages
Health insurance overview
Section overview and Absendernummer / ITSG context.
Manage insurance data
Per-student Krankenkasse tab for notices and timeline checks.
Export exmatriculations
Automated Meldegrund 30 export and what the notice contains.
Configure GKV integration
Absendernummer, ITSG, and insurance start date prerequisites.