Process automation & system orchestration
Automate the hand-offs, not the judgement.
Relay runs the processes that cross system boundaries. An invoice arrives, is read, matched to its order, approved and posted, without anyone retyping it. Every step can be retried safely, every exception reaches the right person with a deadline, and every action is recorded.
VARDA RelayRuns on Orbit
The problem
People have become the integration layer.
Orders are copied from e-mail into the ERP, invoices are keyed in from PDFs, approvals wait in inboxes, and status checks happen by phone. Every hand-off adds delay and a chance of error, and when something goes wrong, no one can say at which step, or why.
- 01
Data rekeyed from e-mails and PDFs into the ERP
- 02
Approvals that stall in inboxes with no deadline
- 03
Scripts and point-to-point integrations that fail silently
- 04
No record of who did what, when, and on what basis
- e-Invoice receivedUBL-TR · GİB✓
- Field extraction12 fields · conf. 0.98✓
- 3-way matchInvoice · PO · receipt✓
- ApprovalProcurement managerwaiting
- Post to ERPSAP S/4HANA·
- NotifySupplier · e-mail·
- 09:41:02e-Invoice received · ETTN 3f9c…a41e
- 09:41:0312 fields extracted · confidence 0.98
- 09:41:053-way match passed
- 09:41:06ERP timeout → retried with the same idempotency key
- 09:41:07Sent for approval · Procurement manager
Capabilities
Let systems talk, so people can think.
Visual design, real code
Analysts model flows in a visual designer; engineers extend them with TypeScript or Python steps, versioned in Git and reviewed like any other code. Flows start on events: an e-mail, a file, a database change, a webhook or a schedule.
Connectors for the systems you run
Relay ships with connectors for ERP and CRM platforms, databases, e-mail, SFTP, REST and SOAP services, and GİB e-Fatura and e-Arşiv through your integrator. New connectors are built against a documented SDK.
Document intelligence
Invoices, delivery notes, orders and forms are classified, read with OCR and extracted into fields, each with a confidence score. Low-confidence fields go to a person, and the correction improves the next extraction.
Human-in-the-loop approvals
Approvals route by amount, department or risk, with delegation, escalation and four-eyes rules. Approvers see the document, the extracted data and the reason they were asked.
SLA timers and escalation
Every step and every case has a clock that respects working hours and public holidays. Relay warns before a deadline is missed, escalates when it is, and reports where time is actually spent.
Safe retries, complete audit trail
Steps carry idempotency keys, so a retry after a timeout never posts an invoice twice. Failed steps go to a dead-letter queue, and every action, automated or human, is written to an append-only audit log.
How it works
From trigger to audit record
Trigger
A process starts on an event: an e-mail arrives, a file lands on SFTP, a record changes in the ERP, a webhook fires or a schedule comes due.
Read
Documents are classified and read. Structured data such as UBL-TR e-invoices is parsed directly; scans and PDFs go through OCR and field extraction.
Validate and match
Business rules check the data against master records: supplier, purchase order, goods receipt, tax number, amounts and tolerances.
Decide
Clean items continue automatically. Exceptions go to the right person with the context, a deadline and a clear question to answer.
Post and record
Relay writes to the target systems with idempotency keys, confirms each result and records every step in the audit log.
Architecture
VARDA Relay · Architecture
01 Sources
- E-mail & SFTP
- GİB e-Fatura / e-Arşiv
- ERP & CRM
- APIs & webhooks
02 Processing
- OCR & field extraction
- Validation & matching
03 VARDA Relay
- Relay orchestration engine
- Approvals & SLA timers
04 Outputs
- ERP postings
- Notifications & tasks
- Audit trail & reports
Use cases
Use cases
Incoming e-Fatura documents are parsed directly from UBL-TR, while paper and PDF invoices go through OCR. Relay matches each invoice to its purchase order and goods receipt, sends mismatches for approval and posts the rest to the ERP.
- Three-way matching with configurable tolerances
- Duplicate checks before anything is posted
- Accept and reject responses to commercial e-invoices tracked against their deadline
Customer purchase orders arrive as e-mail attachments in many formats. Relay reads them, maps customer item codes to your own, checks price, stock and credit, and creates the sales order, sending only the doubtful ones to the sales desk.
- Customer item codes mapped to your catalogue
- Price, stock and credit checks before the order is created
- Order confirmations sent back to the customer automatically
Bank statements in MT940 or camt.053, payment-provider reports and ERP ledgers are compared every night. Matched items close automatically; breaks are grouped into cases with the evidence an accountant needs to resolve them.
- Rule-based and fuzzy matching on references and amounts
- Open items routed with SLA timers ahead of the close
- A reconciliation report with its complete audit trail
Deployment options
Deployment options
On-premises
Relay runs inside your network, next to your ERP and file shares. Suited to organisations whose documents carry personal or financial data that must stay within their own infrastructure.
Private cloud
Deployed into your private cloud, with connectors reaching on-premises systems through a lightweight agent that opens outbound connections only.
Hybrid
Orchestration runs centrally, while document processing and connectors run on site, so documents and personal data are handled where they already live.
Technical specification
VARDA Relay
- Triggers
- E-mail, SFTP, database change (CDC), webhook, schedule, API call
- Workflow definition
- Visual designer with TypeScript and Python steps; versioned in Git
- Execution model
- Durable, event-sourced state; resumes where it left off after a restart
- Retries
- Exponential backoff, idempotency keys, dead-letter queue
- Document formats
- UBL-TR XML, PDF, TIFF and JPEG scans, Excel, CSV, EDI
- Field extraction
- OCR with field-level confidence; human review below threshold
- Approvals and SLAs
- Delegation, escalation, four-eyes; business-calendar timers
- Audit log
- Append-only; every step, input, output and actor; exportable
Integrations
- SAP S/4HANA
- Microsoft Dynamics 365
- Logo Tiger
- Netsis
- Salesforce
- Microsoft 365 / Exchange
- IMAP / SMTP
- SFTP
- REST / SOAP
- PostgreSQL
- Microsoft SQL Server
- GİB e-Fatura / e-Arşiv
- MT940 / camt.053
Compliance & governance
- Designed to support GİB e-Fatura and e-Arşiv workflows run through your integrator, including UBL-TR validation and retention of issued and received documents.
- Designed to support KVKK and GDPR through field-level masking of personal data, role-based access, and configurable retention and deletion.
- Designed to support ISO/IEC 27001-style controls: segregation of duties, four-eyes approval and a tamper-evident audit trail.
- Designed to support internal-control and financial-audit requirements, with evidence for every automated and manual step.
Frequently asked questions
Frequently asked questions
01How is Relay different from RPA?
RPA imitates a person clicking through screens, and it breaks when a screen changes. Relay works through APIs, databases, files and message queues wherever they exist, and treats screen automation as a last resort for systems that offer nothing else. The result is fewer moving parts, and processes that can be tested like software.
02What happens if the ERP is down when Relay tries to post?
The step waits and retries with exponential backoff, and its idempotency key ensures a retry cannot create a second posting. If the outage outlasts the step’s retry limit, the item moves to a dead-letter queue and its owner is notified. Once the system is back, processing resumes from the same step.
03How accurate is document extraction, and who checks it?
Accuracy depends on document quality and layout variety, so we measure it on your own documents before go-live rather than quote a general figure. Every field carries a confidence score; anything below the threshold you set goes to a reviewer, and their corrections improve extraction. Documents received through e-Fatura are structured XML and need no OCR at all.
04Can our own team build and change workflows?
Yes. Analysts adjust flows, rules and approval routes in the designer, and developers add code steps and connectors. Changes pass through versioning, review and a test environment before production, and running instances finish on the version they started with.
05How does Relay handle e-Fatura and e-Arşiv?
Relay connects to GİB through your special integrator or your own direct integration, sends and receives UBL-TR documents, validates them and records the response to each. Incoming invoices enter the same matching and approval flow as any other document. Legal archiving stays with your integrator or your own archive, while Relay keeps document references and the full processing trail.
See VARDA Relay with your own data.
Orchestrates work across ERP, CRM, e-mail and GİB e-invoicing, reads documents with OCR, and routes exceptions to people with SLAs and a full audit trail.