- 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.