The Ledger page provides a transparent, GAAP-compliant double-entry accounting view of all financial movements for your brand. It displays the active brand’s net balance and lists individual journal postings (debits and credits) with their corresponding references, types, amounts, and descriptions.
Getting here
- Log in to the OwnPay admin dashboard
- Under the PAYMENTS section in the left sidebar, click Ledger
Page sections
- Current Balance: The net total of all posted ledger entries in the merchant’s default currency
2. Ledger entries table
- DATE: The exact timestamp when the double-entry movement was recorded
- REFERENCE: The unique identifier (such as Transaction ID, Invoice ID, or Checkout Token)
- TYPE: The direction of the financial movement:
- Debit (DR): Increases assets or expenses; decreases liabilities, equity, or revenue
- Credit (CR): Increases liabilities, equity, or revenue; decreases assets or expenses
- AMOUNT: The cash value of the entry in the brand’s default currency
- STATUS: The posting status (typically
posted once successfully written and balanced)
- DESCRIPTION: Text describing the nature of the entry
The double-entry model
OwnPay automatically registers balanced entries for every transaction. When a checkout completes:
- A credit (CR) entry is posted to the brand’s payable account (
MERCHANT_PAYABLE) representing revenue
- A debit (DR) entry is posted to the asset account representing the processing gateway balance
Best practices
- Verify the Current Balance against your physical gateway summaries (bKash/Nagad/Stripe portals) weekly
- Use the REFERENCE field to trace transaction roots whenever customer disputes or chargebacks arise
- Do not expect the ledger balance to update instantly for offline or unapproved manual gateways
- Do not manually modify the database tables
op_ledger_entries or op_ledger_accounts as it will break the double-entry balance validation constraints
Every ledger transaction must balance. The sum of credits must equal the sum of debits. Do not initiate manually customized payments that bypass the transactional API, as this will lead to ledger imbalance warnings and transaction rollbacks.
Common mistakes and troubleshooting
Related pages
