An EDICOM e-invoice archive does not set the retention rule

Separate platform preservation from the legal retention rule

EDICOM's official product record connects electronic invoicing, authority exchange, signature services, and archiving. The direct operating answer is that a platform archive can retain documents and transaction evidence, but it is not the source of the taxpayer's retention obligation. The required period, original format, integrity method, location, accessibility, language, inspection process, and permitted conversion can differ by jurisdiction, document class, taxpayer population, transaction, and effective date.

Tax and records owners should therefore maintain a jurisdiction-and-record retention matrix outside any product slogan. Each rule should identify the controlling authority or instrument, affected legal entity, invoice or report type, issue and receipt date, authority response, storage period, format, signature or seal requirement, permitted location, access expectation, suspension or litigation hold, and disposal authority. Unknowns should remain explicit until qualified tax, legal, and records review resolves them.

Preserve the whole transaction chain, not one archived file

A legally relevant invoice history can include source transaction data, the generated structured document, human-readable rendering, schema and country profile, signature or seal, transmission envelope, network or authority identifiers, validation messages, acceptance or rejection, corrected versions, credit notes, cancellations, acknowledgments, ledger postings, return treatment, and later audit correspondence. Saving only the final invoice can remove the context needed to explain what was sent, which rules were applied, and how an exception was resolved.

The archive design should keep those objects linked without overwriting prior states. A reproducible retrieval test should start with one invoice line and recover the controlling source data, document version, exchange route, response, correction history, ledger entry, filing period, reviewer action, and export package. The test should also cover unavailable integrations, expired certificates, changed keys, migrated records, duplicate identifiers, legal holds, and a request made after the operating system has changed.

Assign ownership across tax, records, security, and technology

Archiving crosses several accountable functions. Tax owners determine which transaction and authority records matter. Legal and records teams interpret retention, hold, localization, admissibility, and disposal requirements. Security and privacy teams govern access, encryption, monitoring, and personal-data boundaries. Technology teams operate integrations, formats, keys, migrations, backups, and exports. A service provider may perform technical controls, but those roles do not transfer the taxpayer's obligation automatically.

A buyer demonstration should use named jurisdictions and real record types. Ask EDICOM to show how the proposed service identifies versions, preserves authority responses, prevents silent replacement, records access, handles corrected invoices, proves export completeness, supports holds, and returns records at contract exit. The customer should separately confirm which controls are included in the contracted package and which depend on configuration, external trust services, local partners, or customer procedures.

Keep EDICOM claims inside the reviewed source

The registered EDICOM page establishes current provider positioning for an international e-invoicing and tax-compliance platform connected to ERP systems, tax authorities, electronic signatures, and archiving. It does not establish that one archive configuration satisfies every country's law, that every transaction is retained completely, that a signature has the required legal effect, or that an authority will accept a retrieved record in a specific audit or dispute.

Indirect Tax Monitor reviewed the official source on August 19, 2026 and did not operate a customer deployment. Buyers should verify the current product and service boundary, supported jurisdictions and document types, retention configuration, integrity evidence, signature and seal services, authority-response capture, search and retrieval, audit logs, migration, backup, exit export, service continuity, and qualified local interpretation before relying on the archive for a consequential tax record.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Indirect Tax Monitor will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.