Daertho

The backoffice
without the
department.

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

Get started ↗ ↓ Explore the functions
DAERTHO // DAERTHO
APPLICATION
CASE KYC-1042
DIGITAL OPERATOR ACTIVE
APPROVED FOR MARKETING$285,000 PROJECTED · AGE 38
APPROVED FOR TREASURYJPMORGAN CHASE ·••• 8829
01 / SOURCE PDFRECEIVED
Application
Sterling_V.pdf · 2.8 MB
READY
ApplicantVictoria Sterling · Managing Director
CompanySterling Payments Ltd. · UK
Projected income$285,000 per yearAge38
Settlement bank accountJPMorgan Chase ·••• 8829
Identity documentsPassport 88920141 · National ID
ENCRYPTEDSOURCE PRESERVED
02 / CASE ROUTEPROCESSING
INTAKEApplication fields parsedSource retained with coordinatesWAITING
SCREENSanctions screeningOFAC · UN · EU · UK HMTWAITING
IDENTIFYIdentification verifiedPassport · biometric · livenessWAITING
CHECKOther ID checks completedAddress · registry · ownershipWAITING
MARKETINGWAITING
$285,000 · AGE 38Projection and age
TREASURYWAITING
JPMORGAN ·••• 8829Settlement account
CASE ARCHIVESterling_V.pdf
KYC-1042 · SEALED
READY
DOCUMENT RECEIVEDSTEP 01 / 08
PROCESSING CASE…
CASE KYC-1042COMPLETE
ApplicationSterling_V.pdf · archived
Sanctions screeningCLEARED
IdentificationVERIFIED
Other ID checksCOMPLETE
Approved data routesDELIVERED

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 ↗

CASE KYC-1042 COMPLIANCE
REQUEST CREATED
One answer is missing. Compliance needs information held by another function.
Original case KYC-1042 State preserved
Dispatch Route Request only
Answer from Marketing / Sales Projected income
REQUEST ROUTE WAIT RESUME
ORIGINAL CASE STAYS INTACT
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