Skip to main content

Process & It's Stages

What is Process?​

The Process serves as the central orchestration layer for all business workflows. Built on Sumo Ledger’s event-driven architecture, it ensures that business rules, validations, compliance checks, and operational activities are executed in a controlled, sequential, and fully auditable manner.

Think of a process as a blueprint that describes:

  • What information is required.
  • What actions should be performed.
  • What decisions need to be made.
  • What should happen next based on those decisions.

Every process consists of:

  • Parameters
  • Variables
  • Stages
  • Connections between stages

Together, these components define the complete workflow.

Stages​

A process is composed of multiple stages, each acting as a fundamental building block within the workflow. These stages collectively define the flow and behavior of the process. The subsequent sections of this chapter provide a detailed explanation of each stage and its role within the overall process lifecycle.

Journal​

The Journal stage is used to post journal entries into ledger accounts to maintain financial integrity. It facilitates the recording of financial events by creating accounting entries based on predefined posting rules and account mappings. The stage ensures that every financial transaction is properly reflected in the ledger, providing a complete audit trail and supporting accurate financial reporting.

API​

The API stage is used to configure integrations with external or internal systems through APIs. It supports the definition of request structures, response mappings, authentication mechanisms, and data transformations required to exchange information with third-party services. This stage enables processes to retrieve, validate, or submit data to external platforms while maintaining seamless interoperability between systems.

Task​

The Task stage is used to initiate tasks that require manual user intervention within a business workflow. It allows processes to pause and await user actions such as review, approval, verification, data entry, or decision-making. The stage provides a controlled mechanism for incorporating human involvement into otherwise automated workflows.

Tariff​

The Tariff stage is used to validate and calculate charges based on predefined tariff configurations. It supports fee calculations, commissions, pricing rules, interest calculations, and other charge-related logic defined within the system. By centralizing tariff management, this stage ensures consistency and accuracy in the application of financial and operational charges across processes.

Account​

The Account stage is used to manage customer, operational, and financial accounts utilized across products, transactions, and ledger operations. It provides capabilities for creating, updating, and maintaining account information throughout the account lifecycle.

Add Account​

The Add Account action is used to create and configure new accounts using predefined account structures, classifications, attributes, and operational settings. Newly created accounts become immediately available for use within products, transactions, and financial operations.

Update Account​

The Update Account action is used to modify existing account information, including account status, limits, reporting classifications, operational settings, and other account attributes. All changes are tracked to maintain a complete audit history.

Table​

The Table stage is used for flexible data storage and retrieval through configurable table structures. It enables processes to maintain and access structured information required during execution without requiring dedicated database development. Tables can be used as reference repositories, lookup sources, or flexible data containers for process execution.

Feed​

The Feed stage is used to ingest and distribute data from external and internal sources to support automated processing. It provides a mechanism for importing, transforming, and processing large volumes of data received from various systems and channels.

Add Feed Source​

The Add Feed Source action is used to configure a source from which data can be imported into the platform. Feed sources may represent external systems, files, databases, APIs, or other supported integration channels.

Add Feed Posting​

The Add Feed Posting action is used to define posting rules that determine how incoming feed records should be transformed into business events, transactions, journal entries, or other system actions. These rules enable automated processing of imported data.

Form​

The Form stage is used to capture information from external users through administrator-designed forms. Forms can be configured without writing code and can contain various input fields, validation rules, and data collection requirements. Information collected through forms becomes available to subsequent stages within the process and can be used for validations, decision-making, or transaction execution.

Contract​

The Contract stage is used to define and manage executable business agreements within the platform. Contracts may contain business terms, obligations, conditions, parameters, and execution rules that govern how a business relationship or transaction should be processed.

Add Contract​

The Add Contract action is used to create and configure contract templates containing business terms, conditions, rules, and execution parameters. These templates can be reused across multiple business scenarios.

Execute Contract​

The Execute Contract action is used to evaluate contract conditions and perform predefined business actions when the specified execution criteria are satisfied. This ensures that contractual obligations and business rules are enforced consistently.

Initiate Transaction​

The Initiate Transaction stage is used to initiate or trigger another process from within the currently executing process. It enables process orchestration by allowing one workflow to invoke another workflow, thereby supporting modular process design and reusable business operations.

Report​

The Report stage is used to retrieve reports generated through the platform's configurable reporting framework. It leverages a custom query workspace that enables users to generate operational, analytical, financial, and management reports using data available within the system. Reports generated through this stage can support decision-making, monitoring, compliance, and business analysis activities.

Wait Stage​

The Wait Stage is used to temporarily pause workflow execution until a specified event, condition, date, time, or external response is received. During the waiting period, the process remains in a controlled state and automatically resumes execution once the configured criteria are met. This stage is particularly useful for event-driven workflows and long-running business processes.

Policy​

The Policy stage is used for centralized management and enforcement of business policies and financial controls. Policies can define transaction limits, balance restrictions that must be enforced during financial process execution.

Add Policy​

The Add Policy action is used to create new policy definitions containing transaction thresholds, balance limits and enforcement criteria. These policies can then be applied across accounts, sub-accounts, and transactions.

Update Policy​

The Update Policy action is used to modify existing policy definitions while preserving version history and auditability. This ensures that policy changes can be tracked and managed in a controlled manner.

Update Reporting Group​

The Update Reporting Group stage is used to update reporting group assignments associated with accounts and sub-accounts. Reporting groups are used for financial reporting, operational reporting, regulatory reporting, and account classification purposes. This stage ensures that reporting structures remain aligned with changing business requirements and account classifications.