Skip to main content
This glossary defines the core financial and platform terms used throughout Lerian’s documentation. It is designed to help product managers, sales teams, and anyone new to financial infrastructure quickly understand the language used in our guides.

A


Account

The fundamental unit of value storage in a ledger. An account holds a balance denominated in a specific asset (e.g., BRL, USD). Accounts can represent customer accounts, internal settlement accounts, fee collection accounts, or any other container for tracking value.

Account Type

A classification that defines the nature and purpose of an account — such as checking, savings, escrow, or settlement. Account types enable proper transaction routing and ensure that business rules are applied consistently across account categories.

Asset

A unit of value tracked in the ledger. Assets can be traditional currencies (BRL, USD, EUR), digital currencies (BTC, ETH), or custom units like loyalty points or academic credits. Every account is linked to exactly one asset.

Atomic (Atomicity)

A property of transactions where all operations either succeed together or fail together — there is no partial execution. If a transaction involves three operations (a debit, a credit, and a fee), either all three happen or none do. This prevents incomplete financial events.

Audit trail

A chronological record of every action and transaction in the system. Audit trails are immutable — once recorded, they cannot be modified or deleted. This is essential for regulatory compliance (SOX, GLBA) and dispute resolution.

B


Balance

The current amount of an asset held in an account. Midaz tracks three balance types: available (can be used immediately), on hold (reserved for pending transactions), and scale (the number of decimal places used for precision).

BYOC (Bring Your Own Cloud)

A deployment model where you run Lerian software on your own infrastructure — whether public cloud (AWS, GCP, Azure), private cloud, or on-premises. This gives you full control over data residency, security, and scaling. See also: SaaS.

C


CEL (Common Expression Language)

A lightweight, type-safe expression language that Tracer uses for writing business rules. CEL lets analysts and compliance teams define validation logic — such as “if transaction amount exceeds 10,000 and account type is personal, flag for review” — without writing application code or requiring deployments.

Child account

A sub-account created under a parent account, typically used for budgeting or organizational purposes. For example, a customer’s savings account might have child accounts for “Vacation Fund” and “Emergency Fund,” each tracking its own balance while rolling up to the parent.

D


Double-entry accounting

An accounting principle where every financial movement is recorded as at least two operations: a debit from one account and a credit to another. This ensures the system always balances — the total of all debits equals the total of all credits. Midaz enforces double-entry automatically on every transaction.

DSL (Domain-Specific Language)

A simplified programming language designed for a specific domain. In Flowker, the DSL lets teams define workflow steps, conditions, and integrations using a structured format — without writing general-purpose code.

E


ERP (Enterprise Resource Planning)

A business management software system — such as SAP, Oracle, or NetSuite — that integrates core processes like accounting, procurement, and inventory. ERPs are common data sources for reconciliation with Matcher.

External account

A special account in Midaz (prefixed with @external/) that represents value entering or leaving the system from outside. For example, when a student enrolls in a course, credits move from @external/available-courses into the student’s account. External accounts act as boundaries between your ledger and the outside world.

H


Helm Chart

A pre-configured deployment package for Kubernetes. Helm Charts contain all the instructions needed to install, configure, and upgrade software in a Kubernetes cluster. Lerian provides Helm Charts for deploying products in BYOC (self-hosted) environments.

I


Idempotency

The property that an operation produces the same result whether executed once or multiple times. In financial systems, this prevents duplicate transactions — if a payment request is accidentally sent twice, idempotency ensures the money only moves once.

Immutable (Immutability)

A property meaning “cannot be changed or deleted after creation.” In Midaz, all transactions and audit records are immutable — once recorded, they exist permanently. This guarantees data integrity for compliance and auditing.

K


Kubernetes

A platform for running and managing software applications at scale across multiple servers. Kubernetes automates deployment, scaling, and recovery — ensuring applications stay available even when individual servers fail. Required for BYOC deployments of Lerian products.

L


Ledger

The core financial book that records all transactions, balances, and operations for an organization. Think of it as the single source of truth for a business unit’s finances. An organization can have multiple ledgers for different purposes (e.g., retail operations, treasury).

