Counterparties

In Atlar, a counterparty represents any external party you interact with financially — such as a customer, supplier, business partner, or internal entity like a subsidiary. Broadly speaking, a counterparty is a legal entity from which you pull funds (via direct debit) or to which you push funds (via credit transfer).

In the Counterparties tab, you can customize the table to suit your workflow:

• Filter data by entity, counterparty name, account number, and more
• Modify visible columns using the cogwheel in the top-right corner

Viewing counterparty details

Double-click a counterparty to view its full details, including:

• External accounts – The destination accounts or wallets linked to the counterparty.
• Details – Counterparty ID, legal name, associated entity, and identifying details.
• Metadata – Optional tags or attributes used to organize and enrich your records.
• Mandates – Any mandates linked to the counterparty (used for direct debits). If none exist, the section will indicate: “This counterparty has no direct debit mandates.”
• Audit trail – A log of creation and update events, showing who made changes and when.

Creating Counterparties

Counterparties are required whenever you make a credit transfer or direct debit involving an external account. You can create counterparties manually or let Atlar create them automatically.

Creating a counterparty manually

You can create counterparties:

• When creating a credit transfer — see credit transfers
• While creating a direct debit — see direct debits
• Directly in the Counterparties tab by clicking Create New in the top-right corner

Creating counterparties automatically

Counterparties are created automatically:

• When a payment is initiated via your ERP system (e.g. vendors or employees)
• When uploading a credit transfer batch with inline counterparty details — see credit transfer batches
• When initiating payments via the Atlar API

Best practice

When creating a counterparty, provide as much detail as possible—such as the legal name, account identifiers, and routing details. This ensures that the necessary payment information is pre-filled and validated, reducing friction and avoiding errors when initiating transactions.