Finance Operating SystemDocs
Concepts

Fiscal periods

The OPEN/CLOSED model, how it interacts with writes, and the close-reopen lifecycle.

Fiscal periods

A fiscal period is a contiguous date range — usually one month — covering a slice of your fiscal year. Every fiscal period has a status: OPEN (writes allowed) or CLOSED (writes rejected). Closing is a hard guarantee: once a period is closed, the trial balance on its end date never changes (modulo a rare and audited reopen).

Why we bother

A small business with no period close still has functional books — but it has no way to make a number "official". If you re-run last quarter's P&L six months later and it has changed, you cannot trust any number you sent to a tax preparer, a lender, or an investor. Closing periods is the discipline that turns "current best estimate" into "audited history".

The state machine

text
       ┌────────┐    close()    ┌────────┐
START  │  OPEN  │ ─────────────▶│ CLOSED │
       └────────┘                └────────┘
            ▲                         │
            └────────reopen()─────────┘
                  (owner only,
                   audit-logged)

A new period starts OPEN. The owner closes it via the UI or the API. Writes to closed periods are rejected at the API layer with 409 period_closed. Reads are unaffected. An owner can reopen a closed period; this is recorded in the audit log with timestamp + actor + reason.

How writes are gated

Every transaction has a date. When we save it, we look up which period contains that date and check the status. If the period is closed, we refuse the write — both for new transactions and for edits to existing ones. The check happens at the API layer, not just the UI, so scripts and webhooks cannot bypass it.

For deletions of transactions in closed periods, the same rule applies: you cannot delete; you can only post a reversing entry in the next open period.

Multiple closed periods

You can have any number of consecutive closed periods. The usual pattern for small businesses is: most recent 1-3 months OPEN, everything before that CLOSED. You can close in any order; in practice you close oldest-first (close January before closing February), but the system does not require it.

Period generation

When you set your fiscal year start in onboarding, we auto-generate the 12 monthly periods for the current year. At year-end we prompt you to roll forward — accept and we generate the 12 periods for the next year.

If you want quarterly closes instead of monthly, you can manually consolidate by closing Jan + Feb + Mar individually then treating Q1 as a logical close. We do not have a "quarter" period type — but Q1 is just the conjunction of three closed monthly periods, which is functionally identical.

Year-end specifics

The year-end close is the same operation on the last period of the fiscal year, plus an explicit closing entry: a journal that zeroes out all revenue and expense accounts into retained earnings. From Settings → Fiscal periods → Year end → Generate closing entry, we compute the entry and post it after you confirm. The next year's P&L starts at zero, as it should.