xeeFlow – Powered by eABM
EN CZ
Book a demo
Solutions by use case

Start with one process. Expand once it pays for itself.

Every engagement begins with a single process that costs you real time. Below are the five we are asked for most often — each one configured in Xeelo, each one fed by data Integray already moves.

Contracts and corporate documents, approved and generated in one place

A requester fills one form. Xeelo decides the approval path from the values entered — amount, entity, contract type, counterparty risk — collects the signatures in the right order, then generates the final document from your template with placeholders replaced. No copy-paste into Word, no version confusion.

·Conditional paragraphs included or skipped by business rule
·Digital signatures via DigiSign, internal and counterparty
·QR or barcode stamped in for later OCR identification
·Approve from the browser, the mobile app, or straight from Outlook
REQUEST #CZ-2026-0418
CounterpartyDodavatel A s.r.o.
Contract value2 400 000 CZK
Path triggeredLegal → CFO → Board
TemplateFramework_v4.docx
Cycle time3.5 days → 9 hours

Onboard a vendor once, correctly, with the checks already done

The vendor request form validates the company ID against state registers through Integray before anyone approves anything — insolvency, VAT reliability, sanctions. Procurement, finance and compliance sign off in their own steps, and only then is the vendor created in the ERP, once, with a single identifier everyone uses.

·Live lookup against ARES, VAT and insolvency registers
·Duplicate detection before the record is ever created
·Periodic re-validation with automatic notifications on change
·Bank account changes treated as their own approval process
VENDOR ONBOARDING · CHECKS
Company ID in ARESMATCHED
VAT reliabilityRELIABLE
Insolvency registerCLEAR
Possible duplicate1 FOUND
Created in ERPON APPROVAL

One version of the truth, distributed rather than re-typed

Materials, cost centres, org units, price lists, customers — each with an owner, a validation rule and an approval path in Xeelo, then pushed by Integray to every system that consumes it. When something changes in one place, it changes everywhere, and the history explains why.

·Field-level access rights — users never see more than allowed
·Validation on entry, not clean-up projects afterwards
·Bulk imports run through the same rules as manual entry
·Full lineage: every value traceable to a request and an approver
MASTER RECORD · MATERIAL 4410-221
OwnerTechnical dept.
Consuming systemsERP · WMS · BI · e-shop
Last changeUnit of measure
Distributed4 of 4 systems
Duplicates removed1 812 records

A new hire has accounts, access and equipment on day one

One request from the hiring manager drives the whole sequence: HR approves, IT provisions the accounts through Integray, facilities assign the equipment, the manager confirms the training plan. Offboarding runs the same process in reverse, which is the part most companies never close properly.

·Accounts created in AD, Entra, e-mail and ERP automatically
·Access rights derived from position, not from memory
·Equipment handover protocols generated and signed on a tablet
·Offboarding checklist with evidence that every account was closed
ONBOARDING · DAY 0 CHECKLIST
HR approvalDONE
AD & mailbox provisionedDONE
Laptop & phone assignedDONE
Handover protocolAWAITING SIGNATURE
Manual steps remaining0

Reporting that agrees with itself, because the data arrives clean

Integray consolidates operational data from every source on a schedule or in real time, transforms it in SQL, Python or Node, and lands it in your warehouse or straight into Power BI. Because the master data is governed upstream in Xeelo, the dimensions actually match — and monitoring tells you before a report goes stale.

·Scheduled and event-driven loads in the same platform
·Real-time monitoring with notifications on failed runs
·Built-in debugger — no external tooling to prepare test data
·Analytical views and dashboards over integration throughput itself
PIPELINE MONITOR · LAST 24H
Runs completed12 480
Records processed4.1 M
Median latency280 ms
Failed, auto-retried6
Manual interventions1
Your process isn't on this list?
It almost certainly still fits. Tell us how it runs today.
Book a demo