@mindbill/angular 0.8.0 → 0.10.0

package/README.md

@@ -55,6 +55,32 @@ export class CaseBillingComponent {
 
 `MindBillBillSubmissionComponent` marks required fields, scrolls to invalid input, resolves ZIP codes to city and state with an inline status line, searches the MindBill claims-administrator and ICD-10 directories as you type, calculates service-line totals, and uploads attachments. Dates use a masked MM/DD/YYYY input that accepts ISO, US, or bare-digit entry, normalizes the display once a complete date is typed, and submits ISO values — identical to the React form. On success, render `MindBillBillLifecycleComponent` with the returned bill ID. The lifecycle component loads its own immutable bill snapshot, status, EORs, payments, history, and available actions.
 
+When the lifecycle is rejected, it automatically renders the full ordered list of clearinghouse issues with actionable descriptions, acknowledgement codes, and sent/rejected timestamps. For custom layouts, use the same standalone surface directly:
+
+```html
+<mindbill-bill-rejection-notice
+  [rejection]="rejection"
+  [submittedAt]="submittedAt"
+  [appearance]="{ preset: 'mindbill' }"
+/>
+```
+
+```ts
+import { MindBillBillRejectionNoticeComponent } from "@mindbill/angular";
+
+rejection = {
+  reason: "Correct the submitted dates.",
+  source: "Jopari",
+  receivedAt: "2026-09-01T16:11:00.000Z",
+  issues: [
+    { code: "A6:187", description: "From Date of Service cannot be in the future" },
+    { code: "A6:88", description: "Thru Date of Service cannot be in the future" },
+  ],
+};
+```
+
+The component falls back to the legacy singular `reason` and `code` fields when `issues` is absent. Set `appearance.dangerColor` to customize its red treatment.
+
 Procedure codes, modifiers, and rendering taxonomy all use the same styled searchable dropdown (`mindbill-combo-box`) with code + description rows, hover states, and typed custom-code entry for complete CPT/HCPCS/medical-legal codes. Service lines accept multiple modifiers rendered as removable chips. PDFs can be dropped anywhere on the screen — a full-page overlay confirms the drop target — with the same 25 MB per-file, 100 MB total, and 20-document limits as the React form.
 
 The default reference directories and field rules live in the component library. Hosts can provide custom procedure, modifier, and taxonomy options without reimplementing the form. For a fixture or Storybook, pass an async `submitter`; omit it in production so the component talks directly to the Partner API.
@@ -126,3 +152,17 @@ The operations surfaces consume a normalized list of bills, so they can be used
 `mindbill-status-aging-matrix` is the management view billers coming from legacy tools expect: one row per lifecycle status, one column per 0–30 / 31–60 / 61–90 / 91+ aging bucket, clickable counts with outstanding balances, and row/column totals. Every emitted cell carries `{ state, bucket, count, balance, bills }`, so a drill-down never needs a second query. Pin a custom lifecycle ordering with `[stateOrder]`; unknown states append alphabetically.
 
 `summarizeMindBillDashboard`, `buildMindBillReportRows`, `buildMindBillReportCsv`, `buildMindBillStatusAgingMatrix`, and `buildMindBillStatusAgingCsv` are also exported for custom layouts and server-side reporting.
+
+## Organization onboarding and billing settings
+
+`mindbill-organization-onboarding` captures the practice identity, billing provider, locations, and W-9 once — saved straight to your MindBill organization through the browser session. Set `variant="settings"` for the compact edit-after-setup layout.
+
+```html
+<mindbill-organization-onboarding
+  sessionEndpoint="/api/mindbill/session"
+  [appearance]="appearance"
+  (completed)="enableBillingFeatures()"
+/>
+```
+
+The session must be minted with the optional `organization:manage` permission. Each step saves independently through idempotent upserts that never delete records created elsewhere; the review step mirrors MindBill's onboarding checklist.