M


Metadata

Additional information attached to entities like accounts, transactions, or organizations. Metadata is stored as key-value pairs and can hold any custom data your business needs — such as a customer’s external ID, a transaction’s reference number, or a department code. It does not affect ledger logic but enriches records for reporting and integration.

O


Onboarding domain

The part of Midaz responsible for structuring your financial ecosystem — creating organizations, ledgers, assets, accounts, portfolios, and segments. This is the “setup” phase before any transactions occur.

Operation

The atomic unit of movement in the ledger — a single debit or credit. Every transaction is composed of one or more operations, providing precise traceability for compliance and reporting.

Operation Route

A reusable template that defines the rules for one “leg” of a financial transaction — specifying which accounts participate, in what direction (source/destination), and under what accounting annotation.

Organization

The top-level business entity in Midaz — typically a bank, fintech, or subsidiary. Each organization holds its own ledgers, configurations, and access controls.

P


Pix

Brazil’s instant payment system, operated by the Central Bank of Brazil (BACEN). Pix enables real-time transfers 24/7 between individuals, businesses, and government entities. In the Lerian ecosystem, the Pix plugin connects Midaz to the Pix network, handling payment initiation, settlement, and fee management.

Portfolio

A grouping of accounts belonging to the same customer, business unit, or purpose. For example, a single client may hold checking, savings, and investment accounts across different currencies — a portfolio ties them together for a unified view.

Plugin

An optional extension that adds functionality to the Lerian platform. Examples include Pix (instant payments), TED (bank transfers), CRM (customer data), and Fee Engine (automated fee calculation). Plugins integrate with Midaz but can also operate independently.

R


Reconciliation

The process of comparing two sets of records — for example, your internal ledger against bank statements — to verify they match. Matcher automates this process by applying matching rules and flagging discrepancies.

S


SaaS (Software as a Service)

A deployment model where Lerian manages the infrastructure for you. You access the platform through APIs without worrying about servers, scaling, or maintenance. See also: BYOC.

Segment

A classification applied to accounts that share characteristics — like customer tiers (VIP, Student, Business) or regional divisions. Segments enable differentiated rules, pricing, and benefits across your customer base.

Settlement

The process of finalizing a financial transaction — transferring the actual funds between institutions. Settlement accounts in Midaz act as clearing points where money is held temporarily before being moved to its final destination (e.g., via Pix or TED to the central bank).

SOX (Sarbanes-Oxley Act)

A U.S. federal law that mandates strict financial record-keeping and auditing standards for publicly traded companies. SOX compliance requires immutable audit trails and accurate financial reporting — capabilities that Midaz and Matcher provide by design.

Source-available

A software licensing model where the source code is publicly accessible for inspection, modification, and self-hosting, while certain commercial uses may require a license. Midaz, Matcher, Reporter, and Tracer are all source-available.

T


Terraform

An infrastructure automation tool that provisions and manages cloud resources — servers, databases, networks, security groups — through declarative configuration files. Lerian provides Terraform templates for setting up BYOC infrastructure on AWS, GCP, or Azure.

TED (Transferência Eletrônica Disponível)

A Brazilian electronic bank transfer system for high-value or same-day transfers between financial institutions. Unlike Pix, TED operates only during business hours. In the Lerian ecosystem, the TED plugin connects Midaz to the TED network.

Transaction

A movement of value between accounts. Transactions can involve multiple operations (debits and credits) and are processed atomically — either all operations succeed, or none do. This ensures no partial financial events occur.

Transaction domain

The part of Midaz responsible for executing financial movements — processing transactions, updating balances, and maintaining audit trails.

Transaction Route

A complete transaction blueprint composed of multiple Operation Routes. For example, a “Pix Transfer” route defines all the debits and credits involved, ensuring double-entry compliance every time that transaction type is executed.

W


Webhook

An automated notification sent from one system to another when a specific event occurs. For example, Matcher can send a webhook to your JIRA instance when a reconciliation exception is found, automatically creating a ticket for your team to investigate.