@zeniai/web-components 4.3.76-beta12MM → 4.3.76-beta13MM

package/dist/components/aiCfo/components/AiCfoRoutinesBrowser.d.ts

@@ -1,7 +1,7 @@
 import { default as React } from 'react';
 import { Routine } from './helpers/aiCfoRoutines';
 export interface AiCfoRoutinesBrowserProps {
-    /** False withholds "New routine" — the server states the cap, not the client. */
+    /** False withholds "New scheduled task" — the server states the cap, not the client. */
     canCreate: boolean;
     listError: boolean;
     /**

package/dist/components/aiCfo/components/helpers/aiCfoRoutines.d.ts

@@ -79,6 +79,8 @@ export interface RoutineRun {
 }
 /** Whether a run is still going, and so has no outcome to report yet. */
 export declare const isRunInFlight: (run: RoutineRun) => boolean;
+/** Whether this run holds an answer to open: a session, not in flight, and either the answer's message id or (runs from before it was recorded) a succeeded status. */
+export declare const isRunOpenable: (run: RoutineRun) => boolean;
 /**
  * When a run happened, in the routine's own timezone.
  *

package/dist/components/commentsAndNotes/utils/CollaborationHelpers.d.ts

@@ -71,6 +71,21 @@ export declare const canonicalizeColumnKey: (columnKey: string) => string;
  * read so legacy comments match freshly-rendered canonical cells.
  */
 export declare const canonicalizeCellEntityId: (entityId: string) => string;
+/**
+ * True when a stored thread entityId refers to the cell rendered as
+ * `renderedEntityId`.
+ *
+ * Exact (canonical) equality is the normal case. The fallback covers comments
+ * written before the column key used the period end: those carry whatever
+ * `data_available_end_date` was on the day they were made, so a comment left on
+ * September 9th stored `2026-09-01_2026-09-09` and no longer equals the
+ * September cell. Same row and same start date, with the stored end inside the
+ * rendered period, identifies it. A legacy month comment can surface on the
+ * containing quarter when the report is regrouped, which is intended: the
+ * alternative is that it shows nowhere. Keys written now carry the period end,
+ * so they only ever match at the same granularity.
+ */
+export declare const matchesCellEntityId: (renderedEntityId: string, storedEntityId: string) => boolean;
 export interface ReportThreadTarget {
     accountId: string;
     cellEntityId: string;

package/dist/components/common/popUps/RecommendationFeedbackPopup.d.ts

@@ -1,7 +1,9 @@
+import { FetchState } from '@zeniai/client-epic-state';
 import { RecommendationSelectionFeedback } from '../../../common/recommendationSelectionFeedback';
 export interface RecommendationFeedbackPopupProps {
     feedback: RecommendationSelectionFeedback;
     maxReasonLength?: number;
+    submitState?: FetchState;
     onSkip: () => void;
     onSubmit: (reason: string) => void;
     onClose?: () => void;
@@ -13,5 +15,5 @@ export interface RecommendationFeedbackPopupProps {
  * of the transaction read-only, and a required reason. Submit records the
  * feedback; Skip records analytics only.
  */
-export declare function RecommendationFeedbackPopup({ feedback, maxReasonLength, onSubmit, onSkip, onClose, }: Readonly<RecommendationFeedbackPopupProps>): import("react/jsx-runtime").JSX.Element;
+export declare function RecommendationFeedbackPopup({ feedback, maxReasonLength, submitState, onSubmit, onSkip, onClose, }: Readonly<RecommendationFeedbackPopupProps>): import("react/jsx-runtime").JSX.Element;
 export default RecommendationFeedbackPopup;

package/dist/components/dashboard/Dashboard.d.ts

@@ -1,8 +1,9 @@
+import { default as React } from 'react';
 import { ClientAnalytics } from '@zeniai/client-analytics';
 import { CardActions, CardType } from '../cards/cardTypes';
 import { AutoCompleteActions, AutoCompleteData } from '../common/autoComplete/autoCompleteProps';
 import { DashboardCardData } from './dashboardTypes';
-declare function Dashboard({ cardDataArray, cardActions, christmasAnimationEnabled, newYearAnimationEnabled, autoCompleteData, autoCompleteActions, analytics, isReimbursementEnabled, isBillPayEnabled, isVisitingFirstTime, onDragAndDropCard, isAiCfoAccessEnabled, onAskAiCfoClick, onAiCfoDashboardPromptSubmit, onAiCfoDashboardOpenPanel, onAiCfoDashboardOpenScopePage, onAiCfoDashboardExpandToFullPage, isAiCfoFileUploadEnabled, initialSearchFocus, maxColumns, aiAuditScorePercentageEnabled, aiCfoDashboardShouldClearPromptOnSubmit, aiCfoDashboardSuggestedPromptQuestions, aiCfoDashboardSuggestedPromptQuestionsLoading, }: Readonly<{
+declare function Dashboard({ cardDataArray, cardActions, christmasAnimationEnabled, newYearAnimationEnabled, autoCompleteData, autoCompleteActions, analytics, cardsShutdownBanner, isReimbursementEnabled, isBillPayEnabled, isVisitingFirstTime, onDragAndDropCard, isAiCfoAccessEnabled, onAskAiCfoClick, onAiCfoDashboardPromptSubmit, onAiCfoDashboardOpenPanel, onAiCfoDashboardOpenScopePage, onAiCfoDashboardExpandToFullPage, isAiCfoFileUploadEnabled, initialSearchFocus, maxColumns, aiAuditScorePercentageEnabled, aiCfoDashboardShouldClearPromptOnSubmit, aiCfoDashboardSuggestedPromptQuestions, aiCfoDashboardSuggestedPromptQuestionsLoading, }: Readonly<{
     aiAuditScorePercentageEnabled: boolean;
     analytics: ClientAnalytics;
     autoCompleteActions: AutoCompleteActions;
@@ -20,6 +21,11 @@ declare function Dashboard({ cardDataArray, cardActions, christmasAnimationEnabl
     /** Same source as AI CFO side panel suggested questions for the current route (host / Redux). */
     aiCfoDashboardSuggestedPromptQuestions?: string[];
     aiCfoDashboardSuggestedPromptQuestionsLoading?: boolean;
+    /**
+     * Optional shutdown banner rendered at the top of the dashboard (below the NavBar)
+     * for tenants whose cards product is being discontinued. Owned by the host screen.
+     */
+    cardsShutdownBanner?: React.ReactNode;
     christmasAnimationEnabled?: boolean;
     initialSearchFocus?: boolean;
     isAiCfoAccessEnabled?: boolean;

package/dist/components/expenseAutomation/ExpenseAutomationPage.d.ts

@@ -61,6 +61,12 @@ export interface ExpenseAutomationPageProps extends MonthEndReportPageProps, Act
     initialSelectedBaseTransaction?: ScheduleTransaction;
     /** Cron-2's live gate for this company, per Statsig. Off hides one-time accrual creation. */
     isAccrualEnabled?: boolean;
+    /**
+     * Actual Matching JE subtab + match-detail bounce. Independent of
+     * `isAccrualEnabled` so one-time accrual create can stay live while AM
+     * stays hidden. Host reads `agent_je_config` (`ACTUAL_MATCHING_ENABLED`).
+     */
+    isActualMatchingEnabled?: boolean;
     isAiCfoAccessEnabled?: boolean;
     /**
      * Statsig `is_create_transfer_entry_from_expense_enabled`. When false the TC list

package/dist/components/expenseAutomation/components/navbarHeaderData.d.ts

@@ -49,8 +49,9 @@ missingReceiptsOptions?: {
  */
 isExpenseAutomationCommentingEnabled?: boolean, receiptsEmail?: string, 
 /**
- * Cron-2 live gate (`is_accrual_enabled`). Off hides the Actual Matching JE
- * subtab — there are no one-time accruals to match.
+ * Actual Matching JE subtab. Host ANDs `is_accrual_enabled` with
+ * `agent_je_config.global.accrual_config.ACTUAL_MATCHING_ENABLED`. Off
+ * hides the tab — code stays; this is the master-release UI gate.
  */
-isAccrualEnabled?: boolean) => ExpenseAutomationNavbarHeaderData;
+isActualMatchingEnabled?: boolean) => ExpenseAutomationNavbarHeaderData;
 export {};

package/dist/components/expenseAutomation/sections/actualMatching/ActualMatchingMatchNewButton.d.ts

@@ -0,0 +1,5 @@
+export interface ActualMatchingMatchNewButtonProps {
+    onClick: () => void;
+}
+declare function ActualMatchingMatchNewButton({ onClick, }: Readonly<ActualMatchingMatchNewButtonProps>): import("react/jsx-runtime").JSX.Element;
+export default ActualMatchingMatchNewButton;

package/dist/components/expenseAutomation/sections/jeSchedules/common/JEGroupSectionHeader.d.ts

@@ -2,13 +2,13 @@ export interface JEGroupSectionHeaderProps {
     count: number;
     isCollapsed: boolean;
     title: string;
+    subtitle?: string;
     onToggle: () => void;
     /**
      * `badge` is the Review Schedules circle. Matching Design puts the count
      * inline after the title with no ring.
      */
     countAppearance?: "badge" | "plain";
-    subtitle?: string;
 }
 declare function JEGroupSectionHeader({ title, count, countAppearance, isCollapsed, onToggle, subtitle, }: Readonly<JEGroupSectionHeaderProps>): import("react/jsx-runtime").JSX.Element;
 export default JEGroupSectionHeader;

package/dist/components/expenseAutomation/sections/jeSchedules/list/jeScheduleConfig.d.ts

@@ -3,7 +3,7 @@ import { TabSwitcherOption } from '../../../../common/allNavBars/statusSwitcher/
 import { TextAlign } from '../../../../dataListTable';
 export type JEScheduleMainTab = JEPageTab;
 export type JEScheduleColumnKey = "vendor" | "category" | "class" | "depCategory" | "scheduleCategory" | "startMonth" | "type" | "amortizationPeriod" | "jePostingDate" | "remainingMonths" | "runningBalance" | "monthlyAmount" | "totalAmount" | "action" | "transactionDate" | "memo" | "createdBy" | "lifecycle" | "period";
-export type JEScheduleGroupKey = "pending_review" | "created" | "existing";
+export type JEScheduleGroupKey = "pending_review" | "created" | "existing" | "failed_postings";
 export type JESchedulePendingSubTab = "all" | "create" | "resolve";
 export type JEScheduleOngoingCompletedSubTab = "all" | "ai_accountant" | "manual";
 export type JEScheduleSubTab = JESchedulePendingSubTab | JEScheduleOngoingCompletedSubTab;

package/dist/components/expenseAutomation/sections/jeSchedules/list/jeScheduleListItems.d.ts

@@ -49,8 +49,14 @@ export type JEScheduleListItem = {
  */
 export declare function buildJEScheduleListItems(groups: readonly JEScheduleListGroup[]): JEScheduleListItem[];
 /**
- * Prefixed with the group key deliberately. The same schedule can appear as a resolve row in one
- * group and an ongoing row in another while sharing a `jeScheduleTransactionKey`; separate tables
- * made that harmless, one list would give react-window two items with the same key.
+ * Two collisions to avoid, and both are real.
+ *
+ * The group prefix: the same schedule can appear as a resolve row in one group and an ongoing row
+ * in another while sharing a `jeScheduleTransactionKey`. Separate tables made that harmless; one
+ * list would give react-window two items with the same key.
+ *
+ * The row-instance key: a schedule that failed to post in two months is two resolve rows *inside
+ * one group*, which the group prefix cannot separate. `getJEScheduleRowInstanceKey` appends the
+ * journal entry id for exactly those rows.
  */
 export declare function getJEScheduleListItemKey(item: JEScheduleListItem): string;

package/dist/components/expenseAutomation/sections/jeSchedules/list/jeScheduleListRow.helpers.d.ts

@@ -1,4 +1,4 @@
-import { ID, JEOneTimeAccrualKey, JEScheduleKey, JEScheduleRow, JEScheduleTransactionKey } from '@zeniai/client-epic-state';
+import { ID, JEOneTimeAccrualKey, JEScheduleKey, JEScheduleRow, JEScheduleTransactionKey, JEScheduledTransactionWithFailedEntries, JournalEntryErrorCodeType } from '@zeniai/client-epic-state';
 import { ChainOfThoughtData } from '../../../../common/tooltipVariants/types';
 /**
  * The chain-of-thought popover shown on the "Created by" cell of an AI Accountant row.
@@ -20,6 +20,35 @@ export type JEScheduleRowKey = JEOneTimeAccrualKey | JEScheduleTransactionKey |
  * Stable per-row identity for React keys, data-testids and row commenting.
  */
 export declare function getJEScheduleRowKey(row: JEScheduleRow): JEScheduleRowKey;
+/**
+ * Why this entry could not post, as displayable text.
+ *
+ * `deletedFieldNameByCode` supplies the name for the codes whose copy quotes one. Those names are
+ * frequently unknown -- the entity is deleted, which is the whole reason the posting failed, and
+ * the server sends null for it -- so an absent name drops the quoted fragment rather than
+ * rendering an empty pair of quotes.
+ */
+export declare function buildResolveErrorText(errorCodes: JournalEntryErrorCodeType[], deletedFieldNameByCode?: Partial<Record<JournalEntryErrorCodeType, string | undefined>>): string;
+/**
+ * A row standing for one FAILED journal entry rather than a whole schedule.
+ *
+ * Discriminates structurally on `scheduledJournalEntry` being a single entry instead of the array
+ * every other row shape carries — the selector fans a failed schedule out to one row per entry.
+ */
+export declare function isResolveRow(row: JEScheduleRow): row is JEScheduledTransactionWithFailedEntries;
+/**
+ * Render identity for one ROW INSTANCE — for React keys only, never for routing or lookups.
+ *
+ * A failed posting is one row per failed journal ENTRY, so a schedule that failed in two months
+ * produces two rows sharing a `jeScheduleTransactionKey`. `getJEScheduleRowKey` is the schedule's
+ * domain key: it routes the side panel, names comment threads and chain-of-thought entries, and
+ * keys the per-row status maps, so it cannot carry the entry and stay correct. This appends the
+ * entry id for exactly the rows that need it, and returns the domain key unchanged for the rest.
+ *
+ * The group prefix `getJEScheduleListItemKey` adds solves a different collision — the same
+ * schedule appearing in two groups — and both are real.
+ */
+export declare function getJEScheduleRowInstanceKey(row: JEScheduleRow): string;
 /**
  * The plain id the side-panel URL carries for this row — deliberately NOT its row key.
  *

package/dist/components/expenseAutomation/stories/actualMatchingPageStoryActions.d.ts

@@ -0,0 +1,2 @@
+import { ActualMatchingActionProps } from '../sections/actualMatching/actualMatchingTypes';
+export declare const actualMatchingPageStoryActions: ActualMatchingActionProps;

package/dist/components/invoicing/catalogDetail/InvoicingCatalogItemDetailPage.d.ts

@@ -1,14 +1,11 @@
-import { InvoicingCatalogItemLifecycleAction, InvoicingCatalogLifecycleActionOption, InvoicingCatalogProductLifecycleAction, InvoicingNamedOptionsByKey, InvoicingPlan, InvoicingCatalogItemFormLocalData, InvoicingNamedOption } from '@zeniai/client-epic-state';
+import { InvoicingCatalogItemLifecycleAction, InvoicingCatalogLifecycleActionOption, InvoicingCatalogProductLifecycleAction, InvoicingNamedOptionsByKey, InvoicingPlan, NestedAccountHierarchyForReport, NestedClassHierarchyForReport, InvoicingCatalogItemFormLocalData, InvoicingNamedOption } from '@zeniai/client-epic-state';
 import { FieldHelpByCode } from '../../formElements/fieldHelp/FieldHelpContext';
-import { GroupedOption } from '../../formElements/labeledGroupSingleSelectFieldWithRecommendationCheckbox/GroupedSingleSelectField';
 import { InvoicingCatalogApplicableItemOption } from '../catalogForm/InvoicingCatalogItemFormPage';
 type InvoicingPlanWithIdentifiers = InvoicingPlan & {
     externalId?: string;
     productCode?: string;
 };
 export interface InvoicingCatalogItemDetailPageProps {
-    groupedAccountOptions: GroupedOption[];
-    groupedClassOptions: GroupedOption[];
     isLoading: boolean;
     itemId: string;
     localData: InvoicingCatalogItemFormLocalData;
@@ -23,6 +20,16 @@ export interface InvoicingCatalogItemDetailPageProps {
     isRunningLifecycleAction?: boolean;
     isSaving?: boolean;
     plan?: InvoicingPlanWithIdentifiers;
+    /** Account and class trees the price-point pickers render as grouped options. */
+    qboAccountHierarchy?: NestedAccountHierarchyForReport[];
+    qboClassHierarchy?: NestedClassHierarchyForReport[];
+    /**
+     * The ids within `qboAccountHierarchy` the income-account picker may offer.
+     * QuickBooks takes only an income account on a product, so a price point
+     * mapped to anything else stops its invoices syncing. Absent means the tree
+     * is offered whole.
+     */
+    qboIncomeAccountIds?: readonly string[];
     tierTypeOptionsByPricingModel?: InvoicingNamedOptionsByKey;
     onBack?: () => void;
     onEditChange?: (localData: InvoicingCatalogItemFormLocalData) => void;

package/dist/components/invoicing/catalogForm/InvoicingCatalogItemFormPage.d.ts

@@ -36,19 +36,27 @@ export interface InvoicingCatalogItemFormPageProps {
      */
     fieldHelp?: FieldHelpByCode;
     /**
-     * True while the accounting lists are still loading. The form waits rather
-     * than render: the accounting fields choose between a picker and a text input
-     * from these lists, and swapping one for the other on a mounted form replaces
-     * a plain string value with a grouped one under the same field name.
+     * True while anything the fields mount against is still loading — in edit
+     * mode the item itself, and either way the accounting lists. The form waits
+     * rather than render, for two reasons that both outlive the response:
+     * `useForm` seeds its default values once, at first render, so fields mounted
+     * against the blank draft stay blank and the first change writes that
+     * blankness back over the item; and the accounting fields choose between a
+     * picker and a text input from the lists, so swapping one for the other on a
+     * mounted form replaces a plain string value with a grouped one under the
+     * same field name.
      */
-    isQboPickerDataLoading?: boolean;
+    isLoading?: boolean;
     qboAccountHierarchy?: NestedAccountHierarchyForReport[];
+    /** Class tree the price-point pickers render as grouped options. */
+    qboClassHierarchy?: NestedClassHierarchyForReport[];
     /**
-     * Account and class trees the price-point pickers render as grouped options.
-     * The account tree is already narrowed to the income accounts a price may
-     * post to, so this page does no filtering of its own.
+     * The ids within `qboAccountHierarchy` the income-account picker may offer.
+     * QuickBooks takes only an income account on a product, so a price point
+     * mapped to anything else stops its invoices syncing. Absent means the tree
+     * is offered whole.
      */
-    qboClassHierarchy?: NestedClassHierarchyForReport[];
+    qboIncomeAccountIds?: readonly string[];
     /**
      * `catalog_tier_type_options_by_pricing_model` from the invoicing config; the
      * tier `Type` column is driven by it. `undefined` until the config loads.
@@ -66,5 +74,5 @@ export interface InvoicingCatalogItemFormPageProps {
  * invoicing forms. The whole form syncs back to the CES draft (`localData`) on
  * every change; the save payload is derived from the draft in CES.
  */
-export declare function InvoicingCatalogItemFormPage({ applicabilityValues, fieldHelp, applicableItemOptions, defaultType, errorMessage, isSubmitting, localData, mode, onBack, onCancel, onChange, onSubmit, periodUnitOptions, pricingModelValues, prorationValues, isQboPickerDataLoading, qboClassHierarchy, qboAccountHierarchy, tierTypeOptionsByPricingModel, tierTypeValues, trialEndActionOptions, trialUnitOptions, typeOptions, }: Readonly<InvoicingCatalogItemFormPageProps>): import("react/jsx-runtime").JSX.Element;
+export declare function InvoicingCatalogItemFormPage({ applicabilityValues, fieldHelp, applicableItemOptions, defaultType, errorMessage, isLoading, isSubmitting, localData, mode, onBack, onCancel, onChange, onSubmit, periodUnitOptions, pricingModelValues, prorationValues, qboClassHierarchy, qboAccountHierarchy, qboIncomeAccountIds, tierTypeOptionsByPricingModel, tierTypeValues, trialEndActionOptions, trialUnitOptions, typeOptions, }: Readonly<InvoicingCatalogItemFormPageProps>): import("react/jsx-runtime").JSX.Element;
 export default InvoicingCatalogItemFormPage;

package/dist/components/invoicing/catalogForm/catalogItemForm.shared.d.ts

@@ -28,6 +28,17 @@ export interface CatalogFormConfigOptions {
     typeOptions: InvoicingNamedOption[];
     qboAccountHierarchy?: NestedAccountHierarchyForReport[];
     qboClassHierarchy?: NestedClassHierarchyForReport[];
+    /**
+     * The QuickBooks ids within {@link qboAccountHierarchy} an income account may
+     * be picked from. QuickBooks takes only an income account on a product, so a
+     * price point mapped to anything else stops its invoices syncing.
+     *
+     * Narrowed by id rather than by pruning the tree: the tree is flattened into
+     * options by walking each node's children, so dropping a parent that is not
+     * an income account would drop its income descendants with it. Absent means
+     * no narrowing.
+     */
+    qboIncomeAccountIds?: readonly string[];
 }
 export interface CatalogFormOptions {
     account: GroupedOption[];
@@ -56,13 +67,6 @@ export declare const CATALOG_LOCAL_TIER_TYPE_OPTIONS: CatalogSelectOption[];
 export declare const catalogOptionLabel: (allOptions: readonly CatalogSelectOption[], value: string | undefined) => string | undefined;
 /** Block any keystroke that would put a non-digit into a period field. */
 export declare const allowOnlyNumericKeys: (event: KeyboardEvent<HTMLInputElement>) => void;
-/**
- * Accounts as the grouped picker renders them. `getGroupedAccountOptions` falls
- * back to the internal id when a node carries no `qboId`; this form submits the
- * QuickBooks id, so an account without one is dropped rather than offered as a
- * value the invoicing API would reject.
- */
-export declare const toGroupedQboAccountOptions: (hierarchy?: NestedAccountHierarchyForReport[]) => GroupedOption[];
 /**
  * Classes as the grouped picker renders them. `getGroupedClassOptions` labels
  * each option with the internal class id while accounts use `qboId ?? id`, so the

package/dist/components/invoicing/common/InvoicingFormControls.d.ts

@@ -68,6 +68,13 @@ export interface InvoicingFormShellProps<TFieldValues extends FieldValues> {
     title: string;
     cancelLabel?: string;
     errorMessage?: string;
+    /**
+     * Holds submit closed without claiming a save is under way, for a form whose
+     * fields are still standing down behind a skeleton. Distinct from
+     * `isSubmitting`, which also disables cancel and spins the submit button —
+     * neither of which is true of a page that is merely loading.
+     */
+    isSubmitDisabled?: boolean;
     onCancel: () => void;
     onSubmit: (values: TFieldValues) => void;
     /** When provided, renders a back-arrow icon button to the left of the title. */
@@ -81,4 +88,4 @@ export interface InvoicingFormShellProps<TFieldValues extends FieldValues> {
  * should use the shared `formElements/Labeled*` primitives so field color,
  * hover/focus and search behave exactly like bill edit.
  */
-export declare function InvoicingFormShell<TFieldValues extends FieldValues>({ cancelLabel, children, errorMessage, formId, isSubmitting, methods, onBack, onCancel, onSubmit, submitLabel, title, }: Readonly<InvoicingFormShellProps<TFieldValues>>): import("react/jsx-runtime").JSX.Element;
+export declare function InvoicingFormShell<TFieldValues extends FieldValues>({ cancelLabel, children, errorMessage, formId, isSubmitDisabled, isSubmitting, methods, onBack, onCancel, onSubmit, submitLabel, title, }: Readonly<InvoicingFormShellProps<TFieldValues>>): import("react/jsx-runtime").JSX.Element;

package/dist/components/invoicing/common/InvoicingFormRows.d.ts

@@ -10,6 +10,13 @@ export declare function FormColumn({ children, style, }: Readonly<{
     children: ReactNode;
     style?: React.CSSProperties;
 }>): import("react/jsx-runtime").JSX.Element;
+/**
+ * Label-column width shared by these rows and the `formElements/Labeled*` rows
+ * they sit beside. Both families must agree or the labels step in and out
+ * within a section, so the pages pass this to `label.width` rather than
+ * restating the number.
+ */
+export declare const INVOICING_FORM_LABEL_WIDTH = 190;
 export declare const RowInput: import('@emotion/styled').StyledComponent<{
     theme?: import('@emotion/react').Theme;
     as?: React.ElementType;

package/dist/components/invoicing/common/InvoicingSkeletons.d.ts

@@ -34,9 +34,25 @@ export declare function InvoicingSettingsSkeleton({ tab, }: Readonly<{
 /** Shimmer placeholder while create-invoice settings are fetched from the API. */
 export declare function InvoicingCreateInvoiceSkeleton(): import("react/jsx-runtime").JSX.Element;
 /**
- * Stands in for the catalog item form's sections while the accounting pickers
- * load — their options and their registered value shape both depend on the
- * shared account and class lists. Renders inside the form shell's own centered
- * column, so the page keeps its title, back arrow and footer.
+ * Stands in for the catalog item form's sections while the record it edits and
+ * the accounting pickers load — the form seeds react-hook-form once, at first
+ * render, and the pickers' registered value shape depends on the shared account
+ * and class lists, so neither can be picked up after the fields have mounted.
+ * Renders inside the form shell's own centered column, so the page keeps its
+ * title, back arrow and footer.
  */
 export declare function InvoicingCatalogItemFormSkeleton(): import("react/jsx-runtime").JSX.Element;
+/**
+ * Stands in for the customer form's sections while the customer it edits loads.
+ * Same reason as {@link InvoicingCatalogItemFormSkeleton}: the form seeds
+ * react-hook-form once, at first render, so fields mounted against the blank
+ * draft stay blank however late the record lands.
+ */
+export declare function InvoicingCustomerFormSkeleton(): import("react/jsx-runtime").JSX.Element;
+/** Stands in for the discount form's sections while the coupon it edits loads. */
+export declare function InvoicingCouponFormSkeleton(): import("react/jsx-runtime").JSX.Element;
+/**
+ * Stands in for the subscription form's sections while the subscription it
+ * edits loads.
+ */
+export declare function InvoicingSubscriptionFormSkeleton(): import("react/jsx-runtime").JSX.Element;

package/dist/components/invoicing/common/invoicingAccountPickerOptions.d.ts

@@ -0,0 +1,15 @@
+import { NestedAccountHierarchyForReport } from '@zeniai/client-epic-state';
+import { GroupedOption } from '../../formElements/labeledGroupSingleSelectFieldWithRecommendationCheckbox/GroupedSingleSelectField';
+/**
+ * Accounts as the grouped picker renders them. `getGroupedAccountOptions` falls
+ * back to the internal id when a node carries no `qboId`; the invoicing forms
+ * submit the QuickBooks id, so an account without one is dropped rather than
+ * offered as a value the invoicing API would reject.
+ *
+ * `allowedAccountIds`, when given, narrows the result to the QuickBooks ids a
+ * slot accepts — an income-only picker, say. Narrowed here, once the tree has
+ * been flattened into options, rather than on the tree itself: the flattener
+ * recurses into each node's `children`, so dropping a parent that is not
+ * eligible would drop its eligible descendants with it.
+ */
+export declare const toGroupedQboAccountOptions: (hierarchy?: NestedAccountHierarchyForReport[], allowedAccountIds?: readonly string[]) => GroupedOption[];

package/dist/components/invoicing/couponForm/InvoicingCouponFormPage.d.ts

@@ -1,15 +1,40 @@
-import { InvoicingCouponFormLocalData, InvoicingFormOption } from '@zeniai/client-epic-state';
+import { InvoicingCouponFormLocalData, InvoicingFormOption, NestedAccountHierarchyForReport } from '@zeniai/client-epic-state';
 import { FieldHelpByCode } from '../../formElements/fieldHelp/FieldHelpContext';
 export interface InvoicingCouponFormPageProps {
     applyOnOptions: InvoicingFormOption[];
     discountTypeOptions: InvoicingFormOption[];
     durationTypeOptions: InvoicingFormOption[];
+    /**
+     * Whether to offer a discounts account at all. With no QuickBooks connection
+     * there are no accounts to pick from, and a coupon saves fine without one.
+     */
+    isQboConnected: boolean;
     isSubmitting: boolean;
     localData: InvoicingCouponFormLocalData;
     mode: "create" | "edit";
     periodUnitOptions: InvoicingFormOption[];
     errorMessage?: string;
     fieldHelp?: FieldHelpByCode;
+    /**
+     * True while the coupon being edited is still loading. The form holds its
+     * skeleton until the record lands: `useForm` seeds its default values once,
+     * at first render, so mounting the fields against the blank draft leaves them
+     * empty, and the first change writes that blankness back over the coupon.
+     * Always false when creating — there is nothing to load.
+     *
+     * Separate from `isQboPickerDataLoading`, which the discounts-account picker
+     * shows on itself: the rest of the form is usable before the lists land.
+     */
+    isLoading?: boolean;
+    isQboPickerDataLoading?: boolean;
+    /**
+     * The account tree the discounts-account picker renders, and the QuickBooks
+     * ids in it the discounts slot accepts. The tree is filtered by the ids
+     * rather than pruned, so a parent that is not itself an income account still
+     * groups the income accounts under it.
+     */
+    qboAccountHierarchy?: NestedAccountHierarchyForReport[];
+    qboIncomeAccountIds?: string[];
     onCancel: () => void;
     onChange: (localData: InvoicingCouponFormLocalData) => void;
     onSubmit: () => void;
@@ -20,5 +45,5 @@ export interface InvoicingCouponFormPageProps {
  * CES (`localData`) and is synced back on every change; submit triggers the
  * CES-stored draft.
  */
-export declare function InvoicingCouponFormPage({ applyOnOptions, fieldHelp, discountTypeOptions, durationTypeOptions, errorMessage, isSubmitting, localData, mode, onBack, onCancel, onChange, onSubmit, periodUnitOptions, }: Readonly<InvoicingCouponFormPageProps>): import("react/jsx-runtime").JSX.Element;
+export declare function InvoicingCouponFormPage({ applyOnOptions, fieldHelp, discountTypeOptions, durationTypeOptions, errorMessage, isLoading, isQboConnected, isQboPickerDataLoading, isSubmitting, localData, mode, onBack, onCancel, onChange, onSubmit, periodUnitOptions, qboAccountHierarchy, qboIncomeAccountIds, }: Readonly<InvoicingCouponFormPageProps>): import("react/jsx-runtime").JSX.Element;
 export default InvoicingCouponFormPage;

package/dist/components/invoicing/couponForm/couponForm.shared.d.ts

@@ -1,4 +1,5 @@
 import { InvoicingCouponFormLocalData, InvoicingFormOption } from '@zeniai/client-epic-state';
+import { GroupedOption, GroupedSingleSelectFieldValue } from '../../formElements/labeledGroupSingleSelectFieldWithRecommendationCheckbox/GroupedSingleSelectField';
 /**
  * Web-components glue for the coupon form. CES owns the draft `LocalData` and the
  * select-option value sets; this module maps those to the form's UI value shapes
@@ -17,12 +18,25 @@ export interface PickerValue {
  * Every plain field (name, couponCode, couponId, …) flows through by identity,
  * so adding a field to the CES type needs no mapper change.
  */
-export type CouponFormValues = Omit<InvoicingCouponFormLocalData, "applyOn" | "discountAmount" | "discountType" | "durationType" | "periodUnit" | "validFrom" | "validTill"> & {
+export type CouponFormValues = Omit<InvoicingCouponFormLocalData, "applyOn" | "discountAmount" | "discountPercentage" | "discountQuantity" | "discountsAccountId" | "discountType" | "durationType" | "maxRedemptions" | "period" | "periodUnit" | "validFrom" | "validTill"> & {
     applyOn: PickerValue;
     /** Held as a float by `returnValueType: "floatValue"`; `null` when cleared. */
     discountAmount: number | null;
+    /**
+     * The `type: "number"` fields. `TextField` and `FormattedTextField` register
+     * those with react-hook-form's `valueAsNumber`, so the form hands them back
+     * as numbers — `NaN` once the box is cleared — while the values seeded from
+     * CES are the strings it holds. Declared as both, because both occur:
+     * reading one as a string is what `max_redemptions.trim is not a function`
+     * was.
+     */
+    discountPercentage: number | string;
+    discountQuantity: number | string;
+    discountsAccountId: GroupedSingleSelectFieldValue;
     discountType: PickerValue;
     durationType: PickerValue;
+    maxRedemptions: number | string;
+    period: number | string;
     periodUnit: PickerValue;
     validFrom: Date | undefined;
     validTill: Date | undefined;
@@ -31,6 +45,8 @@ export interface CouponFormOptions {
     applyOnOptions: InvoicingFormOption[];
     discountTypeOptions: InvoicingFormOption[];
     durationTypeOptions: InvoicingFormOption[];
+    /** Income accounts for the discounts-account picker, grouped by parent. */
+    groupedAccountOptions: GroupedOption[];
     periodUnitOptions: InvoicingFormOption[];
 }
 export declare const localDataToCouponFormValues: (localData: InvoicingCouponFormLocalData, options: CouponFormOptions) => CouponFormValues;

package/dist/components/invoicing/customerDetail/InvoicingCustomerDetailPage.d.ts

@@ -14,6 +14,12 @@ export interface InvoicingCustomerDetailPageProps {
     /** Error from the last inline-edit save attempt, shown in edit mode. */
     fieldHelp?: FieldHelpByCode;
     hasPaymentLinkEmailPreviewFailed?: boolean;
+    /**
+     * A billing address entered on the Address screen and not yet saved. It is
+     * not a form field, so the form's own dirty state cannot see it; the footer
+     * offers Save on this as well, or the address could never be linked.
+     */
+    hasUnsavedBillingAddress?: boolean;
     /** Open the payment-link email preview modal on mount (Storybook). */
     initialPreviewEmailOpen?: boolean;
     /** Recent invoices for this customer (Figma: "Recent Invoices" table). */
@@ -47,11 +53,16 @@ export interface InvoicingCustomerDetailPageProps {
     onChange?: (localData: InvoicingCustomerFormLocalData) => void;
     onCreateInvoice?: () => void;
     onCreatePromotionalCredits?: () => void;
+    /** Open the shared Address screen to add/edit the billing address. */
+    /**
+     * Cancel discards the pending billing address too — it is not a form field,
+     * so `reset` alone would leave the footer up with nothing left to save.
+     */
+    onDiscardEdit?: () => void;
     /** Asked for when the composer opens, and again behind its Retry. */
     onFetchPaymentLinkEmailPreview?: (cacheOverride?: boolean) => void;
     onInvoiceClick?: (invoiceId: string) => void;
     onNewSubscription?: () => void;
-    /** Open the shared Address screen to add/edit the billing address. */
     onOpenAddress?: () => void;
     /** Navigate to Settings › Payment Destination (Stripe connect). */
     onOpenPaymentSettings?: () => void;

package/dist/components/invoicing/customerForm/InvoicingCustomerFormPage.d.ts

@@ -11,6 +11,14 @@ export interface InvoicingCustomerFormPageProps {
     billingAddressLabel?: string;
     errorMessage?: string;
     fieldHelp?: FieldHelpByCode;
+    /**
+     * True while the customer being edited is still loading. The form holds its
+     * skeleton until the record lands: `useForm` seeds its default values once,
+     * at first render, so mounting the fields against the blank draft leaves them
+     * empty, and the first change writes that blankness back over the customer.
+     * Always false when creating — there is nothing to load.
+     */
+    isLoading?: boolean;
     onCancel: () => void;
     onChange: (localData: InvoicingCustomerFormLocalData) => void;
     onOpenAddress: () => void;
@@ -24,5 +32,5 @@ export interface InvoicingCustomerFormPageProps {
  * focus, and searchable selects behave exactly like the bill edit page. Emits a
  * plain data object for the connector to dispatch.
  */
-export declare function InvoicingCustomerFormPage({ billingAddressLabel, fieldHelp, customerTypeOptions, errorMessage, isSubmitting, localData, mode, netTermDayOptions, onBack, onCancel, onChange, onOpenAddress, onSubmit, taxabilityOptions, }: Readonly<InvoicingCustomerFormPageProps>): import("react/jsx-runtime").JSX.Element;
+export declare function InvoicingCustomerFormPage({ billingAddressLabel, fieldHelp, customerTypeOptions, errorMessage, isLoading, isSubmitting, localData, mode, netTermDayOptions, onBack, onCancel, onChange, onOpenAddress, onSubmit, taxabilityOptions, }: Readonly<InvoicingCustomerFormPageProps>): import("react/jsx-runtime").JSX.Element;
 export default InvoicingCustomerFormPage;

package/dist/components/invoicing/discountDetail/InvoicingDiscountDetailPage.d.ts

@@ -5,6 +5,13 @@ export interface InvoicingDiscountDetailPageProps {
     isLoading: boolean;
     coupon?: InvoicingCoupon;
     discountLifecycleActionOptions?: InvoicingDiscountLifecycleActionOption[];
+    /**
+     * The account the coupon's discount line posts to, resolved from the id the
+     * coupon stores. Absent while the account list is still loading, or when the
+     * coupon names no account of its own — in which case the QBO settings
+     * discounts account applies instead.
+     */
+    discountsAccountName?: string;
     /** Error from the last inline-edit save attempt, shown in edit mode. */
     fieldHelp?: FieldHelpByCode;
     isRunningLifecycleAction?: boolean;

package/dist/components/invoicing/subscriptionDetail/InvoicingSubscriptionDetailPage.d.ts

@@ -15,10 +15,18 @@ export interface InvoicingSubscriptionDetailPageProps {
      * editable whenever save is wired.
      */
     canEditCommercial?: boolean;
+    /** One-time charge price options for commercial inline edit. */
+    charges?: InvoicingSubscriptionFormOption[];
     /** Coupon options for commercial inline edit. */
     coupons?: InvoicingSubscriptionFormOption[];
     /** Error from the last inline-edit save attempt, shown in edit mode. */
     fieldHelp?: FieldHelpByCode;
+    /**
+     * A shipping address entered on the Address screen and not yet saved. It is
+     * not a form field, so the form's own dirty state cannot see it; the footer
+     * offers Save on this as well, or the address could never be linked.
+     */
+    hasUnsavedShippingAddress?: boolean;
     isRunningAction?: boolean;
     /** True while an inline-edit save is in flight. */
     isSaving?: boolean;
@@ -38,6 +46,11 @@ export interface InvoicingSubscriptionDetailPageProps {
     /** Called with the entered date once the change-term-end dialog is confirmed. */
     onChangeTermEnd?: (termEndsAt: string) => void;
     onCustomerClick?: (customerId: string) => void;
+    /**
+     * Cancel discards the pending shipping address too — it is not a form field,
+     * so `reset` alone would leave the footer up with nothing left to save.
+     */
+    onDiscardEdit?: () => void;
     /** `resumeDate` is only supplied for `pause`, collected by the pause dialog. */
     onLifecycleAction?: (action: InvoicingSubscriptionLifecycleAction, resumeDate?: string) => void;
     /** Open the shared Address screen to add/edit the shipping address. */