This section contains the following topics:
How to Set up GL Accounts and Chargebacks
Chargebacks represent the inter-account transfers of investment or service costs to departments. Chargebacks debit (or charge) departments for their shared cost of investments or services that were delivered during a specified period. A chargeback represents the debit-side of an accounting system. A corresponding credit is issued to departments that provide the investment or service crediting them for the work they completed during a specified period.
To process chargeback transactions, set up general ledger accounts and create chargeback rules, such as standard debit rules, credit rules, or overhead rules. The rules you create depend on the type of chargeback processing you want to implement.
Rules drive chargebacks and credits and determine the shared costs of investments and services. A chargeback rule is a set of unique properties that are matched to transactions when debiting and crediting departments. Chargeback rules are composed of:
The following debit and credit rules are supported:
Chargebacks assumes that transactions exist in the system for the associated investments.
Set up the following to work with chargebacks and GL accounts:
For more information, see the Project Management User Guide.
For more information, see the Project Management User Guide.
For more information about managing resources, see the Resource Management User Guide.
Define general ledger (GL) accounts to assign to cost plan details. Later, if you extract the planning data from CA Clarity PPM to an external accounting system, you can use the GL accounts for mapping purposes. You can also import GL accounts into CA Clarity PPM from an external accounting system using XOG.
For more information, see the XML Open Gateway Developer Guide.
Use GL accounts to define time-based GL allocations used in chargebacks.
GL accounts are combinations of main account codes and subaccount codes that are used to categorize accounts. For example, the main Assets account can have a code of 100 and the Asset subaccounts can have a code of 111 for Capital and 112 for Expense.
Verify that an entity exists before creating GL accounts.
Follow these steps:
The GL accounts list appears.
The create page appears.
Defines the first part of the natural account number.
Defines the second part of the natural account number.
Defines the entity associated with the GL account.
Defines the account description.
Defines the account class.
Values:
Defines the account type used for classifying accounts.
Values:
Indicates if this account is active and available for assigning to cost plans.
Indicates if this account is used to charge any costs to designated departments. If selected, be sure to create overhead rules.
Indicates if this account is used for capital expense.
Indicates if this account is used for noncash expense.
You can delete a GL account not referenced by any cost plan or transaction.
Follow these steps:
The GL account properties appear.
Defines the first part of the natural account number.
Defines the second part of the natural account number.
Defines the entity associated with the GL account.
Defines the account description.
Defines the account class.
Values:
Defines the account type used for classifying accounts.
Values:
Indicates if this account is active and available for assigning to cost plans.
Indicates if this account is used to charge any costs to designated departments. If selected, be sure to create overhead rules.
Indicates if this account is used for capital expense.
Indicates if this account is used for noncash expense.
Chargeback rules determine which GL accounts get debited and credited for costs associated with investments or services.
You can configure the unique codes—Allocation Code (for standard rules) and Resource Credit Code (for credit rules)—to auto-populate.
For more information, see the Studio Developer’s Guide.
A standard rule can be globally applied to many investments or services when the same chargeback rules can be used to debit departments for costs.
When setting up chargebacks, investment or service managers can choose to apply standard-based rules (set up by a finance manager) or investment-based rule (set up by the investment or service manager).
Follow these steps:
A list of existing standard rule headers appear.
The create standard allocation rule page appears.
Defines the unique code used to classify the chargeback (or standard debit) rule. Required.
Defines the entity associated with this chargeback rule. Required.
Custom properties. Available for selection only if lookup values have been defined in Studio.
For more information, see the Studio Developer’s Guide.
Defines the charge code associated with the chargeback rule.
Defines the input type code associated with the chargeback rule.
Defines the transaction class associated with this transaction rule.
Specifies whether you want to charge any remaining costs to overhead. If you select this option, be sure to define overhead chargeback rules.
Default: Cleared
Indicates if the standard rule is available for chargebacks. Required.
Values:
To delete a standard rule, select the rule and click Delete.
Follow these steps:
The standard rule properties details appear.
The main properties appear.
Defines the unique code used to classify the chargeback (or standard debit) rule. Required.
Defines the entity associated with this chargeback rule. Required.
Custom properties. Available for selection only if lookup values have been defined in Studio.
For more information, see the Studio Developer’s Guide.
Defines the charge code associated with the chargeback rule.
Defines the input type code associated with the chargeback rule.
Defines the transaction class associated with this transaction rule.
Specifies whether you want to charge any remaining costs to overhead. If you select this option, be sure to define overhead chargeback rules.
Default: Cleared
Indicates if the standard rule is available for chargebacks. Required.
Values:
Credit rules identify the departments that are credited for the cost of delivered investments or services. Departments are credited based on the attributes of the resources assigned to the delivered investments or services. Accordingly, the location and department assigned to a resource must match the location and department assigned to the department receiving the credit.
Follow these steps:
A list of existing rule headers appears.
The create page appears.
Defines the unique code used to classify the credit rule.
Indicates if the credit rule is active, inactive, or on hold.
Defines the entity associated with the department receiving the credit.
Defines the location associated with the department receiving the credit.
Defines the department receiving the credit.
Defines a resource class associated with the credit rule.
Defines the transaction class associated with the credit rule.
To delete a credit rule, select the rule and click Delete.
Follow these steps:
The credit rules properties details appear.
The main properties appear.
Defines the unique code used to classify the credit rule.
Indicates if the credit rule is active, inactive, or on hold.
Defines the entity associated with the department receiving the credit.
Defines the location associated with the department receiving the credit.
Defines the department receiving the credit.
Defines a resource class associated with the credit rule.
Defines the transaction class associated with the credit rule.
GL Allocations identify the GL accounts and departments that are debited (for standard rules) and credited (for credit rules). GL allocations also indicate the percentages of the cost that are charged or credited.
The allocation percentage for a credit rule for any time period must always equal 100 percent.
Follow these steps:
The rule property details appear.
The rule detail page appears.
Defines the GL account associated with the rule.
Defines the department associated with the rule. For credit rules, indicates the department receiving the credit. For standard rules, indicates the department being charged.
By default, an empty row with fields for start and finish dates, and percentage appears.
When the rules for standard or debit rules charge remaining costs to overhead, overhead rules determine which GL accounts are debited. Overhead rules can contain only one set of GL allocations. No header information is required.
To charge departments for overhead costs, set up the following:
Follow these steps:
A list of existing rules appears.
The create page appears.
Defines the entity associated with the rule.
Defines the GL account associated with the rule.
Defines the department associated with the rule.
To delete an overhead rule, select the rule and click Delete.
Follow these steps:
The rule detail page appears.
You need the Financial Maintenance - Financial Management access right to set up resource credits for posting to the general ledger account.
Most IT departments charge back credits to the group for which they worked to allocate expenses and work. A resource credit indicates which department, entity, location, transaction class, or resource class receives the credit. Incidents support resource credits.
You can remove GL allocations from:
You can remove GL allocations only if they are not referenced referenced in chargebacks and cost plans.
Follow these steps:
The rule property details appear.
Follow these steps:
The rule details page appears.
Use the Messages page to view and monitor chargeback errors and warnings:
Once the errors and warning are corrected, messages are removed from this page. The following table includes some of the more common messages and their resolutions:
|
Type |
Message |
Possible Resolution |
|---|---|---|
|
|
[Error disbursing debit charges (overallocation).] |
|
|
|
[Error disbursing overhead charges (overallocation).] |
|
|
Warning |
No Chargeback Type set on investment. |
Set the chargeback options for the investment. |
|
Error |
No credit rule allocation details in range of transaction date. |
Define a GL allocation in the credit rule for the transaction date. |
|
Error |
No debit rule allocation details in range of transaction date. |
Define a GL allocation in the debit rule for the transaction date. |
|
Error |
No matching credit rule found. |
Do one of the following: If no credit rule exists, create a credit rule. Contact the finance manager. If a credit rule exists, compare its criteria with the transaction, and adjust or create a rule to match the transaction. You can also adjust the transaction to match the rule. Contact the finance manager and investment manager. |
|
Error |
No matching debit rule found. |
Do one of the following. If no debit rule exists, create a debit rule. Contact the investment or service manager. If a debit rule exists, compare its criteria with the transaction, and adjust or create a rule to match the transaction. You can also adjust the transaction to match the rule. Contact the finance manager and investment manager. |
|
Error |
No overhead rule found. |
Do one of the following: Create an overhead rule. Contact the finance manager. Clear the option to charge remaining costs to overhead on the debit rule. |
|
Error |
The selected Department, Location combination is invalid. |
Verify that the properties of the credit rule indicate a valid department and location combination. |
|
Warning |
Unable to credit full amount of charge. |
Review the credit rule and verify that the GL allocation equals 100 percent for the specified transaction date. For more information, contact the finance manager. |
|
Warning |
WIP transaction expense type [Capital Expense|Depreciation] does not match investment billing expense type [Capital Expense|Depreciation]. |
Do one of the following: Set the Expense Type of the WIP Transaction to match the Billing Expense Type of the investment. Contact the finance manager. Set the Billing Expense Type of the investment to match the Expense Type of the WIP Transaction. Contact the investment or service manager. |
Follow these steps:
A list of chargeback errors and warnings appear.
Displays the name of the investment used in the transaction.
Displays the charge code type associated with the investment.
Displays the transaction date.
Displays the type of expense.
Displays the resource that incurred cost against the investment.
Displays the rule on which the error or warning occurred.
Indicates if this is a credit or debit rule.
Indicates if the rule is standard or investment-based.
Displays the date the Generate Invoice job was run.
Displays the user who initiated the Generate Invoice job.
Displays that the error message is on hold.
Displays the error or warning.
Rules drive chargebacks and credits and WIP transactions process them. These rules are used during transaction processing to apply charges or credits appropriately to designated departments. Department managers can view their charges and credits using the following tools:
The following chargeback rules are supported:
When setting up debit rules, as the investment manager or service manager, you can base charges on standard rules or investment-specific rules.
Debit and credit rules are composed of a header and a set of time-based GL allocations.
Rule Headers
A header uniquely describes the rule and is used during financial processing to match to transactions. Some examples include:
A debit rule DB-800 is described as charge code Expenses and transaction code techSup. Another debit rule DB-900 is described as charge code Expenses and transaction code SysMaint.
A credit rule CR-000 is described as location Santa Clara and resource class ENG. Another credit rule CR-111 is described as location Bournemouth and resource class ENG.
The GL allocation code used to create and identify rules can be configured to auto-populate.
For more information, see the Studio Developer’s Guide.
Time-based GL Allocations
Debit and credit rules are composed of a header and a set of time-based GL allocations. Time-based allocations determine how much departments are debited or credited for costs during a time period. Chargeback rules are based on the following:
Retail Banking of Forward Inc commissioned the development of a mortgage application whose systems are shared by Retail Self Services and Retail Premier Accounts. Retail Banking is using the Chargeback feature to allocate costs incurred by IT for this development project.
This project required expertise from application developers, analysis expertise from Retail IT technical operators, and technical securities expertise from Investment Banking IT. Retail Banking IT set up investment-specific debit rules and credit rules to charge back costs to departments that commissioned the work and credit those that provided the work.
Crediting Multiple IT Departments for Work Completed
The Retail IT finance manager set up a credit rule to allocate 100 percent credit among three provider departments:
Retail Application Development is doing the bulk of the development work and is credited 50 percent for the first three months and 80 percent for the remaining three months.
Retail Technical Operation is providing consultation at the beginning of the project and is credited for 25 percent for the first three months, and 10 percent for the remaining three months.
Investment Banking IT is also providing consultation at the beginning of the project and is credited for 25 percent for the first three months and 10 percent for the remaining three months.

