Accounting & Bookkeeping · How-to guide

Configure the financial year and close books

Define reporting boundaries and protect completed periods from unauthorised back-dated changes.

Audience: Finance administratorsFeature: Financial controlsModule v1.4.5
Feature pathAccounting → Settings → General
Before you beginThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Accounting Settings: Edit. A related screen can remain hidden when an optional module is inactive, a source record is in an ineligible status, the selected account is inactive or the user is not an assigned approver.

What this feature does

Define reporting boundaries and protect completed periods from unauthorised back-dated changes. It forms part of Britixo Enterprise CRM's Accounting & Bookkeeping module and uses the module's permission-aware controller, status and mapping flow rather than a generic spreadsheet process.

How the module flow works

Close-books protection is a control, not a substitute for staff permissions. Limit journal, delete and settings permissions as well.

If historical transactions must be corrected, document the reason, obtain approval and rerun affected reports. The correct treatment may be a current-period adjustment rather than reopening.

Budgets and comparison reports depend on consistent financial-year boundaries.

Step-by-step workflow

  1. Confirm the approved financial-year start.
  2. Set the financial-year value in General settings.
  3. Complete reconciliation and period-end reports.
  4. Set the close-books date after approval.
  5. Test an attempted back-dated entry using an authorised test process.
  6. Record who approved the close and retain the period reports.

Important fields and decisions

Financial-year startDetermines the annual reporting cycle and budget periods.
Close-books dateMarks the last protected date.
Close-books behaviourMay block or warn against changes, based on configured options.
Adjustment processAuthorised adjustments should use a documented journal and reference.

What happens after completion

After the action is saved, Britixo keeps the Accounting record connected to its source and updates the visible status or ledger data supported by this workflow. Review the saved result rather than relying only on a success message. Where the action posts accounting data, total debits and credits must balance and the accounts must match the approved mapping or manual selection.

  • Open the saved record and confirm its final status.
  • Review the source reference and every debit and credit line where ledger data was created.
  • Use the relevant register, ageing, reconciliation or report to verify the wider effect.

Controls, checks and common mistakes

  • Do not close a period before bank reconciliation is complete.
  • Do not bypass a close-books control by changing source dates.
  • Use a new-period correcting entry where policy requires it.
  • Review recurring and imported transactions before closing.
  • Use the least destructive correction available and record the reason for material changes.
  • Do not bypass a permission, approval or closed-period control by changing unrelated data.
Accounting and data safetyDeletion, reset, void, refund, mapping, journal and reconciliation actions can change financial history. Use approved access, retain supporting evidence and validate the result in the General Ledger or relevant control report.