Dalufy concepts

A separate book of record. You can have a Personal profile and one or more Business profiles. They are not merged: money and tax stay scoped to the profile you are working in.

Your household / individual money book — accounts, transactions, PIT-oriented tax.

A company book — sales, purchases, people/roles, CIT/VAT-oriented tax, and the same ledger rules as Personal for cash movements.

Where accountants and advisers work with client businesses (/clients). It is not your personal budget.

The legal or ownership container behind a profile (for archive/close and some ownership controls). Most day-to-day work happens on the profile, not the entity.

A cash or bank pot inside a profile (e.g. “Kuda”, “Cash”). Transactions post against an account.

The starting amount for an account, posted as a ledger event (not a silent dashboard patch). Entered in ₦; stored internally as kobo.

You enter and see amounts in naira (e.g. 424.63). The API stores integer kobo (100 kobo = ₦1) so money never drifts as floating-point decimals.

Free-text note on a transaction (what you’d write on a bank line: “Shoprite”, “Salary January”). It does not change type or tax treatment by itself.

One posted money event on the ledger: date, amount, account, type, optional category and memo. Everything financial (manual, import, bank sync, sales payment) goes through the same ledger API.

The nature of the movement — income, expense, transfer, loan proceeds, and so on. Type drives whether something counts as income and how it hits the chart of accounts. See Transaction types.

A management label under a type (e.g. “Groceries”, “Salary”). Used for classification and reporting — not the same as type.

Assign a category and move the row through Pending → Classified → Reviewed. Quick classify is for unsettled root rows; after review, change category via Correct so history is preserved.

Break one source amount into lines that still sum to the original (e.g. one POS swipe → groceries + fuel). The bank/import row stays the source; lines are classification, not new money.

Append a new correcting event (amount, type, memo, category, …) without overwriting the original. The memo is required — it labels the correction row and is stored on the audit trail as the reason for the change.

Corrections form a chain: original → correction 1 → correction 2. Only the live tip can be corrected next. Older rows are superseded history. Live CFO totals use the tip.

Posts a paired transfer out/in between two accounts in the same profile. Excluded from income.

Live financial overview (position, inflows, outflows, tax position). Reads the ledger — it does not invent balances.

A ruleset-driven computation (e.g. PIT / CIT) from published Nigeria 2026 rules. Not filing advice and not a live share with FIRS.

A stored Reviewed/Approved tax (or similar artefact) that is out of date because a source transaction changed. The old result is kept; you run a new calculation for an updated figure.

Local/staging connector that posts sample bank activity without real Open Banking. Use for walkthroughs; production uses real providers.

Upload CSV / Excel / PDF statements. Money In/Out or Credit/Debit layouts are detected where possible. Preview, then commit into the ledger with dedupe.

Category (and similar) proposals you Accept or Reject. High-impact suggestions require an extra confirm before they write. AI never silently posts the ledger.

Append-only log of material actions (who, when, what) — posts, transfers, splits, corrections (memo used as the reason), classify, and more. Support cannot open your ledger from this; platform admin is separate and has no tenant money access.

Re-entering your password (or MFA where required) before sensitive exports or admin-style actions.