Receipt, sorting, authorization, workflow, sharing and audit in one traceable process.
No Paper Just Online
NOPA
We organize incoming documents, authorizations, approvals and logistics events into a retrievable, auditable business process.
The goal of the new foundation is testable integration, isolated customer environment and predictable operation.
Process survey, an adapter, a workflow, then expansion based on real use and measured results.
NOPA products
Four independent solutions with a common operating approach
The products can be introduced separately, but they can also be connected to each other and to existing company systems. The starting point is always the business process to be solved.
Document management
Incoming, OCR, document sorting, back-office digitization, linked storage, workflow and audit.
Explore this productE-route
Route import, dispatch, own Android field application, proof, delivery note and retrievable logistics events.
Explore this productEQForm
Configurable data sheets, formulas, lookup tables, testable business rules, reports and integrations.
EQForm in detailBulk email
Controlled posting, list management, scheduling, bounce processing, logging and reporting.
Explore this productOperational focus
One platform for the entire document business journey
NOPA organizes document management, incoming mail, sorting, generation and logistics events into a common operating framework. The solution can be adapted to existing company systems and can be gradually expanded with the necessary business modules.
A document platform to which the required business process is linked
NOPA builds on years of operational knowledge: mail book, incoming mail, document sorting, PDF and invoice generation, configurable form processes and E-route. The implementation always starts from the customer's real process, not from a pre-fixed list of modules.
Document life cycle
Upload, versioning, OCR/text extraction, AI identification suggestion, status, comment, share and audit in a recoverable document history.
Mail directory and incoming mail
The old NOPA mail book, tag number, receipt, incoming mail and automatic closing logic can be inserted into a new document process.
Document sorter
Incoming queue, PDF viewer, metadata panel, partner, project, division, contract or mailbox target, batch operations and audited decisions.
Generation and invoice modules
Invoice and PDF generation, invoice-group layouts, e-invoice delivery and integration with the NAV Online Invoice system can be provided in a separate scope when required by the customer process.
Logistics and E-route
Route-list, picklist, own Android field application, proof, delivery note and invoice connection are not separate islands, but a process built from documents and business events.
Controlled introduction
Start with one document process and the connections it needs, then expand based on measured results and actual use.
Back-office document processing
The paper can also come to us — we digitize it and sort it into the NOPA process
In addition to the software, we also provide a back office service. Incoming letters can arrive directly at our processing site, where we digitize them with industrial scanners in a controlled workflow and forward them to a document sorter.
Direct mail reception
The physical consignments arrive at the designated processing location, so the path of the paper is controlled from the moment it arrives.
Industrial scanning
The service can be scaled to a large volume, even for the digitization of thousands of documents per day.
Service in detailDocument sorter
OCR, metadata proposal, quality control and audited queue help assign documents to a business purpose.
Sorter in detailLinked storage
Nextcloud, OneDrive, Google Drive and S3 compatible object store can be linked to the created process.
Who is it for?
Business, IT and audit see the same process
NOPA is for those who consider cost, risk, lead time, integration and cross-departmental operations.
Executive perspective
Less manual work, lower operational risk, easier audits
NOPA connects documents, access rights, delivery events and supporting records in one traceable process.
- Measurable turnaround times and error rates
- A controlled trial and gradual migration
- Support arrangements and service levels agreed for your needs
IT leadership perspective
A platform designed to connect with your existing systems
Documented interfaces connect your systems. Separate customer environments, controlled changes and traceable background processing help your team operate and test the service.
- Documented system connections and access controls
- Database, storage connections and background processing
- Operating guides, health checks and monitoring
Customer service perspective
Less searching, clearer ownership, easier case resolution
Track document status, ownership, comments, access and customer events in one place, without piecing together information from folders and emails.
- Document queues and sorting
- Comments, case closure, reopening and escalation
- Options for weekly and monthly management reports
Logistics leadership perspective
Keep control of E-route operations across countries
Routes, packages, stops, driver updates, handovers and delivery notes share a controlled process and a traceable event history.
- Import and standardize route lists
- Driver updates and dispatch coordination
- Delivery notes, returns and status history
Executive perspective
Less manual work, lower operational risk, easier audits
NOPA connects documents, access rights, delivery events and supporting records in one traceable process.
- Measurable turnaround times and error rates
- A controlled trial and gradual migration
- Support arrangements and service levels agreed for your needs
Why now
Document flow is no longer a file server issue
Fragmented input
Scan, e-mail, app, manual upload and external system belong to the same business reality.
Proof pressure
Authority, version, share, signature, timestamp and audit cannot be post-Excel.
Integration constraint
ERP, CRM, ERoute, Docserver, storage and external APIs must have a contract-driven connection.
Legacy systems
Existing business systems do not need to be replaced all at once: they can be connected to the new process with adapters and in measurable steps.
Trust and compliance
In addition to the technology, the process also matters
Document management can be protected when access, authentication, retention and points of responsibility operate in a documented process.
Electronic document management for companies
Manage incoming documents, extract text, control access and track sharing in a documented workflow.
Document management in detailElectronic document management and archiving
Read the official Hungarian documentation on document authenticity, long-term preservation and retrieval.
Official siteA digital copy that can be proven from paper
The copying procedure provides a strong basis of trust through content integrity, authentication, an auditable process and long-term preservation.
Official sitePreservation, timestamping, procedural discipline
The official Hungarian archiving policy describes document preservation, timestamping and operating procedures.
Official siteGDPR and Infotv. data management basis according to
At the executive and CTO level, it is important that document management, postal digitization and electronic processing are communicated within a data protection framework.
Official siteConfigurable business logic and controlled dispatch
EQForm and mass email stand-alone NOPA products: rule-based data entry, testable logic, audit, reportable communication and reputation protection.
Platform
The new generation of NOPA is a modular operating backbone
The goal is not another DMS in a box, but a document, workflow and logistics platform that connects to existing company systems through stable APIs, audits and adapters.
Document core
Upload, versioning, metadata, PDF preview, tags, statuses, comments and shared links.
Document management product pageERoute process
Routes, stops, packages, preparation events, digital transfer, driver feed and delivery note connection.
E-route product pagePermissions and audit
Tenant roles, direct user overrides, explainable effective permissions, and append-only event history.
Integration layer
OpenAPI, adapters, idempotent jobs, webhook approach and structured error models.
Knowledge base for decision support
Not a blog stream. Organized professional answers to managerial questions
The knowledge base provides professional reference points for decision-making situations: when it is worth switching, how to reduce the compliance risk, what business results digitization gives, and how to start a controlled introduction.
Technical terms in plain English
A short guide to the abbreviations and technical terms used on our product pages.
- OCR — Optical Character Recognition
- Text recognition converts text in scanned documents or images into searchable, usable data.
- API — Application Programming Interface
- A documented interface through which systems exchange data and request actions.
- Workflow / audit trail
- A workflow defines work steps and responsibilities; an audit trail records who did what and when.
- Tenant / scope
- A tenant is a separate customer environment; a scope limits which data and actions a user or system can access.
- Dispatch / proof
- Dispatch coordinates routes centrally; proof is a recorded item supporting a handover or delivery.
- SLA — Service Level Agreement
- An agreement defining service levels. The specific commitments must be agreed separately.
- ERP / CRM
- ERP means enterprise resource planning; CRM means customer relationship management.
- SPF — Sender Policy Framework
- The domain owner specifies which mail servers are allowed to send email on behalf of the domain.
- DKIM — DomainKeys Identified Mail
- A digital signature helps the receiving server verify the sending domain and detect changes to the message.
- DMARC — Domain-based Message Authentication, Reporting and Conformance
- A policy using SPF or DKIM results and sender-domain alignment to guide how failed authentication is handled and reported.
- AI / metadata
- AI means artificial intelligence. Metadata describes a document, such as its partner, date or type; AI can suggest how to identify it.
5 advantages that NOPA provides to companies
Time, ISO, SLA, law and security: document management is not a back-office topic, but a managerial risk and operational issue. This is the opening material of the knowledge base.
Reading articleHow to deal with the constant pressure of legal compliance?
Compliance is not a one-time task, but a constant operational pressure. Electronic file management is a risk-reducing and audit-preparedness tool here.
Reading articleWhen will a paperless office become a daily operational advantage?
An introductory topic for those who are still looking for the business value of paperless operations. The emphasis is on daily use, not a buzzword.
Reading articleHow does NOPA help in company administration?
Three strong pillars: process optimization, secure data management and compliance automation. A good summary for customer service and back office managers.
Reading articleHow to start the switch from paper to digital document management?
It presents digitization not as a simple technological exchange, but as a transition that requires organizational and legal preparation.
Reading articleWhat does the new era of administration mean for a customer service manager?
Document management, communication and data security as daily operational issues. It is a good leadership bridge between the technology side and teamwork.
Reading articleWhen will mass email become a controlled channel instead of a business risk?
Additional message in the direction of ProofMail and communication workflow: deliverability, reputation and supervision instead of quantity.
Reading articleERoute
One route list is not enough for several national transport operations
At the operational and logistics management level, it matters that the daily preparation, digital handover, field feedback, delivery note and customer service closing are based on the same status machine and audit trail.
Route list and route planning
Preparation workflow
Digital handover
Android field application
Offline proof and events
Delivery note and audit
Intake
Import
Preparation
Driver feed
Handover
Audit
Architecture
CTO-compliant answer to scaling and isolation
Professional credibility
The development discipline is also part of the product
The narrative of the new NOPA works before CTO and enterprise IT if the quality gate is visible behind it: testable API, migration runbook, audit events, release discipline and operational monitoring.
lint + test + smoke
OpenAPI update for API change
migration release image-gel
audit event for critical operation
structured log and correlation id
for runbook deploy, rollback and troubleshooting
Roadmap
New Go-based NOPA platform based on a proven operating basis
Public product roadmap organized into major versions. ERoute and EQForm appear in their respective version line descriptions.
Legacy plant support
Active development
Security support
Maintained version
Pre-release version
Version
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
4.x.x
NOPA import, Symfony, ERoute history
5.x.x
document, archiving, EQForm
6.x.x
ERoute API v4/v5, delivery days, e-mail processing
7.x.x
DataStorage, ERoute app development, security patch
8.x.x
maintained version, security support
9.x.x
API-first, dispatch, customer master
10.x.x
GO basic, maintained version
11.x.x
pre-release version, GO services, enterprise scale
Next step
Show us a real process and we'll design the first working step
In a short meeting, we map the path of the document, the points of responsibility and the need for integration. Then we give a concrete proposal that can be introduced gradually.