Daertho

The backoffice
without the
department.

AML operations first — data, tools, operators, analysts, workflows and reporting in one operating layer for regulated companies.

Get started ↗ ↓ Explore the functions
Daertho logo

Application received

Sample workflow

Digital operator KYC-1042

Sterling_V.pdfKYC-1042
ONBOARDING / SOURCE PDFIncoming
PDFSterling_V.pdf

Application

Individual customer onboarding

Applicant nameVictoria Sterling
Date of birth18 June 1988
ResidenceUK
Projected annual income$285,000
Age38
Bank account informationExample Bank · •••• 8829
Identification documentsPassport · Proof of address
Sample data · 01
PDF archivedLinked to case KYC-1042
01 / 08 · Source documentReceiving
Application receivedSterling_V.pdf
#compliance · checks0 / 3
Sanctions screeningCustomer name screeningQueued
IdentificationPassport + application detailsQueued
Other ID checksDOB cross-check + address evidenceQueued
Department handoffs via #dispatch0 / 2
#marketing
Awaiting data
$285,000Projected / year38Age
Waiting for checks
#banking-treasury
Awaiting data
•••• 8829Example Bank · Account
Waiting for checks
Documents / case archivePDF + case recordWaiting

Complete

One application. Every handoff recorded.

3 checks2 handoffs1 PDF archived

Receiving the application PDF.

Application received. Step 1 of 8.

THE OPERATING MODEL

The backoffice,
function by function.

Other backoffice functions follow as the operating model is proven.

Explore the operating model
FUNCTIONS

01 — AML operationsCURRENT FOCUS

Onboarding, screening, monitoring and review. Evidence and approvals stay with the case.

  • KYB / KYC
  • Screening
  • Monitoring
  • Review
Explore AML Operations

01 / CONTROLLED EXECUTION

A case. Carried through.

CASE AML-01 CASE CONTINUITY
  1. 01 / INTAKEApplicationSource attached ✓
  2. 02 / EXECUTEChecksScreening complete ✓
  3. 03 / AUTHORITYReviewApproval recorded ✓
  4. 04 / RECORDCase recordReconstructable ✓

02 — Document operationsFUTURE

Documents become structured process inputs while the original source remains attached to the work.

  • Receive source
  • Extract information
  • Retain original

02 / SOURCE → STRUCTURE

From source to structure.

APPLICATION01 / 01
Company information
Registered companySterling Payments Ltd.
ApplicantVictoria Sterling
JurisdictionUnited Kingdom
PDFSterling_V.pdf↗

STRUCTURED INPUT

COMPANY
Sterling Payments Ltd.
APPLICANT
Victoria Sterling
JURISDICTION
United Kingdom
ORIGINAL SOURCE RETAINEDSterling_V.pdf

03 — Bank reconciliationFUTURE

Every difference remains visible until the records match, exceptions are resolved and authority is recorded.

  • Compare records
  • Resolve exceptions
  • Record authority

03 / MATCHING & EXCEPTIONS

Every difference accounted for.

3 / 4MATCHEDONE EXCEPTION
REMAINS OPEN
Comparison of four bank transactions and internal records. Three match. TRX-443 and INV-223 differ by $55.
BANK RECORDMatching stateINTERNAL RECORD
TRX-441$18,400✓INV-221$18,400
TRX-442$9,220✓INV-222$9,220
TRX-443$11,875≠INV-223$11,820
TRX-444$6,350✓INV-224$6,350
EXCEPTION REMAINS VISIBLEΔ $55.00
EXCEPTION STATE Review required AUTHORITY PENDING

04 — The wider backofficeEXPANSION

The same operating model can extend to customer records, reporting, billing, settlement and other backoffice work.

  • Customer records
  • Reporting & billing
  • Settlement

04 / AN EXPANDABLE MODEL

The backoffice, connected.

01Customer records
02Complaints
03Vendor & outsourcing risk
SHARED PROCESSDAERTHOOPERATING MODEL
04Regulatory reporting
05Billing
06Settlement

Cross-function coordination

The case stays.
The request moves.

When another function has the answer or information is missing, Daertho sends a request while keeping the original case intact. When the response arrives, the same case resumes.

See exception handling in the Stack ↗

CASEKYC-1042COMPLIANCE

Sample case KYC-1042 stays in Compliance. Dispatch sends one request to Marketing / Sales for projected income and one to Banking / Treasury for the settlement account. Both answers return by the same path and the same case resumes.

Wired into the product.

Create a case. Receive events. Integrate the workflow.

ILLUSTRATIVE API CONTRACT
POST /v1/cases Authorization: Bearer $DAERTHO_KEY Content-Type: application/json { "workflow": "kyb.onboarding", "entity": { "name": "Apex Digital Ltd." }, "jurisdiction": "GB", "approval_policy": "human_required" }
EVENT STREAM / DA-8217
case.created
operator.run.completed
case.approval.required
case.approved
workflow.resumed
case.sealed
Case created. Ready to run the example.
Examples show the intended interaction model. Confirm endpoint availability and integration requirements before implementation.

Built to be
questioned.

Trust starts with precise boundaries: what software can access, what it can do and what gets recorded.

Read Security & Trust ↗

Confirm providers, retention, access and deployment requirements for the agreed setup.

EVIDENCE

Sources stay attached.

Inputs, actions and requests remain with the case.

AUTHORITY

Humans own decisions.

Policy determines where a person must authorize the next action.

POLICY

Gates are explicit.

Define the data and tools each process is permitted to use.

AUDIT

Cases stay reconstructable.

Actions and approvals stay recorded.

  • FAQ

Straight answers.

Daertho is designed to preserve human accountability and a reconstructable evidence trail. Regulatory acceptance still depends on your jurisdiction, controls, governance and implementation; the product should support that process rather than promise approval.

AWS Servers or Daertho built on-premise infrastructure

Can be toggled for finality or pre-finality.

2 weeks

1 bps of GMV

Build your team. we've got your back.

Get started →
Scroll to Top