Skip to content
R&D COPILOT / Integrations EU hosting · Made in EU
RO Scope an integration
// 00 INTEGRATIONS

Make your systems work together.

We scope, build and run integrations between RDCopilot apps, Microsoft 365, automation tools and any REST API. Every run has retries, an owner and a log you can read. After go-live we host, monitor and update it. If you prefer to run it in-house, we hand it over with runbooks.

Scope an integration Run the example sync
  • Scoped API integrations
  • Reliable handoffs and retries
  • Monitoring and reconciliation

One-off setup + monthly licence · EU hosting · Support in English

Your tools runs where you host it
EU when hosted by RDCopilot
RDCopilot apps
Example topology. The actual map, and where each part runs, is agreed for each project.
// 01 HOW A RUN WORKS

The happy path is half the design.

Before anything goes live we agree what happens when data is missing, a system is down or a person has to decide. Scroll through one run, captured from the console further down.

  1. 01 Trigger · validate

    A business event starts the run, and every field is checked.

    An opportunity is qualified, an invoice arrives, a receipt is confirmed. The run validates and maps the record against the data contract, and each step writes a plain line to the log.

    Data error: the owner corrects the source, then the run replays.

    Example data: a completed invoice-to-accounting run, with the run log and the accounting handoff in the step inspector.
    Open full size
  2. 02 Approval gate

    A named person decides before money or stock moves.

    The run waits at the gate with the payload in view. Approve and it continues; nobody answers and it escalates on the agreed route. The decision stays in the audit trail.

    Example data: a lead-to-order run paused at finance approval, with the run log and step inspector.
    Open full size
  3. 03 Action · retry

    The destination times out. The retry creates no duplicate.

    Temporary failures retry with exponential backoff. Each attempt carries the same idempotency key, so the second try completes the same order instead of writing a second one, where the destination accepts the key.

    After the last attempt: dead-letter queue, and the owner is alerted.

    Example data: a run whose destination timed out, retried with the same idempotency key and completed on the second attempt with no duplicate record.
    Open full size
  4. 04 Confirm · reconcile

    Counts are compared, so nothing is stranded in between.

    Source and destination are reconciled on the schedule in the data contract. A record stuck between systems shows up with its owner, and alerts name the flow, the queue and the reason.

    Example data: RDCopilot Integrations monitoring with today’s runs, an error-queue alert with its owner and a CRM-to-ERP reconciliation showing one record waiting approval.
    Open full size
Example data: a completed invoice-to-accounting run, with the run log and the accounting handoff in the step inspector.
Example data: a lead-to-order run paused at finance approval, with the run log and step inspector.
Example data: a run whose destination timed out, retried with the same idempotency key and completed on the second attempt with no duplicate record.
Example data: RDCopilot Integrations monitoring with today’s runs, an error-queue alert with its owner and a CRM-to-ERP reconciliation showing one record waiting approval.

Example data · captured from the interactive console on this page

  1. 01

    Idempotent writes

    Each record carries a key, so a retry updates the same order and does not create a second one, where the destination accepts the key.

  2. 02

    Retries with exponential backoff

    In integrations we run, temporary failures retry with exponential backoff and jitter; after the last attempt the run moves to the dead-letter queue and the owner is alerted.

  3. 03

    Approval gates

    A run can wait for a named person, with an escalation route and a record of the decision.

  4. 04

    Replay after correction

    In integrations we run, you fix the source record and the run replays from the failed step.

  5. 05

    Reconciliation

    Counts and totals are compared between source and destination on the schedule set in the data contract, so a stranded record is found and owned.

GUIDES Keep retries from creating duplicate business records Who notices when an integration stops halfway?
// 02 CONSOLE

Run a sync. Read what happened.

Pick a scenario, change the conditions and press Run. Each step writes a plain line to the log, including pauses, failures and retries.

sync · lead-to-order Example data · interactive · runs in your browser
Scenario
run.logReady to run
  1. · INFOrunready · press Run sync to start
inspectorReceive
INPUT
{}
OUTPUT
Waiting for this step.
Session runs
RunScenarioResultStepsRetriesDuration
No runs yet. Press Run sync.
// 03 CONNECTORS

Connect what you already use, grouped by the work it does.

