ERPNext naming series for invoices

How ERPNext naming series for invoices fit your numbering rules

Finance and operations leads need invoice and document numbers that line up with tax and audit rules, and ERPNext handles this through naming series. In ERPNext, a naming series is the pattern that generates the name of a document when it is saved, such as a sales invoice or a delivery note. The series defines the prefix, the counter and the format the number follows, so the number a customer or auditor sees is set by configuration rather than typed by hand. Before go-live, decide which document types need their own series, who may change them, and how the numbers will be reviewed against your tax and audit requirements.

ERPNext documents two patterns that matter most for regulated invoicing. The first is company-wise naming series, described in the ERPNext documentation on company-wise naming series, which keeps numbering separate for each company in a multi-company setup. This is usually the question to settle first if one legal entity issues invoices under its own sequence. The second is naming series as per GST rules, covered in the ERPNext documentation on GST naming series, which applies to organizations that must follow Indian GST numbering conventions. Confirm with your tax adviser whether either pattern is required in your jurisdiction, and whether a single sequence across companies or branches is acceptable.

Once the patterns are chosen, confirm the details in a test environment before any live invoices are issued. Check that each series produces the expected format for every company and document type, that the counter starts where your records require, and that the people allowed to edit series settings are limited to a named role. Document the approved series in your accounting procedures so auditors can trace each number to its rule. Changes to a series after invoices exist should go through the same review, because they can create gaps or repeated numbers that are hard to explain later. Ask your implementation partner to show these checks in your own configuration, not only in the standard demo.

Which naming series pattern fits your organization

A single legal entity with one chart of accounts and one sequence of sales and purchase documents is the simplest case. The naming series can stay close to the ERPNext defaults, with a short prefix per document type and a counter that rolls forward within a fiscal year if your auditors expect that. The main design work is deciding whether the year belongs in the number at all, since it makes annual resets easy to read but also makes it harder to see continuity across years.

Prefix per document type: Each DocType such as sales invoice or delivery note gets its own series, so a number reveals the document type at a glance.
Year segment: An optional year token, for example in an illustrative pattern like SINV-.YYYY.-, separates periods but requires a plan for the first document of each year.
Single counter: One running sequence per document type avoids any question about which company issued a number.
Manual edits: Changing the current value of a series is possible, but it should be an administrator action logged in your change process.
Migrated history: Imported invoices may keep their old numbers, so confirm how the new series starts above the last migrated value.

Before choosing, confirm with your auditors and tax adviser whether any number format is mandated for invoices in your jurisdiction, and test the pattern with a few documents in a non-production site.

When a group runs several companies in one ERPNext instance, numbering can be made company-wise so that each entity issues documents from its own sequence. A company abbreviation in the prefix, combined with the year if needed, lets a reader identify the issuing entity from the number alone. The decision is about how much isolation each legal entity needs in its paper trail and whether intercompany documents should share or separate sequences.

Company abbreviation: The series prefix carries a short code for each company, for example an illustrative ACME-SINV-.YYYY.- pattern for one entity.
Separate counters: Each company keeps its own running number, so gaps in one entity do not appear as gaps in another.
Intercompany documents: Decide whether intercompany invoices follow the issuing or receiving company's series, and document the rule.
Company-wise setup: ERPNext documents company-wise naming series, so review that page before enabling the pattern across the group.
Cross-company reporting: Confirm that finance reports and tax filings can still group documents by entity regardless of prefix.

Before choosing, confirm the abbreviation scheme with each entity's finance and legal owners and check whether any entity is subject to local rules on document numbering.

Naming series options and when each one fits

This table compares the main naming series choices in ERPNext: year and company in the pattern, company-wise series, GST-rule series for tax documents, and a single shared series. Read each row as a trade-off between reporting, audit readability and day-to-day administration. The main takeaway is that the pattern you pick is hard to change once invoices exist, so confirm it before go-live.

