Numbering for a Custom Transaction Type
All NetSuite transactions are autonumbered. Autonumbering helps you determine the sequence in which transactions were entered. Numbering also helps you find transaction instances.
All transaction types, including custom transaction types, use document numbers and transaction numbers.
Document Numbers
Numbers for document types are external numbers, such as the number that an external vendor uses on a bill, or account-based numbers such as a check number. Document numbers can also store a number for type-based transactions. Type-based numbers are available as custom columns in searches and lists.
The Document Numbers subtab is not relevant for Purchase custom transaction types. Purchase custom transactions use external numbering, similar to that used for vendor bills, where users specify the number themselves. If an automated numbering sequence is needed for a purchase custom transaction type, use Transaction Numbers.
For external numbering sequences such as vendor bill, the document number is unique for each vendor, which permits the same document number to be assigned to more than one vendor. NetSuite prevents a vendor from having a duplicated document number on the same transaction type.
Document numbers are useful in transactions where the account field has special significance. These types of transactions must have numbering that is unique to the account named on the transaction. For example, if five individual transactions are drawing money from the same account, then their document numbers are part of a single sequence even if they are not the same types.
Document numbers can also be required because of government numbering requirements. In those cases, NetSuite customers may want to use the document numbering system to meet the government requirements and transaction numbering to satisfy their own internal needs and requirements.
Transaction Numbers
Autogenerated numbers are internal, gapless numbers that cannot be overwritten and are generated when a transaction record is saved. These internal numbers are generated for each transaction type.
If autogenerated numbering is not set up in your account, transaction numbers begin at 1. For more information about the records and transactions available for autonumbering, see Records and Transactions Available for Auto-Numbering.
Historical transaction records can have duplicate internal numbering. NetSuite prohibits overwriting transaction type numbering sequences but permits the overwriting of document numbers. NetSuite does not renumber historical internal transaction numbers.
For more information about setting up autogenerated document numbers and transaction numbers, see Set Auto-Generated Numbers.
For each of your custom transaction types, you can customize the way these entry numbers are created. These options are described in Components of a Custom Transaction Type’s Entry Number. You may want to review these options before configuring numbering.
The process of configuring numbering includes the following tasks:
-
Defining Numbering for a Custom Transaction Type – Set the main values that define your numbering scheme.
-
Defining Numbering Preferences for Subsidiaries and Locations – (Optional) Tie some aspect of numbering to subsidiary or location.
Related Topics
- Creating and Editing Custom Transaction Types
- Custom Transaction Styles Overview
- Creating a Custom Transaction Type
- Editing a Custom Transaction Type
- Locked Custom Transaction Types
- Custom Transaction Type Classification Fields
- Custom Fields in Custom Transaction Types
- Account Field Setup for Custom Transaction Types
- Statuses for a Custom Transaction Type
- Creating Links for a Custom Transaction Type
- Adding Custom Forms for a Custom Transaction Type
- Permissions for Custom Transaction Instances
- Adding Translations for a Custom Transaction Type