A classification rule tells Avarni how to treat a group of general ledger transactions. It sets the emission factor, the GHG category and the review status.
Rules live inside one assessment. They do not carry to the next year.
Create a rule
Go to Assessments and open your assessment.
Select General Ledger.
Select Rules, then Add rule.
Name the rule, set the conditions, then set the actions.
Two shortcuts save time:
From a transaction. Select a row and create a rule from it. Avarni fills in the account name, description, supplier, country and scope from that row.
From your filters. Filter the ledger to the transactions you want, then select Create Rule from Filters.
What a rule can set
Action | Effect |
Factor | The emission factor applied to matching transactions |
GHG Category | The Scope 3 category. Scope follows from the category |
Status | Pending, Flagged or Confirmed. To exclude transactions, set the GHG Category to Excluded instead. |
Justification | Free text explaining why. Your auditor reads this |
Split Record | Divides the transaction across up to 10 segments by percentage |
A rule cannot set the entity or facility. General ledger transactions do not appear in the Emissions Hub, so they cannot be edited there either. To attribute transactions to an entity or facility, add an entity or facility column to your ledger file before you upload it. See Upload your general ledger.
Split a transaction across categories
Use Split Record when one account holds spend that belongs in more than one place.
Add a segment per category and set the percentage for each. The percentages must total exactly 100.
How do I set up a split?
In the rule form, turn on Split Record. It replaces the actions section.
Select Add segment for each share of the spend. You can add up to 10 segments.
For each segment, set:
Allocation: the percentage, as a whole number.
GHG Category: segments can take different categories, including Scope 1 and Scope 2 categories.
Factor: a spend-based factor.
Emission Status: Pending, Flagged or Confirmed.
Justification: why this share and this factor are right.
Check that the chip above the segments reads 100% balanced.
Save the rule.
Avarni does not fill the remainder for you. If the allocations do not total 100, the rule does not save.
Example: a travel account
Your Travel account holds flights, hotels and meals. A sample of invoices shows that about 55% of the spend is flights, 30% is hotels and 15% is meals.
Create a rule that matches the Travel account, turn on Split Record, and add three segments:
Segment | Allocation | GHG Category | Factor |
1 | 55% | Business travel | A spend-based factor for air travel |
2 | 30% | Business travel | A spend-based factor for hotel stays |
3 | 15% | Purchased goods and services | A spend-based factor for food and drink |
A $1,000 transaction in that account becomes three records of $550, $300 and $150. Each record is calculated with its own factor.
What does a split transaction look like on the General Ledger screen?
The original transaction stays in the list, marked as split in its category, factor and status columns. Its emissions are the sum of its segments. It is not counted twice.
Expand it to see one row for each segment. Each row shows its segment number, its percentage, its share of the amount and its justification.
How do I work out the percentages?
Base them on evidence, such as a sample of invoices, a breakdown from the supplier, or an allocation your finance team already uses. Write the basis in each segment's Justification. Your auditor will ask for it.
Order decides everything
Rules run in order from the top, and the first rule that matches a transaction wins. Later rules never see it.
Put your narrow rules above your broad ones. A broad rule at the top takes the transactions your specific rules were written for.
To reorder, drag the rules in the list. New rules are added at the bottom.
See what a rule will do before you save it
Avarni previews the effect while you build the rule. It tells you how many transactions the rule will apply to, and how many it will reassess because they currently match a different rule.
If the preview says the rule will not affect any transactions, your conditions are too narrow. See What each rule operator does.
Editing or deleting a rule
Avarni reassesses the affected transactions automatically. You do not reload anything.
Limits
A rule can match on at most 100 values in total. A condition using a keyword list counts each keyword separately, so a rule listing 60 suppliers and 50 keywords exceeds the limit.
If you hit it, split the rule in two.