About Using Accounts Payable with Sage 300 Online General Ledger
Printing The G/L Transactions Report
Use this option on the Integration tab of the G/L Integration screen to specify whether to combine transaction details for the same general ledger account into single details, or to send every Accounts Payable transaction detail to General Ledger.
Note that if you consolidate transactions, you lose the ability to drill down to them from General Ledger.
You can choose:
This option applies only if you use Sage 300 General Ledger with Accounts Payable.
You can create transactions by:
Note: If you try to post a G/L batch to a period that is locked for General Ledger, the transactions will be placed in an error batch. Therefore, make it a practice to create and post General Ledger batches for outstanding Accounts Payable transactions before locking a period for General Ledger.
Accounts Payable automatically creates separate general ledger batches for the different types of transactions you can post (invoices, payments, adjustments)
If you do not use Sage 300 General Ledger, all general ledger transactions are added to the same general ledger batch, regardless of the type of transaction and your choice for this option. You are asked to whether to add the transactions to the existing batch or overwrite the batch. Always choose to add to an existing batch.
Use this option to specify when to create general ledger transactions.
You can create transactions for the general ledger when you post Accounts Payable batches, or you can create a batch of general ledger transactions using the Create G/L Batch screen.
You can change your selection at any time. If you have been using the Create G/L Batch screen to create the transactions, before you change the option, be sure to print a copy of the latest G/L Transactions report, then create any outstanding transactions.
If you use the option to create the batch during posting in Accounts Payable, you cannot print the G/L Transactions report.
Use the Source Type fields in this section to define the source code for each type of Accounts Payable transaction, if you prefer not to use the default source codes.
The source code is a combination of the source ledger code (AP, which you cannot change) and the source type code, which you can specify for all the different types of transactions you can process in Accounts Payable
The source codes are used to identify transactions in General Ledger.
Note: The default source code for payments is the same as for payment reversals.
This box lists the posting sequence number of each type of transaction batch for which general ledger transactions have been created.
If all general ledger transactions are up to date, the posting sequence numbers in this box are the same as the posting sequence numbers shown for each batch type on the A/P Create G/L Batch screen.
Tip: If you create G/L batches using the Create G/L Batch screen, you can use this information to check whether you have created all outstanding general ledger transactions.
This field displays, for each detail transaction type, the comment information that will appear with unconsolidated details on the G/L Transactions report and in the general ledger batch.
To include different information as the comment for a selected transaction type, click the Edit icon and enter the information on the G/L Integration Detail screen that appears.
This field displays, for each detail transaction type, the information that will appear with unconsolidated details in the Description column on the G/L Transactions report and in the Description field in the general ledger batch.
Note: If you consolidate details during posting, the description is "CONSOL" for all the transactions in General Ledger.
To edit the information for a selected transaction type, click the Edit icon and enter the information on the G/L Integration Detail screen that appears.
This field displays, for each detail transaction type, the information that will appear with unconsolidated details in the Reference column on the G/L Transactions report and in the Reference field in the general ledger batch.
Note that if you consolidate details during posting, the reference is blank for all the transactions in General Ledger.
To edit the information for a selected transaction type, click the Edit icon and enter the information on the G/L Integration Detail screen that appears.
This field displays, for each entry transaction type, the information that will appear as the entry description on the G/L Transactions report and in the general ledger batch.
To edit the information for a selected transaction type, click the Edit icon and enter the information on the G/L Integration Detail screen that appears.
This column shows the transaction types for which you can assign information for G/L transactions.
To edit the information for a selected transaction type, click the Edit icon and enter the information on the G/L Integration Detail screen that appears.
Use the A/P G/L Integration screen to:
Sage 300 Accounts Payable produces general ledger transactions from all batches you post. Each general ledger transaction includes all the information you need to update Payables data accurately in your general ledger.
Accounts Payable creates batches of payables transactions right in General Ledger, where you can edit and post them. It creates separate General Ledger batches from posted invoice, payment, and adjustment batches
If you use another general ledger system or your Sage 300 General Ledger system is at another location, Accounts Payable creates batches you can import into another application, or print, then enter manually into your general ledger.
You can change any settings on the A/P G/L Integration screen at any time.
Note: Changes to settings are applied only to general ledger transactions created after the change, and do not affect pre-existing general ledger batches.
Tip: If you use the Create G/L Batch screen to produce general ledger batches and want to change to producing them during posting, we recommend that you first run Create G/L Batch to create any outstanding transactions.
Use this tab to:
Note: This option applies only if you use Sage 300 General Ledger with Accounts Payable at the same location.
Before changing the Create G/L Transaction option to create transactions during posting (if it was set to create transactions using the Create G/L Batch screen), print an up-to-date copy of the G/L Transactions report, then create any outstanding transactions.
Any change to your selections for the Consolidate G/L Batch option or the data to include in the transaction description, detail reference, detail description, and detail comment fields for general ledger transactions applies only to transactions posted after the change, and has no effect on transactions already in a general ledger batch.
Use this tab to specify the type of information to use in the G/L Entry Description, G/L Detail Reference, G/L Detail Description, and G/L Detail Comment fields in general ledger transactions.
This information also appears on Accounts Payable posting journals and on General Ledger’s Journal Entry screen and reports.
You can assign one or more pieces of information (segments) to each field, provided that the combined length of the segments and separators does not exceed 60 characters. Fields exceeding this limit will be truncated when you post general ledger transactions.
The segments you can select depend on the type of transaction to which you are assigning information and whether the information is for the transaction header or the details. This ensures that the information passed to General Ledger is relevant for each type of transaction. For example, you can assign the remit-to information from invoice details to any of the General Ledger fields.
When you create general ledger transactions, if no data exists in the source transaction field, the field will be blank in the general ledger transaction. For example, if you assigned the original transaction description to the G/L Entry Description field, but there is no description for a particular entry, the field will be blank in the G/L transaction.