Option	Trade-off on reporting and audit	Administration and what to confirm
Year in the pattern (for example, a prefix with the fiscal year)	Invoice numbers show the period they were raised in, which helps manual review and paper filing. Reports still need the posting date filter, since the number does not guarantee the period.	Confirm how your fiscal year maps to the calendar year and who resets or extends the series each year.
Company in the pattern or company-wise series	Each legal entity keeps its own number sequence, so a multi-company group can report per entity without gaps caused by other companies.	Confirm each company's naming series is set on its own record and that users are restricted to the right company when creating documents.
GST-rule series for tax documents	Tax invoices follow the numbering rules your tax jurisdiction expects, which supports return preparation and reviewer checks.	Confirm the current GST rules in the ERPNext documentation match your registration, and test the series on a copy before using it on live invoices.
Single shared series across companies or document types	One sequence is simple to audit end to end, but numbers from different entities interleave, and a gap in one entity looks like a gap in the group.	Confirm your auditors accept a shared sequence and that you have a process to explain gaps caused by cancelled or draft documents.
Changing the current value of an existing series	Lowering a counter risks duplicates with documents already posted, while raising it creates a visible jump in numbers.	Confirm who holds permission to edit the series counter and log each change with a reason in your change records.
Cancelled and amended documents	Cancelled invoices keep their number, so a gap appears unless you document the cancellation in your audit trail.	Confirm how your team handles cancellations, amendments and draft deletions before go-live, and how reviewers will read those gaps.

How to set up and test naming series in ERPNext

This sequence turns a numbering plan into working naming series for each company and document type, so that generated invoice and document numbers are predictable before any live transaction is posted. It ends with a confirmed starting counter and a record of who signed off on the pattern.

Map document types and companies
Start with a table that lists every company in the ERPNext instance and every document type that needs its own numbering, such as sales invoices, delivery notes, payment entries and purchase invoices. Note where a company needs a separate sequence and where a shared one is acceptable, and identify any tax-driven numbering rules your finance or tax advisers require. The finance lead and the ERPNext administrator should both approve this map. The step is done when every document type has one named owner and one company scope.
Define the series pattern in setup
In the naming series setup, write a prefix pattern for each document type, typically including a fixed code, the company abbreviation and a year segment, followed by a padded counter. Keep the pattern short enough to read on printed documents and consistent across companies. Confirm in the ERPNext documentation how company-wise and GST-driven series are defined for your version, since the rules differ. The check: save the pattern and open a new draft of that document type to see the name the form proposes, without saving it.
Assign series to each company
Apply the company-specific series to each company's document settings so that a draft created under one company cannot draw from another company's counter. Where the design calls for tax-rule numbering, link the series to the tax rule or document type the finance team specified. The administrator makes these assignments, and the finance lead checks them. The step is complete when each company shows only its own series in the selection list on the test company's forms.
Create test drafts on a test company
On a test company or a copy of the instance, create several draft documents for each document type, including at least one for each company and one tax-relevant transaction. Save the drafts but do not submit them, so the counters are not consumed by final records. Use an illustrative set of customers and suppliers that cannot be mistaken for live data. The check is a list of generated draft names that you can compare against the pattern in the design map.
Review generated names against the design
Compare each generated name with the pattern and the company map. Look for wrong company codes, a year segment that does not match the posting date, inconsistent padding, or a series that is shared when it should be separate. Also test a document that is cancelled or amended, and confirm how the name behaves in your version. Record any mismatch and correct the series setup before continuing. The step is done when a reviewer signs off a test log showing that every sample name matches the design.
Confirm the current counter before go-live
Before live use, check the current value of each series in the production instance, especially if the company already has documents or is migrating from another system. Set the starting counter only after confirming the highest number already issued for that series, so the next document does not duplicate an existing number. Ask your ERPNext partner or internal administrator to confirm the procedure for changing a counter in your version. The check is a written record of each series, its starting value and the person who verified it.
Document the pattern and assign ownership
Write down the final pattern for each document type and company, the counter values at go-live and the steps for changing a counter later. Name who may change a series and who must approve the change, so later edits do not create gaps or duplicates. Store the document with your ERPNext configuration records and review it again when a new company or document type is added. The step is complete when the document is approved and a named owner is recorded for each series.

When and how to change the current value of a series

Change a series counter only when you have a specific reason, such as continuing numbering after a data migration or resetting numbers after a test cycle, and never set it below the highest number already issued for that prefix. If the counter is lower than existing documents, ERPNext will eventually generate a name that is already in use, and the result is a duplicate document number on an invoice or delivery note that an auditor or tax authority will see. Before you touch the counter, search for existing documents that share the prefix, including cancelled and draft records, because cancelled documents still hold their names. Plan the new value as the highest existing number plus one, and confirm the exact procedure in the naming series documentation for your ERPNext version before running it on a live company.

Restrict who can edit the counter. Treat it as a financial control: limit editing to a small group of administrators, keep them separate from people who create and approve invoices, and review that access as part of your periodic user access review. Confirm with your own environment which roles can open the naming series settings, since role assignments differ by deployment. Ask your implementation partner to document the access model before go-live, so the list of people allowed to change numbering is written down rather than inherited by accident.

Record every change in a change log outside the system as well as in your normal ticketing workflow. Note the date, the person who made the change, the series prefix, the old value, the new value, the reason, and the document that proves no collision exists at that point. Keep the log with the other evidence for your finance controls. If your organization operates under a formal compliance framework, confirm with your auditor how they expect counter changes to be evidenced, because the record matters as much as the change itself.

How gaps and duplicate numbers happen and how to prevent them

Gaps and duplicates in invoice numbering rarely come from one bad click. They usually trace back to a handful of recurring situations: deleted drafts, imports, shared series, manual counter edits and copied sites. Each card below names the cause, the prevention step and what to check after the change.

Cancelled and deleted drafts

A draft that is deleted before submission can leave its number unused, which shows up as a gap in the sequence. Cancelled submitted documents keep their number, so auditors will see a cancelled entry in place of a missing one. Set a written rule that drafts are reviewed and submitted or discarded in a defined window, and that only documents that never received a number may be removed. Verify the sequence in the register after each month end and explain every gap in writing.

Counter resets after data import

Importing invoices or orders with the Data Import tool can create records that carry numbers outside the current counter, or the import can be followed by a manual counter change to fit the imported range. The next native document may then reuse a number already in use. Decide before the import whether imported records keep their source numbers and how the series will continue. After the import, query for duplicate names and confirm the next value sits above the highest imported number.

Multiple companies sharing one series

When several companies in one ERPNext site point to the same naming series pattern, numbers from different legal entities interleave, and each entity sees gaps that belong to its neighbor. For companies that must each file a continuous sequence, the company-level naming approach keeps the counters separate. Confirm which pattern each company uses in its settings, and test one document per company before go-live so no entity inherits another's counter.

Manual edits to the counter

The current value of a series can be changed by hand, which is useful after a correction but dangerous when done casually. Setting it lower than the highest existing number guarantees duplicates on the next save, and setting it higher silently creates a gap. Restrict who holds the permission to edit series, require a change record with the old and new values, and check the highest existing name for that prefix before and after every change.

Copied sites carrying old counters

A staging or test site created from a production backup carries the same series counters. Documents created there can use numbers that production later issues, and if the copy is ever synchronized or its numbers reach customers, the conflict becomes visible to them. Reset or disable the series on non-production copies, and keep test data out of the live fiscal sequence. Verify by creating a test invoice on the copy and confirming its number does not collide with production.

Access control and audit considerations for document numbers

Document numbers are part of the financial record, so the people who can edit naming series and counters need the same scrutiny as the people who post entries. The cards below cover who should hold that access, how counter changes show up in logs, where finance and administrators should be separated, and what a restore does to the sequence. Confirm each point against your own roles and your auditor's expectations, because ERPNext configuration alone does not establish audit outcomes.

Limit who edits naming series

Changing a naming series or its current counter is an administrative action, and it should sit with a small set of named users rather than with every role that can create invoices. Review the ERPNext roles and permissions area to see which roles can open the Naming Series tool and the document DocTypes that store series settings. Document who holds that access and why, and review the list when staff change roles. A user who can both post invoices and reset the counter can renumber documents without anyone else noticing.

