---
title: "Abakion Legal 27.1.202605.5148 & Abakion Legal DK 27.1.202605.5144"
slug: "abakion-legal-2712026055148-abakion-legal-dk-2712026055144"
description: "New features and fixes enhance invoicing, payment processing, and liability tracking, improving accuracy and efficiency for financial operations."
updated: 2026-01-29T15:11:57Z
published: 2026-01-29T15:11:57Z
canonical: "docs.abakion.com/abakion-legal-2712026055148-abakion-legal-dk-2712026055144"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abakion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Abakion Legal 27.1.202605.5148 & Abakion Legal DK 27.1.202605.5144

**Release Date:** January 29, 2025

## ![](https://cdn.document360.io/b53c92b4-6b2d-4730-b8fc-fa2e7b107470/Images/Documentation/Summary.svg) Release Summary

- **The exchange rate** on invoices is **no longer updated** when the posting date is changed.
- The **Customer dimension code** is now automatically inserted on payments from the **Payment Agent**.
- A new **log** has been added to show changes affecting the **Liability level**.
- Fixes have been made to the **export of client payments to Danske Bank**.

---

## ![](https://cdn.document360.io/b53c92b4-6b2d-4730-b8fc-fa2e7b107470/Images/Documentation/New Feature.svg) New Feature

### Invoicing – Exchange Rate Update Changed

When the posting date on a foreign‑currency invoice is changed, the exchange rate is no longer updated automatically.

This resolves previous posting errors where fee allocation and invoice lines were calculated using different rates and where disbursements were posted with exchange‑rate differences because their values were not recalculated.

In a future version, it will be possible to choose to update the document to the new exchange rate.(2838)

### Finance

### Payment Agent – Customer Dimension on Payments

The Customer dimension code is now automatically added to the payment journal for payments created via the Payment Agent.

This removes the need to manually add the Customer code for payments from joint client accounts after this became a requirement for exports. (3250)

### Liability Log

A new **Liability Log** has been added, automatically showing changes that may affect the liability calculation.

**What is logged?**

- When a bank account is linked to or removed from a client, matter, or group
- When changes occur on a matter:
  - Liability level
  - Group number
  - Client

**Where is the log shown?**

- New list: **Settlement Log**
- Available directly from both the Customer Card and the Job Card

**Only relevant changes are included** — logging only occurs when postings exist on the client/matter. The purpose is to make it easy and quick to see whether the liability setup has changed since the last reconciliation. (3262)

### Setup of new companies

1. The layout setting *“Logo retained proportionally”* is now the default on draft, invoice, and credit memo printouts when creating new standard companies. (3235)
2. Setup packages with data for creating new companies have been updated. (3249)

---

## ![](https://cdn.document360.io/b53c92b4-6b2d-4730-b8fc-fa2e7b107470/Images/Documentation/Group 7.svg) Bug Fixes

### Finance

### Export of Client Payments to Danske Bank

1. The export of client payments to Danske Bank now automatically removes the “‑” in CPR numbers. (3271)
2. A bug has been fixed where the export of payment entries only inserted the client into the first file when the same client had deposits across several bank accounts. This has now been corrected so all files contain the correct data. (3238)

### Payment Agent

A bug in the Payment Agent prevented the automatic creation of new bank accounts. The system could not create new bank accounts on vendors after **BANK99**. Users encountered the issue when importing payment requests into the **payment journal**. This has now been fixed, and automatic creation works as expected. (3251)

### Invoicing

A bug has been fixed where only the first invoice in a split could be reversed if employees without time entries were included in the fee allocation. The issue occurred because the reversal only cleaned up job ledger entries and not fee allocation lines. This has now been corrected so all relevant lines are handled properly during reversal. (3269)