Overview
You can - and should - restrict the flow of information that is passed to General Ledger when you post transactions that use optional fields.
This screen lets you specify groups of accounts for which values for an optional field can be passed to General Ledger. (The optional fields used in a transaction must also match the transaction details optional fields used for an account in order to be passed to General Ledger.)
This screen lists the groups of accounts that are affected when you post transactions of the type for which you are defining the optional field. Select from the list all the account groups for which you want to pass values to General Ledger when you post transactions that include the optional field.
Note: While all account groups are initially selected for new optional fields, you need to consider carefully the purpose of the optional field you are defining. You should send values to General Ledger only for optional fields that require financial analysis, and only to accounts where they are required. For example, you might want to send optional fields that contain customer numbers or sales territories only to revenue accounts.
You do not need to send optional field information for analysis that is performed only in Accounts Receivable. If you routinely send all the optional fields you use in Accounts Receivable transactions, your General Ledger may become hard to use, and you may also considerably slow down processing.
If you use Sage 300 Project and Job Costing, you can also specify whether optional field information for job-related transactions will be passed to Project and Job Costing, if the optional fields match those used for billings or costs in that program.