The Cobre Portal's approval process provides enterprise-grade control over money movements through a maker-checker workflow. This dual-control mechanism ensures that payment actions are reviewed and authorized before execution, protecting your organization from errors and unauthorized transactions while maintaining operational efficiency.Key Benefits#
Enhanced Security: Require multiple parties to review high-value or sensitive transactions
Reduced Risk: Catch errors before payments are processed
Flexible Control: Apply approvals at individual payment or batch level
Audit Trail: Track who created and who approved each payment
The system supports both individual and bulk approvals, allowing you to manage workflows efficiently whether you're processing single payments or large batch files.
How the Approval System Works#
Approval Requirements by Role#
The system determines approval requirements based on user roles:Creator Roles: Always require approval. Users with creator permissions can initiate payments but cannot authorize their own transactions.
Admin Users: Have the flexibility to choose. When creating a payment, admins can decide whether it needs approval or can be processed immediately.
This role-based approach ensures segregation of duties while giving trusted users the flexibility to handle urgent payments.Approval Workflow States#
Each payment moves through a clear workflow:| State | Description |
|---|
| Need Approval | Payment is awaiting authorization from an approver |
| Approved & Processing | Payment has been authorized and moved to processing |
| Cancelled | Payment was declined and will not be processed |
Navigation and Filtering#
The Approval section includes:Tab navigation between Unitary and Batch views
Pagination to browse through multiple pages of payments
Status filters in batch detail views
Search functionality to quickly find specific batches
Managing Approvals#
Accessing the Approval Section#
Navigate to Home → Money Movements → Approvals to view all payments requiring your action.The Approvals section shows:Number of payments awaiting approval in the "Unitary" tab
Number of batches awaiting approval in the "Batches" tab
Payment details including amount, currency, origin, destination, and type
Creation date and current status
Reviewing Individual Payments#
To approve or decline individual payments:1.
Go to the Unitary tab in the Approvals section
2.
Click on any payment row to open the detail
3.
Find there the payment information:Origin and destination accounts
Payment type (SPEI, Fast Pay, ACH, etc.)
Creation date and creator
4.
Click Approve or Decline based on your review
5.
Complete the MFA (Multi-Factor Authentication) verification
Note: MFA is required for all approval actions to ensure security.
Bulk Actions for Multiple Payments#
When you need to process multiple payments efficiently:1.
Select up to 50 payments using the checkboxes on the left side of each row
2.
Use the bulk action buttons that appear at the top
3.
Choose Approve or Decline to apply the action to all selected payments
4.
Complete MFA verification
This feature is particularly useful when reviewing similar payments from the same batch or processing routine transactions.
Batch-Level Approvals#
Understanding Batch Approvals#
When bulk payment files are uploaded, the entire batch and its payments are flagged as Pending Approval. This allows you to approve or decline entire batches at once, streamlining high-volume payment processing.Important: Batch-level decisions only affect payments marked as "Need Approval." If individual payments in the batch have already been approved or declined, those decisions remain unchanged.
How to Approve or Decline Batches#
1.
Navigate to Home → Movements → Approvals → Batches tab
2.
Review the batch list showing:Number of payments in the batch
3.
Click on a batch name to open the detail view
4.
Review the individual payments within the batch; hover the mouse for decline or approve that single transaction
Note: Transactions created from the batch section must also be approved in batch. If you reject one of the transactions within the batch, that transaction will not be processed when you approve the complete batch.
5.
Use the Approve or Decline buttons at the top to approve the whole batch
6.
Complete MFA verification
The batch detail view provides filtering options to help you review payments by status (All, Pending Approval, Processing, Completed, Declined, Error, Failed).Batch Approval Behavior#
When you approve or decline a batch:Payments with status "Need Approval" will be approved/declined
Payments already approved or declined remain unchanged
The system updates only pending decisions, preserving any individual actions taken previously
This design allows flexible workflows where some payments can be fast-tracked while others go through the batch approval process.
Additional Features#
Report a Problem#
If you notice any issues with a payment:1.
Open the payment detail panel
2.
Click the Report Problem option in the action menu

3.
Provide details about the issue for investigation
Integration with Dual Control Rules#
The approval process works seamlessly with Dual Control Rules configured in the Security section. These rules allow you to:Require multiple approvers for transactions above certain thresholds
Enforce specific approval hierarchies
Set different requirements based on payment type or destination
To configure Dual Control Rules, navigate to Home → Settings → Security.
Best Practices#
For Efficient Approval Workflows#
Review payment details carefully before approving, checking amounts and destination accounts
Use bulk actions when processing similar payments to save time
Leverage batch-level approvals for large file uploads
Set up appropriate Dual Control Rules based on your organization's risk tolerance
For Security#
Never share MFA codes or approval credentials
Review unfamiliar payment destinations before approving
Decline suspicious payments and report them immediately
Regularly review approval permissions for your team
FAQs#
Can I approve my own payments?
No, if you have a Creator role. The maker-checker system requires separation between the payment creator and approver. Admin users can create payments that bypass approval, but this should be used judiciously.What happens if I approve a batch with mixed payment statuses?
Only payments marked as "Need Approval" will be affected. Payments already approved, declined, or in other states remain unchanged.How many payments can I approve at once?
In the Unitary view, you can select and approve up to 50 payments simultaneously. For larger volumes, use batch-level approvals.Is MFA required for every approval action?
Yes, MFA is mandatory for all approval and decline actions to ensure security. This applies to individual payments, bulk actions, and batch-level decisions.Can I see who created a payment?
Yes, payment details include the creator's information and the creation timestamp, providing full visibility into the payment lifecycle.
Getting Help#
If you find issues with the approval process or have questions about your organization's specific workflow:Contact your account administrator to review permission settings
Reach out to Cobre support for technical assistance
Go to Settings → Security to verify Dual Control Rules configuration
The approval system is designed to provide security without sacrificing efficiency, giving you confidence that every payment is properly authorized before processing.