Debiting Multiple Business Units for Commissioned Work
The Retail IT project manager for this project set up a debit rule to charge back 50 percent each quarter to the Retail Self Service department and Retail Premier Accounts department.

With flexible chargeback rules, Forward Inc can allocate charge costs appropriately to the departments benefiting from the services IT is providing. It also enables IT departments to get credit for the work they deliver.
Managing chargebacks from investments involves setting up chargeback options. You can select from the following chargeback options or types:
Investment-specific debit rules determine how much of the total cost each consuming department is charged for investments or services.
If you charge remaining costs to overhead, the amount debited to consumer departments does not need to equal 100 percent of the costs. Your finance manager is responsible for setting up any standard, credit, or overhead rules, and for verifying that debits and credits equal. On the Chargebacks page for an investment or service, you can view a list of any debit rules defined for the investment or service. From this page, you can drill down and view, add, or update GL allocations for the selected debit rule.
Bill Expense identifies how costs are booked. Bill Expense is also used to match with transactions to determine whether investment costs are invoiced or not. Suppose your company has a policy to charge back only investments that are considered capital expenses. Suppose further that you manage e-mail servers. Companies consider servers and other mission-critical hardware to be depreciable and handle them differently during transaction processing. Any capital expense transactions that are processed against your e-mail servers are ignored and not charged back.
Chargeback options determine how and when charges are generated during invoicing. Set up chargeback options to process chargebacks.
Chargeback type determines whether an investment-defined rule or a standard debit rule is matched to transactions during financial processing.
Important! Select a chargeback type to generate invoices for matched transactions.
Follow these steps:
The properties page appears.
The chargebacks options page appears.
Defines the chargeback type for the investment or service.
Values:
Indicates how costs are accounted for and whether they are considered for invoicing when transactions are processed
Values:
Debit rule properties uniquely describe a rule and are used to match transactions during financial processing. An overhead rule must exist to charge any remaining costs to the full GL account.
If a rule has not been used to process transactions, you can delete a debit rule.
Follow these steps:
The properties page appears.
The chargeback debit rules page appears.
The create page appears.
Defines the unique code used to classify the debit rule for this investment.
Defines the charge code associated with the debit rule.
Defines custom properties associated with the debit rule. You can select custom attributes only if lookup values have been defined in Studio.
For more information, see the Studio Developer’s Guide.
Defines the input type code associated with the debit rule.
Defines the transaction class associated with the debit rule.
Indicates if the debit rule is available for chargebacks.
Values:
Indicates whether to charge any remaining costs to overhead. Select this check box to charge any remaining costs to overhead.
Follow these steps:
The properties page appears.
The debit rules page appears.
The GL allocations properties main page appears.
Defines the unique code used to classify the debit rule for this investment.
Defines the charge code associated with the debit rule.
Defines custom properties associated with the debit rule. You can select custom attributes only if lookup values have been defined in Studio.
Defines the input type code associated with the debit rule.
Defines the transaction class associated with the debit rule.
Indicates if the debit rule is available for chargebacks.
Values:
On Hold. If no active rule can be matched, the rule can be considered and matched to a transaction.
Indicates whether to charge any remaining costs to overhead. Select this check box to charge any remaining costs to overhead.
Once you have created debit rules, you can define the GL allocations that determine how consumer departments are charged for costs. A GL allocation is composed of a full GL account and a set of allocation rules. The rules represent the percentage of the allocated cost for a specified time period. A full GL account is a combination of the natural GL account and department.
For each GL allocation, you can evenly distribute chargeback percentages across all fiscal time periods, or specify different percentages for each time period. For example, if your company sets up its fiscal time period on a quarterly basis, you can specify 100 percent allocation for the first quarter. You can then specify 50 percent in the remaining quarters. The remaining costs for the last three quarters can be charged to another department or to overhead.
You can remove GL allocations from debit rules as long as they are not referenced in financial plans or chargebacks.
Follow these steps:
The properties page appears.
The chargebacks debit rules page appears.
The GL allocation detail list page appears.
The create GL allocation detail page appears.
The GL allocation properties details page appears.
The entity fiscal time period type determines the time periods available for selection.
You can review transactions processed for your investments or services to verify that they were posted correctly. If you find errors that require reversals, you can reverse charges on selected transactions or on all listed transactions.
When you reverse charges, the allocated charge is removed from department invoices. The charges do not appear when invoices are generated next or when the department manager manually regenerates an invoice. If the invoice is locked or approved when you reverse the charges, this change is reflected in future invoices.
Follow these steps:
The properties page appears.
The chargebacks transactions page appears.
The selected transactions indicate that charges were reversed.
Each department charged for the cost of delivered investments and services receives an invoice for each time period. You can view invoices periodically to monitor charges, make corrections, approve or reject invoices, and manually regenerate invoices.
The investment or service manager sets up the debit rules that identify the departments that get charged. The rules also indicate the percentage of the cost they are debited.
To receive and submit, approve, or reject an invoice, set up the following:
Or
Typically, the finance manager and department manager work together to approve invoices. The finance manager submits invoices for approval and the department manager approves or rejects invoices. Department invoice access rights determine the users who can do invoice-related tasks.
Use your company policies and best practices to identify the roles responsible for invoices and to determine cutoff periods for submitting and approving invoices. The following describes the approval process:
Delegated invoice approval enables sub departments to view and approve their own invoices. Delegated invoice approval is determined when setting up departments.
When sub departments are given delegated invoice approval, invoices are generated for each sub department and the parent department. This condition applies if debit rules exist and transactions are posted against them. Sub department charges are not rolled up to the parent.
When sub departments do not have delegated invoice approval, any charges posted against these sub departments are rolled up into the invoice of the parent department.
Parent departments must have delegated invoice approval to delegate invoice approval to any of their sub departments. If the top-level parent department does not set delegated invoice approval, no sub department in that branch can view or approve invoices. All charges are rolled up to the top-level parent department.
Consider the following organizational structure and the effect delegated invoice approval has on each department:

