Field descriptions: Order Entry transaction definitions

Template name

The name for the transaction definition. This name appears in the user interface. After you save a transaction definition, you cannot change the template name.

Description

A meaningful description of the transaction definition. The description appears in the transaction definition list.

Template type

Determines whether certain fields appear on the transaction (for example, Expiration date versus Ship Date).

Options are: Quote, Order, List, Invoice, Adjustment, Other

Other areas in Sage Intacct where you use the Template type include:

• You can filter the Sales Analysis report by Template type.
• You associate document templates (used for printed output) to transactions by Template type. Learn more about document templates.
• In Salesforce integrations, the integration groups the related list of Sage Intacct objects by transaction definition Template type.
• In Avalara AvaTax integrations, the integration uses the transaction definition Template type to determine if a transaction is positive or negative.

For sales order transactions to appear in the Customer Backlog report, select Order as the template type.

Workflow category

Associates the transaction with the appropriate icon on the Overview page and with the applicable transaction menu grouping in the Order Entry menu. Options are: Quote, Order, Shipping, Invoice, Return.

For sales order transactions to appear in the Customer Backlog report, select Order as the workflow category.

Reporting category

For use with Interactive Custom Report Writer or Interactive Visual Explorer subscriptions only.

Select a reporting category that best reflects the purpose of this transaction definition so that you can group similar documents when building reports. This lets you define filters using one or more reporting categories instead of having to specify each desired transaction definition name.

For example, say that your company has different transaction definitions of Template type = Invoice for regular sales invoices and for invoices that are used to manage revenue recognition. You can specify the Reporting category of "Invoice" for the regular sales invoices and "Rev Rec Activation" for the invoices used to manage revenue recognition.

When building a report on the Order entry transaction detail object, add a filter for Related Objects > Order entry transaction > Transaction definition > Reporting category. In this example, you could choose to display details only for the "Invoice" reporting category.

If you edit a transaction definition to assign a reporting category after the transaction definition has been in use, all transactions created from that transaction definition will be updated to use the selected reporting category.

The reporting categories are standardized across all Sage Intacct tenants and cannot be edited or customized. Follow your business process to determine which reporting category to use for each transaction definition.

Status

• Active: The transaction definition is available for use.
• Inactive: The transaction definition is not available for use.

The status of system-generated transaction definitions cannot be modified.

Enable change order workflow

Enable this option to indicate whether the transaction definition's document type is a source or change document.

Create transaction definitions for your source documents and separate transaction definitions for each change document that you intend to use.

You can enable change management on a transaction definition with existing change documents (transactions), but you cannot disable change management if a source document has existing change documents (transactions).

Learn more about change management.

Numbering sequence

Select the numbering sequence to use to automatically number transactions. To add a new sequence, select Add in the dropdown list.

Leave this field blank to number transactions manually, or if you want converted transactions to inherit the source document number.

Preserve sequence numbers

Ensures that numbers are never skipped. Enabling this option can affect performance when a large volume of transactions is entered at the same time.

Inherit source document number

With this option selected, the document number from the previously converted transaction is assigned to the new transaction. For example, if you convert sales order SO-001 into a OE sales invoice, theOE sales invoice number will be SO-001.

Inventory total, Maintain, and Add or subtract

Use the table to specify the inventory running total that will be affected by the transaction, whether to track the quantity, value, or both, and whether that amount will increase or decrease when the user saves the transaction.

If you define this transaction definition to affect ONHAND Value or Quantity & Value, add at least one debit and credit account pair to the COGS account mapping table on the Posting configuration tab to save the transaction definition.

Best practice: Configure the OE sales invoice to affect ONHAND Quantity & Value and handle all the GL posting for inventory COGS, AR, and revenue. Avoid having separate transaction definitions affect ONHAND Quantity and ONHAND Value in the same workflow.

Learn more about inventory totals.

Warn user if item on hand quantity falls below 0

Alerts the user if the quantity needed is greater than the ONHAND total in the selected warehouse. The warning also shows the ONORDER and ONHOLD totals. The warning appears when the user tabs out of the Quantity field in the transaction.

Enable inventory items for reserving and picking

Select to allow users to commit item quantities when creating sales orders. Committed quantities are no longer available for other orders.

• Reserving sets aside inventory that is still on the shelf.

• Picking allocates inventory that has been taken off the shelf and assigned to the order. This option helps ensure that high priority sales orders can be filled and processed on time.

Warehouse selection method

Determines how warehouses are presented to the user in the warehouse dropdown list in the transaction. Options are:

• Sort by ID
• Sort by name
• Warehouse with available inventory
• Use the default warehouse

Default warehouse

Appears only if the Warehouse selection method is Use the default warehouse. Select the default warehouse from the dropdown menu. A user's Default warehouse setting in their user preferences overrides this selection.

Enable costing for non-inventoried items

This field appears only if your company is not subscribed to Inventory Control. It's selectable when Transaction posting is set to Accounts Receivable.

Allows you to enter COGS journal entries for non-inventoried items. If you select this field, enter the applicable GL accounts in the COGS account mapping table on the Posting configuration tab.

Then identify the Inventory journal to which this transaction definition posts in the Documents configuration tab of the Configure Order Entry page.

Transaction posting

Select one of the following options:

• Accounts Receivable: The transaction posts to the AR subledger. Intacctcreates a summary AR sales invoice in Accounts Receivable and affects the General Ledger.
• General Ledger: The transaction posts directly to the General Ledger.

  The most common case for posting directly to the GL is when you are using a transaction definition to activate the revenue recognition schedule. Learn more about setting up revenue recognition activation transaction definitions.

• Do not post: The transaction post process will not create a GL entry and will ignore any mapping entries in any of the Posting configuration tables.

If you select a posting option, enter at least one debit and credit account pair in the Account mapping table in the Posting configuration tab to save the transaction definition.

If Transaction posting is not Do not post and a user selects an item in a transaction that does not have a mapping entry in the applicable account mapping table, the user receives an error and can't post the transaction.

Enable additional posting

Use this option to enable an additional GL entry posting on this transaction definition. When this field is selected, the Additional GL posting account mapping table is available on the Posting configuration tab.

This option is typically used when a prior transaction in the workflow posts to the GL in a user-defined book. Depending on the GL account mapping you enter in the Additional GL posting account mapping table, you can reverse or reclassify the entry posted in the prior transaction. The amount used for additional GL posting comes from the transaction that's configured for additional posting, not from the source transaction.

For examples of how to use this option, see Track sales commitments using user-defined books.

Enable revenue recognition

This field appears only if your company is subscribed Revenue Management and applicable only to Order Entry revenue recognition.

Options are:

• Post: The revenue recognition posts to the accounts specified in the Posting configuration tab. You can only set this field to Post if the Transaction posting field is set to Accounts Receivable or General Ledger.
• Display only: The Rev rec template, Start date, and End date fields appear on the transaction. The user can select a revenue recognition template and enter start and end dates, but no revenue recognition schedule is generated upon transaction save. For example, you might want to select Display only for a sales order. The user could select the Rev Rec template and set the Start and End dates in the sales order. When the user converts the sales order into a OE sales invoice, the Rev Rec template, Start Date, and End Date would be populated in the OE sales invoice.
• Do not enable: Revenue recognition does not apply to this transaction.

Learn more about Revenue Management.

Enable payment processing

When this option is set to true, the user can apply payments to an invoice in Order Entry.

To enable payment processing, the Template type must be set to Invoice and Transaction posting must be set to Accounts Receivable.

Enable subtotals

Allows you to specify standard subtotals, such as tax or a discount, for this transaction. When you select this field, a table appears in which you must add at least one subtotal.

Subtotal table

This table appears when Enable subtotals is set to true.

Description

Enter a text description of the subtotal. Each subtotal description must be unique.

Subtotal type

Options are: Discount or Charge.

Applied to line

Enter the subtotal line number to which the subtotal will apply. Intacct treats the initial subtotal line as line number 0. The first defined subtotal from the transaction definition is line number 1, the second defined subtotal is line number 2, and so on.

This field does not appear if Enable line-level Simple Tax is selected.

The value of Applied to line is implicitly assumed to be 0. Taxes, all other charges, and discounts are computed at the line level.

Value type

Options are: Amount or Percent.

For a tax subtotal, select Percent. Tax subtotals only support the Percent value type.

Value

Enter a default value for the subtotal.

• If Value type is Amount, enter the amount of the subtotal. For example, enter 250.
• If Value type is Percent, enter a percentage as a whole number. For example, enter 10 for 10%.

