Accounting Period in ERPNext
An Accounting Period defines a specific time frame during which financial transactions can be created and submitted. It helps organizations control accounting activities by restricting selected transactions outside the defined period.
Accounting Periods are commonly used when closing books, preparing financial statements, conducting audits, or ensuring that finalized accounting records are not modified.
An Accounting Period restricts selected transactions from being created or submitted outside the specified date range, helping maintain the accuracy and integrity of financial records.
To access Accounting Periods:
Home > Accounting > Accounting Period
1. Why Use an Accounting Period?
When accounting transactions are submitted, they create General Ledger (GL) entries that directly affect:
- Financial Statements
- General Ledger Reports
- Profit and Loss Statements
- Balance Sheets
- Audit Reports
- Year-End Closing Activities
Allowing users to modify historical transactions after financial reports have been finalized can lead to reporting inconsistencies and audit issues.
Accounting Periods help organizations lock specific periods and prevent unauthorized changes after financial data has been reviewed or reported.
2. How to Create an Accounting Period
Follow these steps to create a new Accounting Period:
- Go to the Accounting Period list and click New.
- Enter a name for the Accounting Period.
- Set the Start Date and End Date.
- Add the transaction types that should be controlled.
- Select the Closed option for transactions that should be restricted after the period ends.
- Save and Submit the document.
Once submitted, ERPNext will enforce restrictions based on the selected settings.
3. Understanding the “Closed” Option
Within the Accounting Period document, a child table allows you to define which transaction types should be restricted.
The Closed checkbox determines whether a transaction type is locked after the Accounting Period ends.
For example:
- If Sales Invoice is marked as Closed, users cannot create or submit Sales Invoices after the period ends.
- If Purchase Invoice is not marked as Closed, users can continue working with Purchase Invoices even after the period expires.
Only transaction types marked as Closed will be restricted after the Accounting Period ends.
4. Transactions That Can Be Restricted
Organizations can choose which transaction types should be controlled during the Accounting Period.
Common examples include:
- Sales Invoice
- Purchase Invoice
- Journal Entry
- Payment Entry
- Stock Entry
- Payroll Entry
- Delivery Note
- Purchase Receipt
- Other submittable accounting and inventory transactions
This flexibility allows businesses to lock only the documents relevant to their accounting processes.
5. What Happens After the Accounting Period Ends?
When a user attempts to create, save, or submit a restricted transaction after the Accounting Period has ended:
- ERPNext performs validation checks.
- The transaction is blocked.
- An error message is displayed.
- The document cannot be submitted until it falls within an active Accounting Period.
ERPNext prevents restricted transactions from being processed after the Accounting Period ends, ensuring that finalized accounting records remain unchanged.
6. Important Limitation
Accounting Period restrictions apply to all users regardless of permissions.
Even users assigned to:
- Role Allowed to Set Frozen Accounts
- Role Allowed to Edit Frozen Entries
- System Managers
- Accounting Managers
cannot bypass Accounting Period restrictions for transaction types defined within the Accounting Period.
No user role can override Accounting Period restrictions once the selected transaction types have been closed.
7. Benefits of Accounting Periods
- Protects finalized financial data
- Prevents accidental backdated transactions
- Improves audit compliance
- Supports financial year-end closing processes
- Maintains report accuracy
- Ensures accounting consistency across teams
- Reduces risks of unauthorized financial changes