Each connection is scoped for your project: which events, which fields, which direction and who owns it. Event names below are examples; the data contract is agreed with you.

  • crm both

    CRM

    Opportunities, contacts and activities.

    Example events
    • opportunity.qualified
    • contact.updated
    Product page Sell & serve
  • pos out

    POS

    Closed sales and end-of-day totals.

    Example events
    • sale.closed
    • day.closed
    Product page Sell & serve
  • erp both

    ERP

    Orders, invoices and master data.

    Example events
    • sales_order.created
    • invoice.issued
    Product page Operations
  • inventory both

    Inventory

    Stock levels and reorder signals.

    Example events
    • stock.below_reorder
    • item.updated
    Product page Operations
  • warehouse both

    Warehouse

    Receipts, picks and shipments.

    Example events
    • receipt.confirmed
    • shipment.dispatched
    Product page Operations
  • accounting in

    Accounting

    Journal entries and documents to post.

    Example events
    • entry.posted
    • document.received
    Product page Finance
  • banking out

    Banking

    Statements and matched transactions.

    Example events
    • statement.imported
    • transaction.matched
    Product page Finance
  • reports in

    Reports

    Datasets for dashboards.

    Example events
    • dataset.refreshed
    Product page Finance
  • hr out

    HR

    Hires, changes and leavers.

    Example events
    • employee.hired
    • employee.updated
    Product page People
  • payroll both

    Payroll

    Approved payroll runs.

    Example events
    • payroll.approved
    Product page People
  • reges in

    REGES

    Contracts and contract changes for REGES-ONLINE.

    Example events
    • contract.change_ready
    Product page People
  • efactura both

    e‑Factura

    ERP invoices sent to the RDCopilot e‑Factura app, with the RO e‑Factura state and ANAF’s response brought back.

    Example events
    • invoice.uploaded
    • invoice.validated
    • invoice.rejected
    Product page Localisation & compliance
  • etransport both

    e‑Transport

    e‑Transport notifications and their UIT codes, through the RDCopilot e‑Transport app.

    Example events
    • uit.issued
    Product page Localisation & compliance
  • etva out

    e‑TVA

    Pre-filled RO e‑TVA return compared with your D300 VAT return, through the RDCopilot e‑TVA app.

    Example events
    • comparison.ready
    Product page Localisation & compliance
  • declarations in

    Declarations

    Data for D100, D101, D300, D390, D394 and D406 (SAF-T).

    Example events
    • declaration.ready
    Product page Localisation & compliance
  • m365 both

    Microsoft 365 / Power Automate

    Approvals, mail and files in your Microsoft environment.

    Example events
    • approval.completed
    Runs in your environment Your tools & runtimes
  • uipath both

    UiPath

    Desktop and legacy screens with human validation.

    Example events
    • job.completed
    • task.validated
    Runs in your environment Your tools & runtimes
  • ai in

    RDCopilot AI

    Document and text steps with a person in the loop.

    Example events
    • extraction.ready
    Product page Your tools & runtimes
  • rest both

    REST API

    Any documented HTTP API.

    Example events
    • GET/POST per contract
    Runs in your environment Custom APIs
  • webhook in

    Webhook

    Events pushed by your systems, verified by HMAC signature and timestamp where the sender supports it, and de-duplicated by event ID.

    Example events
    • POST /hooks/{source}
    Runs in your environment Custom APIs

Don’t see your system? If it has an API, a webhook, a file export or a stable screen, we can scope it. Tell us about it

Need documents read before they move? See Document workflows and Private AI workspace.

// 04 RECIPES

Start from the process, not the app list.

  • integrationapproval

    Lead to order

    crm → erp
    Trigger
    Opportunity marked qualified
    On failure
    Missing data returns to sales; ERP timeouts retry with the same key
    Owner
    Sales operations
  • integrationRO localisation

    Order to invoice

    erp → e-factura → accounting
    Trigger
    Order delivered
    On failure
    A rejected e-invoice returns to the issuer with ANAF’s error message, ready to correct and resend
    Owner
    Finance
  • automation

    Statement to reconciliation

    banking → accounting
    Trigger
    Statement imported
    On failure
    Unmatched lines wait in a review list
    Owner
    Finance
  • integration

    Receipt to stock

    warehouse → inventory
    Trigger
    Receipt confirmed
    On failure
    Quantity differences pause the update
    Owner
    Operations
  • approvalRO localisation

    Hire to payroll

    hr → payroll → reges
    Trigger
    Employee record approved
    On failure
    Missing contract data blocks the REGES-ONLINE submission, due no later than the day before work starts
    Owner
    HR
  • approval

    Invoice to accounting

    inbox → validate → accounting
    Trigger
    Supplier invoice received
    On failure
    Missing reference goes back to operations
    Owner
    Finance
  • approval

    Expense approval in Microsoft 365

    power automate → erp
    Trigger
    Expense request submitted
    On failure
    Expired approvals escalate to the agreed reviewer
    Owner
    Process owner
  • automation

    Legacy screen to record

    uipath → erp
    Trigger
    Scheduled batch or request
    On failure
    Screen changes stop the robot and alert IT
    Owner
    IT
  • integration

    Close to dashboard

    accounting → reports
    Trigger
    Period closed
    On failure
    A stale dataset is flagged on the dashboard
    Owner
    Controlling
