- Gantt Chart Page
 

Visual Project Timeline, Task Distribution & Delivery Control System
 

- What Is the Gantt Chart Page?
 

The Gantt Chart Page is a visual project management control center that transforms complex project data into a clear, time-based timeline.
 

Instead of reading lists, tables, or reports, users can see projects unfold across days, weeks, and months, with color-coded task stages, deadlines, and mission workloads—all on a single screen.
 

It answers one core question instantly:
 

“What is happening in my projects—right now and over time?”

- Why the Gantt Chart Page Exists
 

Projects fail not because of lack of effort—but because of poor visibility.
 

The Gantt Chart Page exists to:
 

• Prevent deadline surprises

• Balance workloads across stages

• Visualize delivery risks early

• Align teams around realistic timelines

• Make project planning intuitive—not technical
   

Together, they form a living timeline—not a static chart.
 

- Left Panel: Project & Column Control
 

Fixed, Always-Visible Columns
 

These columns remain sticky while scrolling:
 

• Project Name

• Customer Name
   

This ensures users never lose context—even in large timelines.

Dynamic Status Columns
 

Each project is broken into status-based columns, such as:
 

• To Do

• Queries

• Testing

• Custom stages (defined by the organization)
   

Each column:
 

• Has a unique color

• Represents a phase of work

• Accepts a numeric days allocation
   

These values are not cosmetic—they directly control the timeline rendering.
 

Due Date: The Anchor Point
 

Every project has a Due Date, shown prominently:
 

• Editable via date picker

• Visually highlighted

• Used as the end anchor for the timeline calculation
   

The entire project schedule is calculated backwards from this date.
 

- Right Panel: Timeline Calendar Visualization
 

This is where the Gantt Chart becomes powerful.
 

Calendar Structure
 

• Month headers (grouped visually)

• Individual day cells

• Day-of-week labels

• Today highlighted automatically

• Week boundaries visually marked
   

The calendar is fully dynamic, expanding or shrinking based on project data.
 

- Colored Timeline Bars: Project Phases in Time
 

Each project row displays:
 

• Colored blocks across calendar days

• Each color corresponds to a status column

• Length equals the number of allocated days

• Sequence follows column order
   

This makes it instantly clear:
 

• When work starts

• How long each phase lasts

• Where bottlenecks may appear
   

No reading required—just visual understanding.

 

- Smart Timeline Calculation (Behind the Scenes)
 

The system calculates timelines intelligently:
 

Timeline Logic:


Project Start Date = Due Date - (Total Allocated Days - 1)
 

Then adjusts for:
 

• Holidays

• Non-working days

• Organization workweek rules
   

This ensures realistic schedules, not theoretical ones.
 

- Holidays & Non-Working Days Awareness
 

The Gantt Chart respects real business calendars.
 

What It Does:
 

• Excludes organization holidays

• Excludes non-working weekdays (configurable)

• Skips weekends if disabled

• Visually marks holidays on the timeline
   

Why It Matters:
 

Deadlines are calculated on actual working days, not calendar days—preventing unrealistic delivery plans.
 

- Mission Integration: Tasks Inside the Timeline
 

Each colored timeline cell can display:
 

• Mission count for that project and column

• A clickable indicator
   

Clicking a cell opens a modal showing:
 

• Mission names

• Notes

• Assigned team members
   

This bridges high-level planning with low-level execution.
 

- Mission Modal: Task-Level Transparency
 

The mission modal provides:
 

• Direct links to project pages

• Clear assignment visibility

• Immediate understanding of workload
   

Users can go from timeline → task → execution in one click.

- Column Management: Fully Customizable Workflow

The Gantt Chart supports three column types:

1️⃣ System Columns

Default stages like:
 

• To Do

• Queries

• Testing
   

2️⃣ Organization Custom Columns
 

Defined globally for projects:

• Custom names

• Custom colors

• Custom ordering
   

3️⃣ Gantt-Only Columns
 

Visible only in the Gantt Chart:
 

• Added via “Add Column”

• Positioned after specific columns

• Can be hidden without deletion
   

This allows different views for different needs.
 

- Column Filtering & Visibility Control
 

Users can:
 

• Show/hide columns via multi-select filter

• Remove Gantt-only columns

• Refresh layout instantly
   

This keeps the interface focused and clean, even for complex projects.
 

- Real-Time Updates Without Page Reload
 

Every interaction is AJAX-driven:
 

• Changing days updates timeline instantly

• Changing due date recalculates entire project span

• Adding/removing columns updates layout immediately
   

The Gantt Chart behaves like a live planning board, not a static report.
 

- Sticky Columns & Synchronized Scrolling
 

To preserve usability:
 

• Project & customer columns remain fixed

• Timeline scrolls horizontally

• Vertical scrolling is synchronized

• Alignment is always preserved
   

This is critical for large project portfolios.

 

- Deep System Connections
 

The Gantt Chart integrates seamlessly with:
 

• Projects module

• Missions module

• Customers

• Calendar logic

• Organization settings
   

It is not a separate tool—it is a visual layer on top of real operational data.
 

- What Makes the Gantt Chart Powerful
 

✔ Visual project clarity
✔ Realistic delivery planning
✔ Holiday-aware timelines
✔ Task-level transparency
✔ Fully customizable workflow
✔ Live updates without refresh
✔ Scales to dozens or hundreds of projects
 

- Final Perspective
 

The Gantt Chart Page is not just a schedule.
 

It is:
 

• A planning engine

• A delivery risk detector

• A visual workload balancer

• A bridge between strategy and execution
   

It turns projects from abstract ideas into visible timelines, helping teams deliver faster, smarter, and with confidence.


 

- Call Tracking Page
 

Complete Call Analytics, Monitoring & Performance Intelligence System
 

- What Is the Call Tracking Page?
 

The Call Tracking Page (also known as Call Log Report) is a central command dashboard for monitoring, analyzing, and optimizing all call-related activity within an organization.
 

It brings together:
 

• Incoming and outgoing calls

• Employee call performance

• Call outcomes and talk time

• Historical trends and real-time data

• Individual call recordings
   

Everything is presented in a single, data-rich, interactive interface, designed for both managers and operations teams.
 

- Why the Call Tracking Page Exists
 

In call-driven businesses, calls are more than conversations—they are:
 

• Leads

• Sales opportunities

• Support touchpoints

• Customer experience moments
   

It transforms raw call logs into actionable business intelligence.
 

- KPI Cards: Instant Operational Awareness
 

At the top of the page, KPI Cards provide an immediate overview of call performance.
 

Core KPIs Displayed:
 

• Total Calls

• Average Talk Time

• Completed Calls

• Abandoned Calls
   

Each KPI card shows:
 

• Overall historical value

• Today’s value

• Visual trend indicators

• Clean, easy-to-scan layout
   

These cards act as a real-time health monitor for call operations.
 

- Visual Analytics: Calls as Trends, Not Tables
 

Numbers alone are not enough.

The Call Tracking Page converts call data into clear visual stories.
 

- Monthly Incoming vs Outgoing Calls
 

• Displays a 12-month trend

• Separates incoming and outgoing traffic

• Highlights growth, decline, and seasonality
   

- Team Member Activity Chart
 

• Breaks down calls by status per employee

• Uses stacked or grouped visualization

• Reveals productivity patterns instantly
   

Visual analytics help managers spot issues before they become problems.
 

- Employee Monitoring: Performance at a Glance
 

The Employee Monitoring tab is where call data becomes performance insight.
 

Each row represents one team member and displays:
 

• Call activity for Today

• Call activity for All Time (Ever)

• Call effectiveness metrics

• Visual percentage representation
   

This view allows managers to compare, evaluate, and coach based on real data.


- Advanced Filtering: Precision Control
 

The Call Tracking Page offers one of the most advanced filtering systems in the platform.
 

Employee Monitoring Filters:
 

• Month selector

• Team member selection

• Range filters for every metric

• Percentage range filter
   

Per Call Filters:
 

• Employee

• Call direction (incoming / outgoing)

• Call status

• Customer name

• Phone number

• Date range

• Call duration range
   

All filters are applied live via AJAX, with no page reloads.
 

- Per Call View: Every Call, Fully Transparent
 

The Per Call tab provides full call-level transparency.
 

Each call record shows:
 

• Employee handling the call

• Customer name and phone

• Call direction

• Date and time

• Call status

• Call duration

• Audio recording (if available)
   

This view is essential for:
 

• Quality assurance

• Dispute resolution

• Training and feedback

• Compliance audits
   

- Call Recording Playback & Actions
 

Answered calls include:
 

• Embedded audio player (HTTPS validated)

• Download fallback if needed

• One-click phone callback option
   

This ensures calls are not just logged—but reviewable and actionable.
 

- Privacy & Security Built In
 

The system respects organizational privacy policies.
 

Phone Number Masking:
 

• Controlled via organization settings

• Masks selected digits dynamically

• Applied consistently across views and exports
   

Access Control:
 

• Module-based access

• Role-based permissions

• Plan-based availability
   

Sensitive call data stays protected and compliant.
 

⚡ Real-Time Updates via Sockets
 

One of the most powerful features is real-time updating.
 

When a new call arrives:
 

• The system receives it via telephony APIs

• Stores it instantly

• Pushes updates via socket notifications

• Refreshes charts and tables automatically
   

No refresh. No delay. True live monitoring.
 

- Deep System Integration
 

The Call Tracking Page is tightly connected to:
 

• Customer Management

• Employee Management

• Messenger / Chat

• Reports & Exports

• External telephony providers (Voicenter, GIS, Link)
   

Calls become part of the customer timeline, not isolated data points.
 

- Export & Reporting Power
 

Both Employee Monitoring and Per Call views support:
 

• Excel export

• Full filter preservation

• Proper formatting

• Privacy masking applied
   

This makes the page ideal for:
 

• Management reporting

• Audits

• Performance reviews

• External sharing
  
   

  - Final Perspective
   

  The Call Tracking Page is not just a call log.
   

  It is:
   

• A call center command center

• A performance analytics engine

• A quality assurance platform

• A real-time operational dashboard
  
  It turns every call into data, insight, and opportunity—helping organizations improve service quality, increase efficiency, and make smarter decisions.
  
  
   

- Goals Page
 

Complete Performance, Productivity & Achievement Tracking System
 

- What Is the Goals Page?
 

The Goals Page is a central performance management dashboard designed to help organizations define, monitor, and measure success—both at the organizational level and at the individual employee level.
 

It transforms everyday actions—such as creating customers, projects, orders, or completing missions—into measurable progress toward clear goals.
 

Instead of guessing performance, the Goals Page provides real-time visibility into who is achieving what, when, and how efficiently.
 

- Why the Goals Page Exists
 

In most organizations:
 

• Work happens continuously

• Effort is not always visible

• Success is often measured too late
   

The Goals Page exists to solve this by:
 

• Turning daily activity into measurable outcomes

• Aligning employee actions with business objectives

• Creating transparency and accountability

• Motivating teams through visible progress
   

It bridges the gap between work done and results achieved.
 

- Organization-Wide Performance Snapshot
 

At the top of the Goals Page, the system presents high-level performance cards that answer one simple question:
 

“How is the organization performing today and overall?”

- Metric Cards (At-a-Glance Intelligence)
 

Each metric card displays:
 

• Today’s achievement (large, bold number)

• Total historical count

• Trend direction (daily & weekly)

• Mini line graph for quick visual context
   

Metrics Tracked:
 

• New Clients

• Projects

• Customer Relationships

• Orders
   

These cards provide instant clarity without needing to open reports or tables.
 

⏱ Real-Time Goal Intelligence (Not Manual Updates)
 

The Goals Page is powered by automatic goal logging.
 

Whenever an action happens elsewhere in the system:
 

• New client created

• Project added

• Order generated

• Mission completed
   

A goal log entry is recorded instantly, ensuring:
 

• Zero manual reporting

• No missed achievements

• Always up-to-date statistics
   

This makes the Goals Page trustworthy by design.
 

- Goals by Employee: Performance Where It Matters
 

The Goals by Employee table is the heart of the system.
 