Trace counter changes in logs

Confirm which changes ERPNext records automatically, such as version history on documents and the Activity Log, and which it does not. A manual change to a series counter may or may not leave a traceable entry, depending on the version and how the change was made. Test the exact action in a non-production site and check what appears, who it is attributed to, and how long the log is kept. Plan an export of those logs on a schedule if your retention policy requires it.

Separate posting from numbering administration

Segregation of duties means the person who records financial transactions should not also control the rules that assign their identifiers. Map finance users who create and submit invoices against administrators who maintain naming series, and confirm that no single role covers both. Where a small team cannot split the roles, record a compensating review, such as a periodic check of counter values against the document register, and assign it to someone outside the posting activity. Your internal control framework should decide the exact split.

Restrict system and database access

Role permissions in the application do not stop someone with direct database or server access from changing a counter. Limit shell access on the bench host, restrict database credentials to the service accounts that need them, and keep administrator logins under individual accounts. Review who can run bench commands on production, because command-line changes may bypass the application layer and its logs. Treat this as part of your wider hosting access model rather than an ERPNext setting.

Check backup and restore effects

A restore returns the counter to its value at the backup point, so documents created after that point may be numbered again. Before go-live, test a restore on a copy of production and compare the last invoice number in the restored site with the last number in your external records, such as the bank feed or the tax filing. Document the reconciliation steps, the person who approves a restored sequence, and how to handle duplicate numbers that a restore creates. Confirm the recovery point objective with your backup owner.

Review numbering controls each release

Naming behavior and the screens that manage it can change between ERPNext releases. Both supported major versions receive frequent minor releases, so the access and log checks in this section should be repeated after each upgrade or patch cycle. Keep a short test script that changes a counter, confirms the log entry, and confirms the role restrictions, and run it in staging before each production change. Record the results with the release number so that the evidence matches the version you actually run.

Questions buyers ask about ERPNext document numbering

Can an internal team configure ERPNext naming series on its own?

Yes, for a single company with a simple numbering scheme, an internal team that knows ERPNext can usually set up naming series from the Naming Series tool and the document settings without custom code. The work is mostly configuration: defining the prefix pattern, choosing whether the year or company appears in the number, and setting the starting counter for each document type. It becomes harder when several companies share one site, when tax authorities require specific numbering, or when historical documents must keep their original numbers. In those cases the team should document the scheme before touching settings, and test it on a copy of the site first. Ask whether your staff has run a numbering change in a live ERPNext site before, because mistakes at this stage are hard to undo cleanly.

What makes ERPNext document numbering effort grow or shrink?

The main drivers are the number of companies, the number of document types that need their own series, the tax rules that dictate format, and how much migrated history must be kept. Each additional company usually adds a separate series per document type, which multiplies the design and testing work. Tax-rule numbering, such as the GST-related patterns ERPNext documents separately, adds validation against the rules your authority or advisers confirm. Migrated history adds the most risk: opening balances, old invoice numbers and the current counter must be reconciled so new documents do not collide with existing ones. A small single-company site with no migration is a short exercise. A multi-company group with several tax regimes and years of imported invoices is a substantial one, and the quote should reflect each of these factors separately.

Can ERPNext naming gaps be avoided completely?

Not in every case, so the honest answer is that gaps can be controlled and explained but not guaranteed away by settings alone. Gaps appear when a draft is created and then deleted, when a submitted document is cancelled, or when a counter is changed manually to a higher or lower value. Cancelled documents keep their numbers, which is usually the correct accounting behavior, but it means sequences look discontinuous to people who expect no holes. Duplicates are a different problem, and they usually come from manual counter edits or from migrated numbers that were not reflected in the series. Agree with your auditors which gaps are acceptable, define the procedure for cancellations and corrections, and restrict who may edit the current value. Those controls matter more than trying to eliminate every gap.

How long does a naming series setup take?

