Each branch in a Method has one action. The action decides what happens to the rows that the branch catches. To see it, select the branch card on the 2. Factor Assignment tab. The action shows in the right panel, under "Action for:" and the branch name.

For how to build branches and conditions, see Build and edit a Method.

Both actions also have Set Field Values and Set Justification. If you change the action type, Avarni clears the factor or the factor set and sets the status back to Pending.

The list shows factors of the Method's Unit type. It includes your organisation's custom factors from Settings › Emission Factors. You cannot type a factor value into a branch.

The list stays disabled until Avarni knows the unit type. Set the Unit type on the 1. Calculation type tab. Or add an Input Unit condition to the branch, with units that are all of one unit type.

The Factor list has a filter dialog, Emission factor search filters. It filters by Factor Series, Regions, Include Sub-regions, Years and GHG Categories.

After you choose a factor, the filters default to that factor's series, year, region and GHG category. The list then shows only factors like the one you chose. To see other factors:

Default sets the filters back to the defaults. Cancel closes the dialog with no change.

Select Clear Factor (the X next to the factor). Rows on a Set Factor branch with no factor get no factor. The branch's Set Field Values still apply to them.

On a Set Factor branch, the Confirm, Flag and Exclude buttons stay disabled until you choose a factor. Until then, the status shows "Unmapped". Avarni applies a status only to rows that get a factor.

After you choose a factor, select a status. Every row the branch maps gets that status. To go back to Pending, select the active status again. The default is Pending.

Set Field Values sets fields on each row that the branch catches. The screen says: "Provide a value for fields to be set to in this action. Leave empty to fall-back to values in your uploaded file."

The rule is:

Use GHG Category on a Method with a fixed GHG category. On a Method set to Auto-select, the GHG category comes from the matched factor.

A branch cannot set the unit, amount, date, description, supplier or country. Set the status with the status buttons, not in this section.

At import, Avarni checks that the facility is in your organisation and that the entity operates it. If a check fails, the import stops with an error. See Troubleshoot a Method.

On a Set Factor branch, yes. They apply whatever the status, also to excluded rows and to rows with no factor.

On a Map Factors with AI branch, they apply only to rows that the AI matches to a factor. Rows with no match keep the values from your file. To set Entity or Facility by rule, use a Set Factor branch.

The AI selects one factor for each row from the Factor set you choose. It reads only the fields you tick under Select AI matching fields.

Rows with the same values in the ticked fields get one prediction together. If no set is available, Avarni shows "No factor sources found that can be mapped to the selected input unit type and GHG category."

With Use saved mappings on, Avarni first looks for an earlier row, from a previous import, with:

If it finds one, the new row takes the status of the most recent such row. It also takes the factor with the same name from the branch's Factor set, for the new row's year and region. Only the other rows go to the AI. Cases where AI matching will not be used opens a summary of these rules.

Year mappings has one row for each calendar year in the Method's date range. For each year, set:

A green line means the factor year and the data year are the same. An amber line means they differ.

Avarni fills in defaults: the closest factor year at or before each data year, the first eligible region, and Exact Match Else Fallback. Avarni regenerates the year mappings, and drops your edits, when you change the factor set, the GHG category filters, the Unit type or a year of the date range.

The Confirm, Flag and Exclude buttons are always available on this action. The status applies to rows that the AI matches. Rows matched by a saved mapping take the earlier row's status. Rows with no match get no factor and stay unmapped.

Exclude is a status, not a GHG category.

Put the branch above any other branch that could catch the same rows. Avarni gives each row to the first branch that matches it.

Set Justification has one field, Justification (optional). Use it to record why the branch exists, so the next person who edits the Method understands it.

An electricity upload has one row for each bill. The NMI is in a custom field called "NMI". The Method has Scope 2, a fixed GHG category and an energy unit type.

A bill for NMI 4103765432 with 12,480 kWh gets the NSW and ACT factor and the facility Sydney office. Entity fills from the facility. A bill for a new NMI goes to the Fallback branch and is flagged for review.

A freight file has one row for each consignment, with a description such as "Linehaul Sydney to Brisbane, B-double". The Method has Scope 3, a fixed GHG category for transport and a mass-distance unit type such as tonne-km.

The Fallback branch uses Map Factors with AI:

The AI gives road rows a road freight factor and rail rows a rail freight factor. After you confirm these rows, the next freight import reuses their factors through saved mappings.

A fuel card file has one row for each transaction. The card number is in a custom field called "Card Number". One card belongs to a subcontractor who reports its own fuel. The Method has Scope 1 and a volume unit type.

Branch 1 is first, so the subcontractor's diesel rows never reach branch 2. A row with the description "PREMIUM DIESEL" goes to branch 2, because DIESEL is a whole word in it.

A change to an action applies only to imports that start after you select Save. Rows you already imported keep their factor, status and field values. For what to do instead, see Troubleshoot a Method.