For financial crime, AML operations and compliance teams at Australian reporting entities who need alerts cleared faster without weakening the evidence behind each decision.
Key takeaways
- Under the AML/CTF Act, once a reporting entity forms a suspicion it has three business days to give AUSTRAC a suspicious matter report, or 24 hours where the suspicion relates to terrorism financing.
- Agento triages each alert on the tools the team already uses: Salesforce for the customer and the case, Outlook for the alerts mailbox and Teams for the restricted channel.
- The disposition it drafts cites the transaction, alert or Salesforce record behind every sentence. A sentence with no evidence fails the check and never reaches the analyst as a finding.
- An analyst decides whether to escalate. The MLRO signs off the report. Agento prepares the work and nothing is sent to the customer.
Every AML alert is hours of work
A transaction monitoring alert is a starting point, not an answer. Before anyone can close it or escalate it, an analyst has to:
- Work through the transactions to see what actually moved, when, and where it went.
- Pull the customer's history, including earlier cases and how they ended.
- Test the facts against known typologies, such as structuring, rapid movement of funds, new payees and mule patterns.
- Write it all up in a way a reviewer, an auditor or AUSTRAC can follow.
Then the clock matters. If the review ends in a suspicion, the report is due within three business days of the day the suspicion was formed. Most of that time is spent gathering and writing, which is the part software can take on.
Point Agento at your alerts inbox
Setup is short. Salesforce, Outlook and Teams are authorised once on the Connectors page. An Outlook inbox trigger then watches the AML alerts mailbox, so each new alert starts a run without anyone forwarding it.
From there, three workflows cover the life of an alert.
1. Alert triage
The triage workflow runs 14 steps and stops for a person before any decision is recorded.
The alert is read and screened
Agento masks any card data in the alert first. It then reads the alert, screens the transactions for red flags, loads the customer's profile from Salesforce, finds the customer's earlier cases and tests the facts against AML typologies.
In the demo run in the video, the alert is for cash structuring below the reporting threshold with rapid outward movement, scored 91. Agento finds three red flags and pulls both the customer record and a prior case.
A disposition where every sentence cites its evidence
Agento drafts the disposition and puts the source of each statement in square brackets: the transaction ids, the alert and the Salesforce records. A reviewer can check any sentence against the record it came from.
No evidence, no statement
A separate step then checks the draft. If a sentence has no source behind it, the draft is rejected. The video shows this happening: a line of opinion with nothing cited fails the evidence check, the analyst step is skipped, and the team is told the disposition failed. Opinion does not get recorded as a finding.
An analyst makes the call
The run pauses for an analyst, who escalates the alert to investigation or closes it as a false positive. Only after that approval is the case escalated and the decision recorded on the AML case in Salesforce. The update goes to the AML Alerts channel in Teams and nowhere else.
2. Suspicious matter report preparation
When an investigator confirms the suspicion, a second workflow of 15 steps takes over.
- The clock starts. The three-business-day deadline is calculated and recorded on the case. In the demo, a suspicion formed on a Thursday gives a due time of 11:59 pm the following Tuesday.
- The grounds are drafted for the MLRO, with every claim cited in the same way as the disposition.
- A tipping-off guard runs. Telling a customer that a suspicion has been formed or a report made is against the law, so the workflow checks for it and only the restricted team is told.
- The MLRO signs off. The run waits for the MLRO's approval, and the approved draft is filed on the case.
Agento prepares the report for lodgement. Your MLRO approves it and your team lodges it with AUSTRAC through your existing process.
3. An hourly clock watcher
The third workflow runs every hour. It finds cases with a confirmed suspicion in Salesforce, checks each report against its deadline and posts the status to Teams. A report that is running close to its deadline is visible to the team well before it is late.
Every step recorded
Each run produces an evidence record: who started it, each step in order, who approved what and when, and how long it took. The triage run in the video finished its 14 steps in 3 minutes 25 seconds, including the analyst's approval. The record can be printed or saved as a PDF for internal QA, audit or a regulator's request.
What changes for the AML team
- Every claim cited. Dispositions and report grounds point to the records behind each sentence.
- People decide. An analyst decides on escalation and the MLRO signs off the report.
- Nothing reaches the customer. Updates go to restricted internal channels only.
- Deadlines in view. The three-business-day clock is calculated when the suspicion is confirmed and checked every hour.
- Evidence by default. Every run leaves a complete record of what was done.
How much analyst time this saves depends on your alert volumes, your monitoring system and how your cases are set up in Salesforce. We scope each rollout against your current process before quoting outcomes.
