Skip to main content

Known Limitations

This page lists what Duely does not do, so you can plan around each boundary before an engagement starts.

Each is a deliberate scope decision. Where the reason is not obvious, the section states it.

Duely does not watch transactions​

Ongoing monitoring in Duely is customer level. It raises a review when a customer's circumstances change, when a verification baseline expires, or when a trigger fires.

It does not screen transactions as they happen, and it does not sit on a feed of payment activity.

In practice, the unusual transaction or behaviour that gives rise to a suspicion is noticed by a person, and raised by them through an unusual activity report. Duely holds and routes that record. It does not detect the pattern for you.

The obligation this relates to is Customer due diligence, and the route for raising a concern is on Suspicious matter reports.

Duely does not lodge reports with AUSTRAC​

The firm lodges every report. There is no submission rail, and nothing is filed automatically on your behalf.

Duely prepares the record: the report data, and for suspicious matter reports an AUSTRAC XML payload you can use. You take that payload and lodge it through your own AUSTRAC channel, then record the response reference back against the case.

Approving a report inside Duely does not send anything to AUSTRAC. Approval is an internal step.

See Suspicious matter reports for the workflow, and Reporting for the deadlines.

Duely does not decide whether something is suspicious​

No part of the workflow forms a suspicion on your behalf, and no threshold in the product triggers a report automatically.

This is deliberate. Forming a suspicion is a judgement about a set of circumstances. If a suspicious matter reporting obligation arises and the firm does not report it in time, the firm can face civil penalties (s 41), and so can a person knowingly involved in that failure (s 174). The product's job is to make raising a concern easy and to hold the record safely.

If something looks wrong, raise it. See Suspicious matter reports.

Duely does not provide a public API​

There is no public API and no API keys for third party access. The integrations that exist connect Duely to its external providers: Duely calls them, and some providers send results back to Duely by webhook. There is no inbound interface for your own systems.

There is no supported way to push engagements, customers, or records into Duely from another system programmatically. Customer records can be imported from a file. See Customer onboarding at a glance.

If an integration matters to your firm, raise it rather than building against something unsupported.

Duely is not a multi-firm console​

The product is built around firm scoped tenancy. Every record belongs to one firm, and other firms cannot see it. There is no console for working across several firms' data, and no cross-firm reporting.

For a firm operating through several legal entities, each entity is its own firm with its own records, program, and reports. Duely does not roll them up.

Duely does not replace your professional judgement​

The product structures the work, records the decisions behind it, and produces evidence that the work was done. It does not tell you whether a customer is acceptable, whether an engagement should proceed, or whether a risk rating is right.

Where the product does enforce a rule, it is enforcing a requirement of the regime, such as refusing to mark a verification verified without an identity binding basis. That is a floor, not an assessment.

Duely does not make a firm compliant, and does not claim to. Compliance depends on what your firm did, whichever software it used.

This knowledge base describes the law as it applies to the obligations covered, and how Duely supports them. It is not legal advice, and it does not account for your firm's particular circumstances.

Where an obligation turns on facts only you know, such as whether a service is a designated service in your case, the product records your determination rather than making it. See Start an engagement.

Things that are planned and not built​

ItemStatus
Auditor portalNot built. External auditor access is not available
Additional verification and screening providersThe current providers are wired. Further adapters are deferred
Engagement templates and quick-startNot built
External engagement workflow for independent evaluationDeferred. The evaluation record itself is available

Where the boundaries are documented​

Each boundary above is also noted on the page it affects, so you meet it in context rather than only here: