Abakion Legal 28.0.202644.7020, 28.0.202645.7044 & 28.0.202645.7045

Prev Next
Release Date: November 3, 2026

Summary Summary


  • Awaiting Payment — summary codes can now hold back disbursements until an incoming payment is received (3792)
  • Payment Agent — retrieving, rejecting, and posting payment requests is now more reliable, with clearer error messages (3822)
  • Conflict Search — relations with the conflict role Both Sides are now included regardless of the subject's role (3832)
  • Group Setup Template — Update All Members and creating new users from a template now work without type errors (3817)

New Features New Features

You can now mark summary codes as "Awaiting Payment" to retrieve payment requests in a purchase journal (3792)+

You can now mark a summary code as Awaiting Payment. Use it for disbursements that shouldn't go to the vendor until an incoming payment has been received. You can only set the marking if the summary code is set to appear in the payment agent.

Payment requests with this kind of summary code go through the payment agent and approval just as before, but you can't retrieve them into the payment journal. Instead, use the new Get Payment Agent Requests action in a purchase journal of your choice. The purchase journal can't be a Banking/Payment Management purchase journal, because Banking/Payment Management doesn't allow this type of posting. Each request creates two lines: a debit on the matter and a credit on the vendor. If the vendor and vendor bank account don't exist, they're created automatically. The payment details from the request (payment method, recipient bank account, vendor number, payment reference, text to recipient, and document) carry over to the vendor line.

On Hold on the vendor line is filled in automatically with your initials, and the line can't be posted without it. Once the journal is posted, the request gets the status Posted. The payment itself happens later in the regular payment process, after On Hold is removed from the vendor ledger entry.

You can't use summary codes with Awaiting Payment together with ad hoc payment, employees as recipients, or negative amounts. If you delete one of the two lines in the purchase journal, the other is deleted too, and you can retrieve the request again.



Bug Fixes Bug Fixes

Case Work

Conflict Search: Business relations with the conflict role Both Sides weren't included when the subject's role was Client, Related Party, or Opposing Party (3832)+

Conflict Search left out a contact if the contact's relation to the matter had a Business Relation with Conflict Role set to Both Sides and the subject's role in the search was Client, Related Party, or Opposing Party. For example, this affected a buyer or seller on a matter when you searched for the firm with the role Client.

Relations with Conflict Role set to Both Sides were previously included only when you searched with the role Other or Target, or when Impartiality Check was turned on. This is now fixed, so relations with Both Sides are included in the conflict search regardless of the subject's role.

Relations with Our Side and Opposing Side work as before. Also, a single relation with Both Sides doesn't automatically pull the contact's other relations into the results. We also fixed an issue where a relation with Both Sides could appear twice in the search filter.


Finance

The payment agent is now more reliable when retrieving, rejecting, and posting payment requests (3822)+

Get Payment Agent Requests in the payment journal could fail with the error "Attempted to divide by zero" when the journal's number series reused a document number, and a single failing request stopped all the others. Document numbers are now validated with a clear error message, and each request is retrieved separately. Requests that fail keep the status Ready and appear in Error Messages with the matter, recipient, amount, and reason. You can open the payment request directly from there. The payment agent card now validates IBAN and SWIFT/BIC and checks that the payment method fits the bank's country. We added SWIFT/BIC Required in Payment Agent to Payment Methods (turned on for BTI during upgrade). When you change the payment method, information from the previous payment type is cleared. From Payment Agent Entries, you can use Open Payment Request to edit an existing request and Undo Changes to discard your edits.

We added the statuses New, Rejected, Rejected by Accounting, and Posted. Approvers can reject multiple requests on Payment Approvals with a single reason. Accountants can use Reject Payment Request in the payment journal or on the list. You can't reject lines that have already been exported to a payment file. The creator gets an email with one card per request, the reason, and a button that opens the request. Rejected and unapproved payments can't be exported or posted. Setup: Rejection Document Template Code, Rejection Email Subject, and the email scenario Payment Request Rejection with an account of type "Current User". If the approval email can't be sent, the request is still saved. You get a notification, and the approver can find the request under My Payment Approvals.

Matter ledger entries and vendor invoices are now posted only for payments that are actually posted, with no duplicates. If you delete a journal line, the request goes back to Ready and is retrieved again. The role center now includes Payment Requests Requiring Action and My Payment Approvals, and Payment Agent Entries has new columns: Rejection Reason, Rejected By, and Rejected On.

Banking for Legal only: You can retrieve payment requests only into a Banking export journal. Otherwise, an error appears in Error Messages. The payment agent's lines are now part of Continia's validation check before posting, and existing lines are corrected during upgrade. Reject Payment Request follows Continia's rules. You can't reject lines that have been approved, exported, or sent to the bank until you cancel the payment with Cancel Payments.


Setup Tools

An error when updating members and creating new users from a Group Setup Template is now fixed (3817)+

When you used Update All Members in Group Setup Template, you could get the error "The following fields must be of the same type." The same error could occur when you created a new user from a template.

The cause was that Priority on the template tried to copy its value to Time Summary Unit on User Setup, even though the two fields are different types. Fields of different types are now skipped, so Update All Members and creating new users from a template work without errors.

Note that the template doesn't control Time Summary Unit, because it's a personal display preference. Each user's value stays unchanged when you update the template. Priority also no longer shows up as a false deviation between the template and the user setup.