 |
| Accpac tip about Accounting and I/C, O/E, P/O |
Week |
Sep week 1 2011 |
Subject |
G/L Setup Form |
Details |
| |
Source Codes
This form lets you add new source codes and descriptions, change descriptions, and delete codes that are no longer needed. |
| |
|
| |
For the steps to add new source codes, |
| |
|
| |
Add Source Codes |
| |
|
| |
To add source codes: |
| |
|
| |
1. Open General Ledger >G/L Setup > Source Codes.
For help with the fields on the Source Codes form, select from the keywords listed below: |
| |
|
| |
Source code
A source code is a two-part code of four characters that is used in General Ledger to show where a transaction originated. Each journal entry is assigned a source code. For example, GL-CD might identify a cash disbursement entered in a General Ledger batch.
The first two characters, the source code prefix, identify the ledger or subledger where the transaction originated (for example, GL for General Ledger). The final one or two characters, the source code suffix, describe the type of transaction — such as a cash disbursement. Source codes are assigned automatically by subledgers.
Use the Source Codes form to define the source codes to use for transactions created in General Ledger and in batches imported into General Ledger. |
| |
|
| |
Description
Source code descriptions can be up to 60 characters long. Type in a description that you will be able to recognize later (like "Accounts Payable checks"). |
| |
|
| |
2. Click New and type a four-character source code. |
| |
2.1) The first two characters must identify the source ledger (such as GL or AR), the second two identify the transaction type.
2.2) You can just type the code and press Tab: G/L will assume you adding a new code. |
| |
|
| |
3. Enter a description for the code. |
| |
|
| |
4. Click Add, or choose Close to leave without adding a source code. |
| |
|
| |
Source codes in imported batches |
| |
Imported transactions must also contain source codes. You can define or import the source codes you want to use in imported transactions in the Source Codes form. |
| |
|
| |
Using source codes for reporting |
| |
Source codes allow you to organize and print source journals of posted transactions according to transaction type (for example, sales, checks, or cash receipts).
Use source journals to group transactions for analysis and auditing requirements. Batch listings and posting journals group transactions only by time of entry. |
| |
|
| |
|
 |
