Is there a way to design a GL Automatic Posting Rule around a Code Part Attribute? For example, we have an attribute of “Category” on our Project code parts. I’d like to set up a rule to post projects of a certain Category to a specific cost center. We have thousands of projects and only 5 attribute categories, so I’m hoping to define a rule around the attribute rather than at the individual project code part level. Appreciate any thoughts you have on this.
Question
Code Part Attributes in GL Automatic Posting Rules
+2
Hi,
Sorry, but the automatic posting rule “as is” or out of the box, does not have the ability to use other attributes such as project category to drive the rule. That would require a modification.
Ideally, when possible, configure posting controls to drive the account string correctly when the transaction is created. The other option could be to pre-post those projects to the appropriate cost center. That could be to enter pre-posting at the project / sub project, or a BPA to automate the pre-posting on things like purchase orders, customer orders, or similar.
If you include the posting types that are missing the correct cost centers, we could look at the options available for a given posting type.
Best regards,
Thomas
+1If the goal is to avoid maintaining posting rules at the individual project level, there may be an opportunity to handle the business logic outside of the standard posting rule setup.
For example, with Novacura Flow, you could potentially use the Project Category as the driver for the posting logic and maintain the mapping between Category and Cost Center in one place. The workflow could then determine the appropriate Cost Center based on the project's attribute rather than requiring a separate rule for each project.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.