This chapter contains these topics:
To understand how the system applies accounting instructions
To learn how to set up accounting instructions for your company
When journal entries are created, the system uses instructions from the Automatic Accounting Instructions (AAIs) to assign an account number to each journal entry created in the Payroll or Time Accounting systems.
During the payroll cycle, the system creates a journal entry of every calculation for every employee. Each journal entry is assigned a Document Type, Journal Type, and a G/L Date.
These calculations include salary and wage expenses, burden, cash disbursements, and liabilities. As an option, you can create journal entries for labour and equipment billings and accruals for payrolls that cross accounting periods.
The AAIs control the account to which each journal entry is assigned. After the journals are created and assigned account numbers, the system summarizes them and passes them to the general ledger.
You can establish AAIs separately for each company and general rules for the default Company 00000. The rules are flexible and, in addition, are changeable within the payroll cycle. For example, labour distribution account numbers can be assigned by company, business unit, group (union), job type, job step, and pay type. If some employees do not follow general rules, you can specify instructions for labour distribution at the employee level.
You can set up rules to summarize journal entries. As full detail exists in payroll or time accounting history, you might not need full detail in the general ledger. You can set up rules to summarize account ranges and business units.
You can post the journals either automatically or manually for each payroll.
Journal entries are created by the payroll system using the AAI instructions. Each timecard transaction creates several journal entries, and the AAIs are used to assign account numbers to those journal entries.
When you run journal entries, you receive a report called the Journal Batch Proof. This report shows all of your journal entries, what accounts they are associated with, whether the entry is a debit or credit, and the amount of the journal entry.
Any errors that you receive in your journal entries will print on this report. For example, when an invalid account from the default line of an AAI table is used, you will see the error "Invalid Account" on the Journal Batch Proof. To find out exactly what is causing this error, it is helpful to print detail for those journal entries. Printing your journal entries in detail can give you information that may make finding the cause of your error easier. This, in turn, makes identifying which line of AAI instructions is missing easier. There are six different levels of detail in which you can print your journal entries. Level 6 will show the most detail, and level 1 will show the least amount of detail. You can change the detail level for all object accounts or for a specific object account and you can rerun your journal entries over as many times as you wish.
Caution:
If you change the detail level to print a lot of detail in order to identify a problem, change the level of detail back to a 1 once you have eliminated the problem, and rerun your journal entries before postingIt is not uncommon that in one pay period there are dates that fall within more than one month. This is called a transition period. An example of a transition period would be if a fiscal period for a company is a calendar month and the pay period dates begin on April 26th and end on May 9th. The time that employees work during this pay period crosses fiscal periods. How will labour and burden be expensed for this transition period?
When running your journal entries for this pay period, an override date can be used. Entering a date in the Override Accounting Date field allows you to specify a specific date for all of the journal entries generated during that pay period. Using the above example, if the company wanted all of the journal entries to be posted to the end of the fiscal period the pay cycle started in, they may enter April 30th.
In a transition period situation, it may be beneficial to have expenses distributed between the two fiscal periods. This can be accomplished using the Accrual Factor field. This is particularly beneficial when all the timecards within a transition pay period are dated with the pay period end date, which, in this example, would be May 9th.
Note:
This field is only used during transition period payrolls.The Accrual Factor allows you to post a certain percentage of your expenses back to the first fiscal period of the payroll. The system creates all the journal entries is normally would and posts them to the later fiscal period, in this example, May. It then credits that same period for the amount of the accrual, and debits the first fiscal period, April.
In our example, approximately 35% of the pay period exists in April. If there are not any timecards for April, the system would not know how much to expense to April, the first fiscal period. The accrual factor allows you to specify a percentage of the payroll expenses to be distributed to the first fiscal period. Entering "35" in the accrual factor field will create journal entries that reflect this.
The system can create journal entries at three stages in the processing:
During a regular payroll cycle
While processing interim cheques during a regular payroll cycle
During a special timecard post
The system initially creates pro forma journal entries during the payroll journal entries step of the payroll cycle. The pro forma journal entries are created in the Payroll Journal table (F06395) and at that point they become part of the Payroll system.
During final update, the system creates actual journal entries in the Account Ledger table (F0911). At this point, the journal entries are part of the General Accounting system.
When you generate timecard journals during a special timecard post, you create pro forma journal entries. The system creates the actual journal entries when you post journals to the general ledger.
The system uses the standard business unit.object.subsidiary and subledger account structure. The general ledger account structure is composed of two parts:
Where - business unit
What - account number
A business unit is a 12 character, alphanumeric field that is the lowest level of organizational reporting. It identifies the "where" within an organization. Each business unit is assigned to a company and can be associated with 20 category codes for higher level reporting. For example,
Department
Branch
Asset (revenue and maintenance expense)
The account number identifies whether the account is an asset, liability, or expense. It identifies the "what" in a transaction and contains two parts:
Object account, which is up to 6-characters, alphanumeric, and is required on all journal entries.
Subsidiary is an 8-character, alphanumeric field that is optional on journal entries. For example, you can use this field to identify an employee number, equipment, number, or asset number.
The following definitions are important in understanding payroll journal entries:
When journals are created in the payroll cycle, the system assigns a general ledger date using a date associated with the payroll, such as pay period end date or payment date. You specify the general ledger date to be used for labour distribution and burden journals (T2, T3, T4, and T5) in the payroll journal entries step of the payroll cycle. Cash disbursement and liability journals (T1 and T7) use the payment date as the general ledger date.
The Pay Cycle Review tracks your choice of general ledger date for labour distribution to reference when you submit the next payroll.
You can specify an override date when you submit the journal entry creation job. The override date you specify becomes the general ledger date for all journal entries created for all document types.
When you use the special timecard post to create journals, you specify the general ledger date to use.
The following example of a Payroll Cycle Journal is based on the following simple payroll:
Employee: Home Company = 1, Home Business Unit = 25, Union = 1000
Time Card: 01/28/17 (Pay Code 001) $1,000
Payroll Taxes and Insurance (P.T.I.): UIC (Tax Type CC & CD) $70
Deductions: Savings Bond (Ded Code 2000) $50
Benefits: Union 1000 (Ben Code 6000) $30
Payment Date: 02/05/17
Figure 46-1 Example: Payroll Journal Entry
When the system creates a journal entry for the general ledger, it codes the journal entry with a document type and reference number. The document type is a two-character code that classifies payroll journal entries into one of seven document types:
Type | Description |
---|---|
Type T1 | Payroll disbursement journal entries |
Type T2 | Labour distribution and flat burden journal entries |
Type T3 | Actual burden journal entries |
Type T4 | Labour billing distribution journal entries |
Type T5 | Equipment distribution journal entries |
Type T6 | Payroll accruals and deferrals |
Type T7 | Payroll voucher journal entries |
The reference number, composed of journal type and general ledger date, further identifies the source of each journal entry within a document type.
The journal entry reference number becomes the Reference 2 value in the actual Account Ledger table (F0911).
Document type T1 contains all journal entries associated with the writing of payments. The journal entries include cash-in-bank, relief of accrued wages, deduction, tax and benefit liabilities, and burden clearing entries.
The system creates T1 journals in the payroll cycle only.
All T1 journals carry the same general ledger date, that is the payment date or the override date.
The specific journal types used for these journal entries include:
The system creates journal entries for document type T2 directly from timecards for labour expenses and associated offsets for accrued wages. You can also generate journal entries to allocate an estimated or flat burden expense.
The system creates T2 journal entries during the payroll cycle or during a special timecard post.
Four possible general ledger dates exist for journal entries created during the payroll cycle:
Date | Description |
---|---|
Work date | The general ledger date is the work date on the timecard. |
Period ending | The general ledger date is the pay period ending date. |
Cost period | You can use the cost period with the creation of payroll journal entries for a transition period. The system assigns a general ledger date equal to the last day of the preceding accounting period for journal entries for those timecards with work dates falling into the preceding accounting period. The system assign a general ledger date equal to the pay period ending date in pre-payroll processing for journal entries for those timecards with work dates in the succeeding period. |
Override date | You provide an override date when you submit the journal entry creation job. The date you specify becomes the general ledger date for all journal entries. |
You specify which general ledger date to use for T2s in the payroll journal entry step of the payroll cycle. When you generate timecard journals during a special timecard post, enter the general ledger date in the processing options.
The specific journal types used for labour distribution journal entries are:
Type | Description |
---|---|
AW | Accrued wages - Credit entry |
FB | Flat burden expense - Debit entry |
FC | Flat burden offset (Clearing) - Credit entry |
LD | Labour distribution straight time - Debit entry |
PR | Labour distribution premium time - Debit entry |
IC | Intercompany Settlements |
The system calculates company-paid payroll taxes, insurance, and benefits on an employee-by-employee basis. These expenses are collectively referred to as burden. Actual burden journal entries are created when the employee burden expenses are allocated to expense accounts based on individual timecards entered for each employee.
The system generates journal entries for document type during the payroll cycle or a special timecard post.
Actual burden journal entries carry the same general ledger date as the associated labour expense.
The specific journal types used for actual burden distribution journal entries are:
Type | Description |
---|---|
BF | Fringe burden (Benefits and Accruals) - Debit entry |
BT | Payroll tax and insurance burden (PTI) - Debit entry |
CF | Burden offset (Clearing) - Fringe - Credit entry |
CT | Burden offset (Clearing) - Taxes - Credit entry |
IC | Intercompany Settlements |
Document type T4 journal entries are for labour billings, also known as recharge, and associated revenue offsets.
You use T4 labour billings for:
Billing internally | Billing externally |
---|---|
For example:
Charging other departments for maintenance people Charging a supervisor's billing rate to a job |
For example, service billing for consulting services |
The system creates these journal entries from the billing rate value. To create T4s for an associated timecard, you must set the Record Type field (originally set up in Employee Master) on the timecard to one of the following settings:
2 (Payroll and recharge processing)
3 (Recharge processing only)
The system creates journal entries for labour billing distribution from timecards during the payroll cycle or a special timecard post.
Four possible general ledger dates exist for journal entries created during the payroll cycle:
Date | Description |
---|---|
Work date | The general ledger date is the work date on the timecard. |
Period ending | The general ledger date is the pay period ending date. |
Cost period | You can use the cost period with the creation of payroll journal entries for a transition period. The system assigns a general ledger date equal to the last day of the preceding accounting period for journal entries for those timecards with work dates falling into the preceding accounting period. The system assign a general ledger date equal to the pay period ending date in pre-payroll processing for journal entries for those timecards with work dates in the succeeding period. |
Override date | You can provide an override date when you submit the journal entry creation job. The date you specify becomes the general ledger date for all journal entries. |
You specify which general ledger date to use for T4s in the payroll journal entry step of the payroll cycle. During a special timecard post, enter the general ledger date in the processing options.
The specific journal types used for labour billing distribution journal entries are:
Type | Description |
---|---|
RD | Labour billing (recharge) distribution - Debit entry |
RO | Labour billing (revenue) offset - Credit entry |
IC | Intercompany Settlements |
Document type T5 journal entries designate billings associated with the use of equipment and the offsets for equipment revenue.
The system creates journal entries for equipment distribution from timecards. They can be generated during the payroll cycle or a special timecard post.
Four possible general ledger dates exist for journals created during the payroll cycle:
Date | Description |
---|---|
Work date | The general ledger date is the work date on the timecard. |
Period ending | The general ledger date is the pay period ending date. |
Cost period | You can use the cost period with the creation of payroll journal entries for a transition period. The system assigns a general ledger date equal to the last day of the preceding accounting period for journal entries for those timecards with work dates falling into the preceding accounting period. The system assign a general ledger date equal to the pay period ending date in pre-payroll processing for journal entries for those timecards with work dates in the succeeding period. |
Override date | You can provide an override date when you submit the journal entry creation job. The date you specify becomes the general ledger date for all journal entries. |
You specify which general ledger date to use for T5s in the payroll journal entry step of the payroll cycle. For a special timecard post, enter the general ledger date in the processing options.
The specific journal types used for equipment distribution journal entries are as follows:
Type | Description |
---|---|
ED | Equipment Billing Distribution - Debit Entry |
EO | Equipment Billing (Revenue) Offset - Credit Entry
Set up the credit entry in Equipment AAIs. |
The Payroll system allows you to specify an accrual factor for transition pay periods instead of using the cost period option of creating payroll journal entries. Through the use of this feature, you can use the accrual factor to accrue a portion of payroll expenses in the previous month and defer the expense in the following month. Prior period entries are made to the last day of the prior accounting period.
The journal types for T6 are the same as T2, T3, T4, and T5.
The system creates journal entries for document type T6 during the payroll cycle. Enter the accrual factor (percentage) in the journal entries step of the payroll cycle.
The accrual entries have a general ledger date that is equal to the end of the prior accounting period. The Reference Number is equal to the journal type plus the original general ledger date.
The deferred entries have a general ledger date that is equal to the date of the original entries.
Document type T7 journal entries designate accounts payable vouchers.
Document type T7s are created during the payroll cycle. All T7 journal entries carry the same general ledger date. This date is the payment date.
The specific journal types used for payroll voucher journal entries are:
Type | Description |
---|---|
AL | Accrued Liabilities - Credit Entry |
AT | Accrued Taxes - Credit Entry |
There are no AAIs for T7s. The account numbers are assigned the same way T1 account numbers are assigned.
The following example of a payroll cycle journal is based on the following simple payroll:
Employee: Home Company = 1, Home Business Unit = 25, Union = 1000
Time Card: 01/28/17 (Pay Code 001) $1,000
P.T.I.: UIC (Tax Types CC & CD) $70
Deductions: Savings Bond (Ded Code 2000) $50
Benefits: Union 1000 (Ben Code 6000) $30
Payment Date: 02/05/17
Figure 46-2 Example: Journal Entry with Document and Journal Types
Company 00000 is the default company in all of the AAI tables. Always start by setting up generic entries in Company 00000. Such entries provide a source for default accounts for all of the various types of journal entries. After you complete table entries for Company 00000, you can enter other companies. Entries for other companies should only be exceptions to the generic rules established under Company 00000.
Every AAI table includes the Journal Type field, which contains one or more codes identifying the type of journal entry. Each table has a hard-coded set of journal types. Rules for some journal types must be set up. Other rules are optional.
Each time the system creates a journal entry, it follows a hierarchy of search criteria to determine which distribution account to debit or credit. The system begins the search with basic data related to the type of accounting entry, referred to as the search argument. The system creates a search argument from the system data, such as the timecard, and searches the accounting rules tables for the table entry that best matches the search argument information.
On the first search, the system uses data appropriate for that table and looks for a match on all fields in the search criteria section of the screen(the entire search argument). Then, one by one, the system drops elements from the search argument until it finds a matching table entry. At the lowest level, the system tries to match only the journal type. In addition, you can have a line in an accounting instruction table that has no search criteria other than the journal type. This is the default line.
Each table should have a default line. Default lines in the AAI tables are used to create journal entries. If a match is not found in the table, the default line is used to create the journal entry. Journal entries created for the default account indicate that instructions are missing from the table.
A default line can be set up at the Company 00000 level, or on company-specific tables. The system will first search the rules for a specific company. If it finds no applicable rules (matches) for that company, it will continue with the rules for Company 00000.
It is recommended that the account number associated with the default line in a table not be a valid account. If your journal entry is produced using the default line, an error, "Invalid Account," will display on the Journal Batch Proof report. This serves as notification that there are additional entries that need to be made to your AAI table.
If the system cannot find a match against employee or timecard information to an AAI line, and there is not a default line set up, an "Invalid Account" error will still display on the Journal Batch Proof report.
The home business unit will print, but employee detail cannot be requested. This makes identifying the problem more difficult, since there is not an account to display detail.