You keep the system you already run. Every night we read it, check it against your own rules and your own history, and by six in the morning there is a short list of things worth your attention — each with the proof beside it. Nothing is decided without a person putting their name on it.
What our systems handle today
Most groups still run important operations through disconnected spreadsheets, email threads, messaging apps, PDFs and manual reporting. On Monday morning the close is in a spreadsheet, the approval is in a message thread, and the difference is found three weeks later by whoever has time.
This is the fragmentation the control layer replaces — without changing the system you already paid for.
Nothing about how your people work has to change: you keep your ERP, your licences and your accountant. We read what already exists, check it every night, and hand a named person a short list with the evidence beside each item.
The findings list is short, and each item carries its evidence. A named person accepts or refuses. The log keeps who and when — which is what an auditor asks for later.
Internal platforms that replace spreadsheets, email approvals and manual reporting with one controlled workflow layer — for companies whose operations run across many sites, teams and departments. We build around how the business already works, roll out site by site with training, and stay on afterwards as new processes are added.
Only the first level works on the first day. The second needs three months of clean history from your own sites, and the third is a proposal that a person still has to accept. We do not promise all three from day one, and we say plainly which is which.
Fixed thresholds and comparisons, set with you before go-live. Cheap to run, always the same answer, and explainable line by line to an auditor or a judge.
Today is compared with this site's own history, not with an industry average. It needs three months of clean data first, so it is scheduled for later and never promised at launch.
Reads invoices, contracts and the remarks your people write, and checks them before they go out. It proposes; it never decides — a named person accepts or refuses every item.
Every level writes to the same findings list, and the same person decides.
Very different industries ask for the same thing without knowing it: a control layer that reads the system they already run, checks it every night and puts a name against every difference. The core — access, audit trail, month lock, daily close, approval chain, findings list — is identical. Only the connector to your system and the checks your sector needs are built per client.
If your sector is not listed, the core still applies. The conversation starts with which system you run.
Start a conversationA market-leading multi-site retail group runs its key operational workflows through the platform Harrimont designed and deployed: 41 sites — 32 points of sale and 9 restaurants — more than 600 employees, 450 active B2B contracts and a ~€150M operating environment. Client named on request, under NDA.
Every site closed its day in Excel. Reports reached head office by email and phone, approvals left no record, and discrepancies in cash, documents and stock surfaced weeks after they happened — when nobody could reconstruct what had occurred.
One platform covering daily site reports, logistics, HR and finance. Every report passes through four control functions in a fixed sequence, with a complete audit trail, role-based access per department, and a defined route for returning a report to the site that filed it.
Rolled out across the network in four waves with training at every site. Management now reviews sales, stock and exceptions per site from a phone the same day. AI checks on delivery notes, supplier invoices and physical counts are being added on top.
The first question is always the same one.
Tell us which system you runOur systems read financial and operational documents — bank statements, invoices, delivery notes and stock counts. How that data is handled, and how each result can be proven later, is designed in from the first sprint rather than retrofitted before an inspection.
We read statements across multiple accounts and legal entities, consolidate them and match them against internal records. Every consolidated figure stays linked to the source line it came from, so a reconciliation can be reopened and defended months later.
Data-processing terms are agreed before any production access. Client data stays in the client's own infrastructure; our access is scoped by role and logged. Because our entity sits outside the EEA, transfers run on standard contractual clauses. Client data is not used to train models.
Transparency duties under Article 50 have applied since 2 August 2026. The high-risk regime for standalone Annex III systems now applies from 2 December 2027 under the Digital Omnibus. Systems touching HR, task allocation or performance monitoring fall in that scope, so we document them to those requirements today instead of rebuilding later.
AI flags, proposes and returns work. It does not approve. Every automated check is recorded with its input, its output and the time, and every decision carries the name of the person who made it — which is what an auditor, a tax inspector or a court actually asks for.
We build to these standards and document how we did it. We are not your legal, tax or audit adviser: responsibility for final compliance sign-off stays with the client and its own advisers.
We learn the departments, documents, approvals and reporting that already exist.
We map the manual work and bottlenecks, and name the processes to fix first.
We build a focused first version around the highest-impact workflow.
We test, train the people who will use it, and launch site by site.
We maintain and extend the system as new requirements appear.
Harrimont L.L.C. is registered in Kosovo and based in Prishtina, working internationally, with engagements run in English, German or Albanian.
Grant-aware, not grant authority. Eligible Luxembourg SMEs may be able to apply for available public support programmes for digitalisation projects, and we can structure a project scope clearly so that clients and their advisers can evaluate the fit. Harrimont does not grant funding and cannot guarantee eligibility, approval, reimbursable costs or reimbursement timing — these are determined by the competent authorities and the client's own situation.
No. You keep your ERP, your licences and your accountant. We read the export your system already produces — a PDF, an Excel file or an e-banking file — and we never write back to it. The only part built specifically for you is the connector to that system; the core is the same for every client.
The core is the same for every client; only the connector and the sector engine change. The sector engines on this page cover multi-site retail — convenience, grocery, fashion and textile — as well as automotive dealer groups, engineering and design offices, and banks and financial services. Our reference client runs its key operational workflows through the system, across 41 sites, more than 600 employees and 450 B2B contracts.
No. There are three levels: rules that work from day one, patterns that compare a site with its own history after ninety days of clean data, and reading of invoices, contracts and free text that proposes a finding. At every level a named person accepts or refuses, and the log records who and when. Automated checks can return a report to a site with the reason attached; they never approve it.
Data-processing terms are agreed before any production access. Client data stays in the client's own infrastructure; our access is scoped by role and logged, and transfers from our entity outside the EEA run on standard contractual clauses. Client data is not used to train models. Under the EU AI Act, transparency duties have applied since 2 August 2026 and the high-risk regime for standalone Annex III systems applies from 2 December 2027; systems touching HR, task allocation or performance monitoring are documented to those requirements today. Final compliance sign-off stays with the client and its own advisers.
It depends on the number of sites and the state of the existing data, so we do not quote a fixed duration. The engagement runs in five stages — discovery, systems audit, a focused first version, rollout site by site with training, then support — and the rule-based checks work from the first day a site is live. Pattern-based checks need ninety days of clean history from that site before they are switched on. Our reference client was rolled out across 41 sites in four waves.
Yes. Harrimont L.L.C. is registered in Kosovo and based in Prishtina, working internationally. Where a project involves personal data, production access starts only after the required data-processing and transfer terms are agreed.
The close that still happens in Excel, the approval that still happens in a message, the report that still arrives late. We will tell you what we would build first.
8GJ3J34H+CM, Fushë-Kosovë 12000, Kosovo
Harrimont L.L.C. is based in Kosovo and works internationally.
