Account Linkage Reconciliation

A primary account is a Cobre Balance, account, or counterparty where funds are consolidated. A secondary account is a Cobre Balance configured to automatically forward every credit it receives to its primary account. This guide covers how to reconcile the Money Movement and Transaction chain that linkage produces, correlate it back to the original collection, and handle the cases where the automatic sweep doesn't happen.

For how to enable and configure the link itself, see Account Linkeage. This guide assumes linkage is already configured and focuses on reconciling what it produces.

The Automatic Sweep Chain

For every incoming credit on a linked secondary balance, Cobre generates a fixed chain of one Money Movement and Transactions on both accounts — near real-time and per transaction, with no batching window:

Credit arrives on the secondary balance

{
  "id": "trx_bC9k2QwXz7Ap",
  "type": "breb_credit",
  "account_id": "acc_SecondaryM01",
  "amount": 500000,
  "previous_balance": 0,
  "current_balance": 500000,
  "currency": "cop",
  "credit_debit_type": "credit",
  "transaction_date": "2026-08-19T14:02:10Z",
  "created_at": "2026-08-19T14:02:11Z",
  "metadata": {
    "key_value": "@MERCHANTONE",
    "sender_name": "JOHN DOE"
  }
}

Webhook: accounts.balance.credit (secondary).

Cobre creates the automatic Money Movement

{
  "id": "mm_sWp84LtRq2Nx",
  "external_id": "trx_bC9k2QwXz7Ap",
  "geo": "col",
  "status": {
    "state": "completed",
    "code": "",
    "description": ""
  },
  "source_id": "acc_SecondaryM01",
  "destination_id": "acc_PrimaryCOP01",
  "currency": "cop",
  "amount": 500000,
  "created_at": "2026-08-19T14:02:12Z",
  "updated_at": "2026-08-19T14:02:14Z"
}

Webhook: money_movements.status.completed. Its external_id carries the transaction ID of the original credit — this is the hop that ties the automatic movement back to the collection that triggered it.

Secondary balance is debited

{
  "id": "trx_sD3fGh81pQr",
  "type": "col_cb_debit",
  "account_id": "acc_SecondaryM01",
  "amount": -500000,
  "previous_balance": 500000,
  "current_balance": 0,
  "currency": "cop",
  "credit_debit_type": "debit",
  "transaction_date": "2026-08-19T14:02:13Z",
  "created_at": "2026-08-19T14:02:14Z",
  "metadata": {
    "money_movement_id": "mm_sWp84LtRq2Nx"
  }
}

Webhook: accounts.balance.debit (secondary).

Primary balance is credited

{
  "id": "trx_pC7mNw92Ldz",
  "type": "col_cb_credit",
  "account_id": "acc_PrimaryCOP01",
  "amount": 500000,
  "previous_balance": 1200000,
  "current_balance": 1700000,
  "currency": "cop",
  "credit_debit_type": "credit",
  "transaction_date": "2026-08-19T14:02:14Z",
  "created_at": "2026-08-19T14:02:15Z",
  "metadata": {
    "money_movement_id": "mm_sWp84LtRq2Nx"
  }
}

Webhook: accounts.balance.credit (primary). This is the leg that confirms the funds are consolidated.

If you subscribe to accounts.balance.credit, you receive credits for all balances, primary and secondary alike. Distinguish them by content.account_id, not by the event key.

Correlating the Chain for Reconciliation

Object	Correlation field	Value
Original credit Transaction	—	its own `id`
Automatic Money Movement	`external_id`	the original credit Transaction's `id`
Secondary debit Transaction	`metadata.money_movement_id`	the automatic Money Movement's `id`
Primary credit Transaction	`metadata.money_movement_id`	the automatic Money Movement's `id`

For a Direct Link / R2P collection into a secondary balance, the same money_movement_id already tracks the original credit and both automatic legs — there's no separate external_id hop to resolve.

Payouts initiated from the primary account reconcile the same way as any other payout in this platform: via metadata.money_movement_id. See Payouts Reconciliation.

Transaction Types Per Geography

Colombia:

Type	Meaning
`col_cb_debit`	A Colombian Cobre Balance is debited to transfer funds to another Cobre Balance
`col_cb_credit`	A Colombian Cobre Balance receives a credit from another Cobre Balance
`col_debit`	Outbound transaction to a Colombian financial institution (e.g. a local payout from the primary account)
`col_credit`	Inbound transaction from a Colombian financial institution (e.g. a rejected payout returning to the primary account)

