Ledger Import is where you upload your general ledger. Once it is loaded, Ledger Analysis reads it and suggests classification rules. See Review suggested rules from a ledger analysis.

Upload your chart of accounts first, and confirm which accounts are included. Avarni matches every general ledger row to an account code in your chart of accounts. If an account is not there, the row cannot be classified.

Your general ledger file needs an account code column. It does not need an account name column. Avarni takes the account name from your chart of accounts and joins it by code.

If you have imported trial balances, each one must have finished importing and must contain at least one account. A balance that is still importing blocks the ledger upload.

If your organisation trades in more than one country, add a country column to the file. See How Avarni decides the country of a row below.

Create one assessment for each financial year. Upload each year's general ledger into that year's assessment.

When you upload, some rows show an error on the account code. In most cases those rows belong to accounts that you excluded from your chart of accounts. Select delete rows with errors, then continue.

Avarni removes excluded accounts from the list of valid codes before the importer opens. An excluded account and a mistyped account therefore produce the same error. If you expect a row to be included and it errors, check the account in your chart of accounts before you delete it.

Extract the transactions for the accounts you included in your chart of accounts. Rows for excluded accounts show an account code error when you upload.

Extract the full financial year you report on. A full year contains more spend patterns, so the suggested rules classify more of your spend.

Keep only the lines that record spend with suppliers. Leave out document types that net to zero, such as reversals and internal journals. Ask your finance team what each document type code means before you filter.

Each row needs an account code, a date and an amount. A supplier name is optional. Without a supplier column, you cannot use Supplier as a prediction field.

You can upload the ledger as several files, for example one file for each quarter. Avarni adds each file to the assessment and applies your rules to it.

Each file must contain different rows. Avarni does not check for duplicate rows across files, so a row that is in two files is counted twice.

You can upload a pre-audit ledger now. When the audit is complete, upload the audit journals as a separate file. That file must contain only the journals that are not in your first file.

Yes. Upload the procurement data through Ledger Import as a separate file. Each row needs an account code from your chart of accounts, a date and an amount.

To use the procurement categories in an analysis, add a custom field for each category column under Settings › Custom Fields. Do this before you upload. The importer then shows each custom field as a column that you can map. When you create a ledger analysis, you can choose these custom fields as prediction fields.

Avarni does not match rows across files. Before you upload, remove from your general ledger extract every row that the procurement file also contains. The total of all your files must not be more than the spend on your trial balance.

Do not attach procurement data as business context. Business context guides the suggestions. It does not add transactions.

Load every entity's ledger for the year into that year's assessment. Assessments in one organisation cannot cover overlapping dates, so you cannot create a separate assessment for each entity.

Upload the ledger of each entity or system as a separate file through Ledger Import. Every account code in every file must be in your chart of accounts. If your systems use different account codes, add all the codes to your chart of accounts before you upload.

To attribute rows to an entity, add an entity column to each file. Avarni matches each value by name to an entity under Settings › Organisation Structure.

You can supply each ledger in the currency of that entity. Add a currency column to the file. A row with no currency takes the reporting currency of your organisation. Avarni converts each amount to the currency of the emission factor, with the rates under Settings › Exchange Rates. You do not need to convert the amounts before you upload.

If you exclude an entity from your reporting boundary, you do not need to load its ledger.

Avarni reads the country from a column in your general ledger file that you map during the import.

If your file has no country column, every row takes the country set on your organisation. You can see that country under Settings › Edit Organisation. One factor set then applies to every row, and the platform does not warn you.

After your first import, open the Emissions Hub and check the country shown against your file.

If your file has no country column, ask your finance team which field identifies the country. Currency does not work once the ledger is converted to a single currency.

Do not upload a second file that repeats rows already in the ledger. Avarni does not check for duplicate rows across files, so a repeated row is counted twice.

Classification rules stay in the assessment when you replace the ledger. Avarni applies them to the new file automatically.

Yes. Deleting the ledger removes the transactions only. You do not lose any of your classification work. These all stay:

When the new file finishes loading, Avarni applies your rules to it on its own.

Every value on a ledger transaction comes from your rules or from your file. Nothing is edited on the transaction directly. Re-uploading the file therefore brings everything back.

When you change the category of an account, or exclude it, Avarni updates the transactions that are already loaded. The counts and the rules update on their own. You do not need to reload the general ledger.

If you include an account that was excluded when you uploaded the general ledger, its transactions are not in Avarni. Rows for excluded accounts show an account code error at upload, so they were not loaded. Upload the missing rows for that account as a separate file, or reload the general ledger.

Run a ledger analysis to get suggested classification rules. See Review suggested rules from a ledger analysis.

Before you rely on the numbers, check that the ledger is complete against your trial balances. See Check your general ledger is complete against your trial balances.