Operational views
Review work, evidence, exceptions and authorised decisions within a defined operating scope.
Logistics & supply chain
Coordinate shipment documents, classification and origin evidence, licensed review, approved filings and clearance-query records.
12 workspace menus · 5 role profiles · Connected records
Designed for import-export compliance directors and customs brokerage managers

Operational workspace and record review. Select a screen to inspect it in full.


Review work, evidence, exceptions and authorised decisions within a defined operating scope.
Coordinate shipment documents, classification and origin evidence, licensed review, approved filings and clearance-query records. A shipment can reach clearance with inconsistent or incomplete commercial evidence. The system keeps document readiness and reviewer decisions connected to the shipment, providing an accountable path for missing classification or origin information and later authority queries.
From intake to authorised completion, with evidence at each decision.
Collect shipment and commercial documents.
Flag missing classification and origin evidence.
Obtain licensed review and filing approval.
Track clearance queries and retain decisions.
Permissions are configured and tested for the agreed responsibilities.
Interface scope, data mapping and testing are agreed for each engagement.
View document status and submit permitted supporting evidence through responsive views.
Access approved workflows through the Dalfin mobile app. Device tasks and permissions are confirmed for the deployment.
Extract document fields and flag inconsistencies for licensed reviewer confirmation.
AI extensions are scoped around the required data, business outcome and review controls.
Connect requirements, roles, records, workflows and interfaces through the agreed Genesis engineering process.
Review dependency impact and validation requirements. Context Memory supports governed changes and accepted application revisions.
Agree customer cloud or on-premises requirements, device access, implementation acceptance and ongoing engineering support.
An example operating scenario
A shipment is missing origin evidence. The coordinator obtains the supporting record, a licensed reviewer confirms the approved filing position and a clearance query is resolved. The final decision remains linked to the supplied documents and approvals.
Roles, approval authority, business rules, records and reporting are configured around your operating model. Scope definition connects the required business outcome to workflows, interfaces and acceptance criteria.
Operators, reviewers and authorised decision makers have defined responsibilities. Approval limits, exception handling and access permissions are agreed with your business owners and tested against the selected workflows.
Interface requirements cover your existing business systems, data ownership, mapping and authentication. Connection design and testing form part of the agreed implementation scope.
Start with a relevant business transaction, then review its approvals, an exception, role permissions and final records. Discuss the integrations, reporting and operating requirements that matter to your organisation.