42 Finance & Accounts

Income

Income create flow and income list.

Illustrations on this page are conceptual examples — not screenshots of the live system.

Concept overview — Trip and client-linked receipts for Income (Line art style, example only, not a software screenshot)
Use-case collage — Approval before posting for Income (Line art style, example only, not a software screenshot)

How you can use it

The same Fleet module supports different transport models — pick the scenarios that match your operation.

Income in daily operations

Income create flow and income list.

Finance & billing alignment

Income for accounts and finance teams — typical in Bangladesh transport ERP deployments.

Trip and client-linked receipts

Teams use Income when they need trip and client-linked receipts — without maintaining a separate spreadsheet or WhatsApp thread.

Approval before posting

Teams use Income when they need approval before posting — without maintaining a separate spreadsheet or WhatsApp thread.

Benefits for your team

What improves when vehicle data lives in one place instead of spreadsheets and phone calls.

Trip and client-linked receipts

Income helps because trip and client-linked receipts — recorded inside the VMS audit trail instead of informal channels.

Approval before posting

Income helps because approval before posting — recorded inside the VMS audit trail instead of informal channels.

Branch-wise income visibility

Income helps because branch-wise income visibility — recorded inside the VMS audit trail instead of informal channels.

Reconciliation with billing

Income helps because reconciliation with billing — recorded inside the VMS audit trail instead of informal channels.

Benefits graph — Branch-wise income visibility for Income (Line art style, example only, not a software screenshot)

Makes daily work easier

Less chasing, less re-entry, fewer surprises on the morning dispatch board.

  • Income supports view, add, list — so users do not jump between unrelated tools for the same task.
  • Less manual follow-up: trip and client-linked receipts
  • Less manual follow-up: approval before posting
  • Less manual follow-up: branch-wise income visibility
  • Branch-scoped access means local teams open Income without seeing other depots' records.

Multi-user & mobile-ready

Different roles see different slices — desktop for planning, mobile for field, dashboard for leadership.

  • Accounts desk (desktop)Posts and reconciles Income vouchers with full ledger context.
  • Branch accountant (web)Branch-scoped Income entries that roll up to head-office books.
  • Transport billing clerkLinks trip and client data into Income without retyping amounts.
  • Auditor (read-only)Exports Income trails for review — no edit rights required.
  • CFO / owner (dashboard)Cashflow and receivable signals from Income widgets.
Integration diagram — Reconciliation with billing for Income (Line art style, example only, not a software screenshot)

Works with your other modules

Fleet is the vehicle master — other modules read from it so data stays consistent across the platform.

  • AccountsLedger postings from Income stay aligned with trip and client billing.
  • ExpenseIncome and Expense share the same platform data — no duplicate entry between modules.
  • Repeat IncomeIncome and Repeat Income share the same platform data — no duplicate entry between modules.
  • Repeat ExpenseIncome and Repeat Expense share the same platform data — no duplicate entry between modules.
  • TransferIncome and Transfer share the same platform data — no duplicate entry between modules.
  • ReportsReport hub aggregates Income metrics for branch and management packs.