- Conto Module
 

Controlled and Conditional Workflow for Check Processing
 

- Conceptual Overview (What is Conto, really?)
 

The Conto Module is a special extension of the Checks system, designed for organizations that require a separate and more controlled workflow for handling checks.
 

While the standard Checks Module handles general check payments, Conto 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 implements additional validation, review, and workflow discipline for check payments.
 

- Why the Conto Module Exists
 

Not all organizations treat checks the same way.
 

Some businesses require:
 

• A separate review process

• A dedicated operational workflow

• Controlled visibility for specific users

• Additional validation before status changes
   

The Conto Module solves this by:
 

• Reusing the same data structure

• Implementing different workflow logic

• Enforcing module-level access rules
   

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

 

- Conto's Workflow Philosophy
 

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

In Conto:
 

• Status changes are intentionally restricted

• UI actions reflect workflow discipline

• Data presentation aligns with process adherence
   

This makes it ideal for:
 

• Regulated environments

• Internal audit workflows

• Sensitive financial operations

• Handling legacy or contractual checks
   

- Status Handling in Conto
 

Although Conto uses the same status values as Checks, how statuses change is different.
 

Status updates:
 

• Undergo Conto-specific validation

• Use a dedicated API endpoint

• Enforce tighter logic before saving
   

This prevents:
 

• Accidental approvals

• Premature status changes

• Unvalidated financial approvals
   

- Conto-Specific Document View
 

The Conto Module provides a custom HTML rendering of documents, even though the underlying data is the same.
 

Why?
 

• To align with Conto's workflow language

• To display only relevant controls

• To visually separate it from general Checks
   

This ensures users immediately understand:
 

"I am in a controlled financial flow."

- Access Control and Accountability
 

Just like Checks, Conto enforces:
 

• Team member-based visibility

• Organizational isolation

• Admin-privileged access
   

But with one key difference:
 

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

This prevents:
 

• Accidental access

• User confusion

• Unauthorized operations
   

- Image and Evidence Handling
 

Conto fully supports:
 

• Multiple check images

• Secure storage

• Embedded previews

• Full-screen inspection
   

This keeps Conto audit-ready, just like Checks.
 

- Reporting and Export Consistency
 

Although the workflow is stricter, Conto data remains compatible with all reports.
 

Data exports:
 

• Respect filters

• Include status and rejection data

• Maintain audit context
   

This means:
 

• Finance teams can trust the numbers

• Auditors can trace the source

• No reconciliation gaps
   

- System Integrations
 

Conto integrates seamlessly with:
 

• Clients

• Tasks

• Documents

• Team management

• Reports and Obligo

• Image storage
   

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

- Security and Compliance
 

Conto reinforces:
 

• Feature-level access control

• User-level visibility

• Intentional status change

• Full traceability
   

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