Data moves on its own.

From input to result

• Inputs: Email with attachment, Web form, CSV / XML export, External system API
• Application core: Field mapping, Validation, Error handling, Transfer log
• Results: Record in the target system, File in an agreed format, Error notification

When it makes sense

• The same data gets manually retyped between two systems.
• Someone manually prepares the same file every week.
• Errors occur during retyping, not in the work itself.
• A report is always out of date because data isn't in one place.

What the first scope includes

• Mapping both sides: what the source provides, what the target expects
• Field and code mapping with agreed rules
• One connection in production, scheduled or real time
• Error handling: what gets rejected and who is notified
• A transfer log showing successful and rejected records
• Short documentation of the connection for your records

What integration is, and what it isn't

Integration is an agreed path along which data moves from one system into another, in the right form, at the right time, with a trail of what happened. It's not a one off export and not a macro running on one computer for as long as it stays switched on.

The key part isn't the transfer itself, but the mapping and error handling. Every system has its own codes, its own required field and its own idea of a date format. An integration has to know what to do when it can't place a record: stop the transfer, set the record aside, or notify a person.

That's why every connection I build has a transfer log. You can see how many records went through, which were rejected and why. Without that, an integration is a black box no one trusts.

Common paths

In practice the paths are surprisingly repeatable, regardless of industry.

• An order from email or a form into an internal register
• Data from an online store into a stock or dispatch register
• Preparing a structured file for accounting or a bank
• Synchronising a customer list between two systems
• Regular data export for reporting and analytics

Two typical scopes

The smaller scope is a single tool: converting payment or sales data into a format the receiving system accepts without manual correction. A small tool, but it removes a repeating step that's a source of errors.

The larger scope is a connected flow from incoming data, through rules and processing, to output into another system. Both cases share the same core, a clearly defined input, rules in the middle, and a verifiable output.

What can technically be connected

Connectivity depends on what a system offers. Where an API exists, the connection is direct and real time. Where only an export exists, it works with files in an agreed format on a schedule. Where neither exists, the honest conclusion is that integration doesn't make sense.

For Slovenian companies the most common technical candidates are Microsoft 365 and SharePoint, accounting solutions such as Minimax, Pantheon and SAOP, and business systems of the Business Central type. I list these as possible connections, not as already delivered projects, I check the feasibility of each one against your licence, version and access before giving an estimate.

How it works

• We clarify the process: I check what both systems actually offer and what is technically feasible.
• Clickable prototype: A trial transfer on a data sample, with a review of rejections.
• Working first version: The connection in production, with a log and error notifications.
• Handover: Documentation, access and an agreement on monitoring.

Frequently asked questions

• Can our accounting software be connected? It depends on what your version offers. If it has an API or a structured export, generally yes. I check this before giving an estimate.
• What if the external system changes its interface? That's exactly why every connection has a log and error notifications. The change is noticed immediately, not at month end close.
• How much does one integration cost? A simple connection falls below the MVP threshold and is estimated separately. A connection that's part of a new application is covered within the scope from EUR 2,500 upwards.
• Do we need a new application for this? Not necessarily. Often a connection between existing systems is enough.