Skip to content

Releases

v0.24.0

Choose a tag to compare

@bisand bisand released this 20 Nov 05:56

You can now start a conversation with an agent over.

New

  • «Ny samtale» in agent conversations (#300). A button in the header of every agent thread in Meldinger starts the conversation over: the agent's next order no longer carries the earlier messages, and a question the agent was waiting on is set aside, so the next message becomes a new task. This closes the gap v0.23.2 left open, where a wrong answer stayed in the history and kept coming back. Nothing is deleted: the old messages stay in the thread, with a line «Ny samtale – ser ikke det som står over» where it started over. The button appears only in conversations with an agent.

Migrations: 0098_chat_restart (new append-only table, nothing changed in existing ones). API: new POST /chat/conversations/{id}/restart; the messages response gains ny_start.

v0.23.2

Choose a tag to compare

@bisand bisand released this 19 Nov 21:32

The agent no longer has to convert øre to kroner itself.

Fixed

  • Every amount an agent reads now comes with kroner beside it (#299). After v0.23.1 the hosted agent still reported a bank balance of 1 117,75 kr as 111 775 kr. The MCP server now adds a <x>_kr field next to every whole-number <x>_ore field in a tool's answer, written as Norwegians write it (balance_kr: "1 117,75"), so there is no division left for the model to get wrong. The øre field stays, because that is what the agent sends when it writes. This applies to every tool, for the hosted agent and external MCP clients alike.

Known: in the portal's agent messages, a wrong answer stays in the conversation history and can be repeated in later answers, since there is no way to start a new conversation.

Migrations: none. API: none; MCP tool answers gain _kr fields.

v0.23.1

Choose a tag to compare

@bisand bisand released this 19 Nov 21:01

A fix to how the agent reads amounts, found by testing its new bank tools in prod.

Fixed

  • The agent reads _ore fields as øre (#298). Asked to report on the bank, the hosted agent gave the 1920 balance as 111 775 kr when the field said balance_ore: 111775, which is 1 117,75 kr. Its ground rule said amounts are whole øre, but only for what it writes. It now covers what it reads too, with that example. bank_kontoer also states the unit.
  • bank_poster_sok searches in kroner. The search amount is read as kroner (as in the portal's search box) while the results are in øre. The description now says so; an agent copying an øre amount into the search would have looked for a hundred times the amount.

Migrations: none. API: none.

v0.23.0

Choose a tag to compare

@bisand bisand released this 19 Nov 20:09

The agent can now do bank reconciliation, and importing a bank statement no longer counts a payment twice.

New

  • Bank tools for the agent (#297). Eight tools over the existing bank endpoints. Reading: bank_kontoer, bank_avstemming (unreconciled lines with suggestions), bank_poster_sok and bankkoblinger. Acting: bank_importer (a camt.053 or CSV statement from disk), bank_hent (fetch now, optionally from a date, as far back as the bank gives), bank_koble (match a bank line to an entry) and bank_bokfor_linje (post a fee or interest straight from its line). Undoing a match has no tool on purpose: a wrong match is fixed by a human.
  • The bookkeeper prompt has a bank procedure, and the accountant's reconciliation step includes the bank. The rule is the same as for the inbox: a bank line is not a voucher. Only fees and interest are posted from a line; anything else comes back as a question.

Fixed

  • A statement file no longer imports payments that are already there (#296). Uploading the same file twice was already refused, but a different file covering the same days (an overlapping export, or days the bank connection had fetched) imported every payment again. Each line already on the account, same day and same amount, is now skipped one for one, and the import message says how many. A second payment of the same amount on the same day still comes in.

Migrations: none.

API: POST /companies/{id}/bank/statements answers with a new field skipped; transactions now counts only the lines imported.

v0.22.1

Choose a tag to compare

@bisand bisand released this 19 Nov 19:02

A fix for the bank connection's «Hent eldre», found the first time it was used in prod.

Fixed

  • A start date the bank refuses is now explained (#295). Asking for more history than the bank gives (Nordea refused 1 January 2025) showed «Banken svarte ikke som ventet. Prøv igjen senere.» and marked the connection as failing. It now says «Banken gir ikke historikk så langt tilbake. Velg en senere dato.», and the connection is left alone.
  • A new connection never ends up fetching nothing (#295). If a bank refuses the first fetch's start of the year, the fetch falls back to the last 90 days instead of failing every night.

Migrations: none. API: none.

v0.22.0

Choose a tag to compare

@bisand bisand released this 19 Nov 17:38

Agents can now file mileage claims and read pages from a short list of official sites, and a bank connection fetches the whole year on its first run instead of 90 days.

New

  • Mileage claims through an agent (#290). New agent tools kjoring_registrer (a km claim with no receipt and no rate; statens sats on the driving date comes from the satsregister) and kjoring_sats (shows that rate). A toll receipt can be filed under the drive and inherits its person, project and billable flag. The prompts now say that reimbursing the employee and rebilling the customer for the same drive is normal, and never to ask for the rate.
  • Agents read official web pages (#290). GET /web?url= and the nettside tool read a page only from domains on a platform list (default Skatteetaten, Lovdata, Regjeringen, Brreg, Altinn, Norges Bank): https only, checked on every redirect, plain text, at most 1 MB. A systemadmin edits the list in the platform console under Innstillinger; customers cannot widen it.
  • «Hent eldre» on a bank connection (#294). Fetches the bank's transactions from a chosen date, once, as far back as the bank gives history. Lines already fetched or uploaded are not imported again.

Changed

  • The first bank fetch covers the year (#294). With nothing on the account yet, it starts at 1 January of the current year instead of 90 days back, but never inside history the ledger already holds: the day after the newest SAF-T-imported voucher, or the date of a manual opening balance. Banks generally give more than 90 days only shortly after the customer has logged in with BankID, so this is the fetch that has to reach back.

Fixed

  • The hosted agent no longer answers every turn twice (#292). It reports through its marked closing reply only; external agents over MCP are unchanged.
  • The reconciliation card's note about missing balances now names the bank connection as well as CSV files (#289).

Migrations: none.

API: new GET /web; POST /companies/{id}/bank/feed/{connection_id}/sync takes an optional ?fra=YYYY-MM-DD; POST /companies/{id}/expenses/receipts takes an optional trip_expense_id.

Operations: the bank connection runs in Enable Banking's restricted mode in prod (our own account only). The Enable Banking response format is now pinned by a real, scrubbed Nordea response in the tests (#293).

v0.21.0

Choose a tag to compare

@bisand bisand released this 19 Nov 09:08

Jobs can now run on a schedule, and the nightly bank fetch is the first one. The bank connection add-on is still switched off, so nothing changes for anyone today.

New, switched off

  • Nightly bank fetch (#288). When a bank connection is completed, the company gets a schedule that fetches from the bank every night, at a default time spread per company between 02:00 and 04:59. It runs exactly what Hent nå runs. Whoever may reconcile the bank can change the times (at most four a day, because banks limit fetching without the user present) or pause it, from the Bankkobling card.
  • A schedule writes nothing when there is nothing to fetch from: no live connection, no bank add-on, or a blocked subscription. It starts again by itself when that changes.
  • A consent past its date ends the connection, as when the bank says the consent is gone. The user connects again.

New

  • A general scheduler (docs/jobs.md, «Tidsplaner»). A schedule turns into an ordinary job when it is due, so claim-once, retries and several worker replicas come from the job machinery that already exists. Missed time is not made up for, and no run starts on top of an unfinished one. Which kinds of job can be scheduled, and how often, is decided in code.
  • Tidsplaner tab in the platform console: what runs when, and how the last run went. No accounting data.
  • regnmed work --once now drains the queue instead of running one sweep.

Fixed

  • Two bank fetches racing for the same lines (Hent nå while a scheduled fetch runs) no longer fail: the loser reports zero new lines.

Migrations: 0097_schedule (new table schedule, SQL function schedule_next, column job.schedule_id, job kind bank_sync; nothing existing is touched).

API: new GET /companies/{id}/schedules, PUT /companies/{id}/schedules/{kind} and GET /platform/schedules.

Operations: the worker now reads the optional secret bank-feed like the API does. At rollout the worker may log one relation "schedule" does not exist before the API's migration step has finished; it goes away on the next sweep, 30 seconds later.

Not in this release: cleanup of old job rows, buying the add-on, and notices before a consent expires.

v0.20.0

Choose a tag to compare

@bisand bisand released this 19 Nov 08:53

You talk to an agent in Meldinger, like a colleague, and the bell shows your unread messages. The first part of the bank connection add-on is included but switched off.

Changed

  • The bell is your unread messages (#287). One row per conversation, with a link straight to it. A question from an agent is a message from the agent, so it shows there too. Reading the conversation clears the notification, and Marker alle som lest clears all of them.
  • One place to talk to an agent. The task card under Administrasjon → Oppdrag og integrasjoner no longer has its own reply box, where answers never reached the conversation in Meldinger. It is now Agentenes oppgaver: a "Skriv til …" button per agent that opens the conversation, and a table of what each agent was asked and where it ended. "Spor" shows the events and the order as the agent received it.
  • The badge on Administrasjon and on the "Oppdrag og integrasjoner" tab is gone; the Meldinger badge and the bell show the same count.

Goes away

  • The form for giving an agent a task from the card. Write to the agent instead. A deadline and "any agent" can still be set over the API.
  • A question on a task given from the old form can no longer be answered in the portal: withdraw it and ask again in Meldinger. (No such question was open in production at release.)

New, switched off

  • Bank connection add-on, first part (#286). Statements fetched from the bank through Enable Banking instead of uploaded, feeding the existing reconciliation. It does not exist until ENABLEBANKING_APP_ID and ENABLEBANKING_KEY_FILE are set, which they are not in production. Scheduled fetch, buying the add-on and expiry notices are not built yet.

Migrations: 0096_bank_feed (three new tables: company_addon, bank_connection, bank_feed_seen; nothing existing is touched).

API: GET /notifications now returns unread conversations (type: "melding") instead of agent questions; new POST /chat/read-all; tasks gain fra_melding; integrations gain person_id; new /companies/{id}/bank/feed…, /bank/callback and POST /platform/companies/{id}/addons.

v0.19.0

Choose a tag to compare

@bisand bisand released this 19 Nov 04:24

Packages get limits, companies can switch package themselves, and the website and user guide read the live price list.

New

  • Package limits (#285). Each package can cap vouchers per year, employees in payroll, and integrations/agents. A package limit never stops bookkeeping: going over the voucher limit is shown in the portal with a suggested package that fits. Payroll and integrations have a hard limit: a new employee or agent beyond the package is refused with a message naming the package. The trial and the old Basis/Standard plans have no limits.
  • Bytt pakke. Invoiced companies switch package themselves under Abonnement. An upgrade applies at once; if the month is already invoiced, the price difference is invoiced in the same step. A downgrade applies from the 1st of next month. Switching to a package the company does not fit (employees, integrations) is refused. Card subscriptions are switched by support for now.
  • Only what is for sale can be chosen. Sign-up offers listed packages with a price in force, never an add-on; a company on an old plan can restart on it after a lapse.
  • Usage in the portal. The Abonnement card shows the package and usage against each limit; a banner appears when over the voucher limit; the employee and agent forms show the limit up front.
  • Vouchers regnmed posts by itself (depreciation, accruals, payroll runs, reminder fees, year-end) and imports do not count toward the voucher limit.
  • The website (pricing, home, accountants and agents pages) and the user guide read the live price list instead of hard-coded prices. Light and dark mode with a toggle on the website (#284).

Migrations: 0094_plan_integration_limit (nullable column), 0095_subscription_upgrade_run (append-only log of billed upgrades).

API: GET /companies/{id}/subscription gains pakke and bruk and lists only choosable plans; new POST /companies/{id}/subscription/change; plans gain integration_limit.

Not yet: no e-mail when over the voucher limit; switching a card subscription.

v0.18.0

Choose a tag to compare

@bisand bisand released this 18 Nov 20:59

Packages, add-ons and prices become data you edit in the platform console, and the public price list is served from the API.

New

  • Planer og priser (#283). A new tab in the platform console, for systemadmin to edit and support to read. Packages and add-ons (tilleggstjenester) have a name, audience, descriptive size limits, a feature list and a flag for whether they are shown publicly. Bank connection is seeded as a coming add-on with no price.
  • Prices are dated, append-only rows. A new price must start today or later and needs a source; it is never edited. A price for a plan that companies are on reprices them, so the console shows how many companies are on the plan and the API requires an explicit confirmation. The type of a plan (package or add-on) cannot change after its first version.
  • Public price list. GET /pricing (no token) returns listed plans and add-ons with today's price and the next dated change. The marketing site reads it at build time and is rebuilt every six hours, so a console edit reaches www within hours.

Also in this release

  • Marketing site (www.regnmed.no) and documentation site (docs.regnmed.no, with English developer docs) (#278, #280, #282).
  • The cluster no longer serves www.regnmed.no; the old redirect ingress is gone (#281).

Migration: 0093_subscription_plan (new table subscription_plan, append-only; basis and standard seeded from the 2026-07-28 prisvedtak, bank as a coming add-on). Billing is unchanged: it still runs Basis 49 / Standard 99.

API: new GET /pricing, GET /platform/plans, PUT /platform/plans/{slug}, POST /platform/plans/{slug}/prices.

Not yet: nothing counts or enforces the size limits, and buying an add-on is not built. The proposed Liten / Standard / Stor plans (#279) are not entered.