Cube board packs need a post-close send receipt

Define the pack release event

Create a release receipt for every board, lender, or investor pack. Record the reporting entity and period, close status, model and source refresh time, deck identifier, bound-object inventory, commentary version, preparer, controller review, CFO approval, recipient group, send time, and file or publication hash. Mark estimates, open adjustments, and figures that were intentionally frozen. A slide connected to a live model can be current when reviewed and different when reopened; the receipt identifies the exact evidence the audience received.

Keep three states separate: a finance draft, a published internal leadership view, and an externally sent pack. Cube's page describes permissioned publication and versions that lock at send, but the buyer must verify what those states mean in its tenant and delivery channel. Test whether a copied deck, exported PDF, chat answer, and data-room version retain the same source date and approval. Do not treat a model refresh or a successful send notification as proof that every intended recipient saw the approved pack.

Reconcile late entries without rewriting history

Use a synthetic late journal entry to test the boundary. Refresh the model after close, identify every bound figure and derived narrative affected, and compare the recalculated pack with the send receipt. The controller should decide whether the entry belongs in the reporting period, whether it changes a material conclusion, and whether a revised pack is required. Preserve both versions and the reason for the change. A convenient automatic refresh must not overwrite evidence of what management or the board relied on.

For each changed number, retain the source transaction, mapping, consolidation treatment, affected KPI, commentary change, reviewer, and disposition. If the story changes while a figure does not, or a figure changes while the commentary remains fixed, stop the release. Drill-through can support investigation, but it does not establish the completeness of the population or the accounting conclusion. The general ledger, approved close policy, and authorized reporting process remain controlling.

Test the control before relying on the workflow

Pilot one recurring management pack with a small set of bound tables, charts, and narrative claims. Exercise late entries, reopened periods, mapping changes, permission changes, a recipient removed after publication, a failed refresh, an exported copy, and a post-send correction. Measure preparation time, unresolved exceptions, reconciliation differences, review effort, wrong-version access, and time to answer a source question. Report the provider's product claims separately from observed tenant behavior.

The CFO should approve the materiality threshold and correction route, while the controller owns close evidence and the reporting owner controls distribution. Security and legal reviewers should confirm audience permissions, retention, and external-sharing terms. Hold expansion if the organization cannot reproduce the sent version, identify the figures affected by a late entry, or show who approved the narrative. A live pack is useful only when finance can also prove the state that became an official communication.

Turn this source into a reviewable decision

For AI for CFOs, use this briefing as a dated decision record rather than a substitute for the source. Preserve Executive & Investor Reporting, the exact URL, the September 23, 2026 review date, the supported facts above, the editorial interpretation, the limitations, and any buyer-specific evidence. Link that record to the decisions most directly affected: Management reporting and external disclosure support; Close, reconciliation, and variance investigation; Internal control and audit evidence. State whether the source changes the scope, evidence requirement, control, sequence, or only the language used to describe the decision.

Before action, name the accountable owner, affected population and workflow, exact offering or configuration, source data and rights, human decision point, exception and appeal path, complete cost, expected benefit, failure and stop conditions, retained evidence, and next review date. Keep official facts, provider statements, buyer observations, representative tests, measured outcomes, editorial inferences, and unknowns visibly separate. Reopen the record when the source, offer, model, integration, data, policy, population, responsible person, or measured result changes.

Limitations and unknowns

Cube is the provider and source for this current product and use-case page, checked September 23, 2026. The page exposes no publication or material-update timestamp sufficient to establish a verified change after the September 22, 2026 12:03:48 UTC cutoff. It describes intended workflow and marketing claims, not a customer's configuration, source completeness, close status, accounting conclusion, permission design, sent artifact, audit result, or outcome. Verify current contract, release, tenant behavior, integrations, source mappings, approval and distribution controls, retention, exported artifacts, and qualified finance, accounting, audit, security, privacy, legal, and investor-relations review before reliance.