Companies

Document management for companies

Contracts, personnel files, invoices and technical documentation — described consistently, searchable across the organisation and shared only where access allows, with the dates that matter announced before they pass.

Described as they arrive

Dates, registration numbers, tax and trade-register numbers are read from each document — in Romanian, English or Dutch — and every value points at the place it was read from.

Deadlines announced

Rules follow a date in a document's fields — a contract's end, an invoice's due date — and tell the people concerned at the moments you choose, such as 90 and 30 days before: in the application and, where e-mail is set up, by e-mail.

Shared outside, under control

A set of documents can be shared with named people for a period. Where external sharing is switched on, recipients get a link by e-mail and a one-time code, see only what was shared, and every step is recorded.

Personnel files and employee requests

Sensitive fields are withheld from anyone without the right to see them, and employees' requests to see or erase their data run against the legal deadline.

Access by department

Access groups and access lists decide who sees which contracts, invoices and files, checked on every request.

Connected to your systems

A REST API covers every function of the portal, so finance and line-of-business systems can file, describe and find documents.

What it does not do

  • It does not read contract parties or amounts. Dates and identifiers are extracted; parties and amounts are entered or imported.
  • A reminder is not a guarantee. A deadline notification tells people in time; it cannot stop a term from being missed.
  • Portal bulk upload carries no metadata. Files uploaded in bulk from the portal arrive without it; importing metadata with them goes through the API.

How we work together

From your record series to a working archive

A demonstration is the first step. What follows is a pilot on your own documents, measured before you commit to anything.

  1. Start from your record series

    We begin with the document types you hold, the fields you need described, which of them hold personal data, and the retention and access rules that apply — not with a generic template.

  2. Configure a repository for them

    A metadata model with your attributes and controlled value lists, rule packs for your references and identifiers, and an identity realm connected to your own identity provider.

  3. Measure on your own documents

    You provide a representative sample. We measure description quality against it, field by field, so you know how much review to expect before any commitment.

  4. Bring the archive in

    Bulk ingestion of the existing holdings, integration with the systems around the archive through the REST API, and a handover to your reviewers and administrators.

See Archystream with your own documents

Tell us about your record series and we will walk you through a portal configured for them, including the description quality we measure on documents like yours.

Or write to us at [email protected]