The Inter-modules Workflow in MokoCRM defines how various functional modules (CRM, Sales, Projects, Accounting, etc.) work together to create a seamless business process. It enables efficient data flow, reduces duplication, and ensures that actions in one module automatically trigger relevant updates or actions in others.
🔗 Core Workflow Relationships
- CRM → Proposals → Sales Orders → Invoices
- Start with a lead or third party
- Create a proposal linked to the contact
- Convert accepted proposals into sales orders
- Generate invoices from validated orders
- Purchase Orders → Receptions → Supplier Invoices
- Place an order with a vendor
- Receive goods through stock reception
- Link supplier invoice to the purchase order
- Projects → Tasks → Time Tracking → Invoicing
- Create a project linked to a customer or internal department
- Assign and track tasks
- Log hours to billable tasks
- Generate invoice based on time spent
- Contracts → Recurring Invoices
- Define service lines in a contract
- Automatically generate recurring invoices
🔁 Bidirectional Data Flow
- Stock movements update inventory across Sales, Purchase, and Manufacturing
- Accounting entries are triggered by invoices, payments, salaries, and expense reports
- Events and Agenda can be linked to projects, third parties, or documents
📂 Document and Record Linkage
- Most modules include a "Linked Objects" tab showing related records
- Example: A sales order shows linked proposal, invoice, shipment, and payments
- Documents (PDFs, notes) follow the data across modules
📊 Centralized Reporting
- Data from different modules can be aggregated into:
- Dashboards
- Exported reports
- Financial summaries
- Filters and tags improve cross-module analysis (e.g., by region, user, or project)
📌 Best Practices
- Always begin with CRM or Projects to define context
- Use module link buttons to avoid duplicate data entry
- Train staff on the full workflow rather than isolated modules
- Use Linked Object Tabs to navigate across workflows
- Enable appropriate user permissions to control workflow visibility and actions