Account Identification
The GL account identification consists of identifying the two parts that are used to post GL transactions. The first part is called the Organization Key (or some other customer given name for the Org Key) and the second is the Object Code (or some other customer given name for the Object Code). Several codes have been established to make the definition of the GL interface easier. The following describes all possible codes for directing entries from subsidiary systems to the proper GL account. Not all of these are applicable for a particular Subsystem and Report/Register and some may never be used by a given customer.
ORGANIZATION KEY ENTRY (Org Key)
Org Key | Description |
---|---|
TRNS | Use the Organization Key entered on the transaction. This is used when each individual transaction is to be posted in the GL. |
TTLKEY | Use the Organization Key entered on the transaction. This is used when each individual transaction is to be posted in the GL. |
CKKEY | Certain types of transactions have a Check Stock ID code entered as part of the transaction (i.e. Cash Receipts), check writing from Accounts Payable and Payroll. The Check Stock IDs can be associated with a particular Organization Key by placing a Key in the Associated Code 1 of the CKID Common Codes. When the user places CKKEY in this field, the system automatically retrieves the Organization Key associated with the given Check Stock ID. |
FDKEY | Using the Fund from the transaction the system looks up the associated FDID Common Code and uses the Associated Code 1 field as the Organization Key. |
CKFDKEY | A combination of FDKEY and CKKEY. It is the Fund Administration Key from the FDID associated with the Org Key on the CKID Common Code (seldom used). |
DVKEY | From the Subsystem Division entered in the AR Set, use the Org Key entered on the Division Definition Form (seldom used). |
1234567890 | Use the specific Org Key entered on this form. |
OBJECT CODE ENTRY (Object)
Object | Description |
---|---|
TRNS | Use the Object Code entered on the transaction. This is used when each individual transaction is to be posted in the GL. |
TTLOBJ | Use the Object Code entered on the transaction. This is used when each individual transaction is to be posted in the GL. |
CKOBJ | Certain types of transactions have a Check Stock ID code entered as part of the transaction (e.g. Cash Receipts, Accounts Payable, and Payroll). The Check Stock ID can be associated with a particular Object Code in the by putting the Object into Associated Code 2 of the Common Codes. When the user places CKOBJ in this field, the system automatically retrieves the Object Code associated with the given Check Stock ID. |
FDOBJ | When detail transactions are entered, a particular Org Key and Object Code is specified. Each Org Key is associated with a particular Fund Code. These Fund Codes can be associated with a particular Object Code in the Common Codes. When the user places FDOBJ in this field, the system automatically retrieves the Object Code associated with the given Fund Code. |
CKFDOBJ | A combination of FDOBJ and CKKEY. It is the Fund Administration (FDID) Object Code within the Fund identified by the Org Key defined on the CKID Common Code. |
DVOBJ | From the Accounts Receivable Division entered in the Set, use the Object Code entered on the Accounts Receivable Division Code (commonly used for AR posting). |
12345678 | Use the Object Code entered on this form. |
LEVEL (L)
L | Description |
---|---|
T | Individual transaction. This is only used when the Org Key is "TRNS" or a hard-coded Key "xxxxxxxxxx" and the Object is "TRNS" or a hard-coded Object "xxxxxxxx." This option posts the greatest detail (vendor ID, Invoice number, PO number…) |
O | Object Code |
K | Organization Key |
P | Posting Code total |
F | Fund total |
G | Grand total all transactions. |
E | Employee |
Any summary control total postings that occur (i.e. O, K, P, F, G, E) will be posted to the general ledger with a transaction description as follows:
AUTO ID:BPxxxxxx JB:xxxxxx
"AUTO" indicates that this is an automatic total posting.
"ID" is followed by the Set ID Number for all entries in the transaction batch.
"JB" is followed by the BusinessPlus Job Number that is automatically assigned at the time of posting.
TYPE (T)
T | Description |
---|---|
A | Distribution amount which is Qty x Price + Tax + Charges + Duty (A+T+C+U) |
D | Discount amount (D) |
N | Net amount which is Qty x Price - Discount + Tax + Charges + Duty (A-D+T+C+U) |
T | Tax Amounts (T) |
F | Net plus Discounts Lost |
F | Net Amount plus Discounts Lost (N + L) |
G | Net Amount less Tax (A-D+C+U) |
H | Distribution Amount less Tax (A+C+U) |
i | Digit 0, 1, 2, ... 9. Used with Payroll subsystem postings |
| 7 represents GROSS, 8 NET CHECK, 1 AMOUNT |
L | Discounts Lost (L) |
C | Charges (C) |
U | Duty (U) |
DATE (D)
D | Description |
---|---|
P | Posting date - Used to direct postings at the time of Set distribution. |
C | Check date - Used to direct postings at the time that checks are printed. |
I | Invoice date - Used to direct postings as of the invoice date of an Accounts Payable transaction (seldom used). |
B | Bank date - Used to direct postings to the GL at the time checks are cleared through the Bank Reconciliation subsystem. This is most often needed when the client uses Warrants Outstanding and needs to adjust cash when the checks clear rather than when they are written (seldom used). |
A | Accrual Entry (used only if posting both Cash and Accrual Balances) (seldom used). |
R | Accrual Reversal (used only if posting both Cash and Accrual Balances) (seldom used). |
Posting Codes (PCi)
PCi | Description |
---|---|
| Blank implies that the posting is not related to a specific posting code. |
@@@ | Each posting code. |
iii | Posting code 000-999. Posting Codes are used to direct the BusinessPlus posting logic to create different automatic entries as defined in the Posting Preferences (GLUTSPPP). Each code is associated with an Org Key and Object Code to tell the system which fully qualified account to use in posting transactions to the GL. When entries are distributed to the GL, the detail transactions will be summarized at the LEVEL (L) defined for the posting code used and posted to the defined Org Key and Object Code. Where multiple accounts are not necessary, a specific posting does not need to be defined. In the examples developed below, effective use of posting codes is discussed under varying situations |
Fund | Description |
---|---|
| Blank implies that this is not a fund level posting. |
@@ | Each Fund. |
ii | Fund code. |