Skip to content

Accounts and coding

Coding means deciding which account an invoice amount belongs to. For example, an invoice for office supplies belongs on an expense account “Office supplies”. fineelik only codes in advance: it suggests accounts and you confirm. Posting happens later in your accounting program or by your tax advisor.

Coding consists of the following for each line item:

  • G/L account: the account itself, for example “5300 Office supplies”
  • Cost center: who or what caused the expense (optional)
  • Cost object: what the expense was incurred for, such as a project (optional)
  • Depending on the system, further details, such as tax and posting groups in Business Central

After the assistant, the review without Business Central shows only G/L account and posting text. You show cost center, cost object and further fields under Settings, Fields.

fineelik needs a list of your accounts so that it has something to suggest. There are four ways. Three of them you find under Settings, Accounts and dimensions.

  1. Template for your country: In the assistant you adopt a ready-made account list with about 40 common accounts, with one click. Before that you can change numbers and names directly in the list there, and add or remove rows. If you skipped the step and there are no accounts yet, the review of an invoice offers you the template. Ready-made templates exist for Austria, Germany, Bosnia and Herzegovina, Slovenia and Croatia. The template is a starting point and can later be replaced by your own list. Have your accounting look at it before you rely on it.
  2. CSV file: columns Code; Bezeichnung; Gesperrt, the header row is optional. This also works for cost centers and cost objects.
  3. By hand: create new accounts one by one.
  4. From the leading system: with Business Central, G/L accounts, cost centers, cost objects and groups come from Business Central, every night and immediately on request. The account template is then hidden. G/L accounts from Business Central are read-only in fineelik, and for cost centers and cost objects you only manage blocking here. A CSV file does not change them. With ERPNext, accounts and cost centers come from ERPNext, see ERPNext.

A blocked value stays visible but can no longer be selected.

For the Unit column of the line items, every company has a list under Settings, Accounts and dimensions, in the list Units of measure.

  • Without Business Central, fineelik creates the standard units itself as soon as the company is created: piece, hour, day, month, year, lump sum, set, package, license, unit, weights, lengths, areas, volumes and kilowatt hour. The labels are in the language of the company. If a company has no units at all yet, fineelik creates them with the next invoice. If the list is empty, Create standard units creates them.
  • Internally every standard unit carries a code according to UN/ECE (Recommendation 20), for example H87 for piece or HUR for hour. The list under Settings shows it, the review shows only the label.
  • With Business Central, the units come from Business Central. If you connect Business Central later, every standard unit becomes the unit from Business Central with the same meaning, and your line items follow. If Business Central delivers no units, the unit is locked in the review until the sync brings them.

Under Settings, Fields you set per company which coding fields the review shows (header and line items), which are mandatory, what they are called and in which order they appear. Hidden fields are also missing from rules and suggestions, values that have already been entered stay saved. Fields without which your system cannot post stay visible and mandatory.

You create custom fields with “Custom field”, for example an order number per line item with a fixed format. fineelik looks for the value in the document and only adopts what fits the format.

Every time you confirm a coding, fineelik learns a rule from it: “For this vendor and this kind of line item, this account is right.” For the next invoice from the vendor, it suggests exactly that. This way you become faster over time.

Values set by hand count as confirmed immediately. An AI suggestion that you accept unchanged only counts as confirmed after several reviews, two by default. You set the number on the Automation card. Until then it remains a suggestion.

  • Under Settings, Posting rules you see the learned rules per vendor with their hit rate. Filters show, for example, only rules that were never applied, new ones or paused ones.
  • A rule that no longer fits can be changed, paused or deleted, one by one, all of a vendor or only the paused ones.
  • Two confirmed values for the same line are called a conflict by fineelik. Decide it in the review or in the posting rules, the chosen value applies from then on.
  • For lines without a rule of their own you can store a default coding per vendor. It is only a suggestion, never automatic.
  • The Automation card defines when a document that the rules have coded completely goes to approval without review: “Only with confirmed rules” (recommended and default), “Always” or “Never”. A document with a suggestion or a notice always goes to review.
  • With Business Central, fineelik can additionally learn from purchase invoices that have already been posted (Settings, Leading system, “Learn from Business Central”).
  • Learning does not replace a review: suggestions remain suggestions, see Using AI correctly.