Changelog
Back to All

One-off payments and SWIFT-ready counterparty addresses

about 1 hour ago

Overview

New features:

  • Pay new accounts: send a payment to an account you have never paid before, without creating a counterparty first
  • Counterparty address updates: find and fix every counterparty address that will not meet the November 2026 SWIFT structured address rules
  • GL classification policies: set rules for how GL accounts are classified, so reconciliation never posts an entry your ERP would reject
  • Atlar AI Agent reasoning: see how the AI Agent reached its answer, step by step, in chat and in Workflows
  • Historical loans: bring existing loans into Atlar with their full history, including loans that have already matured

Pay new accounts

Paying a supplier for the first time used to mean creating a counterparty, adding their account, and only then making the payment. For one-off payments that left your counterparty list full of entries you never used again.

Now enter the account details directly when you make a payment, either in the payment form or in a batch upload. The payment goes out without a counterparty, and you can still review the full destination before approving. Save a counterparty only when you expect to pay them again.

Counterparty address updates

From November 2026, banks will reject cross-border payments where the beneficiary address is not split into structured parts like street, town, and country. Counterparties with incomplete addresses would see their payments fail.

The counterparties page now shows how many addresses need updating and lists them in a Needs update tab. Fix them one at a time, update several at once, or upload a file with all the corrected addresses. Atlar already sends structured addresses to your banks, so once the data is complete there is nothing else to do.

GL classification policies

Every ERP has its own rules for which GL accounts need extra classification like a department, cost center, or project. When reconciliation posted an entry without them, the ERP rejected it and someone had to fix it by hand.

Define GL classification policies on each reconciliation configuration. Atlar applies them to every match, rule, and journal entry, and stops an entry that breaks a policy before it reaches your ERP.

Atlar AI Agent reasoning

An answer is only useful if you can trust it. Until now you saw the AI Agent's conclusion, but not how it got there.

Open the reasoning on any answer to see what the AI Agent looked at and which steps it took, written in plain language. The same view is available on every step of a Workflow run, so when a scheduled Workflow produces a result you did not expect, you can see exactly why.

Historical loans

Loans that started before you used Atlar were hard to bring in, and a loan that had already matured could not be recorded at all.

Record any loan with its real start date, opening balance, and maturity, even if it matured in the past. Atlar warns you when the maturity date has passed and will not pay out principal on a historical loan. You can also correct past benchmark rate fixings, so interest on older loans matches what the lender actually charged.

Additional improvements

  • Approval chains for new accounts: Approval chains can tell apart payments to saved accounts and payments to accounts entered by hand, so you can add an extra approval step to the riskier ones.
  • Copy one-off payments: Copy a payment made to a new account to pay the same account again, without retyping its details.
  • Payments up to 180 days ahead: Schedule credit transfers and direct debits up to 180 days into the future, up from 60.
  • Intermediary banks: Add an intermediary bank to a payment when your beneficiary's bank requires one, in the dashboard, in file uploads, and through the API.
  • Larger approval steps: An approval step can now include up to 30 approver roles.
  • Penny test for payroll: Send a payroll file as a penny test, so the bank receives the exact file it will get on payday without the payments being treated as salary.
  • Whole-number amounts in uploads: Payment upload files accept amounts without decimals.
  • New payment schemes: Pay through CHATS and FPS in Hong Kong, PESONet, PhilPASS, and PDDTS in the Philippines, JomPAY in Malaysia, SARIE in Saudi Arabia, local transfers in Peru, Colombia, and the Czech Republic, T2 euro payments in Denmark, account-to-account payments in Poland, and BACS through Nordea.
  • Counterparty bulk delete: Select up to 500 counterparties and delete them in one action.
  • Entity access on counterparties: When you create or edit a counterparty, choose explicitly whether it is available to all current and future entities or only to the ones you pick.
  • Payment status on transactions: The Reconciled column on transactions is now Payment status, and shows Matched, Partially matched, Unmatched, or Pending to avoid confusion regarding a transactions bank account reconciliation status.
  • Reconciliation configuration overview: Each reconciliation configuration has its own page that shows its posting rules, classification policies, and the ERP it posts to.
  • Resubmit posted matches in bulk: Select several matches that failed to post and resubmit them together.
  • Action required status: Posted matches that your ERP rejected and that need a change from you are marked Action required, and you can resubmit them once they are fixed.
  • Filter by document date: Filter reconciliation matches by the date of the invoice or payment document, not only by the transaction date.
  • Clearer match details: Match details show how documents, transactions, and journal lines connect, and the outgoing documents table links to each document.
  • Bank fees in Business Central: Payments that include bank fee lines post to Business Central with the fees in the same entry.
  • Stricter automatic confirmation: Atlar now confirms a match automatically only when its confidence is high, which is the same level the match details show as High.
  • Reconciliation data in Analysis: Build Analysis views on reconciliation matches, accounting documents, and booked transactions.
  • Custom fields in debt tables: Show custom fields as columns in the loans, facilities, and activity tables.
  • First reset date on facilities: Choose how the first rate reset is set on a floating rate facility, and Atlar suggests the right first reset date on each drawdown.
  • Facility choice on sweeping rules: Pick which facility a sweeping rule draws down from. Expired facilities can no longer be selected.
  • Sweeping run outcomes: The sweeping runs table shows the final outcome of each run.
  • Reorder columns from table settings: Table settings list the columns in the order they appear in the table, and you can drag them into a new order.
  • Tables remember your place: Open a row and go back, and the table keeps the page and scroll position you left it on.
  • Counterparty grouping in statistics: Group credit transfer statistics by counterparty.
  • Larger forecast uploads: Upload up to 15,000 forecasted transactions in one file.
  • New bank connections: Start connecting NatWest Bankline and Ebury directly from the dashboard.