1.7 Numbering Configuration (Invoices, Quotes, Returns) in BEST POS
Summary
This guide shows how to configure number series for invoices, quotes, and returns in BEST POS: prefix/suffix, zero-padding, per-store counters, periodic resets (yearly/monthly), and collision checks. It includes compliance and migration best practices.
Step-by-step Instructions
1) Open the number series settings
- Go to BackOffice > Settings > Documents > Numbering.
- Select the document type: Invoice, Quote, Return (or Credit Note).
- Choose the scope: Company or per Store if each branch needs its own sequence.
- Prefix: text marker (e.g., INV-, Q-, RTN-) or dynamic codes (store ST01-, year 2025-).
- Number length: pick zero-padding (e.g., 6 → 000123).
- Suffix: optional (e.g., -A for special series).
- Example: INV-ST01- + 000001 → INV-ST01-000001.
3) Start, increment, and reset
- Initial counter: set the starting value (e.g., 1 or a carry-over from a legacy system).
- Increment: standard = +1 (recommended for uniqueness and auditability).
- Reset: enable Yearly or Monthly if needed (e.g., INV-2025-000001 each year).
- Per-store scope: each store has an isolated counter when enabled.
4) Prevent collisions and test
- Click Preview to see the next generated numbers (by type and store).
- Use Uniqueness Check to detect conflicts with existing (imported/migrated) documents.
- Create a test document (draft quote) and delete it after confirming the format.
- Lock the configuration (read-only) after validation to avoid changes in production.
5) Legacy carry-over / migration
- Identify the last issued number by type and by store.
- Create prefixes to distinguish legacy vs new series (e.g., INV2-).
- Set the initial counter to the next unused number.
- Import legacy documents as read-only history (not in the active series) if required.
6) Compliance and best practices
- Ensure a continuous sequence (no duplicates, no rollback).
- Keep audit logs of changes (who, when, what).
- Avoid embedding sensitive data in numbers (e.g., full customer IDs).
- Document the internal policy (resets, per-store prefixes, handling voids).
Fixes and FAQs
- Duplicate detected: run Uniqueness Check, adjust counter or prefix, then retest.
- Unexpected format: verify prefix/suffix, length, and scope (company vs store).
- Reset not applied: check the rule (yearly/monthly) and system date/time; correct and simulate.
- Production change: schedule off-hours, back up, and lock after validation.
Popular Articles
Sell by Department in BEST POS (Retail)
Summary This article explains how to record a sale by department in BEST POS, with or without a scale, while respecting HALO limits. It includes useful checks (subtotal, tender) and quick recovery actions if a keying error occurs. No screenshots are ...
Sell by PLU (direct, manual, barcode) in BEST POS (Retail)
Summary This article explains three ways to ring sales by PLU in BEST POS: via the PLU key (direct), by manually keying the code, and using a barcode scanner. It also covers repeating the last item and handling weight-based PLUs (scale). No ...
Price Levels (P1–P4) and Price Override in BEST POS (Retail)
Summary This guide shows how to sell using price levels P1–P4 (forced price) and how to override the item price at the point of sale. It also covers quick price maintenance for price #1–#4 at the register, with access and compliance notes. ...
Apply a discount (closed / open) in BEST POS (retail)
Summary This article explains how to give a discount in BEST POS: closed discount (preset value) and open discount (free-entered value, % or $), either on a single line or on the subtotal. It also covers access controls (HALO, manager approval) and ...
Subtotal and Customer Display in BEST POS (Retail)
Summary This article explains how to show the subtotal at any time during a sale without finalizing it, and how to ensure the customer display reflects amounts correctly. Steps cover discounts, taxes and fixes—no screenshots needed; labels and paths ...