Test document numbering before the accounting system issues real invoices

A transaction can have a draft number, a posted document number, a supplier's reference and an integration identifier. Treating them as interchangeable creates confusion during migration and support. Before choosing a numbering pattern, ask the vendor to show which identifier serves each purpose and which one appears on the document sent outside the company.

Prepare a simple identifier map for the document types in scope. Include sales invoices, credit notes, purchase invoices and journals where relevant. State whether the number is unique within one entity, across the group or within a particular document class. The system's actual uniqueness rule should match the company's operating requirement.

Business Central's documentation describes number series assigned by record or document type, series lines with starting dates and configurable manual numbering. These are useful examples of settings a buyer should inspect. A sequence is a configured process, not merely a prefix printed on a PDF.

Have the accounting and legal owners identify any applicable local invoice-numbering requirements. This software test does not establish a universal rule about gaps or annual resets. It establishes whether the chosen product can implement the requirements that actually apply to the company's documents.

Create a draft, save it, close it and reopen it. Note when the system first assigns an identifier and whether that identifier changes on posting or issuance. Then cancel a separate draft using the supported procedure and inspect what remains in the sequence history.

Cause a controlled validation failure before posting. For example, use an intentionally missing required field in the test environment. Correct the error and retry. Determine whether the failed attempt reserved a number, released it or produced another visible state that a reviewer can explain.

Open two sessions and create the same type of document at nearly the same time. The software should manage allocation of identifiers through its supported mechanism. Inspect the resulting records rather than assuming that a number displayed on an unsaved draft has already been reserved exclusively.

Ask what happens when a user abandons a browser session after requesting a new document. The answer should identify the record or reservation that remains and the supported cleanup process. A buyer needs an explanation for missing-looking numbers without resorting to undocumented edits.

Use two test entities that both issue a document numbered 1001. Check group search, exports, customer statements and integrations. If the chosen design permits the same local number, downstream systems must also carry enough context to distinguish the two records.

Create an invoice and a credit note with similar references. Ask the user to identify their type and entity from each output. A globally unique internal database key does not help a customer or accountant if the visible document references are confusing.

Try a manually entered number already used in the relevant scope. Record whether the application blocks it, warns or permits it under specific conditions. The company's policy should determine who can use manual numbering and how exceptions are reviewed.

Include long prefixes, leading zeros and ordinary punctuation used by the business. Trace the value through the ledger, printed document, export and connected application. An identifier that survives in the source screen can still be shortened or reformatted elsewhere.

If the approved design changes numbering at a year boundary, test documents dated just before and after that boundary. Ask which date selects the series: creation, document, posting or another field. A late-entered prior-year document should follow a deliberate rule.

Supply the last number used in the old system and the intended first number in the new one. Have the implementer show how the opening range is configured and verified. Test an imported historical document alongside a newly issued one to expose a collision before go-live.

Consider work still in progress at cutover. Drafts created in the old system may be completed after new-system issuance begins. Decide which system will issue them and how their references remain traceable. An unused range alone does not settle ownership of those drafts.

Test what happens near the end of a configured range. The user should receive a clear, actionable outcome before ordinary work stops. Ask who monitors capacity and who can extend a range without changing the meaning of previously issued identifiers.

Issue a test invoice, then correct it using the product's supported credit or reversal workflow. Inspect the references on the original, correction and replacement. A recipient should be able to understand the relationship, and finance should be able to retrieve the entire chain.

Import the same supplier invoice reference for two different suppliers. Then import it twice for the same supplier under the controlled test. The system may use different rules for external references and internally assigned numbers; document those rules rather than assuming every duplicate-looking string is an error.

Retry a supported integration submission and inspect whether it creates a second business document. A unique number on each newly created record does not prevent duplicate invoices from being generated. The integration's repeat-submission controls need their own explanation alongside the numbering design.

Check audit and support exports. The file should retain the identifier needed to find the original record, its entity and any separate external reference. Avoid a mapping that exports only a convenient display number when support staff need another key to investigate a problem.

Prefer patterns the company's users and connected systems can handle consistently. Extra letters encoding every business attribute can make a number difficult to maintain when the organization changes. Store descriptive attributes in their intended fields unless an approved document requirement calls for them in the identifier.

Record series ownership, manual-entry permissions, boundary dates and the treatment of canceled or failed drafts. Keep an example of each accepted lifecycle with the implementation materials. The administrator should be able to explain a sequence gap or correction from supported records.

Accept the configuration after concurrent creation, cutover, correction and export cases have been demonstrated. The result should be a durable reference system that distinguishes documents throughout their lives and remains understandable to the people who receive and investigate them.