Reporting Modules – Help Center

Tabla de Contenido

Guide for viewing, downloading, and reconciling transaction and settlement reports available in the Kushki console, with the new Customer Group hierarchy.

1. Context: the hierarchy and its impact on reporting

With the addition of Customer Group as a new level of the hierarchy (Owner → Customer Group → Customer → Branch), Kushki enables consolidated reporting at two new levels: Customer and Customer Group. Before Kushki One, reports could only be generated at the Branch level.

This means that a Customer with 10 branches can now generate a single consolidated report for all of them. And if those Customers are grouped in a Customer Group, the report can cover the entire structure in a single file.

Level	Access	Report type	Payment methods
Branch	Branch credentials (Merchant ID)	On demand. Free date range. Immediate generation.	Card, transfer, and cash.
Customer	Customer credentials	Automatically scheduled. Daily (previous day). Runs at 3:00 a.m. Ecuador time.	Card only (Card Present and Card Not Present).
Customer Group	Customer Group credentials	Automatically scheduled. Daily (previous day). Runs at 3:00 a.m. Ecuador time.	Card only (Card Present and Card Not Present).

⚠️ Important: Customer and Customer Group reports are exclusively for card transactions. Transfer and cash transactions remain reportable only at the Branch level. In the future, transfers may be enabled at these levels, but no date has been defined.

2. Reports module in the console

2.1 How to access

To access the reports module:

Log in with the credentials of the level from which you want to configure or download the report (Branch, Customer, or Customer Group).
In the side menu, select Reports.
The tabs My reports and Pending downloads will be displayed.

2.2 New features: search buttons in the reports module

Two new search buttons have been added in the reports module (Kushki Admin view):

Button	Function
Customer / Branch	Allows searching for a Customer or Branch by name or ID. If a report is already configured, it preloads it for editing. If there is no report, it enables the Create report button.
Customer Group	Allows searching for a Customer Group by name or ID. If a report is already configured, it preloads it. If not, it enables the Create report button.

ℹ️ Note: When a search is executed, the result displays the merchant name for confirmation before creating or editing the report. You can search by name or by Merchant ID / Customer Group ID interchangeably.

3. Branch reports (no changes)

Branch reports maintain exactly the same flow the team already knows. There are no changes to the form structure.

3.1 Features

Type: on demand (the user generates the report when needed).
Date range: free, the user defines the period.
Generation: immediate.
Payment methods: card, transfer, and cash.
Access: with Branch credentials (Merchant ID).

3.2 New fields in Branch card reports

To facilitate the identification of Card Present versus Card Not Present transactions within the same report, two additional fields are being added to card reports:

Field	Description	When is it empty?
Terminal serial number	Serial number of the physical device (SmartPOS) on which the transaction was processed.	Card Not Present transactions (no physical terminal).
Terminal brand	Device manufacturer/model. Currently: Sunmi. In the future, other brands may be included.	Card Not Present transactions, or when the merchant uses their own terminal without integration.

If a card transaction has these fields empty, it corresponds to a Card Not Present operation. The merchant can use this logic to filter and differentiate both types in their own reconciliation tool.

ℹ️ Note: When the merchant uses their own third-party terminals with integration, the serial and brand fields may be populated or empty depending on what the provider sends. When using Kushki One terminals (Sunmi), the provider Payrillium always sends this information.

4. Customer and Customer Group reports

4.1 Main features

These reports are fundamentally different from Branch reports. They are scheduled, not on-demand, and always cover all Branches or Customers at the corresponding level.

Fixed schedule: the report runs automatically at 3:00 a.m. Ecuador time, every day.
Period covered: the previous full day (from 00:00 to 23:59 of the cutoff day).
Scope: includes all Branches of the Customer or all Customers of the Customer Group. It is not possible to generate reports for a subset.
Card only: Card Present and Card Not Present. Transfer and cash are not included.
Transactions only: the form does not offer the subscription report option (not applicable at this level).

⚠️ Important: If the report is configured today, the first available report will be tomorrow at 3:00 a.m. with today's transactions. There is no retroactive generation. For this reason, it is essential to create the report from the merchant's first day of operation.

4.2 Report creation form

When creating a Customer or Customer Group report, the form has the following fields:

Field	Options / Behavior
Report name	Internal identifier to recognize it in the console.
Format	CSV or other available formats, same as in Branch.
Information type	Transactions only (subscriptions do not apply at this level).
Detail level	Detail or summary, under the same structure as Branch.
Payment method	Card only (Pay ins → Card). Card Present and Card Not Present are automatically included if the Customer operates them.
Transaction status	Approved, declined, or all. Same as in Branch.
Execution time	Fixed: 3:00 a.m. Ecuador time. Not configurable.
SFTP (optional)	If the merchant wants to receive the file on their SFTP server, they can configure the connection details here. It is optional.

4.3 Where generated reports become available

Once the 3:00 a.m. process runs, the report becomes available in two places simultaneously:

Always in the console: on the Pending downloads tab of the Reports module. This applies whether or not SFTP was configured.
In the merchant's SFTP (if configured): the file also arrives automatically at the merchant's server.

ℹ️ Note: Unlike Branch reports, Customer and Customer Group reports do not have the option to be sent by email. Distribution is via the console or SFTP (SFTP configured directly in the reports module, not the SFTP from the onboarding process).

4.4 Operational recommendation: create the report from day one

