When Avarni reads an invoice it pulls out two things: the line items, and the invoice total. It then adds up the spend on the line items and compares that sum against the total.

Your emissions are calculated from consumption, not from spend. The spend comparison is a check. If the line-item spend adds up to the invoice total, Avarni captured every line, which means it captured every line that carries consumption.

That comparison is the Completeness column, and it is the only thing you need to read to know which documents to open.

Each document shows the extracted spend against the invoice's current charges, and a chip with the difference.

Avarni compares against current charges, which is the amount due less any balance brought forward. A balance carried over from last month does not count against you.

Do not open them one by one.

You can update 500 documents at a time.

If a run of documents all show the same percentage, that is one fault repeated, not many faults. Fix it once across the batch instead of opening each document.

Select View in emissions hub from the document list. You now have every extracted row across every document in the batch, and you can filter and act on all of them together.

Open a document. The header shows Sum of Spend Extracted, with the extracted figure against the target.

Hover the difference to see the working: line items extracted, amount due, balance brought forward, current charges.

Underneath it, Avarni tells you which way to look:

The usual culprits, all of which look like a line item but are not:

Select the row in the Activities list and select Delete. You can also select a highlighted region on the invoice image to jump to the row it produced.

To fix it across a batch: select View in emissions hub, open Filters, go to Description, select the description that is being duplicated, and apply. Select the rows and use the bulk delete button in the table footer. You will be asked to type DELETE.

Select a row of the same kind, select Clone, then edit the copy to match the line that was missed.

If there is nothing to clone, select Add activity and fill it in.

Supply and connection charges arrive as line items, usually described as other charges and priced per day. They are real spend, so they belong in the completeness check, but they carry no consumption.

Depending on how Avarni read a charge, the charge can get a unit and an emission factor, and then it adds emissions. Exclude them instead of deleting them, so the completeness check still reconciles.

Use the Exclude button on the status bar at the foot of the activity.

To exclude them across a batch: in the Emissions Hub, use the group button and group by Activity Class, then exclude the whole group in one action.

There are two reasons, and they need opposite responses.

The document is not a utility invoice. If your invoices arrive through an integration, everything in the account comes through, not only the ones that matter. Delete the document.

The layout was not recognised. If a vendor's invoices consistently return nothing, that is ours to fix. Tell us. Do not key in a batch by hand.

For one or two awkward invoices, key them in.

Select the activity, then complete:

Check the period against the invoice. The dates Avarni prefills are not always the period the invoice covers.

Select Save. You do not need to complete any other field.

Four causes, and none of them is a failed extraction. Check them before you report a problem.

When a billing period straddles a month, Avarni prorates. Two invoices covering parts of August produce two rows, and each contributes only its share of August. The graph shows the prorated figure, not the sum.

Retailer bills sometimes do not add up. If the line items are right and the printed total is wrong, confirm the document as it is and write down why.

Use the Document Notes tab.

Set Document status to Confirmed. That records that a person checked it.