_Docs/
Get StartedModulesPlatformDeployCookbookChangelogReference
_Stack
_Modules
  • Ledger
  • Numscript
  • Connectivity
  • WalletsEE
  • FlowsEE
  • ReconciliationEE
    • Concepts
    • Getting Started
    • Using Generic Connector
  1. Modules
  3. Reconciliation
  5. Getting Started
Reconciliation

Getting Started

This guide walks you through the basic workflow for using Formance Reconciliation: creating a policy, running reconciliations, and interpreting results.

Prerequisites
Ledger module configuredConnectivity module configured
A cash pool created containing the payment accounts you want to reconcile
API access with reconciliation permissions (reconciliation:read, reconciliation:write)

Step 1: Create a Reconciliation Policy#

A policy defines which ledger accounts to compare with which cash pools. Create your first policy:

cat > policy.json << 'EOF'
{
  "name": "Daily Stripe Reconciliation",
  "ledgerName": "main",
  "ledgerQuery": {
    "account": "world",
    "asset": "USD/2"
  },
  "paymentsPoolID": "your-stripe-cash-pool-id"
}
EOF

fctl reconciliation policies create policy.json
POST/api/reconciliation/policies

Response:

JSON
{
  "data": {
    "id": "01HGW4D6YK8QHZ9VC1T2MXBZ3F",
    "name": "Daily Stripe Reconciliation",
    "createdAt": "2024-01-15T10:30:00Z",
    "ledgerName": "main",
    "ledgerQuery": {
      "account": "world",
      "asset": "USD/2"
    },
    "paymentsPoolID": "your-stripe-cash-pool-id"
  }
}

Save the policy id - you'll need it for running reconciliations.

Step 2: Run Your First Reconciliation#

Execute a reconciliation using your policy to compare balances at a specific point in time:

fctl reconciliation policies reconcile 01HGW4D6YK8QHZ9VC1T2MXBZ3F 2024-01-15T23:59:59Z 2024-01-15T23:59:59Z
POST/api/reconciliation/policies/01HGW4D6YK8QHZ9VC1T2MXBZ3F/reconciliation

Both timestamps must be in the past. You can specify different timestamps for ledger and payments to accommodate processing delays between systems.

Response (Balances Match):

JSON
{
  "data": {
    "id": "01HGW4D7SXRQP8M2N6V1K9J4B3",
    "policyID": "01HGW4D6YK8QHZ9VC1T2MXBZ3F",
    "createdAt": "2024-01-16T09:15:30Z",
    "reconciledAtLedger": "2024-01-15T23:59:59Z",
    "reconciledAtPayments": "2024-01-15T23:59:59Z",
    "status": "OK",
  "ledgerBalances": {
    "USD/2": "100000"
  },
  "paymentsBalances": {
    "USD/2": "100000"
  },
  "driftBalances": {
    "USD/2": "0"
  }
  }
}

Response (Drift Detected):

JSON
{
  "data": {
    "id": "01HGW4D7SXRQP8M2N6V1K9J4B3",
    "policyID": "01HGW4D6YK8QHZ9VC1T2MXBZ3F",
    "createdAt": "2024-01-16T09:15:30Z",
    "reconciledAtLedger": "2024-01-15T23:59:59Z",
    "reconciledAtPayments": "2024-01-15T23:59:59Z",
    "status": "NOT_OK",
  "ledgerBalances": {
    "USD/2": "100000"
  },
  "paymentsBalances": {
    "USD/2": "99950"
  },
  "driftBalances": {
    "USD/2": "50"
  },
  "error": "balance drift for asset USD/2"
  }
}

Step 3: Interpret Results#

Successful reconciliation (status: "OK"): All balances match, driftBalances shows zero.

Drift detected (status: "NOT_OK"): driftBalances shows discrepancies per asset, error field describes the issue. Common causes include balance differences, missing assets, or asset count mismatches.

Step 4: View Historical Reconciliations#

List all reconciliations to track your reconciliation history:

curl -X GET $FORMANCE_API_URL/api/reconciliation/reconciliations
GET/api/reconciliation/reconciliations

Or get a specific reconciliation by ID:

curl -X GET $FORMANCE_API_URL/api/reconciliation/reconciliations/01HGW4D7SXRQP8M2N6V1K9J4B3
GET/api/reconciliation/reconciliations/01HGW4D7SXRQP8M2N6V1K9J4B3
ConceptsUsing Generic Connector
On This Page
  • Step 1: Create a Reconciliation Policy
  • Step 2: Run Your First Reconciliation
  • Step 3: Interpret Results
  • Step 4: View Historical Reconciliations