finance walkthrough 2026 06 18

Finance-team walkthrough — scope decisions (2026-06-18)

Notes from the Google Meet where the finance team walked through which Zoho Books features they actually use, to scope Caesar. This is the operative scope filter — it overrides generic teardown assumptions where they conflict. Recording: fathom.video/share/6HqptWvKQqYYmLw6yxwzfx_FXh5t9V-X (49 min).

Attendees: Ridwan (design/build) · Francis Ogunlaja (finance lead — the accountant voice; “two postings” / debit-credit discipline, channelling Osita) · Deborah Egbele (finance) · Phebe Idowu (finance — journals, audit trail, user management).

Purpose (Ridwan): hear from the team which features are real vs. noise, and where flows can be simplified, so the build optimises the actual jobs rather than cloning Zoho wholesale.

Overarching principle (Francis, repeated): Caesar will be the true source of truth for money, so double-entry integrity is non-negotiable — every document (invoice, bill, payment) posts a debit and a credit and ripples into P&L and balance sheet. “We can’t afford mistakes with money matters.” The concern isn’t the front-end; it’s did it debit the right account. Matches BRD §3/§8.1.

Module-by-module decisions

Area	Decision	Notes
Dashboard – bank/credit-card balances	Keep	Lists all bank accounts + balances. Important.
Dashboard – quick-action shortcuts (New Invoice, New Customer Payment, etc.)	Keep	Just shortcuts into the modules; useful.
Dashboard – Total Receivables / Payables	Keep (with nuance)	See “Receivables nuance” below.
Dashboard – Account Watchlist (accruals)	Drop	“Not necessarily” needed.
Dashboard – Getting Started	Drop	Team already knows the domain.
Items / Inventory	Drop for now	“We don’t use Zoho to track inventory or fixed assets.” Assets are classified as fixed assets, not inventory. A Fixed Asset Register is being built separately. Add Items later only if needed.
Time Tracking / Projects	Drop	Not used (“if we’re billing hours” — we don’t).
Banking – accounts + balances, add bank/credit card, filter by account	Keep	Core.
Banking – transactions (categorise/add)	Keep	Operating transactions flow through here.
Banking – manual bank transfer (account → account)	Add	Not in Zoho’s main view (it’s under the (+) menu). Record-only — the real transfer happens at the bank; Caesar just replicates/records it.
Banking – file upload on transactions	Add / keep	“Very important.”
Banking – bank feed integration	NOT integrated	⚠️ Divergence from BRD: the system is not connected to banks. Entries are recorded manually, not auto-fed. (See §Divergences.)
Exchange rate	Auto-fetch from CBN, with manual override	Zoho auto-picks the market rate and allows an edit. Francis: “I like it to auto-pick because the source is from CBN.” So: default = CBN API rate; allow manual override.
Sales – everything	Keep all	Customers, Estimates, Invoices, Payments Received, Recurring Invoices, Credit Notes — explicitly “everything.” (Note: this keeps Estimates, which the generic teardown suggested dropping.)
Purchases – everything	Keep	Vendors, Expenses, Bills, Payments Made, Recurring Bills/Expenses, Vendor Credits. Recurring items are set up here to auto-repeat monthly.
Tax – standalone Tax Returns module	Drop	Not used; “forget the tax, it’s not relevant” as a separate module.
Tax – rates inside invoices/bills	Keep / Add	Need to create the taxes we charge (e.g. VAT 7.5%) so they appear in the line-item tax dropdown on invoices and bills.
Tax – WHT (withholding)	Manual	Handled via a dedicated COA account + manual journal (calculated manually), not an automated tax engine.
Accountant – Manual Journals	Keep — “very key”	Needs notes/comments, attachments (invoices/pages), and a full audit trail (who created, who updated, when, and what changed). Used for adjustments + posting when there’s no bank statement. (Example below.)
Accountant – Bulk Updates	Keep — “key”	Bulk re-account/update transactions.
Accountant – Chart of Accounts	Keep	The backbone; WHT and other manual treatments hang off dedicated accounts.
Accountant – Currency Adjustments	Keep	Manual FX adjustment + API-fetched rate. “We still need these two just in case.”
Reports	Keep all	“Everything we post flows here.” P&L is bread and butter. All reports needed.
Documents	Keep (light)	A list of all documents ever uploaded/posted.
Users & Roles	Add/Keep	Add/remove users; role-based permissions (currently Admin / Staff). Segregation of duties (BRD §12).

