Skip to content

Solution area

e-Solutions

e-Invoice, e-Signature, e-Reconciliation, e-Ledger, e-Archive and e-Dispatch Note are all document steps inside the same operational processes. Each heading has its own page and is explained together with the process it belongs to.

Starting point

A document is the output of an operation.

These headings are usually discussed one by one: a document type is picked first, and the process that produces it is looked for afterwards. It works the other way round, because a document is the output of an operation such as an order, a delivery, a collection or an accounting entry.

So we plan document steps together with the process that produces them. Which transaction gives rise to which document, which record it attaches to, who approves it: until that is settled, the document side cannot be built on its own.

This page does not present the six headings as one product. Each comes with its own process; what they share is that they all pass through the same operation and are handled in the same way.

What this page is for

  • Showing which document step comes out of which process
  • Starting with one heading and leaving the others for later
  • Spotting where a single transaction produces more than one document
  • Discussing responsibilities on the document side in one place
  • Pointing you to the right page for the detail

Workstreams

How document work is scoped.

Whichever heading you start with, the work follows the same sequence; scope is set together based on your existing systems and process needs.

  • Mapping processes to documents

    Which transaction produces which document, who approves it and which record confirms it are written down.

  • Work on the ERP side

    Where the fields behind a document are held in your enterprise systems, and what still needs completing, is established.

  • Controlled rollout

    A narrow scope is taken first and worked through with real documents; it is widened only once the result holds.

  • Monitoring and the next step

    The live flow is monitored, the steps that do not work are corrected, and the timing of the next document step is agreed together.

Delivery approach

The headings are taken one at a time.

The six are not opened at once; which one comes first depends on your current workload and your calendar.

  1. Order of priority

    When each document step is taken up is decided with workload and dependencies in view.

  2. Together with the process behind it

    A document step is never handled alone; it is taken up with the process that produces it.

  3. Starting narrow

    The first rollout is kept small, and scope is not widened before real use has been seen.

  4. Moving to the next heading

    Once one heading has settled, the next is taken up with what has been learnt.

Scope note

Regulatory detail is addressed at the start of the project

The form and the scope of these document steps follow regulation, and the detail can change over time. That is why this page carries no document-type, compliance or infrastructure claims.

Which headings apply to your organisation, and the scope of each, is confirmed with the relevant specialists after your current systems and processes have been reviewed.

Let's decide together which document step to start with.

Let's talk through your current processes and systems, and set the sequence and the scope from there.