NEW FEATURES

AML Data Model

Matters now have fields to support anti-money laundering tracking: whether AML is required, overall status
and risk, the compliance decision (including approval with conditions), and who recorded the decision. The
matter stays AML locked until the matter AML status is Cleared. Each party also has an AML check status
so you can record verification progress per party involved in the matter.

New Account fields

These fields are intended to be populated by AML integration packages or custom automation; they are
included on the Nebulaw permission set for read/edit access.

New Matter and org settings fields

Validation rule — AMLNotRequiredReason

When AML Checks Enforced is enabled in General Settings and a Matter has AML Required unchecked,
a reason must be provided in AML Not Required Reason. Error message: "A reason needs to be provided
if AML is not required for this Matter".

Field history tracking

The following fields now track field history (previously untracked):

• Matter__c.AMLStatus__c
• Matter__c.IsAMLRequired__c

AML Banner Display

Matters now have fields to support anti-money laundering tracking: whether AML is required, overall status
and risk, the compliance decision (including approval with conditions), and who recorded the decision. The
matter stays AML locked until the matter AML status is Cleared. Each party also has an AML check status
so you can record verification progress per party involved in the matter.

A new lightning component called AML Matter Banner is now available to be included in Matter Lightning
Record Pages which provides a high-level, heads up view of the Matterʼs AML status and any actionable
items for the Fee Earner.

Placement

• Exposed for Matter__c record pages via Lightning App Builder.
• Not pre-placed on a packaged flexipage — add the Matter AML Banner component to your Matter
  Lightning record page(s) after upgrade.

Banner display

• AML Status — interactive status button with colour-coded styling (warning, neutral, success).
• Risk — displays the Matter risk rating, with a warning icon when risk is High.

Status popover

Hovering, clicking, or focusing the AML Status button opens a contextual popover (via the new
nebulawPopover component) with scenario-specific messaging:

Popover actions

• Edit Details — opens a modal to update AML Status, Risk, and (when status is Cleared) Decision,
  Decision By, Decision Date, and Decision Notes.
• Review Parties / View Parties — navigates to the Matter's related Parties list.
• Decision Details — read-only modal for cleared Matters showing full decision information.

Party awareness

The banner queries related Parties (up to 1,999) and counts those whose AML Check Status contains
Review required, feeding the review-required scenario summary.

Technical notes

• API version 65.0.
• Uses lightning/uiRecordApi , lightning/uiRelatedListApi , and existing nebulawModal
  for edit/view dialogs.
• nebulawModal enhanced with contentOverflowVisible so picklist dropdowns are not clipped in
  the edit modal.

BUG FIXES

Adding a validation to Bank Reconciliation process

Added validation to Bank Reconciliation finalisation to prevent transactions from reappearing in future
reconciliations when linked to unresolved draft reconciliations for the same bank account. The system now
checks the transactionʼs “First Seen” reconciliation and, if the related reconciliation is still in Draft status,
prevents finalisation and prompts the user to either finalise or remove the earlier draft before proceeding.

Implement string truncation for Conflict Check Technical Details

Implemented truncation for Conflict Check Technical Details and Party Results to prevent the “String too
long” error during conflict checks. The complete conflict check information is still stored in the Conflict
Check Details object, allowing users to view the full details if the Technical Details or Party Results are
truncated due to character limits.

Time Item Rates Not Applied to Time Entries Created via Tardis

Implemented a fix to ensure that Time Entries created via Tardis correctly apply the configured Time Item
rate, enabling accurate billing and consistent behavior across all Time Entry creation methods in Unity
PMS.

PERMISSIONS

The Nebulaw permission set (Nebulaw) grants read/edit access to new and updated AML fields:

Account

• AMLProviderReference__c
• IDVerificationStatus__c
• IDVerificationTimestamp__c
• LastScreenedDate__c
• PEPSanctionsScreeningStatus__c
• RiskRating__c

Matter

• AMLNotRequiredReason__c
• (Existing AML fields — AMLStatus__c , AMLDecision__c , AMLRisk__c , IsAMLRequired__c ,
  IsAMLLocked__c — remain included)

Party

• AMLCheckStatus__c

Assign the Nebulaw permission set for users who manage AML on Matters, Parties, or Accounts.

CONFIGURATION CHECKLIST

1. Matter record page — in Lightning App Builder, add the Matter AML Banner component to Matter
   record page(s). Place it prominently (e.g. above detail tabs or in the highlights panel region).
2. General Settings — review AML Checks Enforced:
   • Leave off (default) to allow Matters to be marked as not requiring AML without a documented reason.
   • Enable when your firm requires a written exemption reason whenever AML Required is unchecked.
3. Permissions — refresh the Nebulaw permission set assignment for AML-related users.
4. Layouts — verify the updated Matter and Party layouts are assigned to the appropriate record
   types/profiles, or merge the new AML sections into custom layouts.
5. AML provider integration — if using an AML extension package, map provider responses to the new
   Account screening fields ( IDVerificationStatus_ _c , PEPSanctionsScreeningStatus_ _c ,
   etc.).
6. Bank reconciliation — if users encounter the pending-draft error when finalising, finalise or delete the
   earlier draft reconciliation referenced by affected cashbook entries before retrying.

UPGRADE/COMPATIBILITY NOTES

FULL DATA MODEL CHANGES

