Accounting and recognition

Actual, forecast and scenario entries share the journal and calculation engine with explicit state. Reported calculations use integer minor units and preserve their formula versions and inputs.

Posting controls

A proposed journal must have valid company-owned accounts, supported provenance and approvals, an open period, and balanced debits and credits. Entity and currency treatment must also pass the relevant controls.

Moving cash between accounts is not revenue. Correct account classification and balanced entries are necessary before the financial statements or forecast can be relied on.

Actual income statement, balance sheet and cash-flow calculations derive from the ledger. Broader accounting support does not imply every projected statement or goal metric has the same supported scope.

Corrections and close

Use a reversal to correct a posted journal while preserving its relationship to the original entry, basis and lineage. A reversal of an allocated actual reopens the affected forecast obligation for review.

Review reconciliation and close controls before closing a month. Closed periods block inappropriate new postings; reopen through the authorized workflow when a correction requires it. A historical forecast anchor does not certify that a period was closed or complete.

Supported recognition schedules

The planning workflow supports a bounded fixed, single-payment prepaid or accrual schedule with an explicit recognition interval of at most 24 months.

It requires an approved cash/revenue or expense/cash template and an unambiguous active working-capital account classified as receivable, payable, prepaid asset or deferred revenue. Prepayment occurs before recognition; accrued payment follows recognition.

Recognition splits integer minor units across the original interval. Remainder pennies go to the earliest months. The cash payment and non-cash recognition use balanced entries in the same forecast engine.

Continue a schedule across months

When part of the schedule is already in the past, use the recognition continuity review on /progress:

1. Select the actual payment and recognition journals supporting the completed portion.
2. Give the linkage a reason.
3. Preview the remaining schedule and any reconciliation exception.
4. Approve the current preview only after the completed schedule ties.

Cumulative debits and credits by account must exactly match the completed scheduled entries. Valid supporting actuals allow only the future portion to continue; the cash payment is not repeated and penny allocation is not restarted.

Changed, reversed, incomplete or incompatible supporting journals reopen the exception. Revoking a link preserves its history. An unsupported past balance never becomes a guessed opening amount.

Limits

Recurring or formula-based recognition, ambiguous mappings and unsupported entity/FX proof remain exceptions. These controls do not introduce revenue/profit goals or certify projected financial statements. See Supported scope.