Users can override the default subtotal value in the transaction.

Debit or credit

Indicate whether the subtotal will debit or credit the corresponding GL account and GL offset account.

GL account

Select the GL account to which the subtotal will post. Transactions posted to a cash/bank GL account do not appear during reconciliation.

GL offset account

Select the offset GL account to which the subtotal will post. This column is only applicable if you are using advanced workflows.

Department

Optional. Select a default department for the subtotal. This field does not appear at the top level.

Location

Optional. Select a default location for the subtotal. This field does not appear at the top level.

Is tax

Flags the subtotal as a tax. When the transaction posts, the tax will post separately based on the items in the transaction.

Set this flag to true for tax subtotal lines if your organization uses Simple Tax, Advanced Tax, or Avalara AvaTax.

Select for Avalara

Select this field if the subtotal line item applies to AvaTax.

This field appears only if your company uses the Avalara AvaTax integration.

Department and Location

If the Department and/or Location fields are selected, expect the following behavior:

• The Department and/or Location fields will appear on the transaction and the user can select the applicable values
• If the transaction definition has posting set to AR or GL, Intacct ignores any Department and/or Location selected in the Posting Configuration tab and presents blank Department and/or Location fields on the transaction.

If the Department and/or Location fields are not selected, expect the following behavior:

• The Department and/or Location fields will not appear on the transaction.
• If the transaction definition has posting set to AR or GL, the Department and/or Location will default to the Department and/or Location values selected for the applicable item GL group in the Posting Configuration tab. The values will appear in the applicable subledger transaction or journal entry.

These fields do not appear at the top level in a multi-entity company.

Line-item tax

Whether the user can override whether an item is taxable. This field becomes selectable when Enable subtotals = true.

The Taxable field for an item on the transaction is only editable if the Ship to contact for the selected customer is flagged as Taxable.

Line-item price

Whether the user can override the price proposed by Intacct. If set to true, the Price field on the transaction becomes editable.

This field is automatically checked and becomes read-only when Track line-item discount or surcharge is selected.

Track line-item discount or surcharge

Whether the user can discount a line item while Intacct retains the proposed price on the transaction. Displays a Discount percent field in the transaction Entries section that allows the user to enter a percentage by which to discount the line item. The price being discounted appears as read-only in a Suggested price field. The discounted price appears in the Price field.

Enable for Contracts

Whether the transaction definition can be used for contract invoices. This field becomes selectable when Track line-item discount or surcharge is selected. If you want to use this transaction definition for invoices generated from contracts, you must select this field.

This field is only applicable if your company is subscribed to Contracts. This field is only editable if Default decimal places is set to 10 in the Configure Order Entry page.

Require notes for discounts and surcharges

Whether the user has to complete the Discount or surcharge notes field for the line item being discounted before saving the transaction. This field becomes selectable when Track line-item discount or surcharge is selected.

Exchange rate and exchange rate type

Whether the user can edit the Exchange rate and/or Exchange rate type fields on the transaction.

Exchange rate type

If you do not want to use the default Intacct Daily Rate, select a custom exchange rate type.

Display base currency

Whether the transaction amounts are displayed in both base currency and transaction currency.

The following fields display amounts in the currency selected as the Txn currency on a transaction: Price, Extended price, Transaction value, and Transaction total.

When Display base currency is selected, the transaction currency amount fields appear and the following fields also appear: BasepPrice, Extended base price, Base value, and Base total. These additional fields display the amounts in the company's base currency.

Enable payment processing

Allows you to set a recurring template to automatically charge a credit card when an AR sales invoice is generated.

Enable retainage

Allows you to enable retainage for AR sales invoices.

Enable project contract billing

Select this checkbox to display the Project contract billing section on the Transaction tab. This checkbox also displays the Project contract billing details tab on Order Entry Contract AR sales invoices.

Display original contract project billing amount fields

Select this checkbox to display the Billing summary and Project change order summary fields in the Project contract billing section. This checkbox also displays additional fields in the Entries section on the Transaction tab of Order Entry Contract AR sales invoices.

This option is available only when you also select the Enable project contract billing checkbox.

Can be converted from

Use the dropdown list to select a transaction definition from which this transaction can be converted.

For example, if a certain OE sales invoice is always created from a sales order, select the sales order in this table in the applicable OE sales invoice transaction definition.

