Skip to main content
Intranet Portal
Corporate intranet portal · By subscription

Your ERP keeps the record. Who runs the process?

Logo, Mikro, SAP, Netsis, Uyumsoft — your ERP keeps stock, invoices and payroll correct. But leave, approvals, expenses, procurement, maintenance, field work and asset handovers still run on spreadsheets, WhatsApp and email. Intranet Portal fills that gap: it sits on top of your ERP and leaves it as the single source of truth.

  • 10+ portal projects in production
  • 5,000+ employees on one portal
  • 17 ready modules
LVE-2026-0418 Annual Leave Request
Requested by
M. Aydın · Production Planning
Dates
13–17 April · 5 working days
Balance
14 days → 9 days
Timesheet
Posted on approval
  1. Request M. Aydın 09:12
  2. Supervisor H. Demir 10:04
  3. Manager S. Korkmaz 13:27
  4. HR E. Şahin 15:53
How it works today

The process doesn't live in a system. It lives between people.

These three show up in almost every company that runs an ERP. The problem isn't careless staff; it's that the process has nowhere to live.

leave_tracker_2026_FINAL_v3_updated_REV.xlsx

Three people hold three different copies. Nobody knows which one is current, and the balances don't match payroll.
Did you manage to approve my advance request?
Which request? It never reached me — ask Ayşe
The approval was given in a message. Who approved it, when, under what authority — no record, no audit trail.
  1. Subject: FW: FW: RE: FW: Maintenance request — line 2
  2. → procurement@
  3. → technical@
  4. → finance@
  5. → gm@ (no reply for 6 days)
Where in the chain did it stall? Finding out means reading the whole inbox from the beginning.

None of this is the ERP's fault. An ERP is built to keep the record, not to run the process. That is why customising an ERP around leave, approval and expense flows becomes a separate project every time — a separate day-rate invoice, and a cost paid again at every upgrade.

Approach

We don't replace your ERP. We build on top of it.

Intranet Portal does not take your ERP's place. It runs alongside and above it: reads from the ERP, writes the approved result back. The single source of truth stays in the ERP — you never end up with two versions of the truth.

Single source of truth

Your ERP

  • Employees, payroll and leave balances
  • Accounts, stock, orders, invoices
  • Accounting entries and financial statements
  • Fixed asset register
Process layer

Intranet Portal

  • Requests, approval chains and delegation
  • Employee self-service, web and mobile
  • Documents, attachments, notifications, audit trail
  • Operations: maintenance, field service, procurement
Modules

17 modules. Every one came out of a live project.

This is not a feature wishlist; it is the taxonomy of modules actually written and used across ten real portal projects. Each row states the ERP gap it closes in one sentence.

Human resources

5 modules
  • HR · LEAVE

    Leave Management

    Mobile leave requests, team-scoped manager approval and automatic posting of approved leave to the timesheet in one flow. ERP leave records sync without duplicates; the HR dashboard breaks down by type, month and department.

    ERP gap The ERP holds the leave balance for payroll; the request–approve–calendar–timesheet loop stays in email and spreadsheets.
  • HR · PEOPLE

    HR & People Management

    Employee self-service built on a read-only mirror of the ERP: profile, payslip access, personnel documents, org chart and HR analytics. Companies without an ERP are managed through spreadsheet import.

    ERP gap The ERP is the master for payroll but gives employees no self-service face; the bridge that exposes minimised personnel data to thousands of people is not something the ERP provides.
  • HR · TIME

    Time & Attendance

    QR and GPS-geofenced mobile clock in/out, shift definitions and rotation planning, an exception queue, manual entry and overtime requests, and a monthly timesheet that locks and posts to payroll.

    ERP gap Standard ERPs have no native QR+GPS mobile punch, shift rotation or approval flow for field staff; building it is an expensive custom project.
  • HR · PERFORMANCE

    Performance Management

    Review periods, competency and goal catalogues, configurable scoring formulas, multi-step approval chains, self/manager/reviewer flows and PDF scorecards.

    ERP gap Goal setting, competency scoring and 360 approval chains sit outside ERP scope; add-ons that offer them are costly licences and cannot express company-specific weightings.
  • HR · LEARNING

    Training & LMS

    Role-based training matrix, programmes, question bank, timed online exams, automatically issued verifiable certificates and individual/team compliance tracking.

    ERP gap An ERP records that training happened but cannot run an online exam, enforce a mandatory training matrix or issue and verify certificates.

Finance

3 modules
  • FIN · EXPENSE

    Expense & Income Management

    Receipt-based expense entry (mobile photo + OCR), categorised reports, approve/reject flow, paid and offset status, advance reconciliation and role-based budget-versus-actual dashboards. Approved totals transfer cleanly to finance.

    ERP gap The ERP holds the final accounting entry but does not offer the employee-facing submit–approve–pay lifecycle or self-service budget dashboards.
  • FIN · PROCUREMENT

    Procurement & Tendering (P2P)

    Requisition → order → goods receipt, multi-step internal approval by value band, three-way invoice matching, e-invoice inbox, and tendering opened to external suppliers: bid collection, side-by-side comparison and weighted scoring.

    ERP gap The ERP holds orders and invoices, but value-banded internal approval, three-way matching and competitive tendering are either absent or locked behind an expensive upper tier — most companies run it in spreadsheets.
  • FIN · PAYMENT

    Invoice Tracking & Payment Orders

    Pulls e-invoice and tax authority status from the ERP, calculates the net payable after advances and credits, catches double payments, keeps the deferral history and produces bank instructions from the approved payment list.

    ERP gap The ERP holds the invoice but cannot model the pay/defer negotiation between finance, procurement and management, the live budget ceiling, or double-payment protection.

Operations

5 modules
  • OPS · MAINTENANCE

    Maintenance & Breakdown

    Equipment records, a fault → work order → closure state machine, technician assignment, material and labour consumption against the work order, automatic work orders from the preventive schedule, MTTR and fault-density reports.

    ERP gap The equipment fault cycle, preventive schedule and technician execution do not exist in the ERP; a CMMS is either an expensive upper module or separate software that doesn't connect.
  • OPS · FIELD

    Field Service Management

    Alarm → work order → completion → billing; a live operations board on a map, geofenced technician presence checks, SLA countdown, barcode-based part fit/removal, photo evidence and a signed PDF closure report.

    ERP gap The ERP does not tie a field technician's real-time location to a work order; field SLA counters and live dispatch sit outside ERP architecture.
  • OPS · ASSETS

    Asset Custody & Handover

    Tracking of assets assigned to employees, employee acceptance, person-to-person transfer and return flows, a company-wide read-only inventory and QR-based location counts.

    ERP gap The ERP keeps fixed-asset depreciation but not who physically holds the laptop today, the signed handover, or the transfer between employees.
  • OPS · FLEET

    Fleet Management

    Vehicle inventory; inspection, insurance, toll and tyre expiry alerts, fuel and cost records, driver assignment, traffic fines, vehicle booking flow, cost analysis and GPS/CANBus telematics.

    ERP gap The ERP sees a vehicle only as a fixed asset; there are no inspection alerts, booking flows or live telematics, so fleet operations always need a separate system.
  • OPS · BOOKING

    Bookings, Visitors & Meetings

    Conflict-checked room and resource booking, meeting planning with attendees and documents, front-desk visitor registration, appointments and check-in/check-out with a reception board.

    ERP gap Resource scheduling, conflict detection and visitor registration are facility operations; an ERP models neither physical availability nor visitors.

Shared backbone

4 modules
  • CORE · APPROVAL

    Approval Engine & Workflows

    One approval engine that plugs into every document type: dynamic routing by value band, hierarchical and parallel chains, delegation, SLA escalation and step-level permissions. A single "awaiting approval" inbox covers all modules.

    ERP gap ERPs have no single reusable approval matrix that is document-agnostic, supports delegation and routes by value band; customising each document separately is prohibitively expensive.
  • CORE · SERVICE DESK

    Requests & Service Desk

    A full ticketing system for cross-department work, quality and IT requests as well as customer support: category-based routing, assignment and handover, a status machine, internal notes, SLA status and activity trail.

    ERP gap Department-to-department work requests and the support lifecycle are an ITSM need outside ERP scope; the ERP has no such concept.
  • CORE · COMMS

    Internal Comms & Employee Services

    Announcements with read tracking, internal news, surveys, canteen menu, shuttle routes, the employee handbook, a corporate calendar and a partner discount directory. The content layer that makes the portal a daily landing page.

    ERP gap Read-tracked announcements, news feeds, canteen menus and shuttle times are pure employee-experience functions with no ERP equivalent at all.
  • CORE · WORK

    Tasks, Projects & Documents

    Kanban task and project boards, a folder-based file manager, a categorised corporate document library with search and sharing. An idea pool collects bottom-up improvement suggestions.

    ERP gap Team task boards, searchable corporate document management and suggestion pools are territory the ERP never occupies, which leads to separate subscriptions.