Key clarifications

• Receivables nuance (Deborah ↔ Francis): MocX core ops are paid in cash immediately (swap), so there are normally no receivables for operations. Receivables/invoicing apply to non-operational sales — e.g. selling solar panels: issue an invoice → it sits in Receivables until paid → on payment it moves to the bank account. ⇒ The invoicing/AR path exists but is for ad-hoc/non-core sales, not swap revenue (consistent with BRD: riders aren’t customers; swap revenue arrives summarised/cash).
• Double-entry, by example (Francis): create a bill → debit an expense account, credit bank (cash out) or credit accounts payable (if owing). Every action = two postings.
• Manual-journal adjustment, by example (Phebe): a customer paid ₦14,000; ₦12,000 should be revenue and ₦2,000 a loan repayment, but the whole ₦14,000 was posted to revenue. Post a manual journal to move ₦2,000 from revenue to rider’s loan. ⇒ Adjustments are a primary journal use.
• Nigerian context: taxes are VAT + WHT; exchange-rate source is CBN. The team wants the Nigerian Zoho demo as the closer replica (the shared link is the Canada edition). The Canadian tax-return screens are not representative.
• Multi-entity: international movements span the group’s entities — the entity structure matters (BRD §5).

Action items (from the call)

1. Banking: build manual bank transfer (record-only); add file upload; implement CBN exchange rates with manual override.
2. Get the Nigerian Zoho demo link (VAT/WHT edition) and share with ADE; use it as the replica reference.
3. Manual Journal: implement with notes, attachments, and audit trail (who/when/what-changed).
4. Bulk updates: build.
5. Users & Roles: implement user management with roles/permissions.
6. Prepare and present a UI prototype to Francis, Deborah, Phebe (next deliverable).

Divergences to confirm with the CFO / sponsor

These contradict or refine the BRD — worth an explicit confirmation before they harden into the build:

• Bank feeds: BRD §4/§8.4 assumes multi-currency bank feeds + automated reconciliation; the team says the system is not bank-integrated and entries are recorded manually (+ manual transfers, CBN-rate FX). Confirm whether Phase 1 is manual-record (team’s view) or feed-based (BRD).
• Inventory→asset flow: BRD §8.6 calls inventory→capitalised-asset “the single most MocX-specific flow”; the team says inventory isn’t tracked and the fixed-asset register is a separate build. Confirm whether the FA register / inventory→asset flow is in Caesar Phase 1 or a parallel workstream.
• Estimates: kept per the team (“everything” in Sales), though arguably low-value for MocX — confirm it’s worth building in Phase 1.

Net effect on the teardown’s “mirror / drop / add”

Refines zoho-books-teardown.md §13:

• Drop (now confirmed): Items/Inventory module, Time Tracking/Projects, Account Watchlist, Getting Started, standalone Tax Returns module, customer/vendor portals & payment gateways.
• Keep (confirmed): full Sales (incl. Estimates) + Purchases, Banking (manual), Manual Journals, Bulk Updates, COA, Currency Adjustments, all Reports, Documents, Users & Roles, dashboard (bank balances + quick actions + receivables/payables).
• Add/emphasise: manual bank transfer, file uploads, CBN-rate FX with override, VAT-rate setup used in invoices/bills, WHT via COA+journal, manual-journal notes/attachments/audit trail, role-based user management. And the Caesar-native layer (entity tree, segment spine, fixed-asset register, command centre) per the BRD.