The Retail Banking business unit
Delegates invoice approval to its two sub departments, Self-service Banking and Premier Customer Accounts. An invoice for the Retail Banking business unit is generated when transactions are posted against the business unit.
The Self-service Banking department
Does not delegate invoice approval to its two sub departments, Marketing and Customer Service. An invoice is generated for the Self-service Banking department when transactions are posted against it. Any charges posted against Marketing and Customer Service departments are rolled into the Self-service Banking invoice. The Self-service Marketing and Customer Service departments do not receive invoices.
The Premier Customer Accounts department
Delegates invoice approval to its two sub departments, Marketing and Customer Service. An invoice is generated for the Premier Customer Accounts department when transactions are posted against the department. The Premier Accounts Marketing and Premier Accounts Customer Service departments also receive their own invoice when transactions are posted against their department.
Each line item in an invoice shows the aggregate charges of the top-level parent investment or service in a hierarchy. You can drill down and view the detailed charges of the parent and any child investment involved in transactions during the invoice time period.
Refer to the following documents to learn how to work with charges in investment or service hierarchies:
The Retail Self-service department at Forward Inc manages a product named Self-service Banking. This product is the top-level parent to several other child investments, such as the Online Bill Presentment (OBP) system and technical support. When viewing invoices, department managers only see the aggregated charges of the top-level parent. For example, the $4,190.00 for Self-service Banking represents total charges for any investment in the hierarchy involved in a transaction during the invoice period.
Department managers can view detail charges on each investment in the hierarchy by clicking the amount or total amount.
Occasionally you can see charges that are incorrect and require some adjustment or reversal. You can reject the invoice and request an adjustment. The following are examples of adjustments you can request:
Contact the investment or service manager and request an adjustment to your debit allocation percent.
Contact your financial manager to create a WIP adjustment and modify the transaction as needed, such as increasing or decreasing the rate, cost, or units.
Contact your investment or service manager, or finance manager to reverse charges.
Adjustments or reversals to transactions or debit rules trigger adjustments to other departments sharing in the cost of the investment. For example, if your allocation percentage reduces by 5 percent, other departments pick up those additional charges. If the total cost is discounted for one transaction, then all departments sharing the costs also receive an adjustment in their charges.
Any adjustments or reversal made to locked or approved invoices is reflected in the next unlocked invoice or future invoice.
Department managers can view a list of invoices generated for their departments. Finance managers can view all generated invoices, and drill-down and view details and transaction information.
Department managers can view their invoices from department invoice pages.
Follow these steps:
To view a department-specific invoice.
The list page appears.
A list of invoices for your department appears. You can view invoice status and amount.
Finance managers can view all chargeback-related invoices from financial management invoice pages.
Follow these steps:
To view all invoices.
The list page appears. You can view invoice status and amount.
You can view invoice details, prior period adjustments, and the invoice amount. You can also approve or reject invoices depending on their state.
Follow these steps:
The properties page appears.
Displays the investment from which the charges originated.
Displays the amount of the charge for the specified time period. Click this link to view transaction details.
Displays the amount of an adjustment that occurred during a previous time period. If zero, then no prior period adjustments were made. Click this link to view adjustment details.
Displays the total amount of the charges less adjustments for the specified time period. Click this link to view transaction details.
Indicates whether you have subscribed to a service. If you have subscribed to a service, a checkmark is displayed.
Key information includes:
Indicates if the transaction is a work-in-process (WIP) or an adjustment.
Displays the amount of the transaction.
Displays the percentage charged to service.
Example: 100 percent indicates that one service is using the investment and 50 percent indicates the investment is shared between two services.
Displays the scaled dollar amount based on the percentage charged to the service.
Your finance manager typically submits invoices for approval. Submitted invoices are automatically locked and have a status of "Submitted". Submitted invoices can be recalled, approved, or rejected.
Follow these steps:
Your finance manager typically locks and unlocks invoices.
Use the department invoice items page to lock and unlock invoices.
When an invoice is submitted, it is automatically locked. When an invoice is locked, transactions cannot be added to the invoice. If you have rights to submit invoices, you can temporarily unlock and regenerate last-minute changes.
Follow these steps:
The department manager typically approves or rejects an invoice.
When an invoice is approved, you cannot recall or take any other action on the invoice. Any adjustments or reversals made to the invoice after approval are included with the next unlocked or future invoice.
When an invoice is rejected, WIP adjustments or changes to debits rules can be made to correct charges. Contact your finance manager for assistance with WIP adjustments.
Follow these steps:
The invoice status changes to "Approved".
The invoice status changes to "Rejected".
Invoices are updated continually during scheduled runs of the Generate Invoice job. However, you can manually update an invoice in between scheduled runs and view recently added transactions.
If a recalculation affects multiple invoices and all affected invoices are unlocked, the invoice is updated. Recalculations are ignored if any invoice affected by the change is locked. If a recalculation is not possible, a message appears letting you know.
Follow these steps:
A progress bar appears during the regeneration process. When complete, the recalculated invoice appears.
You can change the status of an invoice back to its submitted state by recalling it.
Follow these steps:
The invoice status changes to the "Recalled" state.
A recovery statement tells departments how much of their incurred costs can be recovered from the departments who benefited from services provided. A recovery statement is similar to a company income statement—only for departments.
Incurred costs are charged to the departments that receive services. Department managers can view their charges from an invoice.
Only departments that provide services can view department recovery statements. The following must be set up:
See the IT Service Management User Guide for more information.
Recovery statements are generated with invoices during scheduled runs of the Generate Invoice job.
Forward Inc offers its business units a wide variety of IT supporting services, including email support, desktop support, and network support. The services are vital for each business unit to maintain their lines of business. Each of these departments are charged for those services. Each department that delivers services receives credit for work performed.
Approved Invoices Charge Costs to Departments that Benefit from Services
Department invoices are generated, reviewed, and approved on a quarterly basis by the departments that benefit from services delivered to them. Corporate Human Resources has subscribed to several IT services and has agreed to accept charges for a portion of these services. The Human Resources department has approved an invoice that totals $7,400.
Charged Costs Translate into Credit for Departments that Deliver
The IT Delivery Services department receives credit for services provided. The department manager can view incurred costs and credits by viewing the department recovery statement. This statement shows that some charges were approved and the department has recovered $7,400 so far. Other department managers have yet to approve their charges. The charges appear as recovery variance.
On a recovery statement you can view a summary of all your incurred costs, recovered costs, and credits sorted by your services.
Follow these steps:
The list page appears.
The properties page appears.
The department recovery statement appears.
A list of investments owned by the department appear.
Displays the name of the investment owned by this department and offered as a service to other departments.
Indicates if the investment is a service or some other type of investment.
Displays the total cost incurred to-date by this investment that was charged to other departments. Click this value to drill down to view transaction details.
Displays the total charges approved to-date by departments charged for this investment. This amount represents the total costs recovered to-date by this department. Click this value to drill down and view transaction details.
Displays the difference to-date between incurred costs and recovered costs. This amount represents the total amount this department is expecting to recover.
Displays the total possible credit this department can receive. Click this value to drill down to view transaction details.
Displays the difference to-date between recovered costs and credits.
You can view recovery statement details to view transaction details.
Follow these steps:
A list of investments appears.
A list of the processed transactions affecting this recovery statement appears.
Displays the name of the investment from which costs were incurred.
Displays the name of the department charged for costs.
Displays the date of the transaction.
Displays the total incurred costs.
Displays the GL allocation defined in credit rule by your finance manager.
Displays the scaled amount as per the GL allocation percentage.
|
Copyright © 2013 CA.
All rights reserved.
|
|