Payment accounts and ledgers
Configure cash, bank, mobile, card, or other accounts and preserve a transaction history linked to each operational source.
Accounting
Branch-aware payment accounts and operating ledgers connected directly to sales and purchasing activity.
Keep financial activity connected to the transaction that created it. Sales, refunds, receivables, payables, and expenses feed account histories and reporting without losing branch or payment-account context.
What the Accounting module covers
The workspace is organized around complete operational responsibilities, not a collection of disconnected menu labels.
Customer Balances
Track customer obligations, due dates, balances, statuses, and settlements without disconnecting them from sales or billing.
Supplier bills and expenses
Record supplier obligations and categorized operating expenses with branch, approval, reference, and payment-account context.
Operational reporting
Analyze revenue, costs, margins, payment methods, expenses, promotions, and branch performance from connected records.
Records kept by the workspace
These are the principal operational records staff create, update, review, or hand to another connected module.
- Payment accounts and branch balances
- Account transaction histories
- Receivables and customer settlements
- Payables and supplier settlements
- Expenses, transfers, billing entries, and source references
What the connected workflow is designed to improve
The module combines records, permissions, location scope, and shared services to support these practical operating results.
Transaction-linked ledgers
Sales, refunds, fees, purchasing, and operating expenses remain connected to the account entries they created for faster investigation and reconciliation.
Visible obligations
Finance teams can monitor amounts owed by customers and amounts due to suppliers with due dates, status, settlement, and branch context intact.
Comparable branch performance
Revenue, cost, margin, expenses, payment methods, and account movement can be reviewed by branch without merging unrelated operating locations.
Included functionality
The module connects the following working capabilities through one tenant and branch model.
- Payment accounts with branch balances, defaults, and persistent transaction histories
- Customer receivables, supplier payables, due dates, statuses, and settlements
- Categorized expenses with references, approval state, and payment-account posting
- Sales, return, and billing entries linked to their originating operational records
- Revenue, margin, cost, promotion, payment-method, and branch reporting
How work moves through the module
A typical operating sequence; permissions and branch configuration determine who performs each step.
- 1
Configure payment accounts and branch defaults
- 2
Let sales, refunds, purchasing, fees, or billing create linked financial entries
- 3
Record receivables, payables, expenses, transfers, and settlements
- 4
Reconcile account histories and report by branch, period, account, or transaction source
Deployment, data ownership, and management oversight
The workspace is connected to the wider platform without removing tenant, location, department, or permission boundaries.
Deployment model
Local branches post supported sales and account activity against their assigned accounts. Hosted synchronization consolidates those branch records while preserving source identifiers and account histories.
Access and data scope
Accounts are available only to their permitted tenant and branch context. Financial permissions separately control viewing, creating, approving, settling, transferring, and reporting.
Management visibility
Review balances, settlements, account movements, receivables, payables, expenses, revenue, cost, margin, and branch-level financial performance with permission-controlled access.
Assign the workspace by responsibility
Module enablement makes the workspace available to the organization. User assignments and permissions still control its menus and actions.
Finance officerAccounts receivable clerkAccounts payable clerkOwner or auditor
Administrators can combine module access with branch, store, campus, facility, department, menu, and action permissions. A shared user may work across approved workspaces without receiving access to unrelated records.
Start with Accounting, then assign the right locations and people.
Hosted onboarding records the organization, first branch, business type, module selection, and owner account. Additional branches, roles, and permissions can be configured from administration.