Here, performance becomes:
 

• Personal

• Transparent

• Actionable
   

Each row represents a specific employee goal, clearly showing:
 

• Who owns the goal

• What type of goal it is

• How much has been achieved

• How close they are to completion
   

  - Progress That Speaks Visually
   

  Every goal displays:
   

• Achieved vs Target numbers

• Progress bar

• Percentage completion

• Color feedback
   

• Visual Logic:
   

•  Red: Goal not yet achieved

•  Green: Goal achieved or exceeded
   

• Progress is capped at 100%, ensuring clean visuals even when goals are exceeded.
   

  - Goal Management Made Simple
   

  The Add / Edit Goal modal is designed for clarity and speed.
   

  Goal Setup Includes:
   

• Goal type selection

• Team member assignment

• Target number

• Application time (daily / weekly / monthly)

• Optional custom date & time window
  
  The system handles all calculations automatically—no formulas required from the user.
   

  - Deep System Integration
   

  The Goals Page does not work in isolation.
   

  It is tightly connected with:
   

• Customer creation

• Project management

• Order/invoice generation

• Mission completion

• Dashboard widgets

• Performance reports
  
  Every relevant action across the system feeds directly into goal tracking, making goals a living metric, not a static target.
  
   

  - Security & Access Control
   

• Access is controlled by plan and role permissions

• Only authorized users can view or manage goals

• Team members only appear if active

• All data is scoped to the organization
  
  This ensures performance data stays accurate and protected.
   

  - Final Perspective
   

  The Goals Page is not just a goal list.
   

  It is:
   

• A performance compass

• A motivation engine

• A management visibility tool

• A real-time KPI system
  
  
  By converting daily actions into measurable progress, the Goals Page helps organizations align effort with outcomes—and turn work into achievement.
  
  
   

- Source Page (Source Log)
 

Complete Customer Acquisition & Performance Intelligence Module
 

- What Is the Source Page?
 

The Source Page, also known internally as Source Log, is a central intelligence dashboard designed to answer one of the most critical business questions:
 

“Where are our customers coming from, and what value are those sources generating?”

It is not just a list of leads or contacts.

It is a multi-dimensional analytics engine that connects customers, sources, team members, purchases, orders, income, and statuses into a single, interactive reporting experience.
 

- Why the Source Page Exists
 

In real business environments:
 

• Customers arrive from many channels (website, phone, referral, ads, campaigns)

• Different team members handle different sources

• Not every lead converts

• Not every conversion generates the same value
   

The Source Page exists to turn raw source data into strategic insight, allowing organizations to:
 

• Identify high-performing acquisition channels

• Measure team efficiency by source

• Track income and order value per source

• Monitor approval, rejection, and call outcomes

• Make data-driven marketing and sales decisions
   

- Core Concept: Customer Entier With Source page
 

At its heart, the Source Page tells a story per customer:
 

• How the customer entered the system

• Who handled them

• What type of purchase they made

• What income and orders were generated

• What status and call outcomes occurred
   

To keep data clean and meaningful, the system:
 

• Groups data by customer + source

• Avoids duplicate noise

• Applies intelligent rules for recent vs older data
   

This ensures that analytics reflect reality, not clutter.
 

- Visual Analytics: Data You Can See and Feel
 

The Source Page is designed as a visual-first analytics experience.
 

Pie Charts Answer “Who & Where”
 

• Team Member Chart: Who is bringing or handling customers

• Source Chart: Which acquisition channels are active

• Type of Purchase Chart: What customers are buying

• Status Chart: Where customers stand in the workflow
   

Each chart updates instantly with filters, giving immediate insight.
 

Trend Line Answers “When & How Much”
 

A 12-month rolling trend graph shows:
 

• Customer growth over time

• Income progression

• Order volume

• Conversion percentages
   

This transforms the Source Page from a snapshot into a time-based decision tool.
 

- Multiple Data Perspectives (One Click, New Insight)
 

The Source Page supports four analytical lenses, switchable instantly:
 

1. Default – Customer count

2. Incomes – Revenue generated

3. Order – Order / invoice totals

4. Percentage – Conversion efficiency
    

Each mode recalculates:
 

• Charts

• Table values

• Trend data
  
   

- Advanced Filtering That Respects Reality
 

Filtering on the Source Page is deep but intuitive.
 

Users can filter by:
 

• Team members

• Sources

• Statuses

• Call statuses

• Purchase types

• Income thresholds

• Approval state

• Date range or entire month
   

All filters:
 

• Apply instantly via AJAX

• Update charts and table together

• Persist visually in the header

• Carry into exports
   

This ensures what you see is exactly what you export.
 

- Smart Table Design (More Than Rows)
 

The customer table is not static data — it is interactive intelligence.
 

Key Capabilities:
 

• Dynamic columns (show/hide/reorder)

• Inline approval / rejection

• Expandable rows for recent activity

• Bulk selection across filters

• Campaign assignment directly from analytics
   

The table becomes a working surface, not just a report.
 

⏱ The 60-Day Intelligence Rule
 

To balance performance and insight, the Source Page applies a smart rule:
 

• Older than 60 days:
  
  Only the first source record per customer is shown
   

• Within last 60 days:
  
  All meaningful activity is accessible via expandable rows
   

This ensures:
 

• Clean primary analytics

• Full visibility when drilling down

• No loss of critical recent data
   

- Custom Fields: Analytics Tailored Per User
 

Every user sees the Source Page differently.
 

Through field configuration, users can:
 

• Choose which columns matter

• Rename headers

• Reorder fields via drag-and-drop

• Hide unnecessary data
   

These preferences are saved per user, making the Source Page personalized analytics, not one-size-fits-all.
 

- Export & Campaign Power
 

The Source Page is not a dead-end report.
 

Export
 

• Full Excel export

• Respects all filters

• Includes calculated fields

• No pagination limits
   

Campaign Integration
 

• Select customers directly from analytics

• Add them to campaigns in one action

• Turn insights into marketing execution instantly
   

  - Security, Performance & Trust
   

  The Source Page is built with:
   

• Organization-level isolation

• Role & plan-based access

• Optimized queries

• Pagination & grouping logic

• Secure exports
   

  It is designed to handle large datasets without losing accuracy.
   

  ---

  
  - Final Perspective
   

  The Source Page is not just reporting.

  
  It is:
   

• A decision cockpit

• A marketing attribution engine

• A sales performance analyzer

• A bridge between data and action
  
  It transforms scattered customer entry points into clear, measurable business intelligence.
  
   

- What Is Customer Connections?
 

Customer Connections, internally known as Combo Meeting, is a relationship-centric module designed to manage structured meetings and interactions between two customers inside the same organization.
 

Unlike standard calendars or appointments, this module is not about time alone — it is about intentional connections:
 

Who met whom, why they met, when they met, and what came out of it.

It creates a traceable relationship layer between customers, fully integrated with folders, statuses, tags, automations, and team ownership.
 

- Why This Module Exists
 

In many organizations, customers are not isolated entities:
 

• Partners meet prospects

• Clients meet vendors

• Investors meet startups

• Buyers meet sellers
   

Customer Connections exists to formalize these interactions, replacing informal notes, chats, and memory with structured, auditable data.
 

- Core Concept: A Connection Is a Record
 

Each Combo Meeting record represents one intentional connection event between:
 

• A primary customer

• A secondary (connected) customer
   

This record contains:
 

• Date & time

• Duration (calculated in 15-minute blocks)

• Address / location

• Notes

• Status

• Assigned team members
   

It is not just a meeting — it is a relationship milestone.
 

- Folder-Based Intelligence (Why This Is Powerful)
 

Customer Connections is governed by Folder Pairing Rules.
 

Only customers belonging to compatible folders can be connected.
 

Example:
 

• Folder A: Investors

• Folder B: Startups
   

➡ Investors can only be connected with Startups
➡ Startups can only be connected with Investors
 

This prevents:
 

• Invalid meetings

• Random connections

• Data pollution
   

And enforces business logic at the system level, not by memory.
 

- Multi-Customer & Multi-Member Reality
 

This module understands real business complexity:
 

Multiple Customers
 

• One meeting can be created for multiple primary customers

• Each creates its own relationship record

• All remain independently trackable
   

Multiple Team Members
 

• Multiple users can be assigned

• Responsibility is visible

• Ownership is auditable
   

This makes the module usable for sales teams, account managers, partnerships, and operations.
 

- Time Is Structured, Not Free-Text
 

Meetings are not vague timestamps.
 

They are:
 

• Defined by start time

• Measured in 15-minute intervals

• Stored as structured time_json
   

This allows:
 

• Duration analysis

• Time conflict prevention (future-ready)

• Calendar-style reasoning

• Precise reporting
   

- Table Experience: Designed for Relationships
 

The Customer Connections table is not flat.
 

It is hierarchical:
 

Main Row
 

• Primary customer

• Summary of connections
   

Expandable Sub-Rows
 

• Each connected customer

• Individual status

• Editable inline

• Independent lifecycle
   

This design mirrors real relationships, not spreadsheets.
 

- Status Is the Heart of the Workflow
 

Statuses define where the relationship stands.
 

Examples:
 

• Planned

• Completed

• Follow-up needed

• Canceled

• Successful introduction
   

Statuses are:
 

• Fully customizable

• Multi-language

• Inline editable

• Automation-aware
   

Changing a status can trigger automations instantly.
 

- Automation: Relationships That React
 

Customer Connections is deeply wired into the automation engine.
 

Events that trigger workflows:
 

• Meeting created

• Meeting edited

• Status changed

• Meeting canceled
   

Automations can:
 

• Send emails

• Notify team members

• Update customer fields

• Trigger follow-up tasks
   

This turns meetings into living workflows, not dead data.
 

- Field Customization: One View Never Fits All
 

Every organization works differently.
 

That’s why the module supports:
 

• Drag-and-drop column ordering

• Show / hide fields

• Custom labels

• Customer fields + meeting fields

• Dynamic custom fields
   

Each user sees only what matters to them.
 

- Filtering That Understands Context
 

Filters are not generic — they are relationship-aware:
 

• Customer name

• Folder

• Date range

• Status

• Team member

• Tags
   

This allows users to:
 

• Find meetings quickly

• Track outcomes

• Audit interactions

• Prepare follow-ups
   

- Security & Isolation by Design
 

Every record is protected by:
 

• Organization isolation

• Role-based access

• Folder validation

• User permissions
   

No customer can be connected unless:
 

• Folder logic allows it

• User has permission

• Data belongs to the same organization
   

- Performance & Scalability
 

The module is built for growth:
 

• Server-side pagination

• Lazy loading of sub-rows

• Indexed queries

• Cached field configuration
   

It scales from dozens to thousands of meetings smoothly.

 

- Final Perspective
 

Customer Connections is not a calendar.
It is relationship infrastructure.
 

It captures:
 

• Intent

• Context

• Ownership

• Outcome
   

And turns customer interactions into structured, automated, and scalable business intelligence.

 

- Deposit Report
 

Centralized Tracking of Bank Deposits
 

- What Is the Deposit Report?
 

The Deposit Report is the system’s final financial checkpoint — the place where digital payment records meet real-world bank deposits.
 

While other reports track transactions, documents, or customer balances, the Deposit Report answers one critical operational question:
 

“Has the money actually been deposited into the bank?”

It records and tracks cash, checks, and bank transfers after they are physically or manually deposited, ensuring that every payment eventually reaches the organization’s bank accounts.
 

- Why the Deposit Report Exists
 

In many businesses, payments are received first and deposited later.
 

For example:
 

• Cash is collected during the day and deposited at night

• Checks are gathered and deposited in batches

• Transfers arrive but must be reconciled manually
   

The Deposit Report exists to:
 

• Bridge the gap between payment receipt and bank confirmation

• Prevent lost or untracked deposits

• Assign accountability to team members

• Support accurate reconciliation and audits
   

- What a Deposit Record Represents
 

Each row in the Deposit Report represents one real-world deposit action.
 

A single deposit can include:
 

• Multiple cash payments

• Multiple checks