// 05 MONITORING

Know a run failed before your team does.

Every run is logged step by step with record IDs, result codes and the owner, and failures alert the person who can fix them. What else is logged, and for how long, is set in the data contract. We watch those alerts for you; if your team runs the integration, it gets them with runbooks.

runs · todayExample data
Run history, example data
Run IDFlowStartedDurationStepsStatusOwner
run-7f3a lead-to-order 09:41 9.5 s 5/5 Completed Sales ops
run-7f39 order-to-invoice 09:38 3.1 s 4/4 Completed Finance
run-7f37 statement-to-reconciliation 09:30 12.4 s 3/4 Waiting review Finance
run-7f35 receipt-to-stock 09:12 1.2 s 1/3 Failed · retry 3/3 Operations
alertsExample data
Error queuereceipt-to-stock

“Quantity on receipt R-2210 differs from order (40 vs 42)”

runs
1
owner
Operations
attempts
3/3

actions: open run · replay

An alert names the flow, the queue, the owner and the reason, with the run one click away.
reconcile · crm ⇄ erpExample data
Source · CRM
128
qualified
Destination · ERP
127
orders
Difference
1
Q-1037 · waiting approval
Counts are compared between source and destination, so a record stuck in between is found and owned.
// 06 SECURITY

Every connection has an owner, a scope and a trail.

Your systems & tools
  • Microsoft 365
  • Power Automate
  • UiPath
  • REST APIs · webhooks
Integration layer
  • Credentials per connection
  • Retries & dead-letter queue
  • Run & audit log
  • Alerts to owners
RDCopilot apps
  • CRM · ERP
  • Accounting · Banking
  • Inventory · Warehouse
  • e‑Factura · e‑Transport · e‑TVA
  • HR · Payroll · REGES
Your hosting · Microsoft 365, UiPath, your own servers EU hosting · parts hosted by RDCopilot
Data enters and leaves the integration layer through defined ports. Where each part is hosted is stated, not assumed.
  • 01

    Least-privilege credentials

    Each connection has its own credentials, limited to the objects and actions it needs and agreed in the data contract. In your own Microsoft 365, UiPath or other automation tools they stay in that tool’s credential store.

  • 02

    A named owner

    Every connection and every exception type has a named owner, agreed in the data contract.

  • 03

    Audit trail

    Mapping changes, approvals and replays are recorded with who and when.

  • 04

    Only the fields you agree

    The data contract lists every field that moves, and nothing else is copied (data minimisation, GDPR Art. 5).

  • 05

    Clear hosting

    Integrations RDCopilot hosts run on EU infrastructure; flows that run inside your Microsoft 365, UiPath or other self-hosted tools stay where those tools are hosted, and we record that in the data contract. Log retention is set in the data contract.

  • 06

    Change control

    Mappings are versioned and tested against failure cases before release.

// 07 ENGAGEMENT

One process first. Then the next.

  1. STEP 01

    Map one costly handoff

    We sit with the people who re-key the data and measure where it gets stuck.

    You get process map and a shortlist of what to connect first

  2. STEP 02

    Agree the data contract

    Fields, directions, rules, approvals, owners, where each part runs and what counts as done.

    You get a signed-off contract and acceptance tests

  3. STEP 03

    Build and test failure

    We build one controlled path and test rejection, missing data, timeouts and replay.

    You get a working integration in a test environment

  4. STEP 04

    Go live: we run it

    We host, monitor and update it under the monthly licence, or hand it over to your team with runbooks and alerts.

    You get run history, alerts and runbooks

lead-to-order · data contract v1Example data
Example data contract for the lead-to-order integration
FieldDirectionOwnerRuleOn failure
opportunity_idcrm → erpSales opsrequired, uniquereturn to sales
customer_refcrm → erpFinancemust exist in ERPpause, alert owner
total + currencycrm → erpFinanceapproval requiredwait for approver
erp_ordererp → crmSystem ownerwritten back onceretry 3×, same key
hosting: RDCopilot EU · log retention: set in the data contractChoose the first API integration by the manual work it removes
Where your flow runs

