The Transactions module is your central hub for monitoring all money movements across your Cobre ecosystem. Whether funds move through your Cobre balances or your connected external accounts, every transaction appears here in a unified view—giving you complete visibility into your cross-border payment activity.Understanding the Transactions View#
The Transactions module consolidates activity from two distinct sources into one comprehensive interface:Cobre Balance Movements: Transactions that affect your Cobre account balances—money moving in and out of your Cobre accounts through various payment rails like SPEI, ACH Colombia, Bre-B, and Fast Pay. These include payments you initiate through the Portal, transactions executed via API, incoming transfers from counterparties, and internal movements between your Cobre accounts.Connected External Accounts: Transactions from bank accounts you've connected to Cobre (like BBVA, Bancolombia, or other financial institutions). These external account movements appear alongside your Cobre transactions, creating a unified view of your entire payment ecosystem without requiring you to log into multiple banking platforms.This unified approach means you can track the complete payment lifecycle in one place—from initiating a payment in Cobre, through its processing, to its arrival in external accounts—all without switching between systems.
What You'll See#
Every transaction displays essential information at a glance:| Field | Description |
|---|
| Transaction Date | When the transaction was completed and when it affected the account balance. This is the definitive timestamp for accounting and reconciliation purposes. |
| Account | Which account the transaction affected—either a Cobre balance (shown with the Cobre identifier) or a connected external account (shown with the bank name and last four digits). |
| Amount | The transaction value in its original currency. Credits appear as positive numbers, debits as negative. This makes it immediately clear whether money moved in or out. |
| Currency | The denomination of the transaction—MXN, COP, PEN, USD. Particularly useful when you operate across multiple currencies and need to quickly identify which currency moved. |
| Transaction Type | Describes both the nature of the transaction and the payment rail used. Examples include "Credit via SPEI" (incoming SPEI transfer), "Debit by Bre-B" (outgoing Bre-B payment), "R2P Credit by Bre-B" (request-to-pay credit received), helping you understand not just what happened but how it happened. |
| Counterparty | The entity on the other side of the transaction—who sent you money or who received your payment. This appears when available based on the transaction type and data provided by the payment rail. |
| Description | Additional transaction details, payment concepts, or references that provide context about the purpose or nature of the movement. |
Viewing Transaction Details#
Click any transaction to open its detail view, where you'll find comprehensive information about that specific movement:Transaction Overview: The complete transaction header showing the amount, currency, transaction type, and when it was created in the system.Core Transaction Information: A detailed breakdown including your own account involved, the description or payment concept, any reference numbers from the payment rail, and the unique transaction ID that Cobre assigns for tracking purposes.Additional Details (when available): Depending on the transaction type and payment rail, you may see sender information (name and account number for incoming transactions), beneficiary details (account information for outgoing payments), aliases used, and operation dates (when the payment instruction was initiated, distinct from when funds actually moved).The detail view also includes a convenient copy button next to the transaction ID, making it easy to reference specific transactions when communicating with support or performing internal tracking.
Filtering and Managing Your View#
The Transactions module offers flexible filtering to help you find exactly what you need:Account Filtering: View transactions for all accounts at once, or filter to show only specific Cobre accounts or connected external accounts. This is particularly useful when reconciling a specific account or analyzing activity patterns for different parts of your business.Date Filtering: Use the date picker to focus on specific time periods. Quick presets let you jump to common ranges like "Last 7 days" or "Current month," while custom date ranges give you precise control for period-end reporting or audit requirements.Search and Sort: Find specific transactions by filtering by date, amount, and transaction type.
Customizing Your Columns#
The Transactions view adapts to your specific needs through dynamic column customization. Click "Edit columns" in the top-right corner to show or hide specific data fields based on what matters most to your role.Your column preferences persist across sessions, so the view automatically displays your preferred configuration each time you access Transactions. Available columns include transaction date, operation date, account, amount, currency, transaction type, counterparty, description, sender information, beneficiary details, aliases, and account numbers—giving you granular control over exactly what information appears in your view.
Understanding Transaction Timing#
Transactions display two important timestamps that serve different purposes:Transaction Date: This is when the transaction actually completed and when your account balance changed. Use this date for accounting reconciliation, financial reporting, and understanding when funds were actually available or debited. This is the date that matters for your books.Operation Date: This shows when the payment instruction was initiated in the Cobre Portal. For transactions you create through Cobre, there's often a delay between when you submit the payment (operation date) and when it actually completes (transaction date) due to payment rail processing times. This distinction helps you track the timing of your payment decisions versus when funds actually moved.The difference between these dates becomes particularly important for cross-border payments, which may take longer to settle, or for transactions initiated near payment rail cutoff times that complete the following business day.
Transaction Types You'll Encounter#
The Transactions module displays various transaction types reflecting the diverse payment rails and movement types Cobre supports:| Transaction Type | Description |
|---|
| SPEI Transactions (Mexico) | Credits and debits moving through Mexico's real-time payment system. These typically settle within minutes during operating hours. |
| ACH Colombia / Bre-B Transactions (Colombia) | Movements through Colombia's payment networks, including standard ACH transfers and Bre-B instant payments. |
| Fast Pay Transactions (Colombia) | An exclusive Cobre payment rail that enables instant payments to Colombian accounts without amount restrictions. |
| R2P (Request-to-Pay) Transactions | Credits received in response to payment requests you've sent to counterparties through supported payment rails. |
| Internal Cobre Movements | Transfers between your own Cobre accounts, which settle instantly since they remain within the Cobre network. |
| External Account Activity | Transactions from your connected bank accounts, showing the same types of movements you'd see in your online banking but consolidated into your Cobre view. |
Each transaction type displays with clear labeling that indicates both what happened (credit or debit) and how it happened (which payment rail), helping you understand the nature and speed of each movement at a glance.
Exporting Transaction Data#
When you need to analyze transactions outside the Portal, integrate Cobre data with your accounting systems, or create custom reports, the export functionality gives you complete control over your transaction data.Why Export Transaction Data?#
Exporting your transaction history enables seamless integration with existing financial systems and workflows:Accounting Integration: Import transaction records directly into your ERP, QuickBooks, or accounting software without manual data entry
Audit & Compliance: Generate detailed transaction reports for internal audits, external reviews, or regulatory compliance requirements
Financial Analysis: Analyze payment patterns, cash flow trends, and counterparty activity using your preferred analytics tools
Reconciliation: Cross-reference Cobre transactions with your bank statements and internal records for accurate financial reconciliation
Operational Reporting: Create custom dashboards and reports for stakeholders by combining Cobre data with other business metrics
How to Export Transactions#
The export process gives you complete control over what data you receive:1.
Click Export: Find the "Export" button in the top-right corner of the Transactions module
2.
Configure Your Export: A modal window opens where you can customize your export parameters (detailed below)
3.
Generate File: Click "Generate" to create your export. The system processes your request asynchronously
4.
Access Your File: Once ready, download your CSV from the Files section under the Reports module
Export Configuration Options#
Date Range Selection#
Choose the time period for your export with flexible date range options:Quick Presets: Select common ranges like "Today," "Last 7 days," "Last 30 days," "Previous month," or "Current month"
Custom Range: Use the calendar picker to define any specific date range within the allowed timeframe
Maximum Range: Currently limited to one month per export to ensure optimal performance
Note: The date range limit will progressively increase as system performance testing validates stability with larger datasets.
Timezone & Language#
Ensure your export matches your operational context:Timezone: All timestamps in your export will reflect the timezone you select, ensuring accurate time-based analysis
Language: Choose English or Spanish for column headers. This makes it easier to share reports with team members who work in different languages (note: only column names are translated, not transaction data)
Filter by Transaction Type#
Focus your export on specific transaction types to streamline your analysis:Transaction: Export only the transactions that affected your account balance—the actual money movements in and out
Operation: Include the dates when transactions were initiated (helpful for tracking when payment instructions were created versus when funds actually moved)
Column Selection#
Customize which data fields appear in your export to match your specific needs:Visible Columns: Export matches your current Transactions view exactly—whatever columns you see on screen will appear in the CSV. This is perfect when you've already customized your view for a specific purpose
All Available Columns: Get the complete dataset with every available field. Ideal for comprehensive analysis or when you're not sure which fields you'll need
Personalized Selection: Choose exactly which columns to include. Operation date is mandatory and will always appear in personalized exports
Available Data Fields#
Your exports can include these fields (availability depends on transaction type and column selection):| Field | Description |
|---|
| Transaction Date | When the transaction was completed and your balance was affected (mandatory field) |
| Operation Date | When the payment instruction was initiated in the Portal (mandatory for personalized exports) |
| Account | Your Cobre account or connected external account where the transaction occurred |
| Amount | Transaction value (debits shown as negative, credits as positive) |
| Currency | Currency denomination (MXN, COP, PEN, USD) |
| Transaction Type | Type of transaction and payment rail used (e.g., Credit via SPEI, Debit by Bre-B, R2P Credit by Bre-B) |
| Description | Transaction description or payment concept provided when the transaction was created |
| Counterparty | Name of the person or entity on the other side of the transaction |
| Sender Name | Name of the entity that sent the funds (for incoming transactions) |
| Sender Account Number | Bank account number from which the funds originated |
| Beneficiary Account Number | Bank account number where the funds were sent (for outgoing transactions) |
| Alias | Friendly name or identifier if a beneficiary alias was used |
| Account Number | Full account number details for the transaction |
Important: Not all fields are available for every transaction type. Some fields may appear empty depending on the nature of the transaction and available data.
Accessing Your Exported Files#
Because transaction exports can involve large datasets, the system processes them asynchronously to avoid slowing down your Portal experience. This means your file isn't immediately available—instead, it's generated in the background and made accessible once ready.1.
Navigate to Reports: Access the Reports module from your Portal navigation
2.
Open Files Section: Within Reports, select the Files section
3.
Download Your Export: Locate your completed export file and download it to your local system
Important Limitations & Considerations#
Data Availability & Timing#
| Limitation | Details |
|---|
| Transaction Processing Delay | Newly completed transactions take 3-5 minutes to become available for export as the system processes and indexes the data |
| Historical Data Limit | Currently, only transactions from the last 30 days can be exported. This limit will progressively increase as performance testing validates system stability with larger datasets |
| Date Range Per Export | Each export is limited to one month of data to ensure optimal performance and reliability. For longer periods, generate multiple exports |
Data Format & Content#
| Consideration | Details |
|---|
| Unmasked Data | Exported files contain complete, unmasked account numbers and sensitive information. Store and share these files securely according to your organization's data handling policies |
| Empty Fields | Currently, fields without data appear as 'null' in the export. An improvement is in progress to display these as empty values instead, making the files cleaner for import into other systems |
| Language Settings | The language setting only affects column header names—actual transaction data (descriptions, counterparty names, etc.) remains in its original language |
| Sort Order | Transactions in exports are sorted by transaction date (when funds moved), not by created date as shown in the main Transactions view. This ensures your accounting records reflect the chronological order of actual financial events |
Current Scope#
Module Availability: Export functionality is currently available only for the Transactions module. Additional module support will be added based on user needs and feedback.
Working with Transaction Data#
For Daily Operations#
Use the Transactions module as your operational command center:Monitor incoming payments throughout the day to track expected receipts
Verify that outgoing payments completed successfully and within expected timeframes
Identify any failed or rejected transactions that require attention
Track payment patterns to optimize timing for future transactions
For Accounting & Reconciliation#
The Transactions module serves as your single source of truth for reconciliation:Compare Cobre transaction records against bank statements from connected accounts
Verify that all payments initiated in Cobre appear correctly in your accounting system
Track the timing differences between operation dates and transaction dates to understand payment settlement patterns
Use exported data to feed automated reconciliation processes in your accounting software
For Analysis & Reporting#
Extract insights from your payment activity:Identify your most frequent counterparties and payment patterns
Analyze transaction volumes by currency, payment rail, or time period
Track the distribution of payments across different payment methods to optimize your payment strategy
Monitor the performance of different payment rails in terms of processing times and success rates
Best Practices#
For Accounting Teams#
Perform monthly exports at period close to maintain consistent accounting records. Note that this process is manual and should be coordinated externally by your team.
Use "All Available Columns" to ensure you have complete data for reconciliation and audit trails
Select your accounting system's timezone to ensure transaction timestamps align with your books
Create a standard column configuration for month-end reconciliation and save it for consistent reporting
For Operations Teams#
Use "Visible Columns" when you've already customized your view to track specific operational metrics
Export weekly rather than monthly to keep dataset sizes manageable for analysis in spreadsheet tools
Include Operation Date when tracking payment initiation timing matters for your workflows
Set up different column views for different operational tasks (payment monitoring vs. exception handling)
For Compliance & Audit#
Always use "All Available Columns" to create comprehensive audit trails with maximum detail
Export and archive transaction data monthly to build a complete historical record
Store exported files securely according to your data retention and confidentiality policies—remember, these files contain unmasked account information
Document your export and retention procedures as part of your compliance framework
For Treasury Management#
Monitor the Transactions view multiple times daily during high-volume periods to track liquidity
Use account filtering to focus on specific accounts when managing cash positions
Analyze transaction patterns to optimize the timing of large payments and balance management
Track the mix of Cobre and external account activity to understand your payment distribution
Need Help?#
If you encounter any issues with the Transactions module or need guidance on how to best use transaction data for your specific workflows, contact your Cobre Key Account Manager or reach out to support. We're here to ensure you can monitor, analyze, and leverage your transaction data exactly the way you need it. 