BTC Ledger User Guide

Every movement of money is recorded as a category-driven, double-sided entry with an auto-generated reference (BTC-DE-XXXXXX). Inflow and outflow columns feed a running balance that can never be edited retrospectively.

• Pick a date and category (disbursement, repayment, investor inflow, OpEx, etc.).
• Optionally link the entry to a client so it appears in that client's ledger.
• Reconcile an entry with a coded reason — the reason is written to the audit trail.
• Voiding an entry is a critical action: it needs counterpart governance sign-off.

Book facilities with tri-party sourcing: the borrowing client, the field agent earning commission, and the investor funding the principal.

• Choose flat rate, straight line or reducing balance to preview the amortisation schedule.
• Agent commission is calculated from the agent's default percentage and tracked until paid.
• Collateral type and details are stored against the facility for recovery workflows.

Track equity roll-forward per investor: opening equity, additions, withdrawals and closing equity, with profit-share percentages driving the dividend engine.

• Run the dividend engine to distribute a profit pool pro-rata across active investors.
• Each distribution posts a matching outflow to the daily ledger automatically.

• Every staff member carries a permanent BTC-SID-XXXXXX identifier used across audit logs.
• Tab access and action rights are granted individually and require dual sign-off to change.
• Switching a staff member to Inactive instantly ends all of their active sessions and blocks future sign-in, while their historical records remain intact.

• Critical actions raised by an Admin must be decided by Management, and vice versa.
• Every state change is written to an append-only audit history that cannot be edited or deleted.
• Open 'View Audit History' on any request to see the full timeline with notes and timestamps.

Sarah answers member enquiries, captures entries from messages and escalates anything she cannot verify. Unauthorised numbers and parsing failures are logged and surfaced as live alerts inside the app.