Applied to the linkage flow: the secondary → primary debit is col_cb_debit and the corresponding primary credit is col_cb_credit.

Mexico: the equivalent legs use spei_credit on the secondary, the automatic Money Movement, spei_debit on the secondary, and spei_credit on the primary.

See the full Transaction Types catalog for the complete list.

Minimum Viable Webhook Subscription

You don't need all four events to reconcile a linkage collection:

Secondary credit (accounts.balance.credit filtered to the secondary account_id) tells you a payment arrived for a given merchant — book the collection here.

Primary credit (accounts.balance.credit filtered to the primary account_id) tells you the funds are consolidated.

The automatic Money Movement and the secondary debit are useful for tracing the full chain when something looks wrong, but aren't required to book the collection itself. Treat the primary credit as internal consolidation, not new revenue — the revenue event is the secondary credit.

See Notifications & Subscriptions for how to subscribe and distinguish events by account_id.

When the Sweep Doesn't Happen Automatically

Situation	Behavior
A credit was received on a secondary balance before linkage was configured for it	Not swept retroactively — it must be moved manually.
The automatic Money Movement fails	Funds stay on the secondary balance; there is no automatic retry.
A payout from the primary account completes and later transitions to a late rejection	Not auto-reversed. Issue a refund as a new Money Movement from the primary account — it isn't linked back to the original transaction.
A payout from the primary account is rejected	Funds return to the primary account as a credit Transaction, with a `money_movements.status.rejected` event.
Cobre Balance creation	No webhook exists for it — confirm via the creation response or by polling the account.
Distinguishing an FX leg from a local movement	An FX-related Money Movement carries `fx_quote` information in its `metadata`; local movements don't.

Moving Funds Manually

When reconciliation surfaces an unswept balance, move the funds with an ordinary Money Movement between your own accounts:

POST /money_movements
{
  "source_id": "acc_SecondaryM01",
  "destination_id": "acc_PrimaryCOP01",
  "amount": 500000,
  "external_id": "manual-sweep-acc_SecondaryM01-2026-08-19",
  "metadata": {
    "description": "Secondary to Primary manual sweep"
  },
  "checker_approval": false
}

This can also be done from the Portal: Movimientos → Unitario → Mover Dinero → Enviar, selecting the secondary account as source and the primary account (under Cuentas Propias) as destination.

Allowed Actions on Account Linkage Reconciliation

🔍 Retrieval — Money Movements

🔍 Retrieval — Transactions

Description: Query the automatic Money Movement for a linkage sweep, or create a manual one when reconciliation finds an unswept balance.

What to expect after the action: A Money Movement object with external_id (automatic sweeps) or your own reference (manual sweeps), and a status.

📘 Learn more:

🔗 Obtain all Money Movements

🔗 Obtain one Money Movement

🔗 Create a Money Movement

How to Get Started

Confirm linkage is configured for the accounts you're reconciling

See Account Linkeage. Credits received before linkage was configured are never swept retroactively.

Subscribe to accounts.balance.credit at minimum, routed by account_id

See Notifications & Subscriptions. Add the automatic Money Movement and secondary-debit events if you need full-chain tracing rather than just booking the collection.

Know which correlation field applies at each leg

external_id on the automatic Money Movement, metadata.money_movement_id on both resulting Transactions — and confirm both are populated for your geography before relying on them.

Build a manual sweep path for the exception cases

Pre-linkage credits and failed automatic movements both require moving funds manually — via the API or the Portal.

What to expect after using this API

Every linkage collection resolves to a fully correlated chain

The original credit, the automatic Money Movement, and both resulting Transactions all link together through external_id and metadata.money_movement_id.

Reconciliation books the collection once

The secondary credit is the revenue event; the primary credit is internal consolidation, not a second collection.

Exceptions surface as unswept secondary balances

Anything that didn't sweep automatically shows up as a balance sitting on a secondary account, which you resolve with a manual Money Movement.

Account Linkage Reconciliation

The Automatic Sweep Chain#

Correlating the Chain for Reconciliation#

Transaction Types Per Geography#

Minimum Viable Webhook Subscription#

When the Sweep Doesn't Happen Automatically#

Moving Funds Manually#

Allowed Actions on Account Linkage Reconciliation#

How to Get Started#

What to expect after using this API#

The Automatic Sweep Chain

Correlating the Chain for Reconciliation

Transaction Types Per Geography

Minimum Viable Webhook Subscription

When the Sweep Doesn't Happen Automatically

Moving Funds Manually

Allowed Actions on Account Linkage Reconciliation

How to Get Started

What to expect after using this API