01
Input
Enter data manually, upload structured CSV files or use API intake from your own systems.
A CLEARER WAY TO HANDLE FIU
REPORTING
FIU reporting.
Under control.
Bring reporting data together, catch issues earlier and stay in control from CSV intake to human review and FIU-ready XML export.
Fewer manual steps Validation before export Visible report status
Clear report statusPending · Export ready · Exported
01 / WHY FCAP
Less chasing files.
More control over reporting.
FIU reporting gets difficult when the preparation work is scattered across spreadsheets, emails and individual routines. FCAP brings that work into a clearer, repeatable process.
Without a shared workflow
Files pass between people, details are entered more than once and report status is harder to follow.
With FCAP
Import reporting data, check issues, review report details and track what is ready for XML export.
02 / THE PLATFORM
See how FCAP
puts reporting in order.
Explore the real reporting workflows in our FCAP demonstration environment. The product visuals use synthetic data and have been presented in marketing-style device frames.
INTERACTIVE PRODUCT TOUR
Select any feature below to explore its FCAP screen, or use Next feature to follow the tour.
FEATURE 1 OF 5
REPORT STATUS
One queue.
Less uncertainty.
Filter reports by their current state, find the work that needs attention and see which reports are ready for export.
Filtered reporting queue
Pending, export-ready and exported status
BULK INTAKE
Import instead
of re-entering.
Use a structured CSV template to bring reporting data into FCAP. The import result makes it clear which record was created.
CSV template and upload flow
Import result per row
ERROR FEEDBACK
Catch problems
before they spread.
Malformed values are rejected during CSV import with specific feedback, making corrections easier before data enters the report workflow.
Specific row-level parsing errors
Invalid CSV input rejected
HUMAN REVIEW
Keep the details
in your hands.
Review report data, reporting codes and the selected indicators before preparing an export. Compliance decisions stay with your team.
Report information and indicators
Review before export preparation
FIU-READY OUTPUT
Prepare the XML.
Keep your control.
Generate reporting XML and track the exported file. XML export is the core reporting output. Configured FCAP deployments can also include evidence packages and supervised goAML upload after human approval. FIU acceptance remains separate.
XML file export
Exported status in the workspace
Viewing 1 of 5: Report queues
03 / HOW IT WORKS
A clear path from data
to FIU-ready output.
Designed around the work compliance teams already do, with less friction between each step.
02
Validate
Check required fields and configured reporting rules before preparing XML output.
03
Review
Review and confirm report details, and attach supporting documents to individual reports.
04
Export & submit
Generate FIU-ready XML and support automated submission of approved reports to goAML through supervised upload, as configured.
Supporting documents can be attached to each report and included in
its evidence package. Automated goAML upload requires human approval
and authorized portal access. Reporting responsibility stays with
the reporting entity.
04 / A CLOSER LOOK
Built for the details
that make reporting work.
Go from input to clear records without losing sight of the transactions behind a report.
01 / STRUCTURED INPUT
A familiar starting point.
Upload a CSV file using a defined format or download the available template to prepare your reporting data.
02 / TRANSACTION DETAIL
One report. Distinct transactions.
Where supported by the reporting rules, a report can hold multiple transactions without merging them into a single transaction.
A PRACTICAL REPORTING LAYER
Your system.
Your compliance decisions.
One
clearer workflow.
FCAP helps prepare and organize FIU reporting. Your organization still decides which activity must be reported and remains responsible for final review and official submission.
Talk through your reporting setup
YOUR DATAManual entryCSV uploadsAPI intake
FFCAPCONTROLLED PREPARATION
Validate fields Review report data Generate XML
OFFICIAL STEPFIU / goAMLThe reporting entity remains responsible for submission and
confirmation, including when supervised upload is configured.
05 / EVIDENCE & UPLOAD
Beyond XML.
Take reporting further.
Our FCAP offering includes evidence-inclusive report packages and supervised goAML uploads for configured deployments. Bring supporting files and approved reports together for a more complete reporting workflow.
One connected reporting process
Structured intake, validation, human review and XML export form the foundation for evidence packaging and supervised upload.
REPORT PACKAGE
Evidence with the report.
Attach supporting documents to individual FCAP reports, then package the evidence with FIU-ready XML in a report-specific ZIP for review and delivery.
XML output + supporting evidence
SUPERVISED UPLOAD
Approved, then uploaded.
Support authorized, human-approved uploads through the official goAML portal using a reporting entity account. The upload process depends on portal access and compatibility.
Human approval remains essentialEvidence packaging and supervised upload are included where agreed in the deployment scope, with activation confirmed before go-live. The reporting entity remains responsible for accuracy, authorization and confirmation of FIU acceptance. Upload depends on the external goAML portal and may be affected by portal changes.
06 / WHO IT'S FOR
One platform.
Many regulated industries.
FCAP is designed for regulated organizations with FIU reporting obligations, from individual entities to service providers coordinating multiple clients.
iGaming & operators
Keep reporting manageable as transaction volumes and reporting requirements grow.
Payments & fintech
Connect existing systems to a structured report-preparation workflow.
Banking & finance
Support consistent preparation and review across reporting teams.
Corporate service providers
Work across reporting entities while keeping data and records separated.
07 / BUILT FOR CONTROL
Built to make
control visible.
Compliance software should make responsibilities and reporting status easier to understand, not harder. FCAP focuses on a controlled process around each report.
Discuss your requirements
01Separate reporting entities
Distinct entity workspaces and reporting records.
02Defined user access
Access to reporting workflows controlled through authorized accounts.
03Report visibility
Find pending, export-ready and exported reports in one workspace.
04Human oversight
Your compliance team retains responsibility for final report review and official submission.
08 / GOOD TO KNOW
A few things
worth clarifying.
Direct answers to the questions compliance teams usually ask before exploring a new reporting workflow.
Does FCAP replace goAML?
No. FCAP helps teams prepare, validate and review reports, generate FIU-ready XML and manage evidence and supervised uploads where included in the deployment. The official goAML portal remains the authority for submission and acceptance.
How does reporting data get into FCAP?
FCAP supports manual entry, structured CSV uploads and API data intake from client systems. The appropriate approach depends on the reporting volume and integration needs.
Does FCAP decide which transactions must be reported?
No. The reporting entity remains responsible for identifying reportable transactions, choosing the applicable reporting indicator and confirming the report information.
Can FCAP support multiple reporting entities?
FCAP supports separately configured reporting-entity workspaces. Each entity has its own users and reports according to the agreed setup. Multi-entity oversight and access depend on the deployed configuration and permissions.
How do reports reach the FIU?
FCAP prepares XML for the official FIU/goAML process. An agreed deployment can include supporting-document packages and supervised upload through an authorized goAML account after human approval. The reporting entity remains responsible for final review, submission obligations and confirming FIU acceptance.
Can my FCAP deployment include evidence packages and automated upload?
Yes. These capabilities can be included in an agreed FCAP deployment. We confirm the delivery scope, activation and goAML portal compatibility during onboarding and before production go-live. The reporting entity continues to authorize uploads and confirm their acceptance by the FIU.
READY FOR A CLEARER PROCESS?
Your next report
Your next report
could feel different.
Bring a mock or anonymized sample file. We’ll show the FCAP workflow from data intake to review and XML output.
Request a product demo Synthetic or anonymized sample data only.
