Skip to content
dvnt.io

ERP · CRM · KSEF · PAYMENTS

System integration

Orders, invoices, contacts and stock levels retyped by hand between systems cost hours every week and errors at month-end. We connect ERP, CRM, KSeF, online shops, calendars and public APIs so data flows without spreadsheets.

ERP · CRM · KSeF · public APIs · Google and Microsoft 365

Source of truth

1 → N

one version of the data, many systems, no retyping

WHEN TO INTEGRATE · FOUR SIGNALS

When connecting systems is enough, and when you need a new one

Usually the problem is not the tool itself, but the fact that a person carries data between tools.

  • RETYPING

    You enter the same data in two places

    An order from the shop retyped into the ERP, a contact from a form into the CRM, an invoice from accounting into a spreadsheet. Every retyping costs minutes and invites mistakes.

  • EXPORTS

    Reports are built from spreadsheet exports

    Every week someone pulls data from several systems and stitches it together by hand. An integration does the same automatically, with no typos and no waiting for the one person who knows how.

  • MISMATCH

    Your systems show different numbers

    Stock in the shop does not match the ERP, the customer status in the CRM does not match the invoices. The gap only shows up at month-end close or with a complaint.

  • DECISION

    Connect instead of replace

    If your current tools do their job well and the only problem is how data moves between them, connecting them costs less than replacing them. A new system makes sense only once the tool itself no longer fits the way you work.

// WHAT WE INTEGRATE · SIX AREAS

What we connect

Each area has its own section with examples below.

  • ERP AND CRM

    ERP, CRM, online shop, customer portal

    Orders, invoices, stock levels and contacts between the systems you already have.

  • KSEF

    Poland's national e-invoicing system (KSeF)

    Purchase and sales invoices straight into your system, with no file downloads.

  • PUBLIC APIS

    BZP, TED, CEIDG

    Public registers and tender databases as a data stream, not a website to browse.

  • GOOGLE AND MICROSOFT

    Calendars and email

    Google and Microsoft 365 calendars in both directions, a mailbox connected to the CRM.

  • MEASUREMENT AND ADS

    Tracking and Google Ads

    Your own tag server, offline conversions, GA4 and Search Console data in your reports.

  • PAYMENTS

    Stripe and invoices

    Subscriptions, payments and VAT invoices issued automatically, including in KSeF.

KSEF · NATIONAL E-INVOICING SYSTEM

KSeF integration

Since 2026, invoices in Poland go through the national e-invoicing system (KSeF). Integration means invoices land in your system on their own — no logging in to KSeF, downloading files or retyping.

  • PERMISSIONS

    Permissions instead of certificates

    In the Domyko portal, the accounting firm holds a single credential and each client grants it the right to read invoices in KSeF. The sync switches to the client's tax ID, with no collecting certificates from dozens of companies.

  • SECURITY

    Keys encrypted separately for each firm

    KSeF credentials are encrypted with AES-256-GCM, using a separate key for each accounting firm. A leak of one key does not open anyone else's data.

  • INVOICE NOTES

    Invoices described before they reach the accountant

    Clients annotate purchase invoices pulled from KSeF in the portal (category, notes), and the accounting firm receives them ready to book and export.

  • PITFALLS

    Details that are easy to trip over

    A KSeF export window must end in the past, otherwise the package comes back empty. Things like this only surface in a real integration, not in the documentation.

ERP AND CRM · THREE STEPS

ERP and CRM integration

Orders, invoices, stock levels and contacts flow between ERP, CRM, online shop and customer portal without spreadsheet exports.

  • STEP 01

    We check what the ERP exposes

    An API, file exports, database access or the vendor's middleware. This decides whether the sync can run in real time or in cycles, e.g. every hour.

  • STEP 02

    We set the source of truth for each piece of data

    Which system decides the price, which the stock level, which the customer data. Without this, two systems overwrite each other and the error only shows up at month-end close.

  • STEP 03

    Sync with monitoring

    Every connection has an alert for when the other side starts returning something different from yesterday — before accounting or a customer notices.

  • EXAMPLE

    Leads from email and forms in the CRM

    Enquiries from forms and the mailbox land in the CRM automatically, and the ones that turn out to be real enquiries go back to Google Ads as offline conversions — campaigns learn from leads, not clicks.

PUBLIC APIS · NO CONTRACT, NO GUARANTEE

Public APIs: BZP, TED, CEIDG