This section lists all NebuLAW Core (nebulaw) schema changes since 6.0.0 (git tag Nebulaw-6.0.0-2). Subscribers upgrading directly to 6.3.0 receive these changes in a single install. Extension packages are out of scope. For AML field semantics, relationships, and rollup behaviour, see the AML data model technical reference. 

New custom objects

Credit Notes (6.1)

Multi-Client Wizard (6.1)

AML compliance platform (6.1 foundation + 6.3)

These objects store CDD check detail, beneficial owner registers, risk assessments, audit events, and source-of-funds evidence. Field-level definitions are documented in the AML data model.

New fields on existing objects

Account

• RiskRating__c — Risk Rating
• AMLProviderReference__c — AML Provider Reference
• IDVerificationStatus__c — ID Verification Status
• IDVerificationTimestamp__c — ID Verification Timestamp
• PEPSanctionsScreeningStatus__c — PEP/Sanctions Screening Status
• LastScreenedDate__c — Last Screened Date
• New record type: Multi-Party Client ( MultiPartyClient )

Matter

• IsAMLRequired__c — AML Required
• AMLNotRequiredReason__c — AML Not Required Reason
• AMLStatus__c — AML Status
• AMLRisk__c — AML Risk
• AMLDecision__c — AML Decision
• DecisionById__c — Decision By
• DecisionDate__c — Decision Date
• DecisionNotes__c — Decision Notes
• IsAMLLocked__c — AML Locked
• AutoCreateParties__c — Auto Create Parties

Party

• AMLCheckStatus__c — AML Check Status
• AccountRisk__c — Account Risk
• FromMatterWizard__c — From Matter Wizard

General Settings

• AMLProvider__c — AML Provider
• AMLCheckValidityMonths__c — AML Check Validity Months
• AMLChecksEnforced__c — AML Checks Enforced
• AMLReviewEnforced__c — AML Review Enforced
• AmlAllowSelfReview__c — Allow AML Self-Review

Automation Bypass

• AMLCheckTrigger__c — AML Check Trigger
• RiskAssessmentTrigger__c — Risk Assessment Trigger

Release Note Entry (custom metadata type)

• DisplayOrder__c — Display Order
• EntryType__c — Entry Type

Added to the pre-existing ReleaseNoteEntry_ _mdt type to support grouped release note cards in the hub.

Custom metadata types

Four new AML configuration types ship with seeded records that should be reviewed after install (see AML compliance rollout):

• AmlApplicabilityRule__mdt — AML Applicability Rule (matter-type AML applicability)
• AmlCddRoleRule__mdt — AML CDD Role Rule (party role to CDD requirement mapping)
• AmlEnhancedCddItem__mdt — AML Enhanced CDD Item (enhanced CDD checklist items)
• RiskAssessmentRequirement__mdt — Risk Assessment Requirement (matter-type risk
  assessment gates)

Global value sets

Eight new global value sets support AML picklists and can be extended in future package upgrades:

• AMLProvider — AML integration provider (Legl, easyAML, realAML, Manual)
• AMLCheckType — CDD check types (Identity, PEP/Sanctions, SOF, UBO, and others)
• AMLCheckStatus — Check lifecycle status values
• AMLResultSummary — Provider result summary vocabulary
• AmlAuditEventType — AML audit event categories
• AmlCddRequirement — CDD requirement levels for role rules
• RiskAssessmentScope — Client or Matter assessment scope
• RiskAssessmentStatus — Risk assessment lifecycle status values

Modified fields and terminology

• Party__c.Role__c — field history tracking enabled.
• Matter__c.AMLStatus__c — picklist value Cleared is deactivated; Completed is the new
  terminal value. Existing matters with Cleared are not migrated automatically. Update these records to
  Completed before enabling AML enforcement if your org used the legacy value.

Validation rules

Three new validation rules are included:

• AMLCheck__c.SubjectRequired — requires an Account or Contact on each AML Check
• RiskAssessment__c.SubjectRequired — requires an Account or Contact on each Risk
  Assessment
• Matter__c.AMLNotRequiredReason — requires a reason when AML is not required and
  AMLChecksEnforced__c is enabled
   

PERMISSION AND FIELD-LEVEL SECURITY

New objects and fields are not visible to users until object permissions, field-level security (FLS), and (for AML) custom permissions are granted. If users rely on custom permission sets, permission set groups, or profile-based access instead, you must update those assignments manually.

Use the shipped permission sets as reference templates in Setup → Permission Sets when determining
what to grant.
 

Notes for custom access models:

• Nebulaw alone does not grant AML object or Matter/Party AML field access. Firms adopting AML
  must grant NebulawAmlCore (directly or by replicating its object, field, and custom permission
  entries).
• AML UI actions are gated by custom permissions, not FLS alone. Users without AmlConductCdd
  cannot initiate manual CDD; users without AmlReviewChecks or AmlClearMatter cannot complete
  reviews or clear matters via the AML Banner.
• Segregation of duties: In NebulawAmlCore , Matter AMLDecision_ _c and decision metadata fields
  are read-only; NebulawAmlComplianceOfficer grants edit access. Replicate this split if compliance
  staff must clear matters but fee earners must not.
• General Settings AML fields ( AMLProvider_ _c , AMLChecksEnforced_ _c , and others) are orgwide hierarchy custom settings —  configure via admin profiles or your existing General Settings access
  model, not via the AML permission sets.
• AutomationBypass_ _c AML trigger bypass fields are intended for migration administrators only.