LedgerPro — Cloud Accounting & Business Management System -- 2

Senior Accounting/ERP SaaS Developer – Web & Mobile
Project Overview
We are looking for an experienced senior developer or development team with strong accounting/ERP experience to build a modern, cloud-based, multi-tenant business accounting and financial management SaaS platform.
The platform will be subscription-based and available on Web, iOS and Android.

This is not a simple invoicing application. The system must be built around proper double-entry accounting, financial data integrity, General Ledger, auditability, security and scalable SaaS architecture.

Critical Developer Requirement
The developer must have proven experience building accounting, bookkeeping, ERP, financial or business-management software.
Strong understanding is required of:

Double-entry bookkeeping
Chart of Accounts
General Ledger
Journal entries
A/R and A/P
Cashbook and bank reconciliation
Inventory accounting
Trial Balance
P&L
Balance Sheet
Cash Flow
Tax and financial reporting
Experience with systems such as QuickBooks, Xero, Sage, Zoho Books, Odoo or similar is highly desirable.
A developer with only general web/mobile experience and no accounting-system experience is not suitable as the primary developer.

Core Modules
1. Company & Multi-Tenant Management
Each business must have completely isolated data.
Support:

Multiple companies
Branches/locations
Fiscal years
Accounting periods
Base currency
Company settings
Multiple users
Roles and permissions
2. Accounting Engine
A true double-entry accounting engine is mandatory.
Features:

Chart of Accounts
General Ledger
Journal entries
Debit/credit transactions
Opening balances
Adjusting entries
Recurring journals
Reversals
Period closing
Audit trail
Every posted transaction must satisfy: Total Debits = Total Credits.
Posted transactions must not be silently edited or deleted. Corrections must use proper reversal/adjustment procedures.

3. Cashbook & Banking
Cash and petty cash
Bank accounts
Credit cards
Receipts/payments
Deposits/withdrawals
Transfers
Customer/supplier payments
Bank reconciliation
Statement vs book balance
Reconciliation history
CSV/Excel bank imports
Architecture should support future bank-feed integrations.
4. Accounts Receivable
Customer records
Contacts/addresses
Credit limits
Payment terms
Sales invoices
Credit/debit notes
Customer payments
Partial payments
Payment allocation
Refunds
Discounts
Overpayments
Customer statements
A/R aging
Outstanding invoices
Customer balances
5. Accounts Payable
Supplier/vendor records
Payment terms
Supplier bills
Credit/debit notes
Supplier payments
Partial payments
Payment allocation
Supplier statements
A/P aging
Outstanding bills
Supplier balances
6. Customer/CRM
Customer profiles should show:
Contact information
Sales history
Quotes/orders
Invoices
Payments
Outstanding balance
Products purchased
Notes and communication history
7. Sales
Workflow:
Quotation → Sales Order → Invoice → Payment

Include:

Quotations
Sales orders
Invoices
Recurring invoices
Credit notes
Discounts
Taxes
Shipping
Payment terms
Partial payments
Multiple payment methods
PDF/email invoices
Invoice numbering
Payment/overdue status
8. Purchasing
Workflow:
Purchase Request → Purchase Order → Goods Receipt → Supplier Bill → Payment

Include:

Purchase requests
Purchase orders
Goods receipts
Supplier bills
Returns
Credit notes
Taxes
Discounts
Freight
Partial receipts/payments
9. Inventory
Inventory must be fully integrated with accounting.
Features:

Products/services
Categories
SKU/barcodes
Units of measure
Warehouses/locations
Stock levels
Reorder levels
Stock receipts/issues
Transfers
Adjustments
Sales/purchase returns
Inventory valuation
Low-stock reports
Support FIFO and Weighted Average costing.
Inventory transactions must automatically generate correct accounting entries for inventory, COGS, revenue, A/R and A/P.

10. Tax
Configurable tax engine supporting:
Tax rates/groups
Tax-inclusive/exclusive pricing
Tax-exempt transactions
Input/output tax
Tax adjustments
Tax reports
Architecture must be flexible for different countries and jurisdictions.
Financial Reporting
Required reports:
Profit & Loss
Balance Sheet
Trial Balance
General Ledger
General Journal
Cash Flow Statement
Statement of Changes in Equity
A/R Aging
A/P Aging
Customer statements
Supplier statements
Sales reports
Purchase reports
Tax reports
Inventory valuation
Stock movement
Product profitability
Cash/bank reports
Reports must support date ranges, comparison periods, filters, grouping, PDF, Excel, CSV and printing.
Drill-down from financial reports to source transactions is required.

Financial reports must reconcile with the General Ledger.

Dashboard
Business dashboard should show:
Revenue
Expenses
Net profit
Cash balance
A/R
A/P
Inventory value
Overdue invoices
Outstanding bills
Sales trends
Expense trends
Profit trends
Cash flow
SaaS Subscription System
The platform itself will charge businesses subscriptions.
Support:

Free/trial plans
Monthly/annual billing
Multiple pricing tiers
Feature-based plans
User/transaction/storage limits
Upgrade/downgrade
Cancellation
Renewal
Coupons/discounts
Failed-payment handling
Subscription invoices
Payment history
Integrate with payment providers such as Stripe, PayPal and regional gateways as required.
Pricing and plan limits must be configurable without major redevelopment.

Mobile Applications
iOS and Android should support key functions:
Dashboard
Customers
Suppliers
Products
Quotes
Invoices
Sales orders
Purchase orders
Payments
Expenses
Cashbook
Basic reports
Notifications
Invoice PDF/share
Users should be able to create and send invoices from mobile.
Users & Permissions
Role-based permissions for:
Administrator
Owner
Accountant
Finance Manager
Sales
Purchasing
Inventory
Employee
Read-only
Permissions should control viewing, creating, editing, approving, posting, voiding, exporting and printing.
Security & Audit
Because this is financial software, security and auditability are critical.
Requirements:

HTTPS
Encryption
Secure authentication
Password hashing
Role-based authorization
Multi-tenant isolation
API security
Rate limiting
Input validation
Secure file storage
Automated backups
Monitoring/logging
Preferably support:
2FA
Passkeys
Enterprise SSO
Audit trail should record user, date/time, action, affected record and relevant before/after values.
Documents & Data Import
Allow attachments such as receipts, supplier invoices and contracts.
Support PDF, JPG, PNG, Excel and CSV.

Import:

Customers
Suppliers
Products
Chart of Accounts
Opening balances
Appropriate transaction data
Include validation, field mapping, preview, duplicate detection, errors and import history.
API & Integrations
Provide a secure, documented API.
Architecture should support future integrations with:

Banks
Payment gateways
Shopify
WooCommerce
POS
Payroll
CRM
Expense systems
Tax systems
BI/analytics
Multi-Currency & Dimensions
Support:
Multiple currencies
Exchange rates
Foreign-currency invoices/payments
FX gains/losses
Architecture should support reporting by:
Branch
Department
Project
Location
Cost center
Salesperson
Approval Workflows
Configurable approval workflows for:
Purchase orders
Supplier bills
Expenses
Payments
Journal entries
Support approval limits, multiple approvers, rejection, comments and history.
Technology
Developer may recommend the final stack, but must explain the architecture.
Possible technologies:

Web: React/Next.js, Vue/Nuxt or Angular
Mobile: Flutter or React Native
Backend: Node.js/TypeScript, Python, .NET, Java or Go
Database: PostgreSQL or MySQL
Cloud: AWS, Azure or Google Cloud

Priority is accounting accuracy, security, scalability, performance and maintainability, not a particular programming language.

Testing
Mandatory:
Unit testing
Integration testing
End-to-end testing
Security testing
Performance testing
Critical automated tests must cover:
Debit/credit calculations
Tax
Invoices
Payment allocation
Inventory costing
Currency calculations
Journal posting
Sales, purchasing, inventory, A/R and A/P must be tested through to the General Ledger.
Development Phases
Architecture/UI/UX – accounting design, database, API and prototype
Core Accounting – COA, GL, journals, periods, cashbook
A/R & A/P – customers, suppliers, invoices, bills, payments
Sales & Purchasing
Inventory & Inventory Accounting
Financial Reporting & Dashboard
SaaS Subscriptions & Payments
iOS & Android
Testing, Security, Deployment & Documentation
Deliverables
Developer must deliver:
UI/UX
Technical architecture
Database design
Accounting engine
Backend/API
Web application
iOS/Android applications
Admin portal
Subscription system
Payment integration
Reports
Automated tests
API documentation
Deployment/CI/CD
Cloud deployment
Monitoring
Backups
Technical/user documentation
Complete source code
Project-specific source code and IP must transfer to the client according to the contract.
Freelancer Proposal Requirements
Applicants must provide:
Relevant experience: At least 2–3 accounting/ERP/financial software projects.
Accounting expertise: Explain experience with