ACCT (Accounting Category)

The following control maintenance records belong to the ACCT (Accounting) category.

Activity Trigger Default Inherit

Select the default value the system uses when the Inherit field on a customer or vendor Activity Trigger Maintenance window is blank.

Options	Yes - The entity inherits activity triggers from higher entities. For example, the system executes a ship-to entity’s triggers, along with the triggers assigned to the corresponding bill-to entity, branch entity, and corporate customer, unless one of those entities is set to not inherit triggers. Note: The system sends only one e-mail per e-mail address, even if the entities have duplicate triggers. No - If the entity is a ship-to only customer that has e-mail triggers set, the system uses those triggers. If the system does not find e-mail triggers on the ship-to, the system checks the bill-to for triggers. Customers do not inherit triggers from branch or corporate customer entities if this record is set to No
Outcome of setting this control record	If set to Yes, the customer or vendor inherits the activity triggers from their parent and associated entities. If set to No, the system checks the bill-to for triggers that a ship-to customer should inherit.
Default Value(s)	No
Action if set to Null	The same as if set to No.
Additional Information	If there is an entry in the Inherit field in Activity Trigger Maintenance, the system uses that setting for the customer or vendor instead of the setting in this control maintenance record. For additional information, see Flagging Entities to Inherit Triggers.

Auto Prompt For G/L Account Detail Notes

Indicate whether the system automatically prompts for G/L account detail notes.

Options	Yes - When entering a G/L account, the system prompts you to enter additional details regarding the account and the ledger entry. No- Does not prompt for G/L account detail notes. However, users can sill enter detail notes using the Detail Notes menu options in applicable windows.
Outcome of setting this control record	If set to Yes, each time a G/L account is selected or entered for a ledger entry, such as during the inventory adjustment process, the system prompts the user to enter details about the entry.
Default Value(s)	No
Action if set to Null	The same as if set to No.
Additional Information	If set to Yes, detail notes are required for G/L entries in the following circumstances: In A/P Entry when a user distributes an invoice across G/L accounts instead of reconciling to a purchase order. In Cash Receipts when a user enters an adjustment. When making an inventory adjustment. The user is allowed to enter a note for the one G/L account for which the inventory adjustment is set up. The detail notes that are entered are included on the General Ledger Report when run using the Detail option.

Branch That Controls Branch That Receives Credit For The Sale

Select which branch on a sales order the Branch That Receives Credit For Salecontrol maintenance record uses to determine the branch that records the G/L postings for an order segment.

Options	Pricing Shipping Terminal User Home
Outcome of setting this control record	The system posts an entry to the appropriate G/L account based on the setting in this control maintenance record.
Default Value(s)	Shipping
Dependencies	The Branch That Receives Credit For Sale control maintenance record must also be set for the setting in this control record to apply.
Action if set to Null	System uses the setting in the Branch That Receives Credit For Sale control maintenance record.
Additional Information	A value in the value in the G/L Branch field in the Additional Header Information window, accessed from the Edit > Additional Information option in the Header tab of a sales order, overrides the setting in this control record. Important: If this record is set to Terminal or UserHome, Web Integration implementations use the pricing branch, as they do not know the user or terminal branch.

Default Payment Terms

Set payment terms for standard and direct orders at the system level. For each of the options define which terms code, or payment term, you want to use as defined in Terms Code Maintenance.

Standard Orders	Customer Terms - Define the selling terms you want to use at a global level for standard sales orders. Vendor Terms - Define the pay terms (purchasing terms) you want to use at a global level for standard purchase orders.
	Hierarchy - Customer Terms The system uses the following process for applying a terms code: When customer terms are set, the system uses the Terms Code set in Customer Maintenance. If blank, uses this control record maintenance setting. If the Use Default, Use Parent, or Use Bill-To options are selected in Customer Maintenance, then the system uses those settings to determine the terms code following standard hierarchy rules. Otherwise, terms must be loaded in the Ship-To customer account record.
	Hierarchy - Vendor Terms The system uses the following process for applying a terms code. When customer terms are set, the system uses the Terms Code set in Customer Maintenance. If blank, uses this control record maintenance setting. The system will notcheck the pay-to account. Terms codes much be loaded in the Ship-From vendor account record.
Direct Orders	Customer Terms - Define the selling terms you want to use at a global level for direct sales orders. Vendor Terms - Define the pay terms (purchasing terms) you want to use at a global level for direct purchase orders.
	Hierarchy - Customer Terms The system uses the following process for applying a terms code: When customer terms are set, the system uses the Direct Terms Code set in this control maintenance record. If blank, the system uses the direct terms from Customer Maintenance. If that Customer Maintenance setting is blank, the system uses the control maintenance record setting for standard terms. If the Use Default, Use Parent, or Use Bill-To options are selected in Customer Maintenance, then the system uses those settings to determine the terms code following standard hierarchy rules. Otherwise, terms must be loaded in the Ship-From customer account record.
	Hierarchy - Vendor Terms The system uses the following process for applying a terms code. When customer terms are set, the system uses the Direct Terms Code set in Vendor Maintenance. If this control maintenance record is blank, the system uses the standard terms set in Vendor Maintenance. If that Vendor Maintenance setting is blank, the system uses the control maintenance setting for standard orders. The system will notcheck the pay-to account. Terms must be loaded in the Ship-From vendor account record.
Action if all fields are blank	The system uses the last day of the next month as the due date and the last day of the current month as the discount date.
Outcome of setting this control record	Allows you to set payment terms for orders at the system level that you can set different rules for standard versus direct sales orders and purchase orders. Using this setting automates the process for you rather than having to change terms on orders manually.
Default Value(s)	None.
Action if set to Null	The system uses settings set at the customer and vendor level.
Additional Information	This setting applies to both Solar Eclipse orders and Job Management orders. For information about Job Management, see the online help attached to the Job Management application.
	A/P Entry uses terms codes from Vendor Maintenance. If a direct purchase order is changed and terms codes do not match the Vendor Maintenance entry, then users are alerted of the mismatch.
	Direct Through Stock orders follow the same hierarchy for direct orders and purchase orders, even though the purchase order is a standard purchase order.

Respect Auth Br For A/R/A/P Inq/Ledger, Aging Rpts & Cash Receipts

Use this control maintenance record to limit the customer information a user can view to the branches to which the user has access.

Options	Yes - Displays the customer's balance only for those branches for which a user is authorized. For example, if the user is authorized for branches 1, 2, and 3, they are unable to view information for branch 4. This is the default. No - Displays the customer's total balance for all branches.
Outcome of setting this control record	If set to Yes, your accounting clerks can only view and post payables and receivables to the branch locations to which they are authorized in User Maintenance. If set to No, users can view and post to all branches.
Default Value(s)	Yes
Examples	For example, your customer buys electrical parts from branch 1 and plumbing parts from branch 2. Set this record to Yes if your accounts receivable clerk in branch 1 should only use electrical branch 1 invoices when posting a cash receipt for the sale. Set this record to No if your accounts receivable clerk in branch 1 should be able to post a cash receipt against all invoices in branch 1 and branch 2.
Action if set to Null	Same as if set to Yes.
Additional Information	This control record applies to the following areas: A/P and A/R Inquiry A/P and A/R Ledger Cash Receipts A/R Collection Queue A/R Aging Report A/P Aging Report Aged Unbilled Stock Receipts Report To control whether branch authorizations are respected in A/P Entry, set the Disable User Branch Authorization In A/P Entrycontrol maintenance record.

Terms Codes To Exclude From Anticipation Credit Eligibility