Public-sector APIs come with no contract or SLA and can change their response format without warning. We treat each one separately: server-side filtering where possible, our own filter where the server returns too much, rate limits with retries.

  • RADAR PRZETARGÓW

    Three registers in one stream of notices

    Radar Przetargów (tender radar) pulls from BZP (Polish public procurement bulletin), TED (EU tenders) and Baza Konkurencyjności (Polish grant-funded procurement database) — and each of these sources is broken in its own way. BZP filters CPV codes on its side, TED returns whole code families, and Baza Konkurencyjności does not even expose the list of notices without a token.

    In a measured 72-hour window: 71 notices, 6 of them relevant — the rest filtered out automatically. The radar runs on its own: every hour it fetches new notices and sends the relevant ones to Discord and in a daily email digest. The next version will add AI-based relevance scoring.

  • CEIDG

    Company data from the CEIDG API v3

    An aggregator that fetches, processes and visualises data from CEIDG (Poland's register of sole traders): search across all tables, an overview of PKD activity codes, statistics.

    API limits are handled by adaptive request throttling, and incremental mode fetches only new and changed entries — without downloading the whole database every time.

GOOGLE WORKSPACE AND MICROSOFT 365

Calendars and email: Google and Microsoft 365

More and more companies run both ecosystems at once: the team on Google, the client on Microsoft 365 — and double bookings in the calendar.

  • CALSYNC

    Two-way calendar sync

    The copy of a meeting on the other side is an empty “busy” block — no attendees, links or title. One goal: never have two meetings at the same time.

    No database and no webhooks: the whole state is rebuilt on every run from the events themselves, so moving to another server duplicates nothing. Open source under the MIT licence.

  • EMAIL

    A mailbox connected to the CRM

    Messages from the company mailbox land in the contact's history in the CRM through Microsoft Graph — no copying emails or searching mailboxes.

MEASUREMENT AND ADS

Server-side tracking and advertising APIs

Conversion data that does not depend on how many tags the browser blocks.

  • GTM SERVER

    A dedicated tag server for six domains

    Measurement runs on the server, so conversion data depends less on browser blocking than client-side tags do.

  • GOOGLE ADS

    Offline conversions and reports without exports

    Offline conversion import into Google Ads, GA4 and Search Console data straight into reports — no downloading files by hand.

// HOW WE WORK · FOUR STAGES

How we work on an integration

An integration also costs money to maintain: any external API can change. That is why monitoring is part of the project, not an add-on.

  • 01

    Data map

    We write down which data goes from which system to which, and how often. At this stage it often turns out that some connections are unnecessary.

  • 02

    Source of truth

    For each piece of data, one system decides. This prevents overwrites and mismatches.

  • 03

    Sync

    In real time or in cycles, depending on what the other side allows. With retries on errors and rate limits.

  • 04

    Monitoring and alerts

    When the other side starts returning something different from yesterday, we find out before you do.

PRICING

How much system integration costs

The price depends on the number of systems, the quality of their APIs and whether data flows one way or both ways.

  • ONE CONNECTION

    A simple one-way integration

    We quote after a short call, once we know which data and from which system.

  • SEVERAL SYSTEMS

    Two-way integration of several systems

    We quote after the analysis (discovery): data map, sources of truth, API quality. The final price stays within ±15% after that stage.

  • MAINTENANCE

    Support after launch

    Monitoring, updates after changes in external APIs, support — as part of ongoing technical support (PLN 450–800 / month, depending on scale).

FAQ

Questions about system integration

Will you integrate with our ERP?

Yes. We start by checking what the ERP exposes: an API, file exports, database access or the vendor's middleware. This decides whether the sync can run in real time or in cycles, e.g. every hour.

We also agree which system is the source of truth for each piece of data — so the ERP and the new application do not overwrite each other.

Is KSeF integration mandatory?

Using KSeF has been mandatory since 2026, with deadlines depending on company size. Integrating your own system with KSeF is not mandatory — you can issue and download invoices by hand in the Ministry of Finance application.

Integration makes sense when there are many invoices or they go to several systems: it saves logging in, downloading files and retyping.

What happens when an external API changes?

Every connection has monitoring and an alert. When the other side changes its format or starts returning errors, we learn about it from the alert, not from your accounting team. Fixes after such changes are part of ongoing technical support.

Will you take over an integration you did not build?

Yes, starting with a review: code, documentation, access, how errors are detected today. After the review you get a list of risks and a recommendation: we maintain it, improve it in stages or rewrite a part.

Do we have to replace our current systems?

Usually not — and that is the main advantage of integration. If the tools do their job well, we connect them. We recommend replacing a system only when it does not expose its data or no longer fits the way you work.

RESOURCES · BEFORE WE TALK

Before we talk

// Next step

Describe your project. We reply within 24 h.

A few sentences are enough: what should work, what it connects to and by when. No brief, no commitment.

What happens next

  1. We read your message and reply within one working day.
  2. We set up a short call about the scope, with no sales pitch.
  3. You get proposed stages and a price range.
Meeting date (optional)

Time

CET

Checking free times…

Budget (net)

By sending this form, you accept the Privacy Policy.