Skip to main content

How to create ad-hoc rules

Written by Griff

Occasionally you may have recharge scenarios which are one-off, occur infrequently, or are difficult to codify into a rule set. To cater to these situations, you can create "Ad-hoc" rules from within the Recharge flow. These follow the same logic as regular rules, meaning all the configuration and apportionments are available to you, but they apply only to a specific transaction (or set of transactions), and only apply to that specific recharge.

Creating an Ad-hoc Rule

Begin by creating your recharge from the Recharges dashboard:

If you click into the relevant recharge you will see the Transactions review page:

Find the transactions you want to create an ad-hoc rule for and select them using the checkbox on the left hand side. Once you select 1 or more transactions, a menu will appear with the the option to create an ad-hoc rule:

Note: if you want to create an adhoc for more than one transaction, they need to be from the same entity and of the same type (revenue / expense / balance sheet)

Clicking the create new ad-hoc rule button will open a modal window for you to configure the rule:

This will be pre-configured with the rule type (i.e. an expense rule for an expense transaction, revenue rule for an income transaction and so on) - for expense transactions, you can choose "Cost Plus" from this menu to add a markup.

Then you simply need to define how the transaction(s) should be apportioned between the entities in your group, using either a custom apportionment or one of your pre-defined apportionments.

The name has also been pre-filled for convenience - you can update this if you wish. When you save the rule, it will be applied to the transaction(s) selected and the recharge will automatically update.

Once you have finished creating your ad-hoc recharges, and reviewed your other recharge transactions you can continue through the recharge process to eventually post to your accounting file.

Refer to: How to post recharges for more information.

Note: Due to a limitation of the Xero API, ad-hoc rules won't be retained if the source transaction is updated in Xero. If you need a rule to apply across edits to transactions or over multiple recharge periods, it's best to create a regular recharge rule.

Did this answer your question?