Intranet Portal Fully Integrated With Mikro

You already run Mikro Fly, Mikro Jump or Mikro Run; we open up your corporate internal processes on top of it. The intranet portal runs on top of Mikro, and Mikro remains the single source of truth. It reads personnel, account, stock and cost centre data from Mikro and writes back only approved results. Digitise your leave, approval, expense, time-and-attendance and field processes in a single dashboard. There are no setup fees, licence fees, per-user charges or maintenance costs; it is a subscription model.

Integration Ready

An internal process layer built on top of Mikro

You are already running Mikro; we open up on top of it the internal processes that Mikro does not offer, or that are expensive to customise. The portal pulls master data (personnel/HR records, cost centres, accounts, stock, e-invoice status) read-only, and writes only approved results back to Mikro. Mikro remains the single source of truth (SSOT); subscription-based, zero capex.

SQL Server access Mikro Web Service/API Read-only reads Approved write-back

How We Connect to Mikro

Direct SQL Server database access

We connect directly to the tables in Mikro's SQL Server database. Personnel, accounts, stock cards, cost centres and e-invoice status are read via secure, read-only queries. It runs on the local network or over VPN, without touching Mikro's existing data model.

Mikro Web Service / API layer

To write approved results, we use Mikro's web service/API layer. Expense totals, payment orders, timesheets and purchase requests are passed to Mikro in a controlled manner. This way, write operations are safeguarded by Mikro's own business rules and validations.

Scope analysis before scaling

Before go-live, we clarify your Mikro edition (Fly / Jump / Run), your table structure and field mappings together. Which data will be read, which results will be written back and the approval flows are all determined in a demo session; a measurable integration with no surprises is established.

What Syncs With Mikro

Personnel and HR records

Personnel cards, department, title and HR details are pulled read-only from Mikro. Leave, time-and-attendance and expense processes run on the current headcount; duplicate data entry is eliminated.

Cost centres and approved expense totals

Cost centre definitions are read from Mikro; expense totals approved in the portal are written back to the correct centre. Accounting entries remain consistent in Mikro.

Accounts

Customer and supplier account cards are read from Mikro. Field, quotation and request processes run on the current account list; incorrect account selection is prevented.

Stock cards and status

Stock cards and current status are pulled read-only from Mikro. Purchase requests and field requests are created against the correct stock items.

E-invoice status

E-invoice liability status by account and document is read from Mikro. The correct invoice type is determined up front in approval and purchasing flows.

Approved payment orders and purchase requests

Payment orders and purchase requests approved in the portal are written back to Mikro. The approval chain lives in the portal, the record in Mikro; the single source of truth is preserved.

Timesheets and overtime records

Time-and-attendance and timesheet results are collected in the portal and, once approved, written back to Mikro as timesheets. Pre-payroll reconciliation is accelerated.

Intranet Modules on Top

Every internal process, on top of your ERP — each with its own detail page.

Ready for Mikro integration

The intranet portal is ready for integration via Mikro's SQL Server database and web service/API layer. It is designed to read personnel, account, stock, cost centre and e-invoice data across the Fly, Jump and Run editions, and to write approved results back. Let's schedule a demo session to clarify the scope specific to your organisation's Mikro configuration, and define the field mappings and approval flows together.

How It Works

01

Connect

We connect to your ERP via its API credentials or database access. No data leaves your environment without your consent.

02

Map

We map personnel, cost-centre, invoice, account and stock fields — defining what syncs, in which direction and on which schedule.

03

Go Live

We test end-to-end with your real data, then go live. Sync reliability is monitored and error cases are handled automatically.

Frequently Asked Questions

We are ready to integrate with Mikro Fly, Mikro Jump and Mikro Run. The connection is established via Mikro's SQL Server database and web service/API layer. In the demo session, we clarify the scope according to your edition and table structure.
No. The portal pulls master data (personnel, accounts, stock, cost centres, e-invoice) read-only. Only results approved in the portal (expense totals, payment orders, timesheets, purchase requests) are written back to Mikro. Mikro remains the single source of truth.
For reading, we connect to Mikro's SQL Server database via secure, read-only queries; for writing, to Mikro's web service/API layer. It runs on the local network or over VPN. It is deployed without interfering with Mikro's existing installation.
No. The portal is subscription-based. There are no man-day setup fees, licence fees, per-user charges, maintenance or hosting costs. You start with zero capex.
Mikro is a powerful ERP, but it does not cover internal processes such as leave, approvals, expenses, time-and-attendance, maintenance, field work and requests, or these are expensive to customise. The portal digitises these processes on top of Mikro and writes the results back to Mikro. It doesn't replace your ERP, it complements it.

Open Your Internal Processes on Top of Mikro

Book a 30-minute demo. Tell us your Mikro setup — we’ll scope the integration and your first modules together.

Book a Demo →