RDCopilot connects to the tools you already run.

query

Flows that use Power Automate premium connectors need a Power Automate Premium licence from Microsoft; UiPath robots are licensed by UiPath. We list them separately in the quote. Flows on those tools run where the tool is hosted.

how we connect it

RDCopilot Integrations + Power Automate

Approval flows stay in your Microsoft environment. We connect them to RDCopilot apps and agree connector permissions, environment policies and licence requirements.

Documentation for the tools you connect UiPath Action Center Power Automate approvals
// 08 PRICING

Two parts. Quoted after scoping.

We give a fixed quote once we know the process, the systems and the volumes. No per-run or per-task charges.

01 · once

One-off setup

  • Process mapping
  • Data contract
  • Build
  • Failure testing
  • Go-live with runbooks
02 · monthly

Monthly licence

  • Hosting for the parts RDCopilot runs
  • Monitoring and alerts
  • Updates
  • Support

When a connected API changes, we tell you and estimate any adaptation at the hourly rate. New flows, fields or systems are estimated the same way before we start.

What changes the quote

  • Number of systems
  • Events per day
  • Approval steps
  • Desktop (UiPath) automation
  • Whether your team runs it in-house
  • Third-party licences
Get a scoped quote
Included in bothEU hostingUpdatesSupport in English

Included in every RDCopilot integration

  • Field mapping agreed in a written data contract
  • Rejection, missing data, timeouts and replay tested before go-live
  • Idempotency key (where the destination accepts it) and retry schedule designed in
  • Run log, alerts and reconciliation
  • Monitoring, with notice when a connected API changes
  • One-off setup + fixed monthly licence

Already run flows in Power Automate, UiPath or another automation tool? RDCopilot Integrations connects to them, so they keep running where they are.

From idea to implementation

Guides for your workflow

// 09 FAQ

Questions we get before scoping.

Is this a self-service automation platform?

No. We scope and build each integration with you and test how it fails. After go-live we host, monitor and update it under the monthly licence. If you prefer to run it in-house, we hand it over with runbooks and alerts.

Which systems can you connect?

All RDCopilot apps, Microsoft 365 and Power Automate, UiPath, workflow tools you host yourself, and any system with a documented REST API or webhooks. Systems with only file exports or desktop screens are assessed case by case.

Do we have to use other RDCopilot apps?

No. An integration can link two of your existing systems. RDCopilot apps connect with less setup because we already know their data.

What happens when a system is down?

The run retries with exponential backoff. After a timeout it first checks whether the destination already received the record, using the same idempotency key, so a retry does not create a duplicate. The data contract lists which destinations support this. After the last attempt the run moves to the dead-letter queue and the owner gets an alert.

Where is our data processed and stored?

Integrations RDCopilot hosts run on EU infrastructure; flows that run inside your Microsoft 365, UiPath or other self-hosted tools stay where those tools are hosted, and we record that in the data contract. Only the fields listed in the contract move between systems, and log retention is set in the data contract.

Do you sign a data processing agreement?

Yes. Where an integration processes personal data for you, RDCopilot acts as processor under a data processing agreement (GDPR Art. 28), and the data contract lists the fields, systems and retention.

Can a person approve before data moves?

Yes. Any step can wait for a named approver, with an escalation route if nobody answers, and the decision is kept in the audit trail.

Romanian e-invoicing (localisation): how does it connect?

For companies operating in Romania, e‑Factura, e‑Transport and e‑TVA run through the RDCopilot localisation apps, authorised with the company’s qualified digital certificate (ANAF OAuth). Your ERP sends the invoice to the app, and its ANAF state comes back to your ERP and accounting: the signed response when it is accepted, or ANAF’s error message when it is rejected. The status view shows which invoices are not uploaded yet (the law gives 5 working days from issue) and when the certificate access is due for renewal, at least once a year.

How is it priced?

A one-off setup fee and a monthly licence, quoted after we scope the process. The licence is a fixed monthly amount, with no per-run charges. Third-party licences such as Power Automate Premium or UiPath, if needed, are listed separately.

// NEXT

Which handoff keeps coming back to your desk?

Tell us the process, the systems involved and where it gets stuck. We reply with a scoping proposal.

Scope an integration See pricing

© 2026 R&D COPILOT Made in EU Contact form