Loading

Feed Queue Coding Suggestions

When no coding rule matches a bank or accounting feed line, the Feed Queue can ask Jev to choose the nominal account and tax code from your own chart. Jev picks from the accounts it is shown, so it cannot invent one, and its answer is only ever a suggestion.

The queue, rules and posting are covered in Accounting & Bank Feeds.

Where to find it

Architect Panel → ERP - Finance:

  • Feed Queue — Suggest an account on a line, or Rules, then ask AI for the queue

Architect Panel → Configuration:

  • AI Settings — the installation's switch and bars, in the TypeSafe Jev section

Admin Panel → Finance:

  • Bank Feeds & Reconciliation — the same queue, for finance staff given the tile

Off unless two switches are on

Bank descriptions often contain people's names, so Jev is used for a company's feed coding only when both of these say so:

  1. The installation. Jev must be switched on with a key, and ERP Feed Queue suggestions ticked in the TypeSafe Jev section of AI Settings (or set by your hosting administrator in the AI configuration file).
  2. The tenant. The tickbox Feed Queue: Coding Suggestions by TypeSafe Jev on the tenant's instance configuration screen, which opens under the heading Customisation. Tick it and click Save. It is off by default and is saved for your own tenant only.

The second switch exists because one configuration file serves every tenant on a shared installation: one customer agreeing to a new processor must not send every other customer's bank lines. Tick it only once TypeSafe is in your privacy notice. With either switch off, suggestions come from your rules and, where one is set up, the AI gateway, exactly as before.

The order things are tried

  1. Your coding rules, highest priority first. A matching rule always wins and Jev is not asked.
  2. Jev, when both switches are on.
  3. The language model through the AI gateway, when Jev cannot answer or is not sure enough, and when Feed: fall back to the language model is ticked (it is by default) and a provider is configured for the Feed Queue.

What is sent

The line's date, description, counterparty, amount (as a positive figure, with whether it is money in or money out), currency and document type, plus up to 40 recently coded descriptions with the accounts they went to. The question lists your company's accounts and the tax codes valid on that date. The payment reference is never sent, and a field you have marked for encryption is sent blank.

What comes back

  • The account must be in the company's chart. If its confidence is below Feed: account confidence (0.5 by default) the language model is asked instead; if that gives nothing, Jev's answer is still offered, with its confidence.
  • The tax code must be valid for the company on that date. If Jev says none, or its confidence is below Feed: tax code confidence (0.6 by default), the tax code is left blank rather than guessed.
  • Nothing is posted. The suggestion fills in the line for a person to accept with Code, or Code & learn to turn it into a rule.

When Jev is not used

  • More than 255 accounts can be posted to in the company: Jev cannot choose from that many, so the language model is asked.
  • Jev failed, or the click ran short of time: the language model is asked.
  • The AI budget is spent: no suggestion at all, because the same budget would refuse the language model too.
  • Feed: fall back to the language model unticked: Jev or nothing.

Using it day to day

  1. Open the Feed Queue and click Rules, then ask AI. Up to 100 uncoded lines are tried, and the message counts how many matched a rule, how many were answered by AI (Jev's answers included) and how many are left for a person.
  2. In the Suggested column, each suggestion shows the account, its name and who made it: by rule, by Jev or by AI, with how sure it was.
  3. For a single line, click Code, then Suggest an account. The message names the source and its confidence.
  4. Check the account and VAT, then Code, or Code & learn when the same counterparty will recur.

Each Jev suggestion is one run in AI Usage under the feature erpfeed.suggest.

Worked example

A business with 140 nominal accounts ticks both switches after updating its privacy notice. Of a month's 300 bank lines, rules code 240. Rules, then ask AI suggests accounts for the other 60, 52 of them by Jev at 70% or more. The bookkeeper accepts most, corrects four, and uses Code & learn on three suppliers that will recur, so next month's rules cover them.

Recommendations

  • Rules first, always. A rule is repeatable and auditable; a suggestion is a proposal.
  • Turn recurring suggestions into rules with Code & learn.
  • Sample accepted suggestions at month end, especially tax codes.
  • Raise the account bar if Jev's low-confidence suggestions are often wrong.