Is your process not on the list?

Describe it. If it isn't here yet, we scope it together as a new module within your subscription — no separate project invoice.

Describe your process
Cost of ownership

The expensive part of enterprise software isn't the software

These are the line items that eat the budget in a classic corporate portal project. In a subscription model, none of them exist.

  • Day-rate setup and consultancy none
  • Software licence none
  • Per-user charge none
  • Annual maintenance and upgrade fee none
  • Servers, hosting and sysadmin none
  • A separate project invoice per new module none
What remains

A single monthly subscription

Zero capital expenditure, one predictable operating cost. User count is not a line item — you open the portal to the whole company. New modules are requested within the subscription on transparent terms.

Pricing depends on company size and integration scope. We work out the actual figure together in the demo.

Let's talk pricing
Mobile

The manager holding up the approval isn't at a desk

Processes stall in almost exactly the same place every time: the person who has to approve is on site, on the road or in a meeting. With the iOS and Android app, both the request and the approval are in their pocket.

  • Leave and advance requests
  • One-tap approval
  • Expenses from a receipt photo
  • QR clock in and out
  • Employee directory
  • Announcement notifications
Evidence

These modules came from the field, not from a slide deck

5,000+

Employees served on a single portal — at holding scale, on top of an ERP

10+

Live corporate portal projects behind the module taxonomy

17

Ready business-process modules written and used in real projects

5+

ERP families integrated: Logo, Mikro, SAP, Netsis, Uyumsoft

Process

How we start

We don't switch on every module at once. We start with the process that hurts most and expand from there.

  1. Process call 30 minutes

    We talk about which ERP you run and which processes cost you the most time. You leave the call with a module order tailored to you.

  2. Portal setup same day

    Your portal opens on your own subdomain; your logo, brand colour and org structure are configured. You don't have to provision a server.

  3. First module and approval chain

    We usually start with leave or expenses. Your approval chain is defined by filling in a form, not by writing code — who approves, at what value, in what order.

  4. ERP integration and rollout

    Personnel and financial data start flowing from the ERP and employees join from mobile. Further modules go live in sequence under the same subscription.

Frequently asked

Questions we get

Does it replace our ERP?
No. The ERP remains the single source of truth. The portal reads from it and writes only approved output back. The aim isn't to change your ERP — it's to get the processes it doesn't cover out of spreadsheets and WhatsApp.
Where is our data held?
Each company's portal runs on its own subdomain within its own data scope; tenant data is isolated at the application level. Hosting location, backups and data protection requirements are agreed in writing before setup.
How many users can we add?
User count is not a line item in the subscription. You can open the portal to the entire company, including shop-floor staff. Having no per-user charge is a deliberate choice: a portal that only half the company uses is a portal nobody uses.
The module we need isn't on the list
The 17 modules come from ten real projects, but the scope is deliberately open-ended. Describe your process and we scope it together as a new module within your subscription. No surprise project invoice.
How long until we're using it?
The portal itself is up the same day. What actually sets the timeline is on your side: settling the approval chains, and access for ERP integration. Going live with the first module in one department is typically a matter of weeks, not months.
Our ERP isn't in the supported list
The integration pattern isn't ERP-specific: the portal works by reading data and writing approved documents. Oracle, in-house software or no ERP at all are all workable — without an ERP, personnel data is managed through spreadsheet import. Let's discuss your current system in the demo.
Book a demo

Describe your process and we'll show the portal running

A 30-minute call. Not a sales deck — we talk through how your processes look inside the portal.

  • We explain the integration method for the ERP you run
  • We produce a concrete order for which module to start with
  • We discuss the subscription figure for your scale

Your details are used only to reply to this request. If you'd rather write directly: info@codsol.fi