We are going to be implementing Financials soon and our plan is to create Small Enhancement and Maintenance projects per team then have the teams add whatever tasks that are needed to track those smaller efforts.
Each task would be tied to 1 department but there would be many departments that would need to be charged back in the same project. Based on what I've read, you can create investment chargeback rules but based on a percentage of the actuals, not by specific task.
Does anyone know if there is a way to chargeback at the task level?
The simple answer is that you cannot charge costs from a Task directly to a Department; that can only be done at the Project level. However, the real answer is predicated on what you and your organization REALLY mean by Charge-back. In other words, are you limited to only using the standard Clarity charge-back functionality, or do you simply need to know which departments are incurring which costs as a result of project activity.
In your scenario, you might want to use the OOB functionality where an entire project is allocated on a percentage basis for most projects. But, for your maintenance projects, set up charge codes that correspond to your Departments. Then, with reporting you can combine the costs allocated via the OOB charge-back functionality with the costs associated from the Charge Codes to get a total cost to a Department. And, one of the advantages of using Charge Codes for such cost capture is that you get explicit costs as opposed to a percentage allocation.
Another advantage of using Charge Codes for more sophisticated cost capture is that it allows asymmetric cost capture. For instance, if within a development project certain specific activities are being funded by a given department, you can use charge codes to show those cost charges to that department.
Another alternative might be to create a custom attribute on the Task that uses the Department look-up (especially useful when there might be multiple departments responsible for the activity). Again, reporting can be used to combine these costs with standard project costs. The disadvantage to this approach is that the custom attribute will not be in the WIP table, with the controls associated with the WIP table.
The most important element in a solution is a focus on the end result that is desired, and not being constrained by the limitations of the OOB configuration.