If this transaction definition is the first step in your workflow, leave this table blank.

Select Add to add rows to this table to accommodate multiple transaction definitions. Select the trash can icon to remove a row.

Enable line-item conversion

Allows users to convert a sales transaction by line item into a scheduled recurring transaction. For example, say there's a sales order with the following three line items: hardware, software license, and a maintenance agreement. With line item conversion, the user could potentially do the following:

1. Bill the hardware and recognize revenue immediately.

2. Book the software license as a 24-month contract, bill it entirely, and recognize revenue over 24 months.

3. Book the maintenance agreement as a 12-month contract, set up installment invoicing over 12 months using a recurring schedule, and recognize revenue when each installment is billed.

Partial conversion handling

Indicates how the system processes transactions that are partially completed. Options are:

• Leave transaction open: When the user converts the transaction to another transaction type, the system leaves the original transaction open until the all items are completed.
• Close original and create back order: When the user converts this transaction to another transaction type and enters an item quantity that's less than the original transaction quantity, the system closes the original transaction and creates a new transaction for the remaining item quantity.
• Close transaction: When the user converts this transaction to another transaction type, the system closes this transaction regardless of whether the transaction is complete.

Learn more about partial transaction conversion.

Enable renewals

Allows users to set up contract renewals for transaction line items and allows this transaction type to be selected in a contract renewal instruction set. Options are:

• Generate: Sets up the renewal when the transaction posts. The renewal does not start until the specified date in the renewal instruction set.
• Display renewal fields only: Displays the Renewal template field in the transaction and allows the user to select a renewal instruction set.
• Do not enable: Contract renewals do not apply to this transaction.

Select a Numbering sequence for this transaction definition if you want to enable renewals.

Learn more about setting up renewals in Order Entry.

Initial price list

If you are using layered price lists, this indicates the first price list the system will evaluate when determining a suggested transaction price. Use the dropdown list to select an initial price list if desired. Learn more about how price lists are evaluated.

Special price list

If you are using layered price lists, this indicates a special price list (for example, a discounted price list or seasonal price list). The special price list takes precedence over the Initial price list. Use the dropdown list to select a special price list if desired.

Price list to update

The price list that will be updated when a user saves a transaction. For example, in the 'Regular price list', a widget has a price of £100. A user creates a transaction and enters £90 for a widget. If Price list to update = Regular price list, the price list will now show £90 for widgets. If Price list to update = blank, the Regular price list will still show £100 for widgets. Use the dropdown list to select a price list to update if desired.

Typically this field is left blank.

Enforce credit limit

Select this option to be notified when a transaction total will exceed a customer's allowable credit limit in transactions created from this template. You can choose to ignore the warning and post the transaction. Note: Ignored credit limit warnings are not tracked in the audit trail. For example, you might set Enforce credit limit to false for sales orders and set Enforce credit limit to true for OE sales invoices.

Default AR term

Select a default Accounts Receivable term from the dropdown list. Select a default Accounts Payable term from the dropdown list. If you select a default term, the system autofills the Expiration date for quotes and the Date due for invoices based on the selected term. The user can override those dates as desired.

Default Shipping method

The default for how goods in the transaction are shipped to the customer. If a shipping method is specified for a customer, the customer shipping method takes precedence as the default in the transaction.

Printed document template

Use the dropdown list to select a printed document template to use as the default for printed output (PDFs). Learn more about printed document templates. Intacct strongly recommends that you use a document template.

Enable display of actual billings on printed or emailed invoices

Select to include the actual billings (billed-to-date amounts) of a project within the Document template selected above using the Intacct Word Merge tool. The actual billings amount is determined by the Actual Billings field on the Project summary tab of the Project Information page.

The amount of the Actual Billings field on the invoice includes what was previously billed and the amount of the current invoice.

Optional default text

If you do not select a Document template, enter any text that you want to appear on every document printed from this transaction.

Contact title

In the Contact column change the Bill-to and/or Ship-to labels. This changes the labels on the transaction and on the printed document. The default contacts displayed on the transaction are still the contacts designated as the Bill-to and Ship-to contacts on the associated customer record.

Show on print

Whether to display the Contact title label on the printed document (PDF) when you use a standard template.

Allow editing

Whether to allow the user to select a contact other than the default Bill-to or Ship-to contact in the transaction.

