Skip to content

Financial & Ledger Suite Accounting Guide

The Business M Financial & Ledger Suite is a production-ready, highly audit-compliant double-entry accounting engine. Operating as a unified core or decoupled macroservice, the engine supports multi-tenant ledgers, granular cost centers, and automated reconciliation schedules backed by PostgreSQL.


At the heart of the Financial Suite is a flexible, hierarchically-structured chart of accounts designed for robust auditing.

Every organization tenant configures a master Account structure:

  1. Application Types: Asset, Liability, Equity, Income, Expense.
  2. Parent-Child Hierarchies: Group accounts (non-ledger containers, e.g., “Current Assets”) organize Child accounts (ledger-posting destinations, e.g., “Main Bank Account”).
  3. Fiscal Years: Pre-configured accounting periods with strict lock controls preventing entries in finalized periods.
  • Voucher Types: Standard classification folders for ledger transactions (e.g., Receipt Voucher, Payment Voucher, Journal Voucher, Purchase Voucher, Sales Voucher).
  • Cost Centers: Segmented tags representing divisions, stores, or distribution centers to calculate granular profitability.
  • Tax Masters: Tax rates (e.g., GST or local sales taxes) automatically linked to specific sales/purchase accounts.

2. General Ledger & Double-Entry Workflows

Section titled “2. General Ledger & Double-Entry Workflows”

Business M ensures absolute transactional integrity through strict double-entry journal validation.

graph TD
    Voucher[Accounting Voucher] --> Validation{Debit = Credit?}
    Validation -->|Yes| GL[Post to General Ledger]
    Validation -->|No| Reject[Raise Error & Block Entry]
    GL --> Trial[Generate Trial Balance]
    Trial --> Balance[Balance Sheet & P&L]

The primary document for manual adjustments, transfers between accounts, or depreciation entries. The system enforces that:

  • Total debits must exactly equal total credits before submission.
  • Transactions must post within an active, unlocked Fiscal Year.
  • Transactions immediately project to active financial statements.
  • Payment Entry: Records outbound cash or bank transactions to settle supplier bills, employee expenses, or general operational expenditures.
  • Receipt Entry: Records inbound bank deposits, customer invoice settlements, or Earnest Money Deposits.

When the Finance module is installed, submitting an invoice posts it to the ledger. The invoice itself does not need to know about accounting: the posting is queued on the transactional outbox and confirmed by the ledger before the invoice shows as Submitted.

Invoice Debit Credit
Sales Invoice Receivable (net amount) Revenue per item; output tax per tax row
Purchase Invoice Expense per item; input tax per tax row Payable (net amount)

A tax row with a negative amount (for example TDS) takes the opposite side of the usual tax line, so the entry always balances. Foreign-currency invoices post the company-currency amount and carry the invoice-currency amount and exchange rate on each line.

Accounts used. Configure these once in Finance Settings:

Setting Used for
default_receivable_account Sales Invoice control account (required)
default_payable_account Purchase Invoice control account (required)
default_income_account Revenue when neither the item nor the customer names one
default_expense_account Expense when neither the item nor the supplier names one

Item accounts are resolved in this order: the item’s own income/expense account, then the customer’s default_income_account / supplier’s default_expense_account, then the Finance Settings default. Every tax row with an amount needs a tax account (set on the row, or on the Tax Template item that generated it). If any account is missing, the submit is refused with a message naming it, and nothing is queued. The invoice’s Company is also required; on a site with exactly one Company it is filled in automatically.

stateDiagram-v2
    [*] --> Draft
    Draft --> PendingGL: Submit (posting queued)
    PendingGL --> Submitted: Ledger confirms
    PendingGL --> GLRejected: Ledger rejects, or retries exhausted
    Submitted --> PendingGLCancel: Cancel (reversal queued)
    PendingGLCancel --> Cancelled: Ledger confirms reversal
    PendingGLCancel --> CancelRejected: Reversal rejected
    GLRejected --> Cancelled: Cancel (nothing was posted)
  • Pending GL means the posting is queued; the invoice has not touched the ledger yet. It cannot be cancelled or receive a payment allocation until the ledger confirms.
  • GL Rejected means the posting never happened (a business rejection, or the system gave up after repeated failures, for example because no ledger was configured). Correct the cause, cancel the invoice and create a new one. Rejected invoices are excluded from the Accounts Receivable and Accounts Payable reports.
  • Cancelling a posted invoice reverses the exact ledger transfer it created, then marks the invoice Cancelled. A reversal that cannot be posted never leaves the invoice looking cancelled.
  • An invoice that nets to zero is submitted without a ledger posting.
  • Invoices applied through the POS sync flow are not posted by this mechanism; POS sales post through their own receipt flow.

