A/R G/L Integration Screen

Overview

Note: Depending on how your system is set up, this desktop screen may also be available as a web screen. For more information, see the Web Screens Getting Started Guide or the help for Sage 300 web screens.

You use the A/R G/L Integration screen to:

  • Specify how Accounts Receivable produces and maintains information from posted transactions for General Ledger. (Use the Integration tab.)
  • Define source codes to identify different types of Accounts Receivable transactions created for General Ledger.
  • View the last posting sequence number for each type of batch posted to General Ledger.
  • Specify what data to include in the G/L Entry Description, G/L Detail Reference, G/L Detail Description, and G/L Detail Comment fields for general ledger transactions. (Use the Transactions tab.)

Sage 300 Accounts Receivable produces general ledger transactions from all batches you post. Each general ledger transaction includes all the information you need to accurately update receivables data in your general ledger.

If you use Sage 300 General Ledger, Accounts Receivable creates batches of receivables transactions right in General Ledger, where you can edit and post them. If you use another general ledger system or your Sage 300 General Ledger system is at another location, Accounts Receivable creates batches you can import into another application, or print, then enter manually into your general ledger.

Integration Tab

This tab lets you control how and when GL transactions are created. More...

Use the Integration tab to:

  • Specify whether to add general ledger transactions to the G/L batch each time you post, or to create the transactions at a later date.
  • Choose whether to add new transactions to the existing G/L batch, if an open batch exists, or create a separate G/L batch when you create G/L transactions. You can also choose to post new batches automatically. (This option applies only if you use Sage 300 General Ledger with Accounts Receivable at the same location.)
  • Choose whether to consolidate the G/L batch when you post, or always enter full transaction details in the batch.
  • Look up the posting sequence number to be assigned the next time you post invoices, receipt, or adjustments, or the next time you revalue transactions, if you use multicurrency accounting.

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 icon), 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 Batches option or the data to include in the G/L Entry Description, G/L Detail Reference, G/L Detail Description, and G/L Detail Comment fields applies only to transactions posted after the change, and has no effect on transactions already in a general ledger batch.

Transactions Tab

Use the Transactions tab to specify the type of information to use in the transaction description, detail reference, detail description, and detail comment fields for general ledger transactions. More...

This information also appears on Accounts Receivable 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 ship-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.