Platform

Organization

An organization is your dedicated space within the Atlar platform where you manage team members, accounts, payments, approvals, third-party connections, and more. While it’s possible to create multiple organizations — for example, to use a sandbox for testing — you’ll have just one production organization that contains your real data.

User

A user is a person with access to Atlar. If you're using our API, a user can also be represented by a programmatic access token. Each user has unique login credentials and access to specific organizations, with permissions defined by their role within the organization.

Membership

A membership defines the relationship between a user and an organization. It determines which organization the user can access, their level of access, and the actions they can perform — all based on the role assigned to them.

Role

A role defines a set of permissions and access levels that can be assigned to users. Roles are used to enforce security and control what each user can see or do in the platform based on their responsibilities.

Access is not assigned directly to users. Instead, users are granted roles, which determine their permissions.

Permissions and access

Permissions and access are defined at the role level and can be as granular as needed. For example, a role might have read access to accounts, transactions, and balances, but only permission to create (not approve) credit transfers.

Conditional access can also be set — such as giving a role access to specific accounts or entities within an organization, rather than to the entire organization.

Four-eyes approvals

Four-eyes approval is a security feature requiring two users to approve changes before they take effect. In the Atlar dashboard, organizations can enable four-eyes approval for sensitive settings like user management or changes to payment approval chains.

Note: four-eyes approval does not apply to the approval of payments themselves.

Change requests

When four-eyes approval is enabled, any attempt to change a sensitive setting — such as user management or approval chains — will create a change request. This request must be approved by a second user before it takes effect.

Audit trails

All user and system activities are recorded and available as Audit trail tabs on for example Credit Transfers, and as a general Audit Trail.

Finance

Account

An account in Atlar refers to a bank account or wallet you hold with a third party — such as a bank, payment service provider (PSP), or other financial institution.

Account balance

Account balances can be of different types, such as booked or available:

Booked balance shows the confirmed balance, reflecting all transactions that have been processed by the bank.
Available balance includes pending transactions and reflects the amount that can currently be used.

Atlar uses the first balance of the day as the opening balance and the last as the closing balance.

Affiliation

An affiliation represents your relationship with a third party.

Categorization rule

Categorization rules automatically classify transactions into specific categories based on predefined conditions.

Entity

Entities are created automatically by Atlar based on data from third parties , but you can also create them manually in the dashboard. Regardless of how they’re created, you can update or restructure entities at any time.

Reconciliation

Reconciliation is the process of matching transactions from your bank statements with credit transfers, direct debits, or expected transactions. Atlar performs this matching automatically.

Report

Reports are customizable views of transactional data for one or more accounts, over a selected time range. They allow you to work with subsets of your data, which can be filtered, reviewed, and optionally exported.

Third party

A third party refers to one of your financial providers. This can be a bank, a payment service provider (PSP), or another financial institution. Enterprise resource planning (ERP) systems are also considered third parties.

Transaction

A transaction is an entry on a bank statement that impacts the account balance. Each transaction includes a booked date and value date. Atlar validates that the daily change in booked balance equals the sum of booked transactions.

View

Views are predefined queries used to visualize data. They can be used to monitor real-time statistics or export data.

Investment

Portfolio

A portfolio is associated with an entity and is essentially used to group Holdings together.

Holdings

Holdings represents assets associated with a portfolio.

Position

Positions are points in time to indicate value of a holding.

Payments

Counterparty

A counterparty is a legal entity you want to send payments to or collect funds from.

External account

An external account is the bank account or wallet belonging to a counterparty. When making a credit transfer, the external account is the payment destination.

Account numbers

Account numbers are used to identify accounts within financial institutions, including both your accounts and external accounts. Types include IBAN, CLABE, Swedish Bankgiro or Plusgiro numbers, and more.

Routing Identifiers

Routing identifiers identify the financial institution (and possibly its branch) for a specific payment scheme. Common examples include:

BIC/SWIFT codes (used internationally)
ABA routing numbers (United States)
BSB codes (Australia)
Clearing numbers (e.g. Bankgirot in Sweden, sort codes in the UK)

Payment scheme

A payment scheme is a defined way of moving money, typically managed by banks, clearing houses, or other financial institutions in a given market or region. In Atlar, payment schemes are grouped into two categories:

Credit transfers: push payments sent from your account to a counterparty.
Direct debits: pull payments collected from a counterparty’s account into yours.

Common examples of credit transfer schemes include:

Domestic: Faster Payments (UK), BACS (UK), WIRE/ACH (US), plus local schemes in Sweden, Norway, Denmark, and Switzerland
Regional: SEPA Credit Transfer (EU)
Global: SWIFT (international cross-border)

Examples of direct debit schemes include:

Domestic: Autogiro (Sweden), Betalingsservice (Denmark)
Regional: SEPA Direct Debit CORE and B2B (EU)

Credit transfer

A credit transfer is an instruction to send ("push") funds from a source account to a destination account.

Direct debit

A direct debit is an instruction to collect ("pull") funds from another party’s account into your own. A valid mandate is required.

Mandate

A mandate holds authorization details allowing you to collect funds via direct debit from a company or individual.

Approval chains

Approval chains define how many approvals a payment needs before Atlar can send it to the bank. You can require one, two, or three approvals for different payment types, or allow straight-through processing.

Approval chains can be configured based on criteria such as payment creator, currency, amount, or recipient.

Sweeping rules

Sweeping rules automatically move funds between accounts — typically from subsidiaries to a central account — to optimize cash flow and maintain target balances.

Payment template

Payment templates simplify the creation of new payments by providing pre-filled blueprints.

Connectivity

Connection

A connection is a technical link to a third party. It references the relevant affiliation.

Connection secrets

Connection secrets are parameters or credentials needed to access a third party, used to fetch data or send payment instructions securely.

Connection instruction

Connection instructions are commands sent to a third party (e.g. sending a payment instruction to a bank).

Connection report

A connection report is data retrieved from a third party, usually in raw format (e.g. XML).

Webhook

Webhooks are automated messages sent to a specific URL when certain events occur, allowing real-time data updates between systems.

Webhook key

A webhook key is a unique credential that secures the communication between Atlar and your systems via webhooks.