Submitting a Credit Note (Dr sales return, Cr receivable) or Debit Note (Dr payable, Cr purchase return) posts to the ledger immediately and stores the ledger transfer id. Cancelling reverses that stored transfer and records the reversal’s id in Reversal GL Entry ID; if the reversal fails, the note stays Submitted. The sales and purchase return accounts come from Finance Settings.


Imprest accounts authorize branches or retail canteens to hold local cash limits for minor expenditures:

  • Requisition: Outlets request initial or booster imprest funds from HQ.
  • Remittance: Distribution of funds from the primary bank account to the outlet’s imprest ledger.
  • Statement Submission: Outlets record local daily cash receipts and expenses, uploading statements for HQ audit.
  • Reconciliation & Recoupment: HQ audits local expenses, reconciles balances, and automatically initiates bank transfers to recoup the outlet’s imprest back to its authorized limit.

To prevent over-expenditure, Business M supports hierarchical Budget Allocations:

  • HQ defines corporate budgets for the fiscal year, divided across specific Cost Centers and Expense accounts.
  • Every purchase requisition or expense invoice automatically checks the active projected budget.
  • Control Actions: System alerts administrators or blocks transactions outright when an invoice exceeds 100% of the allocated cost center budget.

4. Accounts Payable & Bank Reconciliations

Section titled “4. Accounts Payable & Bank Reconciliations”
  • Supplier Bills (Purchase Invoices): Ingested directly from purchasing workflows. Submitting a bill posts it to the ledger (see section 2.3) and locks in the accounts payable balance.
  • Earnest Money Deposits (EMD): Special deposit ledgers tracking performance deposits paid to suppliers or held for bidding contractors. The system supports tracking release dates and partial forfeits.
  • Auto-Settle Workflows: Payment entries can be dynamically auto-applied against outstanding supplier invoices using FIFO (First-In, First-Out) or manual allocation tags.
  • Allocation rules: The allocated amounts on a payment cannot exceed the payment amount, nor the outstanding balance of each invoice. Only invoices that are posted to the ledger can receive an allocation; invoices that are Pending GL, GL Rejected, Cancelled or awaiting a cancel confirmation are refused and are not offered as open invoices. Allocations are stored against the invoice’s internal id. A payment with several allocations records its party-ledger lines per invoice, plus any unallocated remainder. Invoice balances are reserved when the payment is submitted and released again if the ledger rejects the payment; cancelling the payment also releases them.

Reconciling active system ledgers against real-world bank statements:

  • Users upload digital bank statement files.
  • The BRS utility auto-matches records using transaction amounts, dates, and payment reference numbers. The matching service compares submitted Payment Receipts (deposits) and Payment Vouchers (withdrawals) by exact amount and same date, and rejects statement lines with an invalid amount or date instead of treating them as unmatched. It is not yet connected to the statement-upload workflow.
  • Reconciled Balances: Auto-updates clearing dates on system payment entries, highlighting discrepancies between the general ledger balance and the bank statement.

For employee business operations, the Financial Suite automates the complete reimbursement lifecycle:

stateDiagram-v2
    [*] --> Draft: Claim Filed
    Draft --> Pending: Submitted
    Pending --> Approved: Audited & Authorized
    Approved --> Paid: Payment Voucher Created
    Paid --> [*]
  • Travel Claims: Staff register itineraries, daily allowance claims, accommodation receipts, and regional mileage.
  • Expense Claims: General out-of-pocket operational costs submitted for manager validation.
  • Multi-Stage Approvals: Claims transition from department audit to financial clearance, automatically creating a Payment Voucher upon final approval.

Business M compiles real-time, audit-ready financial statements from active ledger databases:

  1. Trial Balance: Live summary of debits and credits across all active accounts.
  2. Profit & Loss (P&L) Statement: Real-time revenue vs. operational expenditure projections grouped by cost centers.
  3. Balance Sheet: A snapshot of assets, liabilities, and equity at any specific calendar second.
  4. Tax Ledgers: Segmented records showing input and output tax components for monthly tax filing.