What is the Ledger?
The Ledger is the accounting record of all financial movements in your Owem account. Every credit, debit, fee, and refund is recorded with complete details for auditing and reconciliation.Complete
All movements in one place.
Immutable
Records cannot be changed after creation.
Detailed
Complete information for each transaction.
Advanced Filters
Search by type, status, date, and identifiers.
Entry Structure
Each Ledger entry contains:| Field | Description |
|---|---|
id | Unique identifier (Entry ID) |
endToEndId | PIX transaction ID (E2E) |
externalId | Your external ID (for correlation) |
type | credit or debit |
reason | Movement reason |
status | Current status |
grossAmount | Gross amount |
netAmount | Net amount (after fees) |
feeAmount | Fee amount |
createdAt | Creation date/time |
Movement Types
Credits (type: credit)
| Reason | Description |
|---|---|
pix_in:qrcode_paid | QR Code payment received |
pix_in:refund_received | PIX OUT refund received |
manual_credit | Manual credit (admin) |
Debits (type: debit)
| Reason | Description |
|---|---|
pix_out:processing | PIX transfer in processing |
pix_out:succeeded | PIX transfer completed |
pix_in:refund_sent | PIX IN refund sent |
fee:transaction | Transaction fee |
Entry Status
| Status | Description |
|---|---|
pending | Awaiting processing |
processing | In processing |
succeeded | Completed successfully |
failed | Failed |
refunded | Refunded |
cancelled | Cancelled |
Bank Statement (PDF/CSV)
In addition to API queries, the Ledger offers the generation of complete bank statements in PDF or CSV format, with asynchronous processing.Formatted report with logo, header, summaries and transaction table. Ideal for presentation and auditing.
CSV
Tabular data for import into spreadsheets and systems. Ideal for automated reconciliation.
How It Works
Wait for Processing
The API returns
202 Accepted with an extractId. Processing occurs in the background.Customization
The statement can be customized via theoptions field:
Report sections (options.sections):
| Section | Description |
|---|---|
summary | General summary with credit, debit and fee totals |
monthlyTable | Table with totals grouped by month |
monthSummary | Detailed monthly summary with breakdown by type |
transactionTable | Table with all individual transactions |
options.columns):
| Column | Description |
|---|---|
dateTime | Date and time |
type | Type (Credit/Debit) |
description | Description |
endToEndId | PIX E2E identifier |
payerReceiver | Name, document, branch and account |
payerBankInfo | ISPB and bank name |
grossAmount | Gross amount |
fee | Fee |
netAmount | Net amount |
status | Transaction status |
Financial Reconciliation
The Ledger is the source of truth for reconciliation:Available Queries
By Filters (List)
Search multiple entries with filters:| Filter | Description |
|---|---|
type | credit or debit |
status | Entry status |
reason | Movement reason |
startDate | Start date (epoch ms) |
endDate | End date (epoch ms) |
page | Page (pagination) |
limit | Items per page (max 100) |
By Identifiers
| Endpoint | Search by |
|---|---|
/ledger/external-id/{id} | Your external ID |
/ledger/end-to-end/{e2e} | PIX ID (E2E) |
/ledger/entry-id/{id} | Entry ID (Ledger) |
Related Endpoints
List Movements
GET /v4/i/ledgerBy External ID
GET /v4/i/ledger/external-id/{id}By End-to-End
GET /v4/i/ledger/end-to-end/{e2e}By Entry ID
GET /v4/i/ledger/entry-id/{id}Generate Statement
POST /v4/i/ledger/extractGet Statement
GET /v4/i/ledger/extract/{id}Entry Example
Best Practices
Use externalId
Always include your external ID to facilitate reconciliation.
Paginate Correctly
Use pagination for large data volumes.
Cache Queries
Cache frequent queries to reduce API calls.
Reconcile Daily
Do daily reconciliation to identify problems early.