Exports: rosters, audit packages, evidence bundles
This chapter covers the three export artifacts:
- Billable roster CSV — the per-member, per-month list of who is billable and at what rate.
- Audit package — a PDF + manifest + supporting documents bundle that proves the reasoning behind a billing run.
- Evidence bundle — a deeper export including input files, rule version, decision trace, and audit-chain segment for a specific decision.
1. Billable roster CSV
The roster CSV is the headline output of a billing run. It contains one row per billable member for the billing month, with columns for member identifier (member_id and member_mbi), payer, billable days, per-member-per-month rate, tier (if tiered pricing applies), charge amount, triggering service event IDs (if service-delivery reconciliation applies), and combined-benefit indicator (primary code + suffix).
Generating the CSV
From the Billing screen, locate the billing run row and click Export roster. The CSV is generated server-side and downloaded as <tenant-slug>_<payer-slug>_<YYYY-MM>_roster.csv.
Regeneration
If you re-run a billing cycle, the roster CSV regenerates from the new decisions. The prior CSV remains downloadable from the billing-run history — every regeneration is a new versioned export, never an in-place overwrite.
Permissions
- OWNER, ADMIN, BILLING_MANAGER can export rosters.
- OPERATIONS and VIEWER cannot (rate data is finance-sensitive).
2. Audit package
Self-contained PDF + manifest bundle that an external auditor can review without needing access to Rendum. Each package corresponds to a single billing run and contains:
- Cover sheet (tenant, payer, billing month, run timestamp, billing-run ID).
- Executive summary (total members, billable members, total charge, sanity checks).
- The rule configuration that was active at the run, including the sign-off actor + timestamp.
- Per-decision-class summaries (active billed normally, active not billed with reason, retroactively adjusted, terminated mid-cycle, etc.).
- The audit-chain hash for the run + the hash-chain proof linking it to the prior run.
- Citation snapshots showing the contract regions backing each billable-day rule.
Generating
From the Billing screen, click Generate audit package. Generation runs as a background job (~1–3 minutes per 10,000 billable members).
Permissions
- OWNER, ADMIN, BILLING_MANAGER can generate and download audit packages.
- OPERATIONS and VIEWER cannot.
3. Evidence bundle
The evidence bundle targets a single decision (or a small set) and includes everything needed to answer "why this exact outcome for this exact member-month?":
- The input files that drove the decision.
- The rule version snapshot at the time of the decision.
- The decision-replay trace (input → resolver → tier selection → charge).
- The relevant audit-chain segment.
- The citation snapshots backing each rule application.
Generating
From any decision detail page, click Generate evidence bundle. Output is a ZIP (typical size 5–50 MB).
Use cases
- A payer dispute — they say a member should not have billed; the evidence bundle proves the rule application.
- An internal finance review — finance wants to confirm a high-value charge.
- A compliance audit — auditor requests evidence for a specific member-month.
Permissions
- OWNER, ADMIN, BILLING_MANAGER can generate evidence bundles.
- OPERATIONS via support workflow; cannot generate directly.
- VIEWER cannot generate.
Retention
- Billable roster CSVs: retained for the tenant's billing-decision retention window (default 120 months).
- Audit packages: same window.
- Evidence bundles: generated on demand; regenerate from the underlying decision if needed.
Audit footprint
Every export writes an audit row: ROSTER_EXPORTED, AUDIT_PACKAGE_GENERATED, EVIDENCE_BUNDLE_GENERATED.