Cash forecast and aging

Review expected cash without changing payment terms

Open Finance → Cash forecast & aging. The report reads issued invoices, recorded receipts and corrections, and unpaid business expenses from one consistent database snapshot. Draft or void invoices, unsigned proposals, and potential sales are excluded. Private wedding records belonging to another business never appear.

Aging uses the business timezone and recorded due dates. The buckets are not overdue, 1–30, 31–60, 61–90, over 90 days, and no due date. Unsettled payments remain part of the outstanding balance but are withheld from expected inflows: no settlement date is assumed. Refunds do not automatically reopen an already settled obligation. A recorded correction can reopen principal.

Save an explicit scenario

Choose a start date and one to 26 weeks. Set an optional collection delay for invoices due during the forecast. An overdue invoice or an invoice without a due date stays unscheduled until you enter an assumed payment date. Separate fields handle expenses. These assumptions do not edit invoice terms, charge a payment method, or send reminders.

Enter an opening cash amount only when you want to supply one yourself. Leaving it blank means the report shows expected net movements with an unknown projected balance. A zero opening balance is an explicit assumption, not the default. Currencies remain separate; WeddingBoard does not invent exchange rates or a bank balance.

For example, a $1,500 invoice has a $500 recorded receipt and $250 still processing. Its remaining obligation is $1,000. Only $750 is available to forecast. If its due date precedes the forecast start, that $750 remains unscheduled until reviewed. Assuming collection next Tuesday schedules $750; it does not turn the $250 processing amount into received cash.

Review individual sources

Under Source review, choose Review dates & assumptions. A saved scenario can override one source's expected date or exclude it. Use scenario defaults removes that override. Unscheduled, excluded, and outside-period amounts are shown separately so missing assumptions cannot silently disappear.

An expense's incurred date is not its due date. Save expense due date records the actual due date without changing amount, tax, receipt, or payment status. An expected date only changes the forecast scenario.

Saved scenarios retain their assumptions and always recalculate against current financial records. They are not frozen historical reports. Export the source CSV when you need the current record IDs, balances, assumptions, and read time. The separate last-30-days cash section shows recorded receipts, refunds and corrections, known fees, and expenses marked paid. It is not a bank reconciliation or an accrual profit report. Historical invoice paid flags still reduce the old obligation, but are excluded from the recorded-cash subtotal and shown separately. Their imported record date can fall in the selected period without establishing when cash was actually collected; the original receipt and collection date remain unverified.

Permissions and recovery

Owners, admins and staff with full workspace access can read and edit these private reports. A scoped API key requires finance:read or finance:write; writes require explicit approval. Shared wedding participation does not grant financial access.

Every reviewed change checks its saved revision. If another person saved first, reload and review the new assumptions. Retrying an unchanged interrupted submission uses its original receipt and cannot apply twice. Archiving retains assumptions; restore the scenario before editing. Archived views still use current source balances.

API clients use /api/v1/finance/forecast. Fetch up to 100 source rows and pass the returned reportRevision as ifRevision on later pages. A 409 means sources changed and pagination must restart. Expense changes require their expectedUpdatedAt; scenario changes require expectedRevision. No live banking or prediction model is configured by this feature.