No researched duration is available for this work, so treat any figure you hear, including from us, as something to confirm against a written scope. Duration depends on the scope: the number of companies, the document types in use (sales invoices, purchase invoices, delivery notes, payment entries and others), the tax-rule patterns that must be reproduced, and whether a migration needs reconciliation. The schedule also depends on how quickly finance can approve each pattern and on how many test cycles are needed before go-live. Ask for the schedule to list each document type and company as a separate line, along with the review steps for finance and the test window. A schedule that shows only a total number of days hides the drivers you need to manage.

What does a naming series project need from finance and IT?

Finance owns the rules, and IT owns the environment and the change process. Finance should confirm the number format each document type must follow, the tax or regulatory requirements behind it, the handling of cancellations and corrections, and the acceptable gap policy. Finance should also sign off on the starting counters and on how migrated documents are numbered. IT should provide a non-production copy of the site with realistic data, access to the system with the right roles, and a change window for the final counter updates. IT also needs to restrict who can edit series and counters after go-live, and to record each change. Both teams should agree on a single owner for the numbering scheme, because numbering disputes usually surface after go-live.

When is a partner's help worth paying for with naming series?

A partner is most worth paying for when the scheme spans several companies, several tax regimes or a migration with years of history, because errors there are costly to correct and easy to miss in testing. It is also worth it when your team cannot dedicate time to design, testing and documentation, or when auditors will ask for evidence of how numbers were controlled. The value lies in a written scope that names each series, each rule and each test, so you can compare quotes on the same basis. Ask any provider how they will test cancellations, duplicates and counter changes, and what evidence they will hand over. DeployOpen implements and documents open-source platforms in your own infrastructure and prepares evidence for compliance assessments, but it does not issue audit reports or certifications, so the numbering design still needs your auditors' review.

Should naming series be changed after ERPNext goes live?

Changing a series after go-live is possible but should be rare, deliberate and recorded. Once documents have been submitted under a pattern, changing the format does not renumber existing records, so old and new formats coexist in reports and exports. Changing the current counter upward is generally safer than lowering it, because lowering it can produce duplicates with documents already in the system. Any counter change should be tested on a copy, approved by finance, and logged with the reason and the user who made it. Restrict the permission to edit series to a small group, and review those changes at period close. Plan for these changes in the design phase, because a scheme that needs frequent edits was probably not designed around your real document flow.

Does ERPNext numbering need to meet tax rules such as GST?

ERPNext documents a naming series approach that follows GST rules, so for businesses subject to those rules the numbering pattern should be checked against the requirements that apply to you. Confirm the exact format, sequence and uniqueness rules with your tax adviser or the relevant authority, because the software documentation describes the mechanism and not your legal obligation. Also confirm how credit notes, cancellations and multiple registrations within one company are numbered. Once the rules are confirmed, record them in the design document and link each series to the rule it satisfies. That record is one of the artifacts your auditors or tax reviewers will ask for.

How DeployOpen works on this

DeployOpen starts by writing down how your company numbers invoices, delivery notes and other documents, then configures ERPNext naming series to match that design. Engagements are fixed-scope, so the numbering rules, tests and handover items are agreed in writing before any configuration changes are made.

How we scope

Inventory every document type that needs a naming series, including invoices, credit notes, delivery notes and payments.
Agree the prefix, year and company pattern for each series in writing before configuration starts.
Confirm which tax rules, such as GST-related numbering, apply and which companies share or separate their sequences.

How we build

Configure company-wise and tax-specific naming series in a test environment that mirrors your production setup.
Test rollover at year end, gap behavior after cancelled documents, and the effect of changing a current counter value.
Record each series setting so the configuration can be reviewed and reproduced on any environment.

How we hand over

Deliver a written register of every naming series, its pattern, owner and the people allowed to change its current value.
Train finance and operations staff on cancelling, amending and correcting documents without breaking sequence rules.
Document the change procedure your team should follow before altering any series in production.

How we support

Offer ongoing support and upgrade checks as a retainer if your team wants help after go-live.
Review naming series again when you add a company, change tax rules or upgrade ERPNext versions.
Confirm with your auditors and tax advisers which numbering evidence they expect before the design is signed off.

ERPNext naming series for invoices and documents