• Multiple bank transfers
   

All grouped into one deposit event, with:
 

• A responsible team member

• A specific date

• Clear totals

• Optional notes
   

This mirrors how deposits actually happen in real life.

- How Deposit Data Is Structured
 

Behind the scenes, deposits are stored in the deposit_bank table, which acts as a bank deposit ledger.
 

Each record captures:
 

• Counts (how many cash/check/transfer items)

• Amounts (total money per deposit type)

• Who deposited it

• When it was deposited

• Why / notes (optional explanation)
   

This makes deposits traceable, auditable, and human-readable.
 

- Ownership & Accountability
 

A key strength of the Deposit Report is clear responsibility.
 

Each deposit clearly shows:
 

• The organization owner

• The team member who created the deposit
   

Profile images (or initials fallback) make it instantly obvious who handled the money, which is essential for:
 

• Internal control

• Audit trails

• Accountability

• Trust in financial data
   

- Multiple Deposit Types in One View
 

The report tracks three deposit channels side by side:
 

- Cash
 

• Number of cash items

• Total cash amount
   

- Checks
 

• Number of checks

• Total check amount
   

- Transfers
 

• Number of bank transfers

• Total transfer amount
   

By separating count from amount, the system supports:
 

• Bank reconciliation

• Error detection

• Missing deposit identification
   

- Date & Time: When the Money Hit the Bank
 

The deposit date is not just informational — it is financially critical.
 

It determines:
 

• When money is considered “in the bank”

• Which accounting period it belongs to

• Cash flow accuracy

• Audit alignment
   

Dates are normalized and displayed clearly in d.m.Y format to avoid ambiguity.
 

- How Deposits Connect to Payments
 

The Deposit Report is tightly integrated with Payment Tracking.
 

When a payment is deposited:
 

• deposit_status = 1

• deposit_id is assigned

• A “Deposited” badge appears in Payment Tracking

• The deposit date becomes visible
   

This creates a clear lifecycle:
 

Payment Received → Deposit Created → Bank Reconciliation

No deposit = payment still pending bank confirmation.

 

- Final Perspective
 

The Deposit Report is not about customers or invoices —

it is about financial truth.

It answers the most important question in any business:
 

“Did the money actually arrive?”

And it answers it clearly, transparently, and accountably.


 

- What Is the Monthly Report?
 

The Monthly Report is a time-based financial intelligence report that shows how customer financial activity evolves month by month over a rolling 12-month window.
 

Instead of showing transactions or totals, this report answers a deeper question:
 

“How does each customer’s financial situation change over time?”

It transforms raw documents (invoices, receipts, orders) into a clear monthly timeline that reveals trends, risk patterns, and long-term behavior.
 

- Why This Report Exists
 

In growing organizations, financial risk rarely appears in a single month.
It builds gradually.
 

The Monthly Report exists to help teams:
 

• Detect rising customer debt early

• Identify persistent unpaid behavior

• Understand seasonal patterns

• Track open orders that stay unresolved

• Make credit and collection decisions based on trends
   

This is a strategic report, not an operational one.

 

- Mode 1: Debt Tracking
 

data_type = "debt"
 

What It Shows
 

Debt Mode shows how much money a customer owes at the end of each month.

For every customer and every month, the system calculates:
 

Monthly Debt = Invoices − Receipts

This reveals:

• Months where debt increases

• Months where payments catch up

• Long-term debt accumulation patterns
   

How the System Calculates Debt
 

For each customer, for each month:
 

1. Invoices
    

   • invoice → added

   • receipt_tax_invoice → added

   • credit_invoice → subtracted
      

2. Receipts
    

   • receipt → subtracted

   • gi_ir → subtracted
      

3. Monthly Debit
    

   • Total Invoices − Total Receipts
      

If there is no activity in a month, the report still shows that month with 0, ensuring visual continuity.
 

Why This Is Powerful
 

Debt Mode doesn’t just show how much is owed —
it shows when debt starts, grows, or stabilizes.
 

This allows teams to:
 

• Identify risky customers

• Adjust payment terms

• Trigger collection actions early

• Support financial forecasting
   

- Mode 2: Open Orders
 

data_type = "open_orders"
 

What It Shows
 

Open Orders Mode tracks orders that remain unresolved over time.
 

Instead of money owed, it answers:
 

“Which customers keep orders open, and for how long?”

For each month, the report shows:
 

• Number of open orders

• Associated order amounts

• Persistence of open orders across months
   

How Open Orders Are Calculated

For each month:
 

1. Load order documents:
    

   • detail_orders

   • purchase_orders
      

2. Resolve related documents:
    

   • Check linked invoices

   • Check payment status
      

3. Determine “open”:
    

   • Invoice unpaid or missing

   • Order not fully resolved

This ensures only truly open business obligations are counted.
 

- How the Monthly Timeline Works
 

The report always displays exactly 12 months:
 

• Current month

• Previous 11 months
   

This rolling window:
 

• Updates automatically every month

• Preserves historical continuity

• Eliminates manual date selection errors
   

Month names are localized and displayed clearly (Jan → Dec).

 

- Export: Strategy-Ready Data
 

The Monthly Report supports full Excel export, including:
 

• Customer names

• All 12 month columns

• Localized month headers

• Exact calculated values
   

Exports are ideal for:
 

• Board reports

• Financial planning

• Credit policy reviews

• External accounting analysis
   

- Access Control & Security
 

The report respects:
 

• Organization isolation

• Team-based customer visibility

• Admin vs normal member permissions
   

Normal users only see:
 

• Customers they own

• Customers shared with them
   

Admins see all customers.

- Payers Tracking
 

Customer-Centric Payment Intelligence
 

- What Is Payers Tracking?
 

Payers Tracking is a customer-level payment summary report designed to answer one critical business question:
 

“Who actually pays us — and how much?”

Unlike Payment Tracking (which focuses on transactions) or Order Report (which focuses on debt and invoices), Payers Tracking focuses purely on money that has already been paid, grouped per customer.

It converts thousands of individual payments into a clear financial leaderboard of customers.
 

- Why This Report Exists
 

In real businesses, decision-makers often need to know:
 

• Which customers generate the most revenue

• Which payment gateways are most used

• Which team members close the most payments

• How payments are distributed across projects and companies
   

Payers Tracking exists to provide revenue clarity, not accounting complexity.

 

- How Payers Tracking Thinks
 

This report is customer-grouped, not transaction-based.
 

That means:
 

• Every row = one customer

• Every amount = sum of all payments made by that customer

• Multiple payments → one consolidated total
   

This approach makes it ideal for:
 

• Revenue analysis

• Sales performance review

• Customer value ranking

• Payment gateway evaluation
   

- What the System Calculates Automatically
 

Behind the scenes, Payers Tracking performs live aggregation:
 

• All payments are loaded from documents_payments

• Payments are grouped by cust_id

• The system calculates:
   

Total Paid Amount = SUM(all payments for that customer)

This ensures:
 

• No duplicated data

• Always-up-to-date totals

• Accurate revenue insights
  
  
  - Filters: Precision Revenue Analysis
   

  Payers Tracking includes powerful yet intuitive filtering, allowing users to analyze revenue from any angle.
   

  You can filter by:
   

• Date range (when payments were made)

• Project

• Team member

• Customer name

• Company / invoice settings

• Payment gateway (Stripe, Cash, Credit Card, etc.)

• This enables questions like:

• Revenue paid via Stripe last quarter

• Payments collected by a specific team member

• Top paying customers for a specific project

• One of the strongest features of Payers Tracking is gateway-level visibility.

  Because payments are joined with payment_detail, the system can show:

• Which gateway was used

• How much revenue each gateway processed

• Gateway distribution across customers

• This is critical for:

• Payment strategy decisions

• Gateway fee optimization

• Identifying customer payment preferences
   

• ---

  - Data Flow: From Payments to Insights
   

  The internal flow follows a clear logic:
   

• Load all payments for the organization

• Apply user-selected filters

• Group payments by customer ID

• Sum payment amounts per customer

• Attach customer, gateway, and team member data

• Format results for display

• Paginate and return clean output

• This ensures speed, accuracy, and scalability.
   

  ---

  
  - Export & Bulk Operations
   

  Payers Tracking supports bulk selection and export, making it practical for:
   

• Accounting reviews

• Management reports

• External analysis

• Select individual customers via checkboxes

• Export only selected rows

• Export full filtered results to Excel

• Exports always respect:

• Active filters

• Selected customers

• Sorting order
   

• ---

  - Security & Data Isolation
   

  The module enforces:
   

• User ID validation

• Organization-level isolation

• Team-based visibility rules

• No user can see payments outside their organization, and team permissions limit exposure when required.
   

   

- Order Report
 

Executive-Level Order & Invoice Intelligence
 

- Purpose of the Order Report
 

The Order Report is a high-level financial control module designed specifically for administrators and organization owners.
Its goal is not to list individual invoices, but to summarize customer-level order and invoice performance in a way that immediately answers:
 

“Who owes us money, who has paid, and how healthy are our orders?”

This report consolidates orders, invoices, receipts, and payment status into a single strategic view.
It transforms raw financial documents into actionable customer insights.
 

- Why This Report Is Admin-Only
 

The Order Report exposes aggregated financial truth—including debt, unpaid invoices, and official obligo amounts.
Because of its sensitivity, access is strictly limited to:
 

• Organization owners

• Admin users (member_admin = 1)
   

This ensures:
 

• Financial data integrity

• No accidental exposure of debt information

• Clear responsibility for financial decisions
   

- How the Order Report Thinks
 

Unlike transaction-level reports, the Order Report is customer-centric.
 

Instead of showing:
 

• One invoice per row
   

It shows:
 

• One customer per row, with everything summarized
   

This design allows decision-makers to:
 

• Scan financial health instantly

• Identify problematic customers

• Prioritize collection efforts

• Understand revenue realization
   

- What the Report Calculates (Behind the Scenes)
 

For every customer, the system automatically calculates:
 

• Total Invoice Amount

• Total Paid Invoice Amount

• Total Unpaid Invoice Amount

• Total Orders Created

• Total Receipts Issued

• Customer Debit (Calculated Debt)

• Official Debt (From Customer Profile)
   

These values are not stored statically — they are calculated dynamically using:
 

• Invoice payment status

• Receipt records

• Customer obligo settings
   

This guarantees accuracy even as payments change.

 

- Order Status Distribution – Balance at a Glance
 

The Order Status Pie Chart visualizes the ratio between:
 

• Paid orders

• Unpaid orders
   

This removes guesswork and turns financial health into a visual signal that can be understood in seconds.
 

- Filters: Precision Without Complexity
 

The Order Report includes enterprise-grade filtering, allowing admins to narrow results without losing clarity.
 

Filters include:
 

• Customer name, email, phone

• Team member responsible

• Company / invoice settings

• Date range

• Paid / unpaid status

• Dynamic numeric ranges
   

This enables deep questions such as:
 

• “Unpaid invoices created this month”

• “Debt per company entity”

• “Orders created by a specific team member”
   

All filters update tables and charts together, keeping the story consistent.


 

- Export: From Insight to Action
 

The Order Report supports full data export, including:
 

• All visible columns

• Calculated totals

• Applied filters
   

Exports are typically used for:
 

• Accounting reviews

• External reporting

• Audit preparation

• Management presentations
  
   

- CashFlow Report
 

Week-Based Cash Movement & Liquidity Visibility Module
 

- Conceptual Overview (What the CashFlow Report Is)
 

The CashFlow Report is a time-sensitive financial visualization module designed to show how money moves into the business over time, with a strong emphasis on weekly liquidity awareness.
 

The CashFlow Report answers:
 

“When is money actually coming in — and how strong is our cash position right now?”

It transforms raw payment data into temporal insight, allowing teams to understand cash availability, trends, and momentum.
 

- Why the CashFlow Report Exists
 

In real business operations, profitability alone is not enough.
Cash timing is critical.

A company can be profitable on paper but still fail if cash does not arrive on time.
 

The CashFlow Report exists to:
 

• Monitor short-term liquidity

