Skip to content
Esc
↑↓navigate↵open⌘Jpreview
On this page

Export exmatriculations

How Fuxam sends Meldegrund 30 exmatriculation notices to the Krankenkasse — right after exmatriculation in the study plan or with the daily Dakota export — who is eligible, what the notice contains, where it appears under Sent Notices, and when operators trigger a manual run.

When a student's exmatriculation date approaches or passes, Fuxam must notify their Krankenkasse with a Meldegrund 30 (end of study) notice via the Dakota service. Export exmatriculations is that outbound path: when staff exmatriculate a student in the study plan, Fuxam tries to send the notice right away, and a daily job picks up everyone else whose exmatriculation date is at most 7 days away or already past. Each sent notice is recorded under Sent Notices on the user's Health Insurance tab, so the same notice is not sent twice.

This page explains when Fuxam sends Meldegrund 30, what the notice conceptually contains, what staff see afterward on the Health Insurance tab, how manual triggers work for Fuxam operators, and which prerequisites must be true before anything useful leaves the institution. It does not cover Meldegrund 20 immatriculation traffic or inbound Krankenkasse responses — those run on separate jobs.

Why it matters

In the statutory Studenten-Meldeverfahren, Hochschulen report the end of study so Krankenkassen can end or adjust student membership correctly. Meldegrund 30 typically reflects exmatriculation at or with effect to the end of a semester (and related end-of-study cases under § 199a SGB V). If notices never leave — or leave with wrong dates — insurers keep stale student status, contribution calculations drift, and your institution fails a core compliance obligation.

Fuxam's export exists so registrar staff do not hand-build XML for every leaver. Instead:

  • Study-timeline exmatriculation drives who is selected.
  • Institution configuration and Absendernummer / Dakota connectivity drive whether transmission can succeed.
  • Sent Notices on the user's Health Insurance tab provide an auditable trail next to the same identity used in User Management.

Treat this export as a specialized statutory channel. It complements statistics exports (Prüfungsstatistik, Studierendenstatistik, Report Builder) but is not configured or run from the Statistics Center.

Key concepts

Concept Meaning
Meldegrund 30 Hochschule Meldegrund for end of study / exmatriculation reporting.
Send after exmatriculation When staff exmatriculate a student in the study plan, Fuxam tries Meldegrund 30 for that student at once (only if the GKV integration is configured and the student is eligible).
Daily exmatriculation export Scheduled job that performs the Meldegrund 30 export for all eligible students (in production, 03:00 UTC).
Platform GKV export schedule When this platform schedule is disabled, the daily job completes successfully but processes zero records.
Dakota rate limits Configured GKV Dakota limits that batch outbound notices during each run.
7-day window A student becomes eligible once the exmatriculation date is no more than 7 days in the future, or already past.
Active M30 An M30 under Sent Notices that was not cancelled blocks a second Meldegrund 30 for the same student.

What a Meldegrund 30 notice contains (domain context)

The electronic Meldeverfahren defines structured Hochschule notices. For end of study, Meldegrund 30 typically carries identity and membership facts such as:

Content area Typical meaning in the procedure
Student identity Name, date of birth, address where required, and KV number (Krankenversichertennummer) when available.
Absendernummer The Hochschule (and, where applicable, Dienstleister) sender ID so the Krankenkasse can trust and route the notice.
End of semester The semester end date with which membership at the Hochschule ends.
Day of exmatriculation Reported when exmatriculation happens before semester end (statutory detail under § 199a SGB V as amended).
Meldegrund code 30 — Ende des Studiums.

Fuxam builds these Meldegrund 30 payloads from eligible study-timeline records and transmits them through Dakota. Staff do not edit raw XML; they correct dates in the study plan and verify outcomes under Sent Notices.

How insurers typically respond after Meldegrund 30

Once the Krankenkasse receives end-of-study reporting, it can adjust student membership and contribution treatment for that person. From the Hochschule's operational view:

  • You should see the outbound notice recorded under Sent Notices.
  • You should not expect Meldegrund 30 itself to appear under Insurance Notifications — inbound codes are mainly 10–13.
  • If the student later re-enrolls (for example after arrears were settled), the cycle restarts with insurer status (10) and Hochschule start-of-study (20), not another casual Meldegrund 30.

See Reporting reasons and lifecycle for the full code set and scenarios (including Meldegrund 30 after arrears-driven refusal of re-enrollment).

When Fuxam sends Meldegrund 30

Right after exmatriculation

When staff exmatriculate a student in the study plan, Fuxam checks that student in the background and sends Meldegrund 30 at once if the GKV integration is configured and the student is eligible (see the table below). If the exmatriculation date is more than 7 days away, nothing is sent yet; the daily export picks the student up later.

Daily export

Fuxam also runs the exmatriculation insurance export every day (03:00 UTC in production). Each run:

  1. Finds students whose exmatriculation date is no more than 7 days away (or already past) and who have no active M30 yet.
  2. Builds Meldegrund 30 payloads.
  3. Sends notices in batches using configured GKV Dakota rate limits.
  4. Records successful transmissions under Sent Notices so the same notice is not sent twice.

The job runs only when the platform GKV export schedule is enabled. If that schedule is disabled, the job returns success with zero processed records.

What selection depends on

