goAML Report Quality Assurance: A Pre-Submission Checklist for UAE Businesses
Submitting an accurate report through goAML is an important part of an organisation's AML reporting process in the UAE. Before clicking the submission button, compliance teams should review the information entered in the report and confirm that the supporting details are complete, consistent and relevant.
The UAE Financial Intelligence Unit's goAML submission guidance notes that fields marked with an asterisk are mandatory, while certain additional fields may also be required under Business Rejection Rules.
A structured goAML report quality assurance process can therefore help businesses identify missing information and inconsistencies before submission.
What Is goAML Report Quality Assurance?
goAML report quality assurance is the process of reviewing a report before submission to check whether the information is complete, accurate, internally consistent and properly supported.
It should not replace the organisation's AML procedures or the MLRO's professional judgment. Instead, it provides a final control step between preparing a report and submitting it through the goAML system.
A practical review can cover:
- Reporting entity information
- Report type
- Reporting person and MLRO information
- Reason for reporting
- Subject or party information
- Transaction details
- Dates and amounts
- Supporting documents
- Internal reference numbers
- Narrative or case summary
- Consistency between different sections
Why a Pre-Submission Check Matters
A report may contain the correct overall conclusion but still require correction because individual fields are incomplete, inconsistent or unclear.
For example, a compliance reviewer may identify:
- A transaction amount that does not match internal records
- An incorrect transaction date
- Missing party information
- An incomplete explanation of the suspicious activity
- Inconsistent names or identification details
- Missing supporting documentation
- Incorrect report classification
- A narrative that does not clearly explain the reason for reporting
The purpose of quality assurance is to identify these issues before submission rather than discovering them afterward.
The UAE FIU's official goAML guidance also provides a preview function, allowing users to review a report before submission.
10-Point goAML Pre-Submission Checklist
1. Confirm the Reporting Entity
Check that the report is being prepared under the correct reporting entity and that the relevant organisation information is accurate.
Do not rely only on the person preparing the report. A second-level review can help identify simple administrative mistakes.
2. Verify the Report Type
Confirm that the selected report type matches the circumstances being reported.
The goAML reporting interface provides different report types, so selecting the appropriate option should be part of the review process.
3. Review Mandatory Fields
Check every mandatory field before submission.
The UAE FIU's goAML guidance specifically states that fields marked with an asterisk must be completed before a report can be submitted.
However, compliance teams should not treat the presence of a completed mandatory field as proof that the information itself is correct.
The reviewer should ask:
Is the information accurate, relevant and consistent with the underlying records?
4. Check Customer and Party Information
Review names, identification information, account information and other relevant party details against the organisation's records.
Pay particular attention to:
- Spelling of names
- Identification numbers
- Account details
- Entity names
- Dates of birth where applicable
- Beneficial ownership information
- Relationships between relevant parties
Small inconsistencies can make a report harder to understand.
5. Reconcile Transaction Details
Transaction information should be checked against the organisation's source records.
Review:
- Transaction date
- Transaction reference
- Amount
- Currency
- Transaction type
- Sender
- Recipient
- Account information
- Related transactions
If multiple transactions are included, the reviewer should confirm that the information is consistent throughout the report.
6. Review the Reason for Reporting
The reason for reporting should clearly explain why the activity requires attention.
Avoid using vague statements such as:
" The transaction appears suspicious.”
Instead, the narrative should explain the relevant facts and circumstances that led to the reporting decision.
The objective is to provide a clear factual explanation that allows the relevant information to be understood without unnecessary repetition.
7. Check the Case Narrative
The narrative should be reviewed for clarity and consistency.
A useful review can ask:
- What happened?
- Who was involved?
- When did it happen?
- What transactions or activities are relevant?
- Why did the activity raise concern?
- What information supports the explanation?
- What action did the organisation take?
The narrative should correspond with the structured information entered elsewhere in the report.
8. Verify Supporting Documents
Where supporting documentation is appropriate, check that the relevant files are available and correctly associated with the report.
The UAE FIU's goAML documentation explains that attachments can be added to reports through the system.
Before submission, check:
- Correct document
- Correct customer or transaction
- Readable file
- Appropriate file name
- No unnecessary confidential information
- Document matches the explanation in the report
9. Compare the Report With Internal Records
A final reconciliation should compare the goAML report against the organisation's underlying records.
Depending on the case, this could include:
- KYC records
- Transaction records
- Customer profile
- Internal investigation notes
- Screening results
- Supporting correspondence
- Account information
- Internal case references
This step helps identify contradictions between the report and the organisation's own documentation.
10. Complete a Final Preview
Before submission, review the completed report as a whole.
The UAE FIU FAQ confirms that users can preview a report before submitting it.
The final reviewer should check the report from beginning to end rather than reviewing only the fields that were recently edited.
Common goAML Quality Problems
Some common quality problems can be grouped into four categories.
Data errors
These include incorrect names, dates, amounts, identification numbers or transaction references.
Missing information
Important information may be omitted even though the overall report has been completed.
Inconsistencies
Information in the narrative may conflict with transaction data or customer information elsewhere in the report.
Weak explanations
A report may contain the relevant data but fail to clearly explain the circumstances that resulted in the reporting decision.
A pre-submission QA process should address all four categories.
Who Should Perform the Final Review?
The appropriate review structure depends on the organisation's AML framework, size and internal controls.
For some organisations, the MLRO may conduct the final review. Larger organisations may use a maker-checker process in which one employee prepares the report and another authorised person reviews it.
The important principle is that report preparation and quality control should be appropriately structured within the organisation's existing AML governance.
How to Create a goAML QA Workflow
A simple workflow can be:
Identify reporting requirement → Prepare report → Verify source information → Complete goAML fields → Review narrative → Check supporting documents → Preview report → Final approval → Submit → Record internal reference
Businesses can turn this workflow into a standard internal checklist.
For recurring reporting activity, the checklist can also be incorporated into the organisation's AML procedures and staff training.
What Should Happen After Submission?
Submission should not necessarily be treated as the end of the internal process.
Organisations should maintain appropriate internal records of the report and monitor communications through the available goAML channels.
The UAE FIU FAQ explains that the goAML Message Board is used for communication between the FIU and goAML users, including notifications concerning reports and requests for additional information.
Therefore, organisations should have a process for reviewing relevant communications and responding through the appropriate channels.
Frequently Asked Questions
1. What is goAML report quality assurance?
goAML report quality assurance is the process of reviewing a report before submission to check that the required information is complete, accurate, consistent, and properly supported.
2. Why should businesses review a goAML report before submission?
A pre-submission review can help identify missing information, incorrect details, inconsistencies, and unclear explanations before the report is submitted through goAML.
3. What should be checked before submitting a goAML report?
Businesses should check the reporting entity details, report type, mandatory fields, customer and party information, transaction details, reason for reporting, narrative, supporting documents, and consistency with internal records.
4. Can a goAML report be reviewed before submission?
Yes. The UAE FIU goAML Web Submission Guide states that users can preview report information before submitting it. This provides an opportunity to review the information entered in the report.
5. What are common goAML reporting errors?
Common issues may include missing mandatory information, incorrect customer or transaction details, inconsistent information, incomplete narratives, and insufficient supporting documentation.
6. Who should review a goAML report before submission?
The final review should normally be completed by the person responsible for AML reporting or another appropriately authorised member of the compliance team who understands the relevant transaction and customer information.
7. What should a goAML report narrative contain?
The narrative should clearly explain the relevant facts and circumstances behind the report. It should be consistent with the information provided elsewhere in the report and should avoid unnecessary or contradictory information.