• Identify strong or weak weeks

• Track payment inflow patterns

• Support financial planning and forecasting

• Help management act before cash shortages occur
   

- What the CashFlow Report Represents
 

The CashFlow Report is a time-based financial intelligence view that shows how money actually moves into the business over time.
It does not focus on invoices, promises, or obligations — it focuses purely on real incoming payments.
 

This report is designed to answer one critical business question:
 

“When does money actually arrive, and how strong is our cash position over time?”

By transforming individual payment records into weekly and monthly trends, the CashFlow Report gives management a clear understanding of liquidity, momentum, and financial stability.
 

- Core Philosophy: Time Over Transactions
 

Unlike transaction-level reports, the CashFlow Report is time-centric, not document-centric.
 

This means:
 

• Payments are aggregated

• Individual invoices are abstracted

• The focus is on period strength, not record count
   

This makes the report ideal for:
 

• CFOs

• Business owners

• Financial controllers

• Strategic decision-makers
   

- Week-Based Intelligence (The Heart of CashFlow)
 

Why Weeks Matter - 
 

Weeks represent a natural operational rhythm:
 

• Payroll cycles

• Supplier payments

• Customer payment habits

• Banking settlement patterns
   

The CashFlow Report is therefore built around ISO week numbers, ensuring consistency and accuracy.
 

- Current Week Highlighting (Real-Time Awareness)
 

The system automatically detects the current ISO week and visually highlights it in the interface.
 

This provides:
 

• Immediate orientation (“Where are we now?”)

• Context for recent performance

• A reference point for comparison with past weeks
   

This small visual cue dramatically improves financial awareness.

- Monthly Cash Inflow 
 

Purpose:

To show long-term cash trends.

What it displays:
 

• Last 12 months

• Total incoming payments per month

• Currency-aware amounts

• Color-coded bars for clarity
   

Business insight provided:
 

• Growth or decline patterns

• Seasonal behavior

• Performance comparison between months

• Long-term cash stability
  
  
   

  - Final Perspective
   

  The CashFlow Report is not just a chart — it is a financial control panel.
   

  It gives businesses:
   

• Confidence in daily decisions

• Visibility into short-term liquidity

• In simple terms:
  
  If Payment Tracking shows what happened, the CashFlow Report shows what matters next.
   

- Obligo Report
 

Customer Obligation & Debt Visibility Module
 

- Conceptual Overview (What the Obligo Report Is)
 

The Obligo Report is a financial responsibility and exposure reporting module designed to give organizations a clear, aggregated view of how much money customers owe at any given time.
 

Rather than focusing on individual invoices or payments, the Obligo Report answers a higher-level business question:
 

“What is each customer’s total financial obligation to us?”

It consolidates data from documents, payments, and customer records into a single, customer-centric financial view.
 

- Why the Obligo Report Exists
 

In real-world business operations, financial risk is not measured per invoice — it is measured per customer.
 

The Obligo Report exists to:
 

• Monitor customer debt exposure

• Support credit control decisions

• Identify high-risk or overdue customers

• Enable management-level financial oversight

• Provide a foundation for collections, follow-ups, and policy enforcement
   

This report is especially critical for:
 

• Finance teams

• Account managers

• Business owners

• Credit control departments
   

- Understanding “Obligo” in the System
 

The term Obligo represents financial commitment, not just unpaid invoices.
 

It combines:
 

• Open invoices

• Outstanding balances

• Customer-level obligation limits

• Historical document data
   

This is why the Obligo Report reads from both:
 

• documents (actual financial transactions)

• contactus (customer obligation metadata)
   

- Data Sources & Their Roles
 

- Documents Table
 

Provides:
 

• Invoice totals

• Credit documents

• Financial movement history
   

- Contactus Table
 

Provides:
 

• Official obligo amount

• Payment terms

• Shared ownership (team visibility)

• Customer identity
   

Together, these create a reliable, reconciled view of customer debt.
 

- Filtering Philosophy (Why So Many Filters Exist)
 

The Obligo Report supports extensive filtering because financial questions vary by role.
 

Examples:
 

• Management: “Who owes us the most?”

• Sales: “Which of my customers are overdue?”

• Finance: “What is our exposure per company or team member?”
   

Filters allow slicing the same data from multiple strategic angles.
 

- Company-Level Filtering
 

Supports organizations that:
 

• Operate under multiple companies

• Use different invoice settings

• Need legal separation of obligations
   

This ensures:
 

• Accurate reporting

• Legal clarity

• Correct financial responsibility
   

- Team Member Visibility & Control
 

The Obligo Report respects internal ownership.
 

How this works:
 

• Normal users see only customers assigned to them

• Shared customers are visible via shared_with

• Admins and member-admins see everything
   

This prevents:
 

• Data leakage

• Unauthorized financial insight

• Cross-team confusion
  
   

⚙️ Smart Processing Logic (Behind the Scenes)
 

The module dynamically decides:
 

• Whether to filter in SQL (for performance)

• Or filter in PHP (for flexibility)
   

This hybrid approach ensures:
 

• Speed for large datasets

• Accuracy for complex filters

• Scalability as data grows
   

- Export & Reporting Use
 

The Obligo Report supports full export, making it suitable for:
 

• Management presentations

• External accounting

• Audits

• Legal follow-ups
   

Exports always respect:
 

• Active filters

• Visible columns

• User permissions
   

- Integration with the Rest of the System
 

The Obligo Report is deeply connected to:
 

• Customer profiles

• Document history

• Payment tracking

• Team management

• Invoice creation
   

It acts as a financial hub, not an isolated report.
 

- Security & Data Isolation
 

Because obligo data represents financial risk, strict controls apply:
 

• Organization-level isolation

• Role-based access

• Shared-customer logic

• SQL injection protection
   

This ensures financial confidentiality at all times.
 

- Cunto Module
 

A Controlled, Conditional Check-Processing Workflow
 

- Conceptual Overview (What Cunto Really Is)
 

The Cunto module is a specialized extension of the Checks system, designed for organizations that require a separate, more controlled check-handling workflow.
 

While the standard Checks module handles general check payments, Cunto exists for scenarios where checks must follow stricter business, accounting, or compliance rules.
 

It is not a duplicate module.
It is a conditional operational layer that applies additional validation, review, and workflow discipline to check payments.
 

- Why the Cunto Module Exists
 

Not all organizations treat checks the same way.
 

Some businesses require:
 

• A separate review process

• A dedicated operational flow

• Controlled visibility to specific users

• Additional validation before status changes
   

The Cunto module solves this by:
 

• Reusing the same data structure

• Applying a different workflow logic

• Enforcing module-level access rules
   

This allows organizations to maintain financial consistency while supporting custom operational requirements.

 

- Cunto Workflow Philosophy
 

Cunto enforces the idea that not every check can be processed freely.
 

In Cunto:
 

• Status changes are intentionally gated

• UI actions reflect workflow discipline

• Data presentation is aligned with process compliance
   

This makes it ideal for:
 

• Regulated environments

• Internal audit workflows

• Sensitive financial operations

• Legacy or contractual check handling
   

- Status Handling in Cunto
 

Although Cunto uses the same status values as Checks, the way statuses change is different.
 

Status updates:
 

• Pass through Cunto-specific validation

• Use a dedicated API endpoint

• Enforce tighter logic before persistence
   

This prevents:
 

• Accidental approvals

• Premature status changes

• Unverified financial confirmations
   

- Cunto-Specific Document View
 

The Cunto module provides a custom document HTML rendering, even though the underlying data is the same.
 

Why?
 

• To match the Cunto workflow language

• To show only relevant controls

• To visually separate it from general Checks
   

This ensures users immediately understand:
 

“I am in a controlled financial flow.”

- Access Control & Responsibility
 

Just like Checks, Cunto enforces:
 

• Team-member-based visibility

• Organization isolation

• Admin override access
   

But with one key difference:
 

If the module is disabled, the tab does not exist.

This eliminates:
 

• Accidental access

• User confusion

• Unauthorized actions
   

- Image & Evidence Handling
 

Cunto fully supports:
 

• Multiple check images

• Secure storage

• Inline previews

• Full-screen inspection
   

This keeps Cunto audit-ready, just like Checks.
 

- Reporting & Export Consistency
 

Even though the workflow is stricter, Cunto data remains compatible with all reports.
 

Exports:
 

• Respect filters

• Include status & rejection data

• Preserve audit context
   

This means:
 

• Finance teams can trust the numbers

• Auditors can trace the origin

• No reconciliation gaps exist
   

- System Integrations
 

Cunto integrates seamlessly with:
 

• Customers

• Missions

• Documents

• Team management

• Reports & obligo

• Image storage
   

It does not create a parallel universe — it creates a controlled lane within the same system.
 

- Security & Compliance
 

Cunto reinforces:
 

• Feature-level access control

• User-level visibility

• Intentional status mutation

• Full traceability
   

It is designed for high-trust financial environments where mistakes are costly.


 

- Checks Module
 

Controlled, Auditable, and Legally Traceable Check Payment Management
 

- Conceptual Overview (What the Checks Module Really Is)
 

The Checks module is a specialized financial control layer designed exclusively for managing check-based payments, which are fundamentally different from digital payments.
 

Unlike credit cards or bank transfers, checks are delayed, conditional, and legally sensitive.
They may:
 

• Be deposited days later

• Bounce due to technical or legal reasons

• Enter legal recovery workflows

• Require manual follow-up and documentation
   

Because of this, the Checks module exists as a dedicated operational system, not just another payment list.
 

- Why Checks Require Their Own Module
 

Checks introduce risk, delay, and legal exposure.
 

This module ensures:
 

• Every check has a life cycle

• Every status change is intentional

• Every rejection is explicitly documented

• Every image is stored and traceable

• Every check is owned by a responsible team member
   

Without this structure, checks would become financial blind spots.
 

- Life Cycle of a Check (High-Level Flow)


Check Received
   │
   ▼
In Treatment
   │
   ├─► Paid Up
   │
   ├─► In Agreement
   │
   └─► Legal / Attorney

 

Each stage reflects a real-world banking and legal state, not just an internal label.
 

- Status System (Operational Meaning, Not Just Colors)
 

Each check status represents a financial and legal condition:
 

• Paid Up (Green)
  
  The check cleared the bank. Money is confirmed. No further action required.
   

• In Treatment (Yellow)
  
  The check is deposited or under review. Outcome is not yet known.
   

• In the Care of an Attorney (Red)
  
  The check failed and entered legal recovery. This status freezes financial assumptions.

• In Agreement (Gray)
  
  A settlement exists. Payment may be structured, delayed, or partially agreed.
   

These statuses directly affect reports, obligo, and risk exposure.

❌ Rejection Reasons – Legal Accountability Layer

 

A rejected check is never “just failed”.

The system enforces 27 predefined banking-standard rejection reasons, ensuring:
 

• Uniform terminology

• Legal defensibility

• Bank compatibility

• Accurate recovery workflows
   

Each rejection reason is stored permanently and linked to:
 

• Status

• Notes

• Team member

• Customer record
   

This is essential for legal disputes, audits, and debt recovery.
 

- Extra Detail JSON – Why It Exists
 

Checks carry non-relational data:
 

• Holder name

• ID number

• Pay-to-order text

• Images

• Assigned team members
   

Instead of fragmenting the schema, all check-specific data is stored inside a structured JSON object, giving flexibility while preserving consistency.
 

This allows:
 

• Future expansion

• Multiple images

• Multi-member responsibility

• Zero schema migrations
   

- Team Member Assignment (Ownership & Responsibility)
 

Every check can be assigned to one or more team members.

This transforms checks from passive records into owned financial tasks.
 

Benefits:
 

• Clear responsibility

• Targeted visibility

• Reduced errors

• Faster resolution
   

Non-admin users see only checks assigned to them, while admins retain full oversight.
 

- Image Management (Proof & Evidence)
 

Each check can store multiple images, such as:
 

• Front / back of check

• Bank stamp

• Legal annotations
   

Images are:
 

• Stored securely

• Previewed inline

• Viewable in full resolution