If you select Enable ship-to contact at the line level in the Configure Order Entry page, you can select Allow editing for all applicable transaction definitions to allow users to change the Ship to field on sales transactions.

Item GL group, Warehouse, and Customer GL group

The Item GL group, Warehouse, and Customer GL group together form the criteria set for the account mapping. For example, you could have the Maintenance item GL group, Warehouse 13, and Hardware Customer GL group mapped to a COGS account and Inventory account, and the Maintenance item GL group, Warehouse 13, and Software Customer GL group mapped to a different COGS account and Inventory account.

Debit or credit

Choose whether to debit or credit the account.

GL account

Use the GL account selection list to select the applicable account to which this transaction posts for the mapped criteria set. Transactions posted to a Cash/Bank account do not appear during reconciliation.

The Debit account is usually the COGS account.

The Credit account is usually the Inventory account.

Department

Use the Department selection list to select a default department against which the line item will be recorded. This field is only applicable if Department in the User overrides section is not selected. This field is not applicable at the top level.

Location

Use the Location selection list to select a default location against which the line item will be recorded. This field is only applicable if Location in the User overrides section is not selected. This field is not applicable at the top level.

Item GL group and Warehouse

The Item GL group and Warehouse together form the criteria set for the account mapping. For example, you could have the Maintenance item GL group and Warehouse 13 mapped to a GL account and offset account, and the Software item GL group and Warehouse 13 mapped to a different GL account and offset account.

Debit or credit

Choose whether to debit or credit the account.

GL account

Use the GL account selection list to select the applicable account to which this transaction posts for the mapped criteria set. Transactions posted to a Cash/Bank account do not appear during reconciliation.

Whether or not the corresponding GL account is an offset account. Each Item GL group and Warehouse criteria set must have one offset account.

Department

Use the Department selection list to select a default department against which the line item will be recorded. If you select Department in the User overrides section, the user can select a different department in the transaction. This field is not applicable at the top level entity.

Location

Use the Location selection list to select a default location against which the line item will be recorded. If you select Location in the User overrides section, the user can select a different location in the transaction. This field is not applicable at the top level entity.

Item GL group, Warehouse, Customer GL group, and Supplier GL group

The Item GL group, Warehouse, and Customer GL group together form the criteria set for the account mapping. For example, you could have the Maintenance item GL group, Warehouse 13, and Hardware Customer GL group mapped to a GL account and offset account, and the Maintenance item GL group, Warehouse 13, and Software Customer GL group mapped to a different GL account and offset account.

Debit or credit

Choose whether to debit or credit the account.

GL account

Use the GL account selection list to select the applicable account to which this transaction posts for the mapped criteria set. Transactions posted to a Cash/Bank account do not appear during reconciliation.

Is offset?

Whether the corresponding GL account is an offset account. Each Item GL group, Warehouse, and Customer GL group criteria set must have one offset account.

Department

Use the Department selection list to select a default department against which the line item will be recorded. If you select Department in the User overrides section, the user can select a different department in the transaction. This field is not applicable at the top level entity.

Location

Use the Location selection list to select a default location against which the line item will be recorded. If you select Location in the User overrides section, the user can select a different location in the transaction. This field is not applicable at the top level entity.

Edit policy

Sets the edit permission for this transaction type. Options are:

• No edit: The user cannot edit this transaction after it is created, unless it is in draft state.
• Before printing: The user can edit this transaction until it has been printed to PDF. After it has been printed, the transaction cannot be edited.
• Draft only: The user can edit this transaction until it has been posted. After it has been posted, the transaction cannot be edited.
• All: The user can edit this transaction as allowed by the transaction's condition. See Editing a sales transaction for editing restrictions.

Allow edit of customer

Allows users to change the customer in Draft or Pending transactions under the following conditions:

• The transaction has not been converted to another transaction.
• If the transaction posts to the GL or to Accounts Receivable, the transaction date is in an open period.
• The transaction's Payment status does not equal "Paid" or "Partially paid".

This field follows any editing restrictions imposed by the transaction definition's Edit policy and is only editable if the Edit policy is set to "All" or "Before printing".

Options are:

• Always: The user can edit the customer in all applicable scenarios.
• Except converted documents: The user can edit the customer in the first transaction in a workflow but not in transactions created by conversion.
• Never: The user cannot edit the customer unless the transaction is in draft state.