Input Effect on the run
Exmatriculation date in the study plan Primary eligibility signal: the student is picked up once the date is at most 7 days away. Wrong dates mean a wrong or missing Meldegrund 30.
Processed Meldegrund 10 or 11 from the Krankenkasse Fuxam takes the student's name, date of birth, address, KV number, and insurer number from that notification. Without it, the student is skipped.
Active M30 under Sent Notices A sent, uncancelled M30 blocks a second one. To correct it, use Cancel & Update.
Student insurance information The health insurance number on the user must match the Krankenkasse notification.
Absendernummer saved in the GKV settings Without it, nothing is sent for the institution.

What appears on the user tab

Each transmitted notice shows under Campus Management → User Management → [user] → Health Insurance → Sent Notices. Staff can review M20 and M30 history and correct a wrong notice with Cancel & Update (see Manage insurance data).

If you exmatriculated the student in the study plan, check Sent Notices a few minutes later. For exmatriculation dates set in advance, check the morning after the date comes within 7 days (the daily run is at 03:00 UTC, which is 04:00 or 05:00 German time).

Manual trigger

Institution admins do not have a self-service button in Settings to rerun exmatriculation export. Fuxam operators with access to internal platform tools can manually trigger the same export function used by the daily job — useful after fixing study-timeline data or when testing the Dakota connection.

Typical situations where an operator-triggered run helps:

  • Bulk correction of exmatriculation dates on study plans after a data migration.
  • Dakota connectivity testing in a controlled window (without waiting for 03:00 UTC).
  • Catch-up after the platform GKV export schedule was temporarily disabled.

Outside those cases, prefer the nightly schedule so rate limits and duplicate protection behave consistently.

Prerequisites for successful export

Requirement Why it matters
Configure GKV integration saved complete Needed for the send right after exmatriculation.
Processed Meldegrund 10 or 11 for the student Supplies the identity and address data for the notice.
Valid Absendernummer and Dakota connectivity Notices must reach the GKV middleware.
Accurate exmatriculation dates in the study plan Selection is driven by the exmatriculation date.
Student insurance information complete Missing KV or provider data can block or fail transmission.
Platform GKV export schedule enabled Otherwise the daily job processes zero records.

Best practices

  • Close the academic record first. Confirm exmatriculation on the study plan (and cohort context) before expecting Meldegrund 30 — insurance export will not invent an end-of-study date.
  • Spot-check Sent Notices after go-live or large leavers cohorts. A quiet job can mean success with nothing eligible, a disabled schedule, or systemic Dakota failure — the per-user tab distinguishes "not selected" from "sent".
  • Coordinate with student services on leave vs exmatriculation. Leave statuses on the timeline are not the same as end-of-study Meldegrund 30; keep statuses precise so the export selects the right population.
  • Keep Statistics and GKV mentally separate. Use Statistics Center for ministry and internal tables; use this export only for Krankenkasse Meldegrund 30 obligations.
  • After corrections, decide whether to wait or escalate. If you fixed timelines today, either wait for the next 03:00 UTC run or ask a Fuxam operator for a manual trigger — there is no institution Settings button to rerun export. If an M30 already went out with a wrong date, use Cancel & Update on Sent Notices instead.
  • Remember mid-semester exmatriculation. When a student leaves before semester end, statutory reporting expects the exmatriculation day in addition to semester end — keep the study timeline precise so the Meldegrund 30 payload reflects reality.

Common pitfalls

Symptom Likely cause What to do
Job "succeeds" but nothing is sent Platform GKV export schedule disabled, or no eligible timelines Confirm the schedule is enabled and that students have an exmatriculation date within 7 days and a processed Meldegrund 10 or 11.
Expected student missing from Sent Notices Exmatriculation date more than 7 days away, active M30 already sent, or no processed Meldegrund 10/11 Check Study Timeline, Sent Notices, and Insurance Notifications on the Health Insurance tab.
Wrong Meldegrund 30 content Incorrect exmatriculation date in the study plan Correct the study plan, then use Cancel & Update on the notice under Sent Notices.
Staff look for a Settings "Run export" control Not provided for institutions Rely on nightly job or request an operator manual trigger.
Confusion with Meldegrund 20 Different job family Immatriculation and inbound responses use separate notification-processing jobs, not this daily export.

FAQ

When does the daily export run?

In production, the exmatriculation insurance export runs daily at 03:00 UTC, subject to the platform GKV export schedule being enabled. When staff exmatriculate a student in the study plan, Fuxam also tries to send that student's Meldegrund 30 right away.

Can my institution click a button to rerun Meldegrund 30 export?

No. Institution admins do not have a self-service button in Settings. Fuxam operators with internal platform tools can manually trigger the same export function the daily job uses.

Does this job also send Meldegrund 20?

No. Meldegrund 20 immatriculation notices and inbound Krankenkasse responses are handled by separate jobs — including notification processing that typically runs every 30 minutes.

Where do I verify that an export worked for one student?

Campus Management → User Management → [user] → Health Insurance → Sent Notices.

What happens if we exmatriculate someone mid-semester?

Domain rules expect Meldegrund 30 to reflect end of the relevant semester and, when exmatriculation is earlier, the day of exmatriculation. Keep those dates accurate on the study timeline before relying on the export.

Last updated on

Was this page helpful?