• Permanently linked to the check record
   

This makes the module audit-ready at all demonstrates proof of payment or failure.
 

✏️ Editing Philosophy (Controlled, Not Freeform)
 

Check details can be edited, but never casually.
 

Edits update:
 

• Structured JSON fields

• Notes

• Status

• Rejection reasons
   

Every change is intentional and reflected immediately in:
 

• Reports

• Obligations

• Legal workflows
   

There is no “silent correction.”
 

- Export & Reporting Integrity
 

Exports include:
 

• Check holder details

• Status

• Rejection reasons

• Assigned members

• Notes

• Amounts & currency
   

Exports always:
 

• Respect filters

• Reflect live status

• Preserve legal context
   

This ensures exported data is safe for accountants, lawyers, and auditors.
 

- Security & Access Control
 

The Checks module enforces:
 

• Organization-level isolation

• Role-based visibility

• Assignment-based access

• Safe deletion with confirmation
   

No user can accidentally:
 

• View unauthorized checks

• Modify unrelated records

• Delete checks without intent
  
  
   

- Documents Module
 

Unified Financial Document Intelligence & Control Layer
 

- Conceptual Overview (Why This Module Exists)
 

The Documents module is the authoritative registry of all financial documents created inside the system.

It does not only display invoices — it connects documents, payments, customers, companies, projects, and compliance logic into a single operational view.
 

Every document that has financial meaning eventually appears here:
 

• Invoices

• Receipts

• Tax invoices (GI / IR)

• Credit invoices

• Orders (detail, purchase)
   

If the Payment Tracking module answers “what happened to the money?”,
the Documents module answers “why does this money exist?”
 

- Role of Documents in the Financial Ecosystem
 

Customer
   │
   ▼
Document Created
   │
   ├─► Invoice / Order
   │
   ├─► Receipt / Tax Invoice
   │
   ├─► Credit / Adjustment
   │
   ▼
Payment Tracking
   │
   ▼
Accounting Reports

Documents are the legal and logical anchor that:
 

• Define payment obligations

• Control VAT / tax behavior

• Drive payment expectations

• Support audits and disputes
   

- Document Types (Operational Meaning)

 

Each document type has a distinct accounting role:
 

• Invoice → Requests payment

• Receipt → Confirms payment

• GI / IR (Tax Invoice) → Legal tax declaration

• Receipt Tax Invoice → Combined payment + tax

• Credit Invoice → Reduces liability

• Orders → Operational intent (pre-financial)
   

The module does not merge these roles — it keeps them clearly separated, which is essential for compliance.
 

- Views System – Why “Everything / Moved / Did Not Pass” Exists

The Documents module is context-aware, not static.
 

- Everything
 

Shows all documents, regardless of payment state.

Used for:
 

• Full audits

• Legal history

• Long-term reporting
   

✅ Moved
 

Shows documents linked to successful payments.

Used for:
 

• Revenue confirmation

• Accounting exports

• Tax submissions
   

❌ Did Not Pass
 

Shows documents linked to failed or incomplete payments.

Used for:
 

• Collection follow-ups

• Risk analysis

• Customer support
   

Each view uses its own column configuration, so users see only what matters in that context.
 

- Custom Fields Engine (Core Differentiator)
 

The Documents table is not hard-coded.
 

Each user can:
 

• Choose visible fields

• Reorder columns

• Pin important columns

• Rename column labels

• Mix static + dynamic fields
   

Why this matters:
 

Different roles ask different questions:
 

• Accountant → Amounts, tax, company

• Sales → Customer, manager, tags

• Operations → Status, folders, notes
   

The system adapts without duplicating screens.


- Filtering Philosophy (Real Business Use Cases)

 

Filters are designed around human workflows, not database structure.
 

• Date range → Period accounting

• Amount range → Fraud & exception detection

• Company → Multi-company organizations

• Team member → Responsibility tracking

• Customer status / manager → Sales & CRM alignment

• Tags → Business classification

• Shared with → Internal collaboration
   

This allows the same dataset to serve finance, sales, and management simultaneously.
 

- Status & Payment Awareness
 

Documents do not guess payment state — they reflect it.
 

• Paid → Green

• Unpaid → Red

• Partial → Yellow
   

These states are directly synced with Payment Tracking and cannot drift.
 

This guarantees:
 

• Accurate cash reports

• Reliable aging analysis

• Correct revenue recognition
  
  
  - Export Logic (Why It’s Safe for Accounting)
  
   

  Exports are not raw dumps.
   

  They:
   

• Respect active filters

• Respect visible columns

• Include custom fields

• Preserve order and labels

• This ensures exported data can go directly to accountants, without cleanup.
   

  ---

  - Data Flow (From Click to Screen)
   

  1️⃣ User opens Documents
  
  2️⃣ System loads:
   

• Column config

• Field order

• View type
   

• 3️⃣ Query is dynamically built
  
  4️⃣ Headers are generated
  
  5️⃣ Rows are rendered with:
   

• Icons

• Images

• Status indicators
   

• 6️⃣ HTML + pagination returned via API
   

  This makes the module:
   

• Fast

• Flexible

• Stateless
   

• ---

  - Security & Compliance Layer
   

• User-scoped data isolation

• Role-based field visibility

• No silent deletion

• Full audit trail

• Every document is legally defensible.
  
  
  
   

- What is Payment Tracking?
 

Payment Tracking is the core financial intelligence engine of the Reports module.
It aggregates all incoming payments, regardless of source, method, or document type, and presents them in a searchable, filterable, auditable timeline.
 

This module is read-only by default, except for:
 

• Refund actions

• Status handling

• Deposit linking
   

- Architecture Overview (Visual Concept)
 

documents_payments
│
├─ contactus        → Customer identity
├─ user_detail      → Team member (who charged)
├─ documents        → Invoice / Receipt / GI-IR
├─ invoices_settings→ Company & invoice config
├─ deposit_bank     → Bank deposit status
│
▼
Payment Controller
(loadrecord_payment)
│
▼
HTML + Chart JSON
│
▼
Payment Tracking UI

 

Why Payment Tracking Exists (Business Purpose)
 

Payment Tracking exists to replace manual accounting uncertainty with:
 

✅ Full transparency
✅ Real-time visibility
✅ Accurate reconciliation
✅ Audit-ready records
✅ Automated reporting
 

It acts as the single source of truth for:
 

• Finance teams

• Management

• Auditors

• Customer support
  
  
  - Where Payment Tracking Sits in the System
  
  
  Customer
     │
     ▼
  Invoice / Order
     │
     ▼
  Payment Attempt
     │
     ├─► Success ──► Deposit ──► Accounting Reports
     │
     └─► Failure ──► Retry / Audit / Support
  
  
  Payment Tracking sits between operations and accounting, ensuring no financial action is ever invisible.
  
  
  - Payment Lifecycle – Visual Breakdown
   

  1️⃣ Creation Phase – Intent Becomes Action
   

  A payment record is created whenever:
   

• A customer pays via gateway (card, Bit, transfer, etc.)

• A cashier records cash or check

• A subscription renews automatically

• An external API submits a transaction

• At this moment, the system captures:
   

• Customer identity

• Payment amount & currency

• Payment method

• Related document(s)

• Processing team member

• Technical gateway response

• This guarantees traceability from the first second.
   

  ---

  
  2️⃣ Processing Phase – Reality Check
   

  Not all payments are immediately “real money”.

  During this phase, the system evaluates:
   

• Gateway approval vs settlement

• Check clearance

• Payments may exist in temporary states, allowing the system to:

• Retry safely

• Show failures transparently

• Prevent premature revenue reporting
  
   

• ---

  3️⃣ Finalization Phase – Accounting Truth
   

  Only when a payment is confirmed does it:
   

• Change status to Moved

• Appear in revenue calculations

• Become eligible for deposit & refund

• Flow into CashFlow and Obligo reports

• This protects accounting integrity.
   

  ---

  
  - Payment Status System (Why It’s Critical)
  
   

  ✅ Moved (Successful)
   

  Represents verified money.
   

• Included in financial reports

• Eligible for refund

• Can be deposited to bank

• Considered accounting-safe
   

• ❌ Did Not Pass (Failed)
   

  Represents attempted but unrealized money.
   

• Never deleted
   

• Failed payments are business evidence, not errors to hide.

   

  ---

  - Filtering Logic – Designed for Real Business Questions
   

  Every filter exists because someone in finance or support actually needs it.
   

  - Date Filters
   

  Accountants work by periods, not guesses.
  Filters operate on payment creation date, ensuring accurate cash-basis reporting.
   

  ---

  
  - Amount Range
   

  Used for:
   

• Fraud detection

• High-value audits

• Exception analysis

• ---

  - Customer, Email, Phone
   

  Support teams search by human memory, not IDs.
  This enables fast issue resolution.

  ---

  - Payment Method
   

  Each method has different:
   

• Fees

• Risks

• Settlement delays

• Separating them allows:

• Gateway performance evaluation

• Cost optimization

• Bank reconciliation planning
   

• ---

  - Multiple Payments & Mixed Methods (Real-World Accounting)
  
   

  One invoice can be paid using:
   

• Cash

• Credit card

• Transfer

• All together
   

• Instead of duplicating invoices, the system stores structured multi-receipt data, ensuring:
   

• VAT accuracy

• Correct refunds

• Legal compliance
   

• - Deposit Awareness – Bridging Software & Banks
   

  A successful payment ≠ money in the bank.
   

  Payment Tracking explicitly tracks:
   

• Payment success

• Deposit status

• Deposit date

• Bank linkage

• This enables:

• Accurate cash flow forecasts

• Deposit reconciliation

• Audit-ready reports
  
   

  - Security, Audit & Trust Layer
   

  Every payment:
   

• Is scoped to organization

• Is role-validated

• This ensures:

• Legal defensibility

• Auditor confidence

• Internal accountability

• Cannot be silently removed

• Is traceable to a user
  
  
  
   

- Reports Page
 

Central Payment, Finance & Cash Intelligence Module

- High-Level Overview (Main Module Purpose)
 

The Reports Page is the financial brain of the biz1 system.
 

It consolidates all monetary activity—payments, invoices, checks, deposits, obligations, cash flow, and orders—into a single, structured reporting hub.
 

 If Products & Orders generate money, the Reports Page explains what happened to that money.

• - Architecture Position (Very Important)
   

  SYSTEM CORE
  │
  ├── Customers
  ├── Products
  ├── Orders
  ├── Documents (Invoices / Receipts)
  │
  └── REPORTS PAGE  ← THIS MODULE
       ├── Payment Tracking
       ├── Documents
       ├── Checks / Cunto
       ├── Obligo
       ├── CashFlow
       ├── Order Report
       ├── Payers Tracking
       ├── Monthly Report
       └── Deposit
  
  

  
  ✔ Reports do not create data
  ✔ Reports read, analyze, group, and visualize data
  ✔ Reports are 100% dependent on other modules
  
  
   

  - Sub-Modules Explained (Conceptual, Not CRUD)
   

  ---

  1️⃣ Payment Tracking
   

  - Purpose:
  
  Tracks actual money movements.
   

• Key Characteristics:
   

• Chart-driven (monthly bars, pie charts)

• Filters by date, customer, project, team, gateway

• Export-ready

• Status-based (Moved / Did Not Pass)
   

• ---

  2️⃣ Documents
   

  - Purpose:
  
  Financial visibility per document, not per payment.
   

• Key Characteristics:
   

• Multi-document support (invoice, receipt, GI/IR, credit)

• Custom fields per organization

• Company-based filtering

• Deep integration with Documents module

• ---

  3️⃣ Checks
   

  - Purpose:
  
  Full lifecycle tracking of check-based payments.
   

• Key Characteristics:
   

• 27 structured rejection reasons

• Status workflow

• Image upload (check photo)

• Mission creation from checks

• ---

  4️⃣ Cunto (Conditional Module)
   

  - Purpose:
  
  Specialized check workflow for Cunto-enabled organizations.
   

  Key Characteristics:

• Same financial logic as Checks

• Different approval/status flow

