Rules in Mayday Recharger describe the logic behind how transactions are recharged between your entities. It's a simple process to create the rules, but it’s important to do this with care. Mistakes in your rules can lead to mistakes and oversights in your recharge calculations, and these could cost you more time further down the line.

There are four types of rule in Recharger:

We'll look at these in more detail below.

Recharger creates three 'Don't recharge' rules by default for each entity in the recharge group. These apply to all transactions in that entity (expense, revenue, and balance sheet) so they won't be recharged to any other entity in the group, unless you create rules which supersede them.

You can create an expense rule using the '+ Add new' button under the 'Expense Rules' tab:

This takes you to the New Expense Recharge Rule page:

There are three types of expense rule you can create:

Once you've chosen the type of rule you're creating, you'll need to set up the transaction matchers in section 2 for cost rules or section 3 for cost plus rules. This is described in the Transaction Matching section below.

Section 3 for cost rules or Section 4 for cost plus rules, lets you define which entities should be recharged for the expenses:

You can add whichever entities are required using the '+ Add another entity' button. The figure you enter in the first box is what apportionment of the transaction's value will be recharged. Finally, the last column is the account code the costs will be assigned to in that entity.

For more information please see this helpful video.

You can create a revenue rule using the '+ Add new' button under the 'Revenue Rules' tab:

This will take you to the New Revenue Recharge Rule page:

There are two types of revenue rule you can create:

Once you've chosen the type of rule you're creating, you'll need to set up the transaction matchers in section 2. This is described in the Transaction Matching section below.

Section 4 lets you define which entities should receive the recharged revenue:

You can add whichever entities are required using the '+ Add another entity' button. The figure you enter in the '%' column is what percentage of the transaction's value will be recharged. Finally, the last column is the account code the revenue will be assigned to in that entity.

For more information please see this helpful video.

You can create a balance sheet rule using the '+ Add new' button under the 'Balance Sheet Rules' tab:

This will take you to the New Balance Sheet Rule page:

There are two types of balance sheet rule you can create:

Once you've chosen the type of rule you're creating, you'll need to set up the transaction matchers in section 2. This is described in the Transaction Matching section below.

Section 3 lets you define which entities should be recharged the transactions:

You can add whichever entities are required using the '+ Add another entity' button. The figure you enter in the first box is what apportionment of the transaction's value will be recharged. Finally, the last column is the account code the recharges will be assigned to in that entity.

For more information please see this helpful video.

You can create a Mayday rule using the '+ Add new' button under the 'Mayday Rules' tab:

This will take you to the New Mayday Rule page:

Then you follow these simple steps to set up a Mayday rule:

For more information please see this helpful video.

For all expense, revenue and balance sheet rules, you'll need to define parameters to configure exactly which transactions in that entity the rule will be applied to.

The first option is to apply the rule to all transactions under that entity. Choosing this will mean the rule becomes the default rule for that entity, and it will be applied to all transactions which do not match other rules you've configured. You can only have one rule with this option set - if you wish to change which rule that is, you'll need to edit that rule's configuration first.

The second option is to define matchers to tell Recharger how to identify the right transactions for this rule. You can define as many of these as you'd like, and configure whether to match all or any of them:

You can create matchers based on the following transaction properties:

In the event that a transaction matches more than one rule, Recharger will pick one of the rules based on a set precedence order, shown at the bottom of the page.

Once the transaction matchers are set up, you can define how the matched transactions will be apportioned between other entities in the recharge group. There are two ways of doing this.

You can use the Apportionments page to define commonly-used apportionments. This is handy if you'd like to use the same methodology to apportion several different recharge rules. Doing this means you'll only need to update them in one place if they change in the future. See this article for more info.

When you choose a pre-defined apportionment, the list of entities and the numbers will be pre-filled for you. You only need to set the account codes: this is where the cost from this recharge rule will be posted in that particular entity's accounting system.

Choosing 'Custom' gives you much more flexibility in defining the apportionments.

You can choose whichever other entities you'd like from your recharge group, and then adjust the apportionment percentages using the apportionment and 'total apportionment units' boxes. The 'total apportionment units' is a whole number from which you create fractions using the 'apportionment units' above.

You will then need to set the account codes: - this is where the cost from this recharge rule will be posted in that particular entity's accounting system.

With Recharger, you can split costs and revenues between account codes or tracking categories both within and between entities. If you want to create inter-departmental recharges, follow the steps in 'How to create Intra-entity Recharges'

In the event that a transaction matches more than one rule, Recharger will pick one of the rules based on the following precedence order: