Every document type you issue needs a numbering series before it can be posted. Numbering is configured per branch, so two branches can run independent sequences.
The fields
| Field | What it does |
|---|---|
| Description | Names the series, e.g. “Sales invoice — Thamel branch”. |
| Prefix / Suffix | Fixed text around the number, e.g. INV- and /82-83. |
| Start no. / End no. | The range the series may use. Posting stops when the end number is reached. |
| Current no. | Where the series has reached. Read this rather than guessing. |
| Body length / Total length | How wide the numeric part and the whole number are. |
| Fill character / Is fill | Whether to pad the number, and with what — usually a zero, giving INV-000148. |
| Start date / End date | The period the series is valid for, in Bikram Sambat. |
| Is default | Which series is used when a user does not pick one. |
| Branch | Which branch the series belongs to. |
Practical advice
- Set the date range to match your fiscal year, and create the next year’s series before the year turns.
- Give the end number plenty of headroom. Running out mid-period blocks posting.
- Mark exactly one series per document type per branch as default.
- Do not reuse a prefix across branches — it makes documents ambiguous in consolidated reports.
Did this answer your question? If not, our support team can look at your actual configuration.
Contact support