• Enabled only if cunto_module exists
   

• ---

  5️⃣ Obligo Report
   

  ⚠️ Purpose:
  
  Shows customer debt exposure.
   

   

• Key Characteristics:
   

• Grouped by customer

• Date-based filtering

• Company & team filtering

• Critical for risk management
   

• ---

  6️⃣ CashFlow Report
   

  - Purpose:
  
  Shows timing of money, not just totals.
   

• Key Characteristics:
   

• Week-based analysis

• Predictive financial planning

• Visual flow representation
   

• ---

  7️⃣ Order Report (Admin Only)
   

  - Purpose:
  
  Connects orders → invoices → payments.
   

• Key Characteristics:

• Chart-driven

• Admin-level visibility

• Operational finance control
   

• ---

  8️⃣ Payers Tracking
   

  - Purpose:
  
  Customer-centric payment summary.
   

• Key Characteristics:
   

• Aggregated totals per customer

• Gateway filtering

• Export-ready
   

• ---

  9️⃣ Monthly Report
   

  - Purpose:
  
  Long-term financial trend analysis.
   

  Two Modes:
   

• Debt View

• Open Orders View
   

• Key Characteristics:
   

• Rolling 12-month window

• Debit / credit calculation

• Customer grouping
   

• ---

  - Deposit Report
  
   

  - Purpose:
  
  Tracks bank-level deposits.
   

• Key Characteristics:
   

• Cash, checks, transfers

• Bank selection

• Team member attribution
   

• ---

  - Connected Systems (Critical)
   

  The Reports Page pulls data from:

• Customers (contactus)

• Documents (documents)

• Orders

• Payment gateways

• Banks

• Teams

• Campaigns

• Subscriptions
   

• ✔ No data duplication
  ✔ Read-only analytics layer
   

  ---

  
  ⚙️ Settings & Customization
   

• Default tab per user

• Custom payment fields

• Company-based invoice filtering

• Payment gateway configurations

• Role & plan restrictions
   

• All stored in:
   

• user_detail

• invoices_settings

• payment_detail
   

• ---

  - Security & Governance
   

• Login enforcement

• Plan-based access

• Role-based tab visibility

• Organization-level data isolation

• Secure export & API access
  
   

• ---

  - Final Summary
   

  
  Reports Page =
  
  ✔ Financial transparency
  ✔ Payment intelligence
  ✔ Risk & obligation control
  ✔ Cash flow forecasting
  ✔ Multi-gateway reporting
  ✔ Enterprise-grade analytics
  
  
  
  

   

- What Is the Storage Section?
 

The Storage section displays all products physically stored in warehouses, along with:
 

• Inventory quantities

• Sold quantities

• Damaged quantities

• Category & sub-category

• Cost price (permission-based)
   

Each row represents a product in a specific storage location.

- What Storage Is Used For
 

- Inventory Control
 

• View real-time stock

• Track available quantities

• Monitor sold & damaged units
   

- Multi-Storage Tracking
 

• Same product in multiple storages

• Central + branch warehouses

• Sub-storage inclusion
   

- Reporting & Export
 

• Export inventory to Excel

• Category-wise stock analysis

• Storage utilization review
   

- Storage Interface – How It Works
 

Top Bar:
[ Select Storage ▼ ]   [ Search Product ]   [ Export File ]

Table Columns:
# | SKU | Product | Supplier | Category | Cost | Sold | Inventory | Action
 

Storage Selector
 

• All → Shows products from all storages

• Specific Storage → Shows products from that storage + its sub-storages

? Filtering & Search
 

• ? Search by product name or SKU

• ? Filter by category

• ? Filter by sub-category

• All filters work together in real time
   

➕ Adding Products to Storage
 

Add Flow

1. Click green “+” icon

2. Select storage

3. Enter stock quantity

4. Optional: damaged units & notes

5. Save → inventory updates instantly
    

✏️ Editing Inventory
 

• Edit stock quantity

• Adjust damaged count

• Inventory auto-recalculates

• Changes reflect across reports
   

? Exporting Inventory
 

• Click Export File

• Excel downloads

• Respects filters (storage, category, search)
   

? Inventory Calculation Logic
 

Available Inventory =
stock
- sold
- damaged
- moved_from_storage
+ moved_to_storage

✔ Automatic
✔ No manual recalculation
✔ Always consistent
 

Product Movement & Storage Request 
 

? What Is the Request Section?
 

The Request section manages how products move:
 

• Between storages

• From suppliers into storage
   

Every request creates a controlled, auditable workflow.
 

? Request Use Cases
 

? Storage-to-Storage Transfer
 

• Move stock from one warehouse to another

• Track outgoing & incoming quantities
   

? Supplier Orders
 

• Order products from suppliers

• Receive inventory into storage
   

? Documentation
 

• Generate PDF transfer / order documents

• Maintain audit trail
   

? Request Interface Overview
 

Table Columns:
Request ID | User | Date | Type | From | To | Qty | Notes | Status | Actions

Request Types
 

• Moving Request – Storage → Storage

• Supplier Order – Supplier → Storage
   

➕ Creating a Request
 

Step-by-Step
 

1. Click Add Request

2. Select request type

3. Choose:

   • From storage

   • To storage OR supplier

4. Add products & quantities

5. Optional: save as Draft

6. Submit
    

✔ Supports multiple products
✔ Single request = multiple items
 

✅ Approve / ❌ Reject / ? Receive
 

• Approve → authorizes movement

• Reject → cancels request

• Receive → updates inventory automatically
   

Inventory updates happen only on Receive.
 

? PDF Generation
 

• One-click PDF

• Includes:

  • Storage details

  • Products & quantities

  • Notes

  • Request metadata
     

? How Storage & Request Work Together

 

Supplier / Storage
       ↓
    Request
       ↓
   Approval
       ↓
   Receive
       ↓
Inventory Updated

✔ Zero manual stock edits
✔ Full traceability
✔ Clean audit trail
 

? Permissions & Control
 

Storage Permissions
 

• View inventory

• Edit inventory

• View cost & sold

• Delete inventory entries
   

Request Permissions
 

• Create requests

• Approve / reject

• Edit drafts

• Receive inventory
   

All permissions controlled via role-based JSON config.
 

?️ Database Integrity (Conceptual)
 

• storage_products → inventory truth

• storage_request → movement log

• ec_product → aggregated stock

• JSON used for flexibility & scale
   

✔ No duplication
✔ No race conditions
✔ Always consistent

? Final Summary
 

Storage & Request Module =
✔ Physical inventory control
✔ Multi-warehouse support
✔ Secure movement workflow
✔ Supplier integration
✔ Automatic stock calculation
✔ PDF documentation
✔ Enterprise-ready design

What This Module Is
 

The Storage List module is the physical inventory backbone of the system.

It represents real-world warehouses, rooms, shelves, or locations and connects them directly to:
 

• Products

• Inventory quantities

• Team members

• Transfers & requests
   

If Products define what you sell,
Storage List defines where it physically exists.

- How the Storage Module Is Structured (Visual Concept)
 

Main Warehouse (Parent)
├── Section A
│   ├── Room 1
│   └── Room 2
└── Section B
    └── Room 3

✔ Unlimited hierarchy depth
✔ Real-world mapping
✔ Clean parent → child logic
 

- Core Responsibilities of Storage List

- Storage Location Management

Create unlimited storage locations

Rename, edit, or remove locations

Add notes for internal clarity
 

- Team-Based Access

Assign team members to storages

Control who manages which warehouse

Visual avatar-based team display
 

- Hierarchical Organization

Parent storages (main warehouses)

Child storages (sections, rooms)

Nested storage logic
 

- Product Placement

Add existing products to storage

Create new products directly in storage

Track inventory per location

 

What Default Storage Means
 

• Only one storage can be default

• First storage created → auto default

• Used when:

  • Creating new products

  • Auto-assigning inventory

✔ Changeable anytime
✔ System-enforced uniqueness
 

- Expandable Views (Power Feature)
 

- View Products in Storage

Click the eye icon to expand:
 

Storage → Products
# | SKU | Product Name | Category | Stock

✔ Live inventory per storage
✔ No navigation away from page

- View Sub-Storages
 

Click the sub-storage icon:
 

Storage → Sub-Storages
# | Sub-Storage Name | Actions

 

✔ Tree-style navigation
✔ Easy hierarchy management

➕ Adding Products to Storage

 

Two Ways to Add Products
 

1️⃣ Add Existing Product
 

• Select product

• Enter quantity

• Assign to storage
   

2️⃣ Create New Product
 

• Full product form

• Auto-linked to storage

• Inventory created instantly
   

- What Happens on Delete (Smart Logic)
 

When a storage is deleted:
✔ Storage requests removed
✔ Products are unlinked, not deleted
✔ Inventory integrity preserved
 

- Cannot delete if:
 

• Products still exist inside storage

- Behind-the-Scenes Intelligence
 

Inventory Sync
 

• Each storage has its own stock count

• Products can exist in multiple storages

• Inventory tracked per location
   

JSON-Based Flexibility
 

• Team members stored as JSON

• Product-storage mapping stored as JSON

• Easy scaling without schema explosion
   

- Connected Modules (Ecosystem View)
 

•  Products – Where items are assigned

•  Storage Requests – Transfers between storages

•  Team Members – Storage access control

•  Reports – Inventory & movement insights

- Permissions & Control
 

• View storages

• Add / edit storages

• Delete storages

• Assign team members

• Manage inventory
   

All controlled via role-based permissions.
 

- Real-World Example
 

Company:
- Main Warehouse (default)
- Tel Aviv Branch
- Jerusalem Branch

Each branch:
- Has its own stock
- Has its own team
- Shares same product catalog
 

✔ Accurate
✔ Scalable
✔ Business-ready

- Final Summary (One Look)
 

Storage List =
✔ Warehouse control
✔ Inventory precision
✔ Team-based access
✔ Real-world hierarchy
✔ Clean UI
✔ Enterprise-ready logic


 

- What Is the Insurance Module?
 

The Insurance module is a specialized financial & customer-risk management system.
 

It does not behave like regular products or orders.
 

Instead, it models:
 

• Long-term commitments

• Recurring financial responsibility

• Family-based coverage

• Regulatory and compliance-sensitive data
   

Insurance is not a transaction.
It is a relationship over time.

- Why the Insurance Module Exists
 

Traditional sales systems fail at insurance because insurance:
 

• Is time-bound

• Is family-centric

• Has multiple statuses

• Requires continuous monitoring

• Is not completed in one payment
   

This module exists to solve that complexity.
 

- Core Concept: Insurance Is a Living Entity
 

An insurance record is not static.
 

It evolves through:
 

• Status changes

• Coverage updates

• Family changes

• Amount recalculations

• Regulatory updates
   

The Insurance module is designed to track life cycles, not snapshots.
 

- Family-Centric Insurance Architecture

At the heart of the module lies a family model:
 

Customer
   ↓
Insurance Family
   ↓
Main Member
   ↓
Dependents
   ↓
Multiple Insurance Policies

This reflects real-world insurance structures, not accounting shortcuts.
 

- What the Insurance Module Manages
 

- Insurance Family Members
 

Each family member represents:
 

• A real insured individual

• A legal identity

• A coverage relationship
   

This enables:

✔ Accurate compliance
✔ Clear beneficiary structure
✔ Family-level reporting
 

- Insurance Policies
 

Each policy tracks:
 

• Contract reference

• Insurance category

• Coverage dates

• Financial amount

• Operational status
   

Policies are attached to people, not just customers.
 

- Insurance Amount Intelligence
 

The system calculates and maintains:
 

• Total insurance amount

• Life insurance totals

• Health insurance totals
   

These values are:
 

• Auto-aggregated

• Displayed at customer level

• Used in reporting & analytics
   

- Insurance Status Lifecycle (Business-Critical)
 

Insurance does not jump from created to completed.

Statuses reflect real insurance workflows:

 טרם הוזמן    =      Not Yet Ordered
 נשלחה בקשה    = Request Sent 
 התקבל     =   Approved / Rejected
 ריגקט      = Rejected
 

