Automated reporting
Automated reporting is the process of preparing regulatory notifications and internal reports without the need to manually collect data. TruvaLI generates both suspicious transaction report drafts and the institution’s own business reports using data available within the system.
Suspicious Transaction Report Draft
When a case reaches the point where it needs to be reported, the analyst often has a fragmented set of information in front of them: transaction records, customer information, screening matches, and investigation notes.
Turning all of this into the narrative expected by the regulator takes time and may lead to inconsistencies across institutions.
TruvaLI prepares a report draft based on the evidence within the case, including the chronology of events, the specific indicators supporting the suspicion, and the relevant transaction list.
The analyst reviews the draft, makes corrections, and approves it by taking responsibility for the content. Corrections made by the analyst can help improve the quality of future drafts.
The draft is never submitted automatically; the institution remains responsible for the content and submission of the report.
No-Code Report Builder
SQL knowledge is not required to create internal reports.
You can build your own report directly from the interface by selecting fields, filters, and groupings. Frequently used filter combinations can also be saved as reusable views.
Alternatively, you can describe the report in natural language:
> "List the corporate customers who required manual review this month and also matched our PEP list."
The system generates the query and presents the report.
Scheduling and Distribution
Reports can be scheduled to run daily, weekly, or monthly and can be delivered to relevant users in PDF or Excel format.
Resource-intensive reports can run in the background without requiring the user to wait for completion.
From Report to Rule
A trend identified in a report can be turned into a scenario.
The finding can be transferred to the Rule Engine, thresholds can be adjusted, and the resulting rule can be tested through simulation.
This helps reduce the distance between analysis and action.
Audit and Retention
Tables can be exported in PDF, Excel, or CSV format.
Data can be archived for the required retention period, while archive integrity can be verified using hash values.
What It Provides to the Institution
- Reduced time spent preparing regulatory report drafts.
- No need to write database queries for standard reports.
- Scheduled reports delivered to relevant users without manual triggering.
- A shorter path from analysis to rule creation.
Common questions
- Is the suspicious transaction report draft submitted automatically?
- No. The draft is prepared for review, and the compliance officer reads, edits, and approves it. The institution remains responsible for the content and submission of the report; the system does not assume this responsibility.
- Is SQL knowledge required to create reports?
- No. Reports can be created by selecting fields and filters through the interface or by describing the required report in natural language, after which the system generates the query.
- Can reports be distributed on a recurring schedule?
- Yes. Reports can be scheduled to run daily, weekly, or monthly and can be delivered to relevant users in PDF or Excel format.