The case pipeline, in one operator console.

Advoware fires a trigger. This server snapshots the file, reads every document, asks Gemini or Claude, then writes claims, opponents, reminders and SEPA back into the Akte — while you watch it happen.

4 queuesFetch · OCR · AI · writeback

2 modelsGemini 2.5 Pro · Claude Opus

1 snapshotLocal extra-server copy

Trigger

POST /api/trigger with case nr and secret.

Sync

Histories, files, participants, RefData C50.

Mind

Vision OCR + Notion prompt + Vertex.

Act

K-steps write Advoware and SEPA XML.

End to end

From Advoware art to a finished K-step.

K1 / K6

Client questions

Mail or phone questions become a drafted KI answer and a Wiedervorlage in the Akte.

Invoice readout

RE-Upload extraction updates wert, creates Gegner, address, claim and a check reminder.

SEPA payment

ATM invoice payment notes the transfer, then queues a pain.001 payment for the nightly batch.

KIQ files

The AI answer is rendered to PDF, uploaded to Advoware, and flagged for the Sachbearbeiter.

Operator tools

Built for the night shift, not a marketing page.

Live monitor

Triggers, Redis workers, failed jobs and Vertex responses on one radar.

Connectivity tests

Ping Advoware, ADC, prompts, OCR binaries and mint a Vertex token on demand.

Log tails

Application, trigger, reminder and file channels without leaving the console.

Masked config

See what the pipeline is actually using — secrets stay dotted out.

Connected systems

The mesh behind every case.

Advoware Google Vision Vertex Gemini Claude on Vertex Notion prompts Redis workers SEPA pain.001