Color-coding ensures instant visual understanding.
 

- Analytics & Reporting Philosophy
 

Insurance reporting focuses on patterns, not totals.
 

The module answers questions like:
 

• How many active insured members?

• Which agents close more policies?

• What is the monthly insurance growth?

• Where are insurance requests stuck?
   

This is why charts are core, not optional.
 

- Visual Intelligence Built In
 

The Insurance dashboard provides:
 

•  Distribution charts

•  Member-based analysis

•  Agent/seller performance

•  Monthly & yearly trends
   

This allows management-level insight at a glance.
 

- Bulk Data & External Reality
 

Insurance data often comes from:
 

• External agencies

• Government platforms

• Excel exports

• Legacy systems
   

The module supports structured import, ensuring:

✔ Data normalization
✔ Column mapping
✔ Error handling
 

- How Insurance Connects to the System
 

- Customers
 

Insurance lives inside customer profiles, not outside.

Customer dashboards instantly reflect:
 

• Insurance status

• Coverage amount

• Order state
   

- Orders
 

Insurance order status integrates with:
 

• Order tracking

• Workflow management

• Operational follow-ups
   

- Products & Categories
 

Insurance categories are organized using:

• Product category logic

• Reporting hierarchy

• Business classification
   

- Dashboard
 

Insurance KPIs feed:
 

• Executive dashboards

• Risk analysis

• Performance summaries
   

- Compliance & Governance
 

Insurance data is:
 

• Identity-sensitive

• Financially regulated

• Time-critical
   

This module ensures:

✔ Controlled access
✔ Role-based permissions
✔ Audit-ready structure
 

- Who Uses the Insurance Module?
 

This module is essential for:

 Insurance agents
 Managers & supervisors
 Back-office operations
 Executives
 System administrators
 

- Strategic Business Value
 

Without this module:
 

• Insurance data becomes fragmented

• Families are misrepresented

• Status tracking is manual

• Reporting is unreliable
   

With this module:

✔ Insurance becomes measurable
✔ Operations become predictable
✔ Customers gain transparency
 

- Final Summary
 

Insurance is not a product.

It is a long-term financial relationship.
 

This module transforms insurance from:
 

“Scattered records”

Into:

A structured, visual, reportable system

- What Is the Suppliers Module?
 

The Suppliers module is the foundation of inbound business operations.
 

It represents who you buy from, not who you sell to.
 

Every product you stock, every purchase order you create, every supplier invoice you receive — all of it starts here.
 

If Customers power revenue,
Suppliers power availability, cost
control, and inventory flow.

- Why the Suppliers Module Exists
 

Businesses don’t operate in isolation.

They rely on vendors for:
 

• Products

• Raw materials

• Services

• Inventory replenishment
   

The Suppliers module exists to centralize and control supplier relationships, ensuring:
 

✔ Accurate supplier records
✔ Clear financial tracking
✔ Traceable procurement
✔ Reduced operational risk
 

- Where Suppliers Fit in the System
 

Suppliers sit upstream of sales and inventory.

Supplier
   ↓
Purchase / Storage Request
   ↓
Inventory / Stock
   ↓
Products
   ↓
Orders → Customers
 

This makes Suppliers a critical starting point, not a side module.
 

- Who Uses the Suppliers Module?
 

This module is used daily by:
 

 Procurement teams – manage vendors
 Inventory managers – restock products
 Finance teams – track supplier payments
 Managers – monitor supplier performance
 Admins – maintain clean vendor data
 

- What a Supplier Represents
 

A supplier is not just a name.
 

In the system, a supplier represents:
 

• A business entity

• A financial counterparty

• A source of products or services

• A recurring operational dependency
   

Each supplier becomes a hub for expenses, orders, and invoices.
 

- Core Responsibilities of the Suppliers Module
 

- Supplier Identity
 

Stores:
 

• Name

• Contact details

• Company ID

• Language preference

• Primary contact person
   

This ensures communication and compliance accuracy.
 

- Supplier Expense Tracking
 

Every cost associated with a supplier can be:
 

• Recorded

• Categorized

• Paid or unpaid

• Reported
   

This allows finance teams to:

✔ Track liabilities
✔ Monitor unpaid invoices
✔ Control cash flow
 

- Supplier Orders & Procurement
 

Suppliers are directly linked to:
 

• Purchase orders

• Storage requests

• Inventory inflow
   

This ensures:
 

• Clear traceability of stock origins

• Accurate inventory valuation

• Supplier accountability
   

- Supplier Invoices
 

Each supplier can have:
 

• Multiple invoices

• Paid or unpaid documents

• Linked storage or order records
   

This enables end-to-end procurement visibility.
 

- Why Suppliers Matter Operationally
 

Without structured supplier management:
 

• Inventory shortages increase

• Costs become unclear

• Duplicate vendors appear

• Financial audits become painful
   

With Suppliers module:

✔ Procurement becomes controlled
✔ Costs become transparent
✔ Vendor relationships improve
 

- Supplier-Centric Business Intelligence
 

Using supplier data, businesses can answer:
 

• Which suppliers cost us the most?

• Who has the most unpaid invoices?

• Which suppliers provide which products?

• Where are procurement bottlenecks?
   

This turns suppliers into measurable assets, not just contacts.
 

- How Suppliers Connect to Other Modules
 

The Suppliers module integrates deeply with:
 

- Products
 

Suppliers are linked to products to identify:
 

• Source of goods

• Supplier-specific pricing

• Product availability
   

- Expenses
 

All supplier-related expenses are centralized, allowing:
 

• Vendor cost analysis

• Payment tracking

• Expense auditing
   

- Storage & Inventory
 

Supplier orders feed directly into:
 

• Storage requests

• Inventory updates

• Stock availability
   

- Documents
 

Supplier invoices and purchase documents ensure:
 

• Financial traceability

• Legal compliance

• Procurement history
   

- Governance & Control
 

Supplier data is protected by:
 

• Role-based permissions

• Controlled editing

• Centralized ownership
   

This prevents:

❌ Duplicate suppliers
❌ Unauthorized changes
❌ Financial inconsistencies
 

- Strategic Value of the Suppliers Module
 

The Suppliers module enables:
 

✔ Reliable procurement
✔ Predictable inventory
✔ Financial clarity
✔ Vendor accountability
✔ Scalable operations

It transforms suppliers from external chaos into structured partners.
 

- Final Summary
 

Suppliers are the backbone of supply-side operations.
 

They define:
 

• Where products come from

• How much they cost

• When inventory is replenished

• What the business owes
   

Without Suppliers:

You sell blindly.

With Suppliers:

You operate intelligently.

- What Is the Detail Orders Module?
 

The Detail Orders module is the most granular and accurate view of sales activity inside the Product Report system.
 

While high-level Orders give summaries,

Detail Orders answer the question:
 

What exactly was sold, to whom, how, when, and under what conditions?

Each record represents a fully expanded order, including:
 

• Every product or group

• Quantities

• Pricing logic

• Customer linkage

• Payment and fulfillment state
   

- Why the Detail Orders Module Exists
 

As businesses grow, summaries are not enough.
 

Organizations need:
 

• Proof of transactions

• Item-level accountability

• Financial traceability

• Customer dispute clarity

• Operational accuracy
   

The Detail Orders module exists to provide absolute transparency at the lowest transaction level.
 

- Where Detail Orders Fit in the System
 

Detail Orders sit between Sales, Finance, Inventory, and Customers.

Product / Group
       ↓
Detail Order (items, quantities, prices)
       ↓
Customer
       ↓
Payment & Status
       ↓
Invoices / Receipts / Inventory
 

This makes Detail Orders the single source of truth for what was actually sold.
 

- Who Uses Detail Orders?
 

This module is heavily used by:
 

 Managers – audit sales accuracy
 Operations – verify fulfillment
 Finance teams – validate revenue
 Support teams – resolve disputes
 Admins – system-level reporting
 

- What a Detail Order Represents
 

Each Detail Order represents a real business transaction, not an estimate or draft.
 

It includes:
 

• Exact items sold

• Prices applied (discounts, VAT, custom pricing)

• Customer identity

• Order lifecycle status

• Payment completion state

• Linked business documents
   

This makes it legally and financially reliable.
 

- What You Can Track with Detail Orders
 

Detail Orders allow you to analyze:
 

• Which exact products were sold

• Which customer bought which item

• How discounts were applied

• Partial vs full payments

• Order lifecycle progress

• Revenue at item level
   

This enables deep business intelligence.
 

- Order Items as First-Class Data
 

Each order contains structured item records, including:
 

• Product / Group / Title

• Quantity

• Unit price

• Discounts

• Final amount

• Item notes

• Item type
   

This allows:

✔ Inventory validation
✔ Margin analysis
✔ Item-level reporting
 

- Payment & Financial Clarity
 

Detail Orders clearly show:
 

• Paid

• Unpaid

• Partially paid
   

This helps finance teams:
 

• Track outstanding amounts

• Identify payment gaps

• Reconcile revenue
   

No guessing. No ambiguity.
 

- Order Lifecycle Tracking
 

Each detail order follows a lifecycle:
 

1️⃣ Created
2️⃣ Processed
3️⃣ Paid (or pending)
4️⃣ Fulfilled
5️⃣ Closed
 

Statuses are configurable and visible, allowing teams to:
 

• Track progress

• Prevent missed steps

• Maintain consistency
   

- Powerful Filtering = Control
 

Detail Orders support filtering by:
 

• Customer

• Date range

• Amount range

• Team member

• Status

• Payment state

• Custom order fields
   

This enables:

✔ Audits
✔ Investigations
✔ Monthly reviews
✔ Compliance checks
 

- Business Scenarios Powered by Detail Orders
 

- Financial Audits

Verify every item sold and paid.
 

- Customer Support

Resolve disputes using item-level evidence.
 

- Inventory Validation

Confirm stock movements align with sales.
 

- Performance Analysis

Understand which products actually generate revenue.
 

- Governance & Accuracy
 

Detail Orders are protected by:
 

• Role-based permissions

• Controlled editing

• Status locking
   

Once an order is closed, it becomes a trusted record, not just editable data.
 

- How Detail Orders Connect to Other Modules
 

Detail Orders integrate deeply with:
 

• Products → item reference

• Customers → buyer identity

• Orders → order workflow

• Documents → invoices & receipts

• Storage → inventory impact

• Reports → sales analytics
   

This makes them central, not optional.
 

- Strategic Value of Detail Orders
 

Without Detail Orders:
 

• Sales data is vague

• Financial audits are slow

• Disputes are harder

• Inventory mismatches increase
   

With Detail Orders:

✔ Precision
✔ Accountability
✔ Transparency
✔ Scalability
 

- Final Summary
 

Detail Orders are the backbone of transactional truth.
 

They transform sales into:

 Auditable records
 Financial evidence
 Operational signals
 Customer history
 

If Products define what you sell,
and Orders define that you sold,
then Detail Orders define how exactly the sale happened.


 

- What Is the Meeting Reports Module?
 

The Meeting Reports Module is the central tracking system for all meetings, appointments, and online sessions across the organization.
 

It answers one critical question:
 

Who met whom, when, why, and with what result?

Meetings are not just calendar events — they represent:
 

• Sales conversations

• Client follow-ups

• Support sessions

• Internal coordination
   

This module turns meetings into structured, reportable business data.
 

- Why the Meeting Reports Module Exists
 

Without structured reporting:
 

• Meetings get forgotten

• Follow-ups are missed

• Team performance is unclear

• Customer engagement is invisible
   

The Meeting Reports module ensures:
 

✔ Accountability
✔ Visibility
✔ Follow-up discipline
✔ Operational clarity
 

- Where Meeting Reports Fit in the System
 

Meeting Reports sit between CRM, Sales, and Operations.
 

Customer / Lead
       ↓
Meeting / Appointment
       ↓
Team Member Interaction
       ↓
Status & Outcome
       ↓
Sales / Support / Follow-up
 

This creates a complete engagement timeline for every customer.
 

- Who Uses Meeting Reports?
 