Since reports do not generate retroactive data, it is essential for the onboarding team to create the Customer (or Customer Group) report from the moment the merchant is activated. If the merchant starts transacting on May 1 and the report is created on May 16, the first available report will be on May 17 with data from May 16. The prior history cannot be recovered automatically.

ℹ️ Note: Although the Customer Group is an optional field, it is recommended to assign it from the start so the merchant can access consolidated reports from day one. For existing merchants who want this type of reporting, the Customer Group can be assigned at any time, but will only generate data going forward.

5. Settlements module

5.1 What is the settlements module?

The settlements module is a new section of the console that allows merchants to view and download settlement reports (payments made to their bank account) directly from the console, without needing to access an external SFTP server.

ℹ️ Note: This module is not exclusive to Kushki One. It is available for all Kushki merchants, regardless of whether they operate with physical terminals or not. It is already developed and in production (pending official activation).

5.2 What reports does it show?

The settlements module shows the same reports that the FinOps team already generates today and delivers to merchants via SFTP. There are no changes to the structure, grouping, or frequency of existing reports.

Feature	Details
Available reports	The same ones FinOps currently generates (no changes in structure or format).
Frequency	Daily and monthly, depending on the report type configured with FinOps.
Access	Exclusive to users with the Visor de reportes role at the Customer level.
Relationship with existing SFTP	Merchants who already receive reports on their SFTP will continue to do so. The console is an additional channel, not a replacement.
New merchants	If the merchant does not want to configure SFTP, FinOps generates the reports anyway and the console displays them automatically.

5.3 Required role: Visor de reportes

To access the settlements and consolidated reports module, the merchant's user must have the Visor de reportes role assigned. This is a new role configured at the Customer level.

Role	Access to reports	Access to settlements	Access to transactions
Visor de reportes (new)	Yes — can configure and download reports.	Yes — can view and download settlement reports.	No (not currently enabled for this role).
Visor maestro (existing)	Yes	No (does not apply to the Branch Visor maestro)	Yes, with download.

⚠️ Important: The transactions module will not be enabled for the Visor de reportes role in this first phase. If it is enabled in the future, downloading information from that module will be deactivated for this role, so that data downloads are performed exclusively from the reports module.

5.4 Grouping of settlement reports

For merchants who receive multiple settlement reports (for example, because they operate Card Present and Card Not Present with different bank accounts), the module displays reports grouped together. The grouping reflects what FinOps already manages internally. The merchant can select and download reports individually or by period.

ℹ️ Note: The client grouping that appears in the settlements module corresponds to the grouping logic that FinOps applies today when generating its reports. It is not related to the Customer Group in the console hierarchy.

6. Known capacity and limitations

During the testing phase and first months of production, there are some limitations to keep in mind:

Limitation	Current status	Recommended action
Maximum download size (Branch)	Approx. 25 MB / 400,000 records in the current console. Capacity is being reviewed for the new console.	For high-volume merchants, use SFTP to avoid download issues.
Retroactive reports (Customer / Customer Group)	Not available. Scheduled reports only generate data from the configuration date onward.	Create the report from the merchant's first day of operation.
Maximum volume of simultaneous reports	Under evaluation. Tests are being conducted with high-volume transactional merchants.	Monitor during the Small Test and escalate if incidents occur.
Terminal reports in console	Not available. The console only handles transactions, not terminals.	For terminal reports, consult the DMS or Mongo.

7. Available fields for advanced queries (Mongo)

For teams that need more detailed or real-time queries not available in the console modules, the following fields travel at the transactional level in the database (Mongo) for card transactions:

Merchant ID (Branch ID)
Customer ID
Customer Group ID
Terminal serial number
Terminal brand
Indicator of whether it is Kushki One or a third-party terminal (field being synced, not yet uploaded to reports)

ℹ️ Note: The Customer Group ID travels at the transactional level only for card transactions (Card Present and Card Not Present). Transfer transactions do not include the Customer ID or Customer Group ID at this time.

Frequently asked questions (FAQ)

Is it possible to generate a Customer report with only some Branches?

No. The Customer report automatically consolidates all Branches belonging to that Customer. It is not possible to select a subset. If groups of Branches need to be separated, the alternative is to decentralize those Branches and manage independent credentials.

If an SFTP is configured for the Customer Group report, does the report stop appearing in the console?

No. The report is always available in the console under the Pending downloads tab, regardless of whether SFTP was configured or not. SFTP is an additional channel, it does not replace availability in the console.

Does the settlements module replace the SFTP the merchant already has configured with FinOps?

No. Merchants who already receive settlement reports on their SFTP will continue to receive them there without changes. The settlements module in the console is an additional access channel. The structure, frequency, and format of the reports continues to be defined by FinOps directly with the merchant.

How can you tell if a transaction in the report is Card Present or Card Not Present?

In card reports there are two new fields: terminal serial number and terminal brand. If those fields are empty, the transaction is Card Not Present (no physical terminal was used). If they contain data (serial number and Sunmi, for example), the transaction is Card Present processed with a Kushki One terminal.

Where can terminal reports (not transaction reports) be consulted?

Terminal reports are not available in the console. The console manages transactional information only. To query terminal data (serial number, status, associated Merchant ID, etc.), you must access the DMS or, for the internal team, through queries in Mongo.

What happens to the history of a merchant who joined Kushki One but only configured the report months later?

The history prior to the report configuration is not generated automatically. If that history is needed, it must be requested as an internal process from the corresponding team. That is why it is essential to create the Customer or Customer Group report from the merchant's first day of activation.