Delete policy

Sets the delete permission for this transaction type. Options are:

• No delete: The user cannot delete this transaction after it is created, unless the transaction is in draft state.
• Before printing: The user can delete this transaction until it has been printed to PDF. After it has been printed, the transaction cannot be deleted.
• All: The user can delete this transaction as allowed by the transaction’s condition. See Deleting a sales transaction for deletion restrictions.

Sets the create permissions for this transaction type. Options are:

• New document or convert: The user can create this transaction as a standalone transaction by (selecting Add from a transaction list, or the plus icon next to the transaction definition in the menu, or by copying an existing transaction, and so on) or the user can create this transaction by converting the previous transaction in the workflow.
• Convert only: The user can only create this document by converting the previous transaction in the workflow. For example, the user can only create a OE sales invoice by converting an existing sales order.

Sets the context for where users can create transactions from this transaction definition within a multi-entity, shared environment. Options are:

• Top level only
• Top level or entity
• Entity only

If you use an advanced workflow, when you select "Top level or entity" or "Entity only", an Entity settings tab appears. This tab allows you to define which entities can create transactions and define entity-specific numbering sequences and/or document templates if desired.

This field only appears on transaction definitions at the top level of a multi-entity, shared environment.

Enable permissions for specific users or groups

By default, all users with the appropriate application permissions (List, View, Add, Edit, Delete Transactions) have access to transactions that use this transaction definition. If you want to only allow certain users or user groups access or if you want to deny certain users or user groups access to this specific transaction definition, set this field to true.

When this field is set to true, you can use the fields that appear to add the applicable users and user groups to the Access rights table. Any user or user group that you deny access to will not be able to see this type of transaction in Order Entry or Accounts Receivable transaction lists. The transaction is still visible in reports and email delivery logs if they have the appropriate permissions.

The system evaluates all permission settings to determine the effective permissions. For example, say that Jerry Garfield is in the Analysts group. Say we set Allow access for the Analysts group and set Deny access for Jerry Garfield for the NFP OE sales invoice transaction definition. Jerry Garfield will not have access to NFP OE sales invoices in Order Entry or Accounts Receivable.

To set access rights for a user group or user:

1. Use the selection list to select Group or User. Depending on your selection, the applicable User group or User list becomes available.
2. Select the applicable user group or user from the list and select Add. The group or user appears in the table.
3. In the table, select Allow or Deny from the selection list next to the applicable user group or user.

Entity name

Use the dropdown list to select an entity.

Numbering sequence

Select the numbering sequence to use to automatically number transactions for the corresponding entity. To add a new sequence, select Add in the dropdown list.

Leave this field blank to use the numbering sequence defined on the General tab, or if you want converted transactions to inherit the source document number.

Preserve sequence numbers

Ensures that numbers are never skipped. Enabling this option can affect performance when a large volume of transactions is entered at the same time. This field is grayed-out if you did not select a Numbering sequence for the corresponding entity.

Inherit source document number

With this option selected, the document number from the previously converted transaction is assigned to the new transaction. For example, if you convert sales order SO-001 into a OE sales invoice, theOE sales invoice number will be SO-001.

Document template

Use the dropdown list to select a printed document template to use as the default for printed output (PDFs) for the corresponding entity. Leave this field blank to use the document template defined on the General tab. Learn more about printed document templates.

Show expanded tax details

Whether the subtotal section shows expanded tax details in the transaction user interface and in the printed output. For example, you might have State, Territory, Local, and District taxes. If you want the transaction printed output to show all taxes, set this field to true. If you want the printed output to have one tax subtotal, set this field to false.

This field is only applicable to companies that use Avalara AvaTax or Advanced Tax and appears only if Enable subtotals is selected.

Line-item tax

Whether the user can override whether an item is taxable. This option appears only if Enable subtotals is selected.

The Taxable field for an item on the transaction is only editable if the Ship to contact for the selected customer is flagged as Taxable.

Enable line-level Simple Tax

Allows the tax rate to be overridden at the line level when using Simple Tax. This option appears only if Enable subtotals is selected.

Subtotal template

Use the dropdown list to select the subtotal template to use for calculating subtotals. This option appears only if your Order Entry configuration has been enabled for subtotal templates and Enable subtotals is selected.