Multi-Branch Accounting Module Implementation
Rayscan Diagnostic operates across multiple branches and requires an accounting system capable of capturing transactions at each branch independently while maintaining the ability to consolidate all branches into a single set of financial statements. This proposal outlines the implementation of a multi-branch accounting module within the AutoBooks AI Accounting Solution (ABAAS) platform, tailored specifically for Rayscan Diagnostic's operational structure.
Following our discussion, we understand that Rayscan Diagnostic operates two (2) branches with staffing distributed as follows: • Branch 1 — 6 staff members • Branch 2 — 12 staff members Each branch records its own income, expenses, and accounting transactions. Management requires the ability to: (a) Capture and view accounting transactions for each branch separately. (b) Consolidate all branch transactions into one unified set of accounts for group-level financial reporting. (c) Restrict branch staff to viewing only their own branch's records, while granting management full visibility across all branches and the consolidated position.
We propose the implementation of a Branch Management Module within the ABAAS platform. The module will deliver the following capabilities: (a) Branch Setup • Create and manage branches under the Rayscan Diagnostic company profile. • Assign staff members to specific branches. • Each staff member's transactions are automatically tagged to their assigned branch. (b) Branch-Level Transaction Capture • Income, expenses, journal entries, and inventory movements are recorded against a specific branch. • Branch staff can only view and transact within their assigned branch. (c) Consolidated Reporting • Trial Balance, Profit & Loss, Balance Sheet, Cash Flow, and General Ledger reports include a branch filter. • Selecting a specific branch displays that branch's financials. • Selecting "All Branches" produces a consolidated report across every branch. • Inter-branch transactions are properly eliminated in consolidation. (d) Access Control • Branch staff see only their branch. • Branch accountants see their branch and can export reports. • Management (MD/CFO) see all branches and the consolidated view. (e) Shared Chart of Accounts • One unified chart of accounts across all branches ensures clean consolidation and consistent reporting.
1. Branch entity and data model configuration. 2. Branch assignment field on all financial records (transactions, income, expenses, inventory, stock movements). 3. Branch filter on all reporting pages (Trial Balance, P&L, Balance Sheet, Cash Flow, General Ledger, Reports). 4. Branch management interface for creating branches and assigning staff. 5. User profile branch assignment for access control. 6. Consolidated reporting with inter-branch elimination handling. 7. Staff training and documentation.
Phase 1 (Week 1): Data model design, branch entity creation, and backend configuration. Phase 2 (Week 2): Branch assignment on financial records and user profiles. Phase 3 (Week 3): Branch filter integration on all reporting pages. Phase 4 (Week 4): Testing, consolidation validation, staff training, and go-live. Estimated completion: 4 weeks from project commencement.
One-Time Implementation Fee: • Multi-Branch Module Setup and Configuration — ₦250,000.00 Monthly Subscription (ABAAS Platform): • Business Plan (includes multi-branch, AI classification, and full reporting) — ₦99,999.99 per month Payment Terms: • 50% of implementation fee on project commencement. • 50% on go-live and sign-off. • Monthly subscription billed in advance via Paystack or Stripe. All amounts are exclusive of applicable taxes.
1. This proposal is valid for 30 days from the date of issue. 2. Implementation commences upon receipt of the initial payment and signed acceptance of this proposal. 3. The monthly subscription fee covers platform hosting, support, and updates. It does not include custom development beyond the scope outlined in this proposal. 4. Any additional branches beyond the initial two (2) can be added at no extra implementation cost. 5. Data migration from existing systems, if required, will be quoted separately. 6. Either party may terminate the subscription with 30 days written notice.
To proceed, please sign and return a copy of this proposal. Upon receipt, we will issue an invoice for the initial payment and schedule a project kickoff meeting. Accepted by: _______________________________ Name: _______________________________ Position: _______________________________ Date: _______________________________