Activating an e-Delivery address does not complete a company’s preparation for e-Delivery (e-Doręczenia, Poland’s electronic registered mail). A document may be waiting in the mailbox even though no one in the organization has opened a case, assigned an owner, or started monitoring the deadline. A legal issue then becomes an operational problem: who receives the message, how is its significance identified, who receives it next, and where are the proofs retained?
In a well-prepared organization, e-Delivery is one of the mailroom’s channels. The message enters a shared register together with its attachments and proofs, is linked to a case, and gives the responsible person a task and deadline. Paper, email, eNadawca, and courier services do not disappear—each channel has a defined role, but none creates a separate, invisible workflow.
Who is required to use e-Delivery, and from when?
The obligation arises from Poland’s Electronic Delivery Act and is being introduced in stages. According to the schedule of Poland’s Ministry of Digital Affairs:
- most public entities specified in the act and members of regulated professions have used e-Delivery since January 1, 2025;
- private entities registering in Poland’s National Court Register (KRS) since January 1, 2025 establish an address during registration, while entities previously entered in the KRS register of businesses became subject to the obligation on April 1, 2025;
- entrepreneurs registering in Poland’s Central Register and Information on Economic Activity (CEIDG) since January 1, 2025 establish an address during registration;
- entrepreneurs entered in CEIDG by the end of 2024 had to establish an address when amending their record from July 1, 2025, and the remaining entrepreneurs became subject to the obligation no later than October 1, 2026.
This means that October 1, 2026 was the final general deadline for entrepreneurs previously registered in CEIDG. Not all public institutions follow the same schedule—the act sets later dates for selected groups. Before making a decision, check the organization’s current position in the official e-Delivery implementation schedule.
An electronic delivery address, known in Poland as an ADE, is not a regular email address. It identifies the owner and is entered in the Electronic Address Database. Once the mailbox is activated, the company can receive correspondence from entities that use e-Delivery. It therefore cannot be treated as an extra channel that someone checks occasionally. It needs continuous service, substitutes, and controls.
How does e-Delivery change mailroom work?
In a paper-based workflow, reception staff see an envelope and usually know where to send it. With e-Delivery, receipt is immediate, attachments may concern different companies or departments, and proofs are created as separate electronic documents. Administrator access to the mailbox alone does not provide business handling.
A common mistake looks like this: one person receives an email notification, logs in to the mailbox, downloads the files, and forwards them. When that person is absent, the message waits. After the attachment is forwarded by email, the mailroom loses visibility: it does not know whether the recipient opened a case, who is responsible, or where the proof of sending or receipt was stored.
The target process should separate four responsibilities:
- Mailbox administration—managing the ADE, access, and configuration, not reviewing the substance of every document.
- Mailroom or intake point—checking new messages, registering them, verifying completeness, and performing initial routing.
- Case owner—reviewing the content, preparing a response, and meeting the deadline.
- Records or archive owner—classification, retention, access, and completion of the case life cycle.
Every role needs a substitute. An email notification is a supporting signal, not a register of responsibility.
From message to case: a practical workflow
1. Receipt and completeness
The process retrieves the message, metadata, attachments, and available proofs. It records the technical identifier and prevents a duplicate case if the integration retries. The mailroom can see whether the complete set of documents arrived and which entity or case they should be linked to.
2. Registration and classification
The document receives a number, receipt date, sender, channel, category, and access level. If the organization has several companies or ADE addresses, the process retains information about which mailbox received the message. Confidential correspondence follows a different path from a general letter or an invoice.
3. Routing and acknowledgment of ownership
Rules identify a department, role, or person based on the recipient, sender, category, and content. The recipient acknowledges ownership of the case. If the document was routed incorrectly, the recipient returns it to the mailroom with a reason instead of forwarding the attachment outside the process.
4. Deadline and response
The system records the deadline that requires monitoring and the responsible person. Reminders and escalations do not replace a legal assessment: the appropriate team should determine a procedural deadline and how it is calculated. The result of that assessment must, however, be stored with the case rather than in an employee’s private calendar.
5. Dispatch and proofs
Once the response has been prepared and approved, it goes to the appropriate channel. Proof of sending and proof of receipt return to the same case. The operator provides proofs for Poland’s Public Registered Electronic Delivery Service (PURDE) in PDF and XML formats, so the archive should retain both a readable file and the data required for later verification.
The mailbox works, but documents are still forwarded by email? We will map the path from receipt to response, responsibilities, and integrations. Discuss your correspondence workflow →
Five decisions before launching the integration
One service point or several?
A corporate group may have several ADE addresses, companies, and mailrooms. The organization must decide whether a central team performs the first review for all entities or each unit maintains its own register. A shared platform does not have to mean shared access to every case.
Which documents require human review?
Automated rules handle unambiguous senders and categories well. Formal, confidential, or incomplete documents should go through review. AI reads the content and recommends a category and recipient, but a mailroom employee approves the routing. Full control over the data processing location in EU regions and models that are not trained on client data ensure compliance with GDPR and the AI Act.
Where is the master register maintained?
The e-Delivery mailbox is used to exchange messages. The case register should reside where the organization manages responsibility, deadlines, versions, and relationships with other documents. The organization must designate the system of record and rules for synchronizing statuses.
How are errors handled?
The process must detect a lost connection, rejected dispatch, duplicate, incomplete attachment, and insufficient mailbox capacity. Every error needs an owner, an alert, and a safe retry. A silent integration error is more dangerous than a manual action because the user assumes the system completed the task.
What do we retain and for how long?
One retention period should not be assigned to all correspondence. Retention follows from the type of case, legal basis, and organizational rules. Entities that use Poland’s uniform file classification schedule (JRWA) assign records to the relevant class and archival category. Other companies should combine their retention policy with legal, contractual, and business requirements. The message, attachments, metadata, and proofs must remain connected.
eNadawca and courier services are still necessary
e-Delivery does not cover every correspondence scenario. Companies still send paper originals, items to recipients without an appropriate electronic address, parcels, and materials requiring physical transport. Poczta Polska’s eNadawca supports postal dispatch, while courier integrations transfer shipment data, generate a label, and return a status.
The key is a single channel decision. The user selects the correspondence type and recipient, while the process checks available data, manages approval, and routes the dispatch to e-Delivery, eNadawca, or a courier. The confirmation returns to the case regardless of the channel. The mailroom therefore does not maintain three separate spreadsheets or search for statuses in operators’ portals.
An archive is more than a mailbox copy
The government service allows a message with attachments and proofs to be downloaded as a ZIP archive. This is a useful technical mechanism, but the file itself does not provide classification, access control, or a relationship to the process. The organization’s archive should retain the context: case number, sender, recipient, dates, category, owner, response versions, and delivery outcome.
In practice, three operations should be separated: retrieving the correspondence from the mailbox, storing it in the repository, and applying the retention rule. A message should not be deleted from the mailbox until the system confirms a complete and recoverable record. For records subject to JRWA, the process should support classification, archival qualification, review before disposal, and an audit trail of the decision.
Mailroom readiness checklist
- Does the organization have an active ADE and designated administrators?
- Does someone monitor incoming messages every business day, with a substitute in place during absences?
- Do the message, attachments, and proofs enter one register without manual re-entry?
- Does every case have an owner, deadline, confidentiality level, and routing history?
- Is there a path for returning an incorrectly routed document to the mailroom?
- Does the response go through the appropriate approval and signature before dispatch?
- Do e-Delivery, eNadawca, and courier services return a status to the same case?
- Does monitoring detect integration errors, duplicates, and mailbox capacity issues?
- Does retention cover the message, attachments, metadata, and proofs?
- Do test scenarios include an absence, confidential document, wrong recipient, and channel unavailability?
The role of AMODIT and automation
AMODIT connects the e-Delivery mailbox to the case workflow. It registers correspondence, manages classification and assignment, records responsibility and deadlines, supports preparation and approval of the response, and then retains statuses and proofs. The same process covers paper correspondence, email, eNadawca, and courier services, so the channel does not fragment the case history.
Astrafox also designs integrations with company systems, repositories, and reporting. When a document concerns an invoice, contract, employee, or order, the process sends it to the appropriate workflow instead of ending at registration. The mailroom, correspondence, and archive solution covers process analysis, integrations, migration, and post-launch maintenance.
When selecting a platform, review not only e-Delivery support but also roles, substitutions, exceptions, history, and the development of subsequent processes. The guide on how to choose a document workflow and process automation system supports this assessment. A practical example of the path from document receipt to the ERP is provided in the article on purchase invoice approval.
FAQ: e-Delivery in a company
Is an active e-Delivery mailbox enough to meet the obligation?
An active ADE provides the company with a delivery channel, but it does not organize internal handling. The company must still ensure regular retrieval, permissions, substitutions, document routing, deadline monitoring, and archiving appropriate to the type of records.
Does e-Delivery replace email, eNadawca, and courier services?
No. It is a registered electronic delivery channel. Email continues to handle working correspondence, eNadawca supports postal items, and courier services handle physical transport. All relevant statuses should return to the shared case.
Can a document be routed automatically to a department?
Yes. Rules use the mailbox, sender, recipient, category, and case data. For formal documents, the system records the classification, the mailroom’s decision, and the person who assumed responsibility.
Is the e-Delivery mailbox a document archive?
It should not be the organization’s only archive. It stores messages and allows them to be downloaded, but a company archive or an electronic document management/workflow system provides classification, permissions, retention, search, and a relationship between the document and the complete case.
Must every company use JRWA?
No. JRWA is a Polish tool for classifying and qualifying records, used by entities subject to the relevant office and archival regulations. Other companies establish retention under their applicable legal obligations, contracts, and justified business needs. The scope should be confirmed by the person responsible for records and compliance.
Want to connect e-Delivery with the mailroom, cases, and archive? Describe your current channels, roles, and systems. Discuss an AMODIT implementation →