Number ranges for every master and transaction record

Every record known by a code or a number now has a range of its own, by default, in every company — new ones included. Platform › Configuration › Core Settings › Number Ranges lists them by module, filters master and transaction data, says how each is numbered (System generated, Manually entered or Either) and refuses a next number at or below one already used.

Before this release some records were numbered outside any range — a converted lead, an approved supplier application, card mandates, automation results — and many master records had no range at all. Now every master and transaction record has a default range, and creating, copying and importing a record all follow it.

اسے کہاں تلاش کرنا ہے۔

Platform › Configuration › Core Settings › Number Ranges. Only an administrator can open and change it.

What the screen shows

• The ranges grouped by module — every module, from Accounting to Agentic AI, Platform and Administration — each heading with its count; master data before transaction data inside each module.
• Two filters: Module (All modules or one) and Data (All, Master data, Transaction data). The pill beside the title says how many of all the ranges are shown.
• Columns: Document, Key, Module, Data, Numbering, Format (what the next number will look like, for example <PO-000123>), Next, Reset, and Edit.

How a range numbers: the three modes

The defaults: codes people already type today (an item number, a customer code) stay Manually entered, so the code stays a required field — Save, Copy and an import preview say “<Code> is required” when it is empty; record and document numbers are Either.

Change a range

1. Choose Edit on the range’s row.
2. Change Document name, Module, Data, Numbering, Prefix, Suffix, Digits (how many digits, padded with zeros) or Next number. The form shows Next document will be <prefix-000001>.
3. Optionally set Minimum and Maximum, and Reset: Never, Every year or Every month.
4. Untick Active to stop using the range. Save.

The guard against reusing a number

• While you edit, the form shows the Highest number already used with this prefix.
• A Next number at or below it is marked at once — “Next number must be above the highest number already used (<120>).” — and Save is not offered; the API refuses it too: “Next number must be above <120>: <PO-000120> is already used. Set it to <121> or higher.”
• It is judged on the prefix and suffix being saved, so moving to a prefix whose numbers already run further is caught too. A range that resets every year or month restarts by design and is not judged.
• Next number must be a whole number of 1 or more.

Every company has every range

• When the release was installed, every existing company was given every default range, each counter set past the highest number the company has already used, so no number is issued twice.
• A new company is given the product’s default ranges when it is created, each starting at 1 — its first purchase order is PO-…1.
• Automation results (AUT-) and intake items (INT-), converted-lead accounts and approved supplier applications are now numbered from their ranges too.
• New range adds one for a document of your own: Document key (upper-case letters, digits and underscores, cannot be changed later) and Document name. A key that already has a range is refused.
• India’s statutory series (EPF runs, gratuity, GSTR-1, GSTR-3B, TDS returns, UPI) and the payment engine range are given to Indian companies only, under India. Standard identifiers (currency, unit, HSN codes), numbers issued by others (certificates, cheques, e-way bills) and line numbers are deliberately not ranged.