Accounting
A ledger nobody can quietly edit.
Your auditor checks the figures, not the process around them. Every product event posts through the same journal, an entry that does not balance is refused twice, and a correction is a linked reversal because the database refuses edits and deletes.
| Account | Debit | Credit |
|---|---|---|
| 1110Cash in hand | 4,982,500.00 | |
| 1210Loan portfolio | 118,406,250.00 | |
| 2110Savings deposits | 36,705,937.50 | |
| 4110Interest income | 16,813,687.50 | |
| Seven other accounts | 23,410,000.00 | 93,279,125.00 |
| Totals | 146,798,750.00 | 146,798,750.00 |
Balanced. Debits equal credits.
What it does
A starter chart for finance companies
Leasing, pawning, hire purchase, factoring and their impairment allowances beside the loan portfolio. Account groups fix each account's type and the band of codes it may take.
Balanced, and checked twice
An entry that does not balance is refused in the application and again by the database. Amounts are exact decimals, never floating point.
Corrections are reversals
The database refuses edits and deletes on the journal, so a correction is a new entry mirroring the original, linked to it and made once.
Every product event mapped
Each posting resolves to an account, most specific first, with an institution-level fallback. A product cannot be released while an account it needs resolves nowhere.
Derived, never stored
Trial balance, account ledger and financial statements are computed from postings. Statement layouts map code ranges, so a new account appears without anyone editing the layout.
Close the month and the year
A month-end checklist, period close through the approval flow, year-end carry-forward to retained earnings, and opening balances for go-live.
What it refuses
A control is only a control if the system enforces it.
- Fused refuses an entry whose debits and credits differ.
- Fused refuses an edit or deletion of a posted entry.
- Fused refuses a posting dated in the future or in a closed period.
- Fused refuses a hand posting to a system account such as inter-office clearing.
- Fused refuses a second reversal of the same entry.
The rules underneath
The detail your finance and IT teams will ask about.
- Amounts
- Debit-positive signed NUMERIC(19,4), so every subtotal is a plain sum. At least two lines, summing to exactly zero.
- Voucher numbers
- Per branch and per financial year, default pattern {office}/JV/{yy}/{seq:5}, allocated inside the posting so the series has no holes.
- Reversal date
- The original entry's date, today, or a date the person chooses, as the institution sets.
- Branch attribution
- Every entry carries one office, one currency and one business date in an open posting period.
- Accounting rules
- Named templates that limit which accounts a person may debit and credit on a manual entry, enforced on the server.
- Year-end carry-forward
- One entry per branch and currency, dated the year's last day. A re-run after a reopened period posts only the difference.
Works with
- ReportingFour built-in reports, a designer for your own queries over sandboxed views, and scheduled CSV, XLSX or PDF.
- Approvals and controlsApproval flows you draw, quorum rules, one inbox per person, office-scoped roles and a hash-chained audit trail.
- Branch counterReceipts and vouchers from gap-free branch series, tills counted by denomination, mirror reversals and bank reconciliation.
Accounting: questions
Can we use our own chart of accounts?
Yes. The starter chart is a starting point, and accounts are yours to add, arrange and deactivate. System accounts such as inter-office clearing cannot be deleted.
How is a wrong entry corrected?
By a reversal: a new entry that mirrors the original, linked to it, with its own voucher number and a reason. The original is never touched.
How do we post opening balances when we go live?
One entry per branch and currency, with the balancing amount computed rather than typed.
See it on your own products and numbers.
A walkthrough with the team that builds Fused: your loan products, your branches, your month-end.