Business Units API
Copy for LLM
Copy page as Markdown for LLMs
View as Markdown
Open this page as Markdown
Open in ChatGPT
Get insights from ChatGPT
Open in Claude
Get insights from Claude

Overview

Business Units are independent sub-accounts that can be created under a client’s main account.

Each Business Unit is treated as its own legal entity; it has a CLABE, its own balance, and when a CEP (Comprobante Electrónico de Pago) is generated, it shows the Business Unit’s name, not the parent client’s.

This structure allows companies to organize their operations while maintaining the legal and accounting separation they require.

Business Units are represented as Customers in the API.
Each Customer is essentially a Business Unit account, treated as its own legal entity: it has a RFC, CLABE, and independent balance.

All Customers (Business Units) belong to a parent Merchant account, which must be provisioned by Monato before you can create or manage Private accounts.

Typical use cases include:

Assigning CLABEs to subsidiaries or affiliates.
Handling projects or business units that require independent balances and reporting.
Ensuring that CEP receipts match the correct legal entity for compliance and accounting.
Structuring private debt facilities by modeling SPVs, facilities, and reserve accounts as Business Units, enabling clear separation of balances and automated allocation of inflows.

Key Benefits

Legal & Accounting Compliance: Each Business Unit appears as a distinct legal entity, simplifying audits and tax obligations.
Simplified Finance Management: Centralize treasury while avoiding the complexity of opening multiple bank accounts.
Operational Flexibility: Receive and send payments directly from each entity’s CLABE.
Scalable Setup: Add new Business Unit quickly as the business grows, without extra bureaucracy.
Integration Ready: Manage entities via API, enabling automation and custom workflows.

Important Considerations

Business Unit Main Account: A Merchant account (the “parent” of all Business Units) is required. This step is handled by Monato. Please contact us if you do not yet have a Merchant account.
Customer Creation and Validation: When a Business Unit (Customer) is first created, its customerValidationStatus will be PENDING until KYB checks are completed. Only VALIDATED Customers should be used for production operations. This step si also performed by Monato
Processing Time: Account creation and activation may take a few seconds to propagate across systems.
Account Status: Newly created accounts start in ACTIVE if successful.
Unique CLABE: Each Business Unit account generates a unique CLABE that cannot be reused or reassigned.

Step 1: Create an account for a Business Unit endpoint

Prerequisites
- A valid clientId and customerId must exist.
- Authentication token must be included in the request headers.

Endpoint POST /v1/clients/{{clientId}}/customers/{{customersId}}/private_accounts

Path parameters: none

Query Parameters: none

Request Body:

{
  "client_id": "{{client_id}}",
  "client_bank_adapter_id": "{{client_bank_adapter_id}}",
  "bank_id": "{{bank_id}}",
  "owner_id": "{{owner_id}}"
}

Response
Status Code: 200 OK
Response Body:

{
    "id": "9bde649b-a109-4304-848d-4af4dd898f5b",
    "bankId": "14b392f6-0dd9-4cd9-ac51-d13c5547c137",
    "clientId": "d9836d30-b235-4k4b-8c51-f994326c0888",
    "clientBankAdapterId": "848af863-fe20-4f3a-96a5-a8d4909995c1",
    "accountId": "ac8e89e6-fbfa-41ce-8c77-058b6c485891",
    "instrumentId": "53826860-8426-4876-90e0-3ffc5314d35c",
    "ownerId": "85cb81bb-f3ff-4294-8864-988e83f02b3c",
    "ownerType": "CUSTOMER",
    "accountNumber": "123456789012",
    "clabeNumber": "734180123456789012",
    "availableBalance": "0.00",
    "accountType": "PRIVATE_ACCOUNT",
    "accountStatus": "ACTIVE",
    "audit": {
        "createdAt": "2025-09-08 16:56:30.668821-06:00",
        "updatedAt": "2025-09-08 16:56:30.668821-06:00",
        "deletedAt": "None",
        "blockedAt": "None",
        "activatedAt": "None",
        "suspendedAt": "None"
    },
    "bankAdapter": "SIES"
}

As you can see, the response includes not only the account identifiers (such as accountId, accountNumber, and clabeNumber), but also metadata like the audit trail (createdAt, updatedAt) and the current accountStatus.
This detailed payload ensures you can immediately confirm the account’s state, trace when it was created, and map it to your internal systems with certainty.

Step 2: List Customers

Once Business Units (Customers) are created, you can retrieve them and their details using the following endpoint:

ℹ️ Note: Customers always start with customerValidationStatus = PENDING and move to VALIDATED once KYB checks are completed.

Prerequisites
- A valid clientId must exist.
- Authentication token must be included in the request headers.

Endpoint
GET /v1/clients/{{clientId}}/customers

Request
Path Parameters: none
Query Parameters: none

Request Body: none