User Manual

Accounting Periods & Period Close

Last updated March 28, 2026 · Super Admin

Accounting Periods & Period Close

Accounting periods define the time boundaries over which CryptaCount aggregates transactions, calculates balances, and produces financial reports. The period close workflow ensures data completeness and integrity before finalizing each period.

Creating Accounting Periods

Navigate to Accounting → Accounting Periods to manage the period calendar for your workspace.

![Accounting periods list](../../../assets/screenshots/accounting-periods.png)

Monthly Periods

CryptaCount can auto-generate monthly periods for a fiscal year. Each period spans a calendar month (e.g., 2025-01-01 to 2025-01-31). Monthly periods are the most common configuration and align with standard reporting cadences.

To create monthly periods:

1. Navigate to Accounting → Accounting Periods 2. Select the fiscal year start month 3. Click Generate Monthly Periods — CryptaCount creates 12 periods

Custom Periods

For non-standard fiscal calendars (4-4-5, 4-week periods, stub periods), create periods manually:

1. Click Create Period 2. Set the start and end dates 3. Assign a period name (e.g., "Q1 2025" or "Stub — Jan 1–15") 4. Save

:::caution Periods must not overlap. CryptaCount validates that each new period's date range does not conflict with existing periods in the workspace. :::

Period States

Each period moves through a lifecycle:

| State | Description | |---|---| | Open | Transactions can be posted, journals created, balances calculated | | Closed | No new postings allowed — period has passed close workflow | | Locked | Permanently sealed — cannot be reopened |

Monthly Close Workflow

The period close under Accounting → Period Close follows a structured four-stage process designed to match professional accounting practice.

![Period close workflow](../../../assets/screenshots/period-close.png)

Stage 1 — Initiate Close

Select the period to close and click Initiate Close. This triggers the automated check suite and moves the period into "closing" status. No new journal entries can be posted while the close is in progress.

Stage 2 — Run Checks

CryptaCount runs a series of validation checks against the period:

| Check | What It Validates | |---|---| | Unmapped addresses | All wallet addresses have GL account mappings | | Transaction counts | On-chain transaction counts match imported counts | | Opening vs. closing balances | Opening balances for this period match closing balances of the prior period | | Internal transfers | Internal transfer pairs are balanced (no orphans) | | Fee completeness | All transactions with fees have fee amounts recorded | | Price availability | All assets have price data for the period's date range | | CEX matching | CEX import transactions are matched or accounted for | | Double-entry integrity | Total debits equal total credits across the period | | Ledger replay | Journal entries can be replayed from source transactions without discrepancy | | Hash chain integrity | Journal hash chain is unbroken through the period |

Each check returns a pass, warning, or fail status with details.

Stage 3 — Validate & Waive

Review the check results:

  • All passed — Proceed directly to close
  • Warnings present — Review each warning. Warnings do not block close but should be investigated.
  • Failures present — Either fix the underlying issue and re-run checks, or waive the failed check with a written justification
Waived checks are recorded in the audit trail with the user who waived, the timestamp, and the justification text. This is visible to auditors reviewing the period.

Example: *Acme Digital Holdings* might waive a price availability check for an obscure governance token if the position is immaterial, documenting: "GOVXYZ position is €12.40 — immaterial, price manually verified."

Stage 4 — Complete Close

Click Complete Close to finalize:

  • The period status moves to Closed
  • A close timestamp and closing user are recorded
  • Closing balances are frozen as the opening balances for the next period
  • The period appears as "Closed" in the period list

Reopening a Closed Period

If an error is discovered after close:

1. Navigate to the period in Accounting → Accounting Periods 2. Click Reopen 3. Provide a justification (recorded in audit trail) 4. The period returns to Open status 5. Make corrections, then run the close workflow again

:::note Reopening a period may affect downstream periods. If Period 2's opening balances were derived from Period 1's close, reopening Period 1 invalidates Period 2's opening balances. CryptaCount warns about this cascade. :::

Year-End Close

The year-end close is a special close operation available on the last period of a fiscal year. In addition to the standard close checks, it:

1. Closes all remaining open periods in the fiscal year (runs checks on each) 2. Generates closing entries — Revenue and expense accounts are zeroed out to Retained Earnings 3. Carries forward balances — Balance sheet accounts (assets, liabilities, equity) carry forward as opening balances for the new fiscal year 4. Locks the fiscal year — All periods in the year are locked to prevent accidental reopening

To run year-end close:

1. Ensure all periods except the final one are already closed 2. Navigate to the final period's close workflow 3. Select Year-End Close instead of standard close 4. Review the generated closing entries before confirming

Opening Balances

Set the starting position for wallets that held assets before connecting to CryptaCount under Accounting → Opening Balances.

![Opening balances import](../../../assets/screenshots/opening-balances.png)

When to Use Opening Balances

  • Migrating from another accounting system to CryptaCount
  • Connecting a wallet that has historical activity predating your CryptaCount start date
  • Starting a new fiscal year with carried-forward positions

Import Methods

File import:

1. Navigate to Accounting → Opening Balances 2. Click Import 3. Upload a CSV with columns: asset, quantity, cost basis, GL account, date 4. Preview the import and confirm

Auto-populate:

CryptaCount can suggest opening balance dates based on wallet sync history. Click Suggested Date to use the earliest synced transaction date minus one day. The system calculates positions from on-chain data up to that date.

Manual entry:

Set individual asset balances directly in the UI. Specify the asset, quantity, unit cost basis, and target GL account.

Opening Balance Rules

  • Opening balances must be set before running balance calculations for the period
  • Each asset's opening balance is recorded as a journal entry (debit asset account, credit opening balance equity account)
  • Once a period is closed, its opening balances cannot be modified without reopening the period

Locking Periods

Locked periods are permanently sealed:

  • Cannot be reopened
  • No journal entries can be posted or reversed
  • Opening balances cannot be modified
  • Provides the strongest audit guarantee
To lock a period, it must already be in Closed status. Navigate to the period and click Lock. This action requires Owner or Manager role and is recorded in the audit trail.

:::tip Lock periods after your external audit is complete. This ensures the audited figures cannot be accidentally altered. :::

Was this article helpful?

Let us know if this answered your question

Accounting Periods & Period Close — CryptaCount Support