Intra-university charges are entered using GL journals. These charges may cross funds. When that happens, the system creates the balancing entries for each fund. This will be added to the lines that you entered and you will see all of the lines.
The Revenue (credit) side of the entry should use Account Code 471100 for all funds. Departments should use whatever Class Code they would normally use for their fund. The most common Class Code to use for Fund 14100 is Class Code 41500.
The Account Code for the expense (debit) side of the entry should properly classify the type of goods or service being purchased.
The two lines that you create reflect the actual movement of the amount between the chartstrings you enter. If there are two different funds on those lines, lines to balance the fund will be created by charging the amounts with the opposite sign to make the funds balance.
This balancing entry will use the same account for both so that the account nets to a zero amount. The transaction uses a special control account and a fund affiliate. The control account is not used for regular transactions, only for these balancing entries.
The Chart of Accounts Report that contains a full list of revenue and expense account codes may be found on the Chart of Accounts Resources page on the OneSource website.
Additional Information on recording intra-university charges: Recording Intra-University Charges
Supporting documentation must be attached to all General Ledger Journals and should reflect the entry being made. A good rule of thumb is to include an electronic copy of what was used to create the journal entry. For intra-university charges (tickets), invoices should be attached that equal the revenue amount being credited. For correcting/moving a transaction, provide supporting documentation that shows where the transaction originally posted. Remember to be concise with journal entries and combine documents when reasonable; reviewing fewer documents can be helpful for your approvers! Documents included are also available during auditing and historical review. Examples of supporting documentation:
- UGA_GL_LEDGER_DETAIL query results can be included to show what transaction is being corrected/moved.
- Any analysis/spreadsheet that was used to determine the amounts included in the journal entry.
- Invoices and agreements for Intra-University charges.