Allocation Types on the General Ledger menu lets you set up allocation types using different methods, applying rules for General Ledger and/or Job Status apportionment of sales or costs. This is a global table across all companies.
The GF method is based on fixed GL allocations. Use this method if overhead GL accounts are allocated to departments based on a fixed percentage such as number of employees or square footage.
The GV method is based on GL account balances. Use this method if overhead GL accounts are allocated to departments based on sales.
The JC method is based on the amounts in certain cost codes for specific jobs.
The JR method is based on the revenue on specific jobs.
The JV method lets you allocate costs from the General Ledger or an overhead job to many jobs based on costs from other jobs.
To set up a new allocation type
Go to Allocation Types.
Use the Method drop-down to choose the method for the allocation type, and click Add (
).
Enter a code for the new allocation type.
If you add an allocation type with the same code as an existing one, the sequence number is automatically incremented. This means you can set up different allocation rules and process them together. When you specify an allocation type to process, all the sequences for that type are processed.
Fill in the other fields:
Field
Description
A description for the allocation type.
Group
The group to which this allocation type belongs. Groups give you an alternative way to select allocation types when processing allocations.
Allocation Base
Whether to use period movement or balance value as a base for allocation.
Override Credit Analysis
The GL account or job analysis to be credited when a journal is processed, if this is different from the source defined in the GL Allocation area or the Cost Code Allocation area.
Allocate GL or Job Costs
(For ‘JV’ method only.) Whether to allocate to the General Ledger or to a job.
Matches Job
(For ‘J’ methods only.) The job or jobs to process using this type.
Use the GL Allocation, Cost Code Allocation or GL or Job Costs Allocation panel to identify the source and the amount to be allocated.
If you are using a job-based (J) method, use the Job Details panel to specify which jobs the allocation applies to.
Click Save (
).
Depending which method you chose, one or both of the following tabs are available:
Allocation Basis – Use this to specify how the allocation is split by percentage.
Allocation Overrides – Use this to override where the allocation goes.
GL Allocation - Method GF
The GF method is based on fixed GL allocations.
Use this method if overhead GL accounts are allocated to departments based on a fixed percentage such as number of employees or square footage.
Example
You want to allocate 90% of the total rent of $15000 to the Rent expense account 7090, based on the square footage for each department, as follows: dept 1 = 3420 sq ft, dept 2 = 5670 sq ft, dept 3 = 5210 sq ft.
GL Allocation
Override Credit Analysis | 00.00.7120 |
Starting Code | Ending Code | Matches Code | % to Allocate |
00.00.7010 | 00.00.7020 | * | 90 |
Allocation Basis
Fixed Value | Debit Account |
3420 | 01.01.7090 |
5670 | 02.01.7090 |
5210 | 03.01.7090 |
The system takes the balance in the account range Allocation line, and multiplies it by the percentage to determine the amount to allocate. Then it takes the fixed value in each allocation basis line to determine a percentage for each line, and creates a GL transaction to the debit account on each line, with the balancing transaction hitting the credit account on the first screen.
So if 00.00.7010 has a balance of $10000 and 00.00.7020 has a balance of $5000, the amount to be allocated is $15000x90%= $13500. This is allocated based on square footage as follows: dept. 1 = 3420 sq. ft., dept. 2 = 5670 sq. ft., dept. 3 = 5210 sq. ft. and the following GL entries are created.
Account | Debit Amount | Credit Amount | Overhead | Notes/Calculation |
01.01.7090 | 3228.67 |
| 3420.00 | Percentage of total floor area = (3420/14300*100) = 23.91608%. |
02.01.7090 | 5352.80 |
| 5670.00 | Percentage of total floor area = (5670/14300*100) = 39.6503%. |
03.01.7090 | 4918.53 |
| 5210.00 | Percentage of total floor area = (5210/14300*100) = 36.4336%. |
00.00.7120 |
| 13500.00 |
| Account is based on Override Credit Analysis. |
GL Allocation - Method GV
The GV method is based on GL account balances.
Use this method if overhead GL accounts are allocated to departments based on sales.
Example
You want to allocate 90% of sales salaries/benefits to each department’s sales expense account 7080 based on sales. Sales salaries/benefits hit overhead accounts 00.00.7010 and 00.00.7020, while sales in each department hit 4010 and 4020.
GL Allocation
Override Credit Analysis | 00.00.7120 |
Starting Code | Ending Code | Matches Code | % to Allocate |
00.00.7010 | 00.00.7020 | * | 90 |
Allocation Basis
Starting GL Code | Ending GL Code | Matches GL Code | Debit Account |
01.01.4010 | 01.01.4020 | * | 01.01.7080 |
02.01.4010 | 02.01.4020 | * | 02.01.7080 |
03.01.4010 | 03.01.4020 | * | 03.01.7080 |
04.01.4010 | 04.01.4020 | * | 04.01.7080 |
The system takes the balance in the account range Allocation line, and multiplies it by the percentage to determine the amount to allocate. Then it takes the account balance in each allocation basis line to determine a percentage for each line, and creates a GL transaction to the debit account on each line, with the balancing transaction hitting the credit account on the first screen.
So if 00.00.7010 had a balance of $40000 and 00.00.7020 had a balance of $10000, the amount to be allocated would be $50000x90%= $45000. If Div 1 had sales of 7000, 2 = 9000, 3 = 3000, 4 = 4000 and 5 = 12000, the GL entries below would get created.
If Override Credit Analysis on the first screen is populated as above (00.00.7120), the following postings would happen.
Account | Debit Amount | Credit Amount | Sales Amount | Notes/Calculation |
01.01.7080 | 9000.00 |
| 7000.00 | Difference between balance and sales = 45000–35000 = 10000 |
02.01.7080 | 11571.43 |
| 9000.00 | Difference between balance and sales = 10000 |
03.01.7080 | 3857.14 |
| 3000.00 | Difference between balance and sales = 10000 |
04.01.7080 | 5142.86 |
| 4000.00 | Difference between balance and sales = 10000 |
05.01.7080 | 15428.57 |
| 12000.00 | Difference between balance and sales = 10000 |
00.00.7120 |
| 45000.00 |
| Account is based on Override Credit Analysis. |
If Override Credit Analysis is blank, the following GL accounts from the GL Allocations screen above would be used in the postings.
Account | Debit Amount | Credit Amount | Sales Amount | Notes/Calculation |
01.01.7080 | 9000.00 |
| 7000.00 | Difference between balance and sales = 45000–35000 = 10000 |
02.01.7080 | 11571.43 |
| 9000.00 | Difference between balance and sales = 10000 |
03.01.7080 | 3857.14 |
| 3000.00 | Difference between balance and sales = 10000 |
04.01.7080 | 5142.86 |
| 4000.00 | Difference between balance and sales = 10000 |
05.01.7080 | 15428.57 |
| 12000.00 | Difference between balance and sales = 10000 |
00.00.7010 |
| 36000 |
| Account is based on GL Allocations |
00.00.7020 |
| 9000 |
| Account is based on GL Allocations |
GL Allocation - Method JC
The JC method is based on the amounts in certain cost codes for specific contracts.
Example 1
You want to charge certain contracts (in contract group CONST, allocation group WARR) a warranty burden of 1% on all labour costs with cost head FIELD, and you want the burden to hit the same cost code, but the AL category, and the GL code __.__.6300. You want the credit to hit a warranty liability account 10.10.6400.
Override Credit Analysis | Contract 10.10.6400 |
Contract Details
Contract Allocation Type | WARR |
Matches Contract Type |
|
Matches Contract Group | CONST |
Cost Code Allocation
Starting Code | Ending Code | Matches Code | Category | % to Allocate |
|
| *FIELD | LA | 1 |
|
|
| MA | 0 |
|
|
| EQ | 0 |
|
|
| SU | 0 |
|
|
| OT | 0 |
|
|
| AL | 0 |
Allocation Overrides
Contract | Section | Activity | Cost Head | Category | Account |
|
|
|
| AL | __.__.6300 |
|
|
|
|
|
|
So if a cost code with a section of 10, activity of 400, cost head of FIELD and a cost category of LA has $60,000 of costs this period, a contract cost transaction for 600 based on the % to Allocate and would hit the same cost code but the AL cost category based on the overrides. This figure will be posted to GL account 10.10.6300, while the credit hits a warranty Liability Acct in 10.10.6400 if the credit was also masked on the first screen.
Account | Debit Amount | Credit Amount | Notes/Calculation |
10.10.6300 | 600.00 |
| (60,000 *1) / 100 =600 |
10.10.6400 |
| 600.00 | Warranty liability account |
If the allocation should hit a different cost head, it will use the same section and activity as the original cost unless they are overridden.
Example 2
You want to allocate small tools or consumables at 0.5% of material cost to a cost head of CONSU, category AL.
Main screen
Override Credit Analysis | Contract 10.10.7120 |
GL Allocation
Starting Code | Ending Code | Matches Code | Category | % to Allocate |
|
|
| LA | 0 |
|
|
| MA | 0.5 |
|
|
| EQ | 0 |
|
|
| SU | 0 |
|
|
| OT | 0 |
|
|
| AL | 0 |
Allocation Overrides
Contract | Section | Activity | Cost Head | Account |
|
| CONSU | AL |
|
|
|
|
|
|
So if a cost code with a section of 10, activity of 400 and a cost category of MA has $120,000 of costs this period, a contract cost transaction for 600 based on the % to Allocate and would hit the cost head of CONSU and AL Cost category based on the overrides. This figure is posted to GL account 10.10.6300, while the credit hits a warranty Liability Account in 10.10.7120.
Account | Debit Amount | Credit Amount | Notes/Calculation |
10.10.6300 | 600 |
| (120,000 *0.5) / 100 =600 |
01.01.7120 |
| 600 |
|
If the allocation should hit a different cost head, it will use the same section and activity as the original cost unless they are overridden.
If there are multiple overrides defined, then the Debit Amount will be pro-rated across the overrides proportionally.
GL Allocation - Method JR
The JR method is based on the revenue on specific contracts.
The JR allocation works the same way as the JC method, except it allocates based on revenue not costs.
Example
Warranty Expense is 2% of contract revenue, a contract with $100000 would have a contract cost allocation of 2000 that would hit either the same cost code as the revenue or the cost codes entered as overrides.
GL Allocation
Starting Code | Ending Code | Matches Code | Category | % to Allocate |
|
|
| REV | 2 |
So if a revenue cost code has $100,000 of Revenue this period, a contract revenue transaction for 2000 based on the % to Allocate and would hit the cost head of REV and blank cost category (Revenue). This figure is posted to GL account 10.10.6300, while the credit hits a warranty Liability Account in 10.10.7120 if the credit was also masked on the first screen.
Account | Debit Amount | Credit Amount | Notes/Calculation |
10.10.6300 | 2000 |
| (100,000 *2) / 100 =2000 |
01.01.7120 |
| 2000 |
|
If the allocation should hit a different cost head, it will use the same section and activity as the original cost unless they are overridden.
GL Allocation - Method JV
The JV method lets you allocate costs from the General Ledger or an overhead contract to many contracts based on costs from other contracts.
Example 1
You want to allocate amount in the Executive Burden GL Account to all contracts based on labour costs. So if there is $10,000 in the GL account 01.01.8300, and contracts that have labour for the month are:
Contract A – $20000
Contract B – $30000
Contract C – $50000
The allocation is costed to cost code 10001burd.AL based on labour costs.
Allocate GL or Contract Costs
Type | Starting Code | Ending Code | Matches Code | Category | % to Allocate |
GL |
|
| 01.01.8300 |
| 50 |
Allocation Basis
Contract | Section | Activity | Cost Head | Category |
|
|
|
| MA |
Allocation Overrides
Contract | Section | Activity | Cost Head | Category | Account |
| 10 | 001 | burd | AL |
|
Analysis | Account | Debit Amount | Credit Amount | Notes/Calculation |
JobA.10001burd.AL | 01.01.8300 | 1000.00 |
|
|
JobB.10001burd.AL | 01.01.8300 | 1500.00 |
|
|
JobC.10001burd.AL | 01.01.8300 | 2500.00 |
|
|
| 01.01.8500 |
| 5000.00 |
|
Example 2
There is $1,000 office expense in the overhead contract ZZ.0001off.OC, and contracts that have materials for the month are:
Contract A – $20000
Contract B – $30000
Contract C – $50000
The allocation is 10% of other costs costed to cost code 10001off.oc based on material costs.
Allocate GL or Contract Costs
Type | Starting Code | Ending Code | Matches Code | Category | % to Allocate |
GL |
|
| ZZ.0001off | OC | 10 |
Allocation Basis
Contract | Section | Activity | Cost Head | Category |
|
|
|
| MA |
Allocation Overrides
Contract | Section | Activity | Cost Head | Category | Debit Account |
| 10 | 001 | off | OC |
|
Analysis | Account | Debit Amount | Credit Amount | Notes/Calculation |
A.10001off.oc | 01.01.8300 | 200.00 |
|
|
B.10001off.oc | 01.01.8300 | 300.00 |
|
|
C.10001off.oc | 01.01.8300 | 500.00 |
|
|
| 01.01.8500 |
| 1000.00 |
|
Processing GL Allocations
GL Allocations Processing on the General Ledger Administration menu lets you extract allocations for reporting, with an option to process the data as a General Ledger Journal.
Field Definitions
Allocation Type
The allocation type (or types) to include in this process.
Allocation Group
The allocation group (or groups) to include in this process.
Financial Period for Transactions
The financial period of the transactions to include in this process.
Process Allocations
Whether to produce an allocation journal as part of this process. If this is not ticked, a report only is produced.
When you select the Process Allocations field, four additional fields appear below it:
Financial Period to Allocate, Transaction Date, Transaction Type, and Post Batch.
Financial Period to Allocate
Post Batch
Use these fields to further define how you wish to process the allocations, such as selecting the financial period to post the journal to, the transaction date and type to use for the journal, and whether to post the batch automatically during the process.