This module is used by:
 

 Managers – monitor team activity
 Sales teams – track client meetings
 Support teams – log service calls
 Admins – analyze workload & outcomes
 Operations – schedule optimization
 

- What the Meeting Reports Represent
 

Each row in the Meeting Report represents one real interaction.
 

That interaction can be:
 

• A physical appointment

• A scheduled customer meeting

• A Zoom video call

• A follow-up session
   

Each entry captures:
 

• Time

• People involved

• Purpose

• Status

• Outcome indicators
   

- Types of Meetings Covered
 

- Appointments (In-Person / Manual)
 

• Client visits

• Office meetings

• On-site appointments

• Stored as structured calendar events
   

- Zoom Meetings
 

• Online video calls

• Remote consultations

• Virtual sales meetings

• Fully tracked and reportable
   

Both types are unified into one reporting view.
 

- Meeting Status & Visual Language
 

Meetings are visually categorized using color & status indicators.
 

• Blue → Normal / scheduled

• Green → Completed

• Yellow → Pending / upcoming

• Red → Urgent / overdue
   

This allows managers to scan activity instantly without reading details.
 

- What You Can Analyze with Meeting Reports
 

Meeting Reports provide insight into:
 

• How active each team member is

• Which customers receive the most attention

• Missed or overdue meetings

• Meeting completion rates

• Engagement trends over time
   

This turns calendars into performance dashboards.
 

- How Teams Use the Meeting Reports (Real Use Cases)
 

- Sales Teams
 

• Track sales meetings

• Ensure follow-ups happen

• Review customer engagement history
   

- Support Teams
 

• Log customer support sessions

• Track resolution meetings

• Measure response consistency
   

- Managers
 

• Compare team workloads

• Identify inactive members

• Balance scheduling
   

- Calendar Integration (Operational Advantage)
 

Meetings are not isolated reports.
 

They are:
 

• Synced with calendar views

• Displayed visually by day/week/month

• Clickable for detailed review
   

This ensures planning and reporting stay aligned.
 

- Filtering = Control
 

The Meeting Reports module includes practical filters:
 

• By team member

• By customer

• By date range

• By meeting type

• By approval status
   

This allows:

✔ Fast audits
✔ Daily reviews
✔ Monthly performance analysis
 

- Permissions & Governance
 

Meetings involve customer data and internal schedules.
 

The system enforces:
 

• Role-based access

• Approval workflows

• Controlled editing rights
   

Only authorized users can:
 

• Edit meetings

• Approve meetings

• Delete records
   

- How Meeting Reports Connect to Other Modules
 

Meeting Reports do not exist alone.
 

They connect naturally to:
 

• Customers → meeting history

• Team Members → activity tracking

• Calendar → scheduling & planning

• Sales / Orders → pre-sale interactions

• Support workflows → service continuity
   

This ensures meetings are part of the business process, not just events.
 

- Business Value of Meeting Reports
 

This module delivers:
 

✔ Better customer engagement
✔ Clear team accountability
✔ Improved follow-up discipline
✔ Reduced missed opportunities
✔ Transparent activity tracking
 

It transforms meetings from memory-based events into measurable business actions.
 

- Final Summary
 

Meeting Reports are not just logs.
 

They are:
 

 An interaction history
 A team performance mirror
 A customer engagement tracker
 A scheduling intelligence tool
 

Without Meeting Reports, organizations rely on memory.

With them, every interaction becomes visible and actionable.


 

- What Is the Subscriptions Report?
 

The Subscriptions Report is the central control panel for recurring revenue.
 

It shows everything that repeats automatically:
 

• Monthly charges

• Ongoing customer commitments

• Subscription-based products

• Paid vs unpaid cycles
   

In simple terms:
 

If a customer pays again and again — it lives here.

- Why the Subscriptions Report Exists
 

One-time sales are easy to track.

Recurring revenue is not.
 

Subscriptions require:
 

• Continuous monitoring

• Monthly validation

• Payment confirmation

• Customer accountability
   

The Subscriptions Report exists to prevent revenue leakage and ensure predictable income.
 

- Where Subscriptions Fit in the Business Flow
 

Subscriptions are created from subscription-type products, but they live a longer lifecycle.

Subscription Product
        ↓
Customer Subscribed
        ↓
Monthly Payment Cycle
        ↓
Paid / Unpaid Tracking
        ↓
Revenue Reports & Invoices
 

This module ensures nothing slips between months.
 

- Who Uses the Subscriptions Report?
 

The Subscriptions Report is used by:
 

 Business owners – recurring revenue overview
 Finance teams – paid vs unpaid tracking
 Operations – customer activity monitoring
 Sales teams – subscription performance
 Admins – payment follow-ups
 

- What the Subscriptions Report Represents
 

Each row in the Subscriptions Report represents:
 

• A customer commitment

• A recurring payment obligation

• A long-term product relationship
   

It answers critical questions like:
 

• Who should have paid this month?

• Who did not?

• Which products generate recurring income?

• Which team member sold or manages the subscription?
   

- What the Subscriptions Report Tracks
 

- Customer Information
 

• Customer name

• Contact linkage

• Subscription ownership
   

- Subscription Product
 

• Product name

• Subscription type

• Pricing logic
   

- Responsibility
 

• Team member responsible

• Sales ownership

• Account handling
   

- Payment State (Monthly)
 

• Paid for current cycle

• Unpaid for current cycle

• Payment method
   

- Timing Logic
 

• Start date

• End date (if limited)

• Charge timing (monthly rules)
   

- Paid vs ? Unpaid — The Core Indicator
 

The most important part of this report is payment status.

- Paid
 

• Subscription payment received for the current month

• Entry exists in payment history

• Revenue is secured
   

- Unpaid
 

• No payment recorded for the current month

• Immediate action required

• Revenue at risk
   

This visual distinction allows teams to react instantly.
 

- Subscription Payment Logic (How It Really Works)
 

Subscriptions are evaluated monthly.
 

For each subscription:
 

• The system checks the current billing cycle

• Looks for a payment entry

• Marks status accordingly
   

This ensures:

✔ Accurate month-by-month tracking
✔ No double billing
✔ No missed payments
 

- Powerful Filters = Operational Control
 

The Subscriptions Report includes focused filters so teams can isolate problems fast.
 

You can filter by:
 

• Product

• Customer

• Team member

• Payment status (Paid / Unpaid)

• Search by product name
   

This turns the report into a monthly control tool, not just a list.
 

- Business Insights You Get From This Report
 

Using the Subscriptions Report, you can quickly understand:
 

• Monthly recurring revenue stability

• Which customers are falling behind

• Which subscription products perform best

• Team members driving recurring income

• Risk exposure for the current month
   

- How Subscriptions Connect to Other Modules
 

The Subscriptions Report does not work alone.
 

It is tightly connected to:
 

• Products → only products marked as subscription

• Customers → subscription ownership

• Payments → monthly payment records

• Documents → invoices & receipts

• Sales reports → recurring revenue analytics
   

This keeps subscription revenue fully integrated, not isolated.
 

- Control & Permissions
 

Subscriptions involve sensitive financial data.
 

The system ensures:
 

• Role-based visibility

• Controlled access

• Secure payment handling
   

Only authorized users can:
 

• View subscription data

• Track payment status

• Manage subscription records
   

- Business Value of the Subscriptions Report
 

This module delivers:
 

✔ Predictable revenue tracking
✔ Early unpaid detection
✔ Reduced revenue loss
✔ Better customer follow-up
✔ Clear monthly accountability

It transforms subscriptions from passive billing into active revenue control.
 

- Final Summary
 

The Subscriptions Report is not just a report.
 

It is:
 

 A recurring revenue monitor
 A monthly payment validator
 A customer commitment ledger
 A financial risk detector
 

Without it, subscription businesses operate blind month-to-month.

With it, revenue becomes visible, predictable, and controllable.


 

- What Is the Orders Section?
 

The Orders Section is the operational backbone of the Product Report module.
 

It represents every commercial movement that happens between:
 

• Customers

• Suppliers

• Inventory

• Payments
   

In simple terms:
 

If money, products, or stock moved — it passed through Orders.

- Why the Orders Section Exists
 

Orders exist to bridge intention and execution.
 

A product alone does nothing.
A customer alone buys nothing.
 

An order is the moment where:
 

• Products become sales

• Stock becomes inventory movement

• Amounts become revenue or cost
   

This module ensures every transaction is traceable, reportable, and auditable.
 

- Where Orders Fit in the System
 

Orders sit at the center of the business flow.
 

Customers
   ↓
Documents (Invoices, Orders, Receipts)
   ↓
Customer Sales Reports
   ↓
Customer Insights & Strategy
 

All major modules depend on Orders:
 

• Sales reports

• Inventory updates

• Customer history

• Financial reporting
   

- Who Uses the Orders Section?
 

The Orders Section is used daily by:
 

 Business owners
 Operations teams
 Finance & accounting
 Sales managers
 Admin staff

Each role sees the same data, but for different decisions.
 

- What the Orders Section Represents
 

The Orders Section is not just a list.

It represents:
 

• Commercial intent

• Financial obligation

• Stock responsibility

• Legal documentation
   

Every row answers:
 

Who ordered what, when, for how much, and what happened next?

- What Orders Actually Track
 

Each order consolidates multiple dimensions:
 

- Transaction Information
 

• Order ID

• Order type

• Date created

• Due date
   

- People Involved
 

• Customer or supplier

• Created by (team member)

• Payment receiver
   

- Items & Quantities
 

• Products or product groups

• Quantities

• Prices

• Discounts
   

- Financial State
 

• Total amount

• Paid / unpaid / partially paid

• Payment method

• Currency
   

- Lifecycle State
 

• Order status

• Internal status

• Closed or open
   

- Order Types: Different Business Purposes
 

Orders are not one-size-fits-all.
 

- Detail Orders (Sales Orders)
 

Used for:
 

• Customer purchases

• Sales tracking

• Revenue generation
   

This is the most common order type.
 

- Purchase Orders
 

Used for:
 

• Buying from suppliers

• Inventory replenishment

• Cost tracking
   

These orders increase stock, not revenue.
 

- GI / IR (Goods Issue / Goods Receipt)
 

Used for:
 

• Internal stock movement

• Inventory corrections

• Warehouse control
   

These orders focus on quantity accuracy, not money.
 

- Powerful Filtering = Operational Control
 

The Orders Section includes deep filtering, allowing teams to instantly isolate exactly what they need.

You can filter by:
 

 Date range
 Customer
 Team member
 Amount range
 Order type
 Payment status
 Tags & folders
 Custom fields

This turns thousands of records into clear, usable insights.
 

- Smart Search Across Orders
 

Search is not limited to IDs.
 

You can search by:
 

• Customer name

• Document reference

• Notes

• Item names

• Internal identifiers
   

This makes the Orders Section fast even at scale.
 

- Orders as a Reporting Engine
 

Orders are the source of truth for:
 

✔ Sales reports
✔ Customer sales
✔ User sales
✔ Inventory movements
✔ Financial summaries

Every report you generate later depends on the accuracy of this section.
 

- Exporting Orders = Business Portability
 

Orders can be exported to:
 

Excel — for analysis
PDF — for sharing or compliance
 

Exports respect:
 

• Filters

• Selected fields

• Language

• Formatting

This makes Orders suitable for audits, meetings, and external systems.
 

- Custom Fields: Orders Adapt to Your Business
 

No two businesses operate the same way.
 

Custom fields allow you to:
 

• Add internal references

• Track insurance data

• Store operational metadata

• Apply business-specific logic

Orders become tailored, not generic.
 

- Permissions & Control
 

Orders are sensitive.
 

The system ensures:
 

• Viewing permissions

• Deletion control

• Role-based access
   

This prevents:

❌ Accidental data loss
❌ Unauthorized access
❌ Compliance issues
 

- How Orders Connect to Other Modules
 

Orders are deeply integrated:
 

• Products → order items

• Customers → order history

• Payments → financial state

• Storage → stock updates

• Invoices & Receipts → financial documents

• Dashboard → KPIs and summaries
   

Orders act as the central connector.