Network · Documents and EDI

Order, confirmation and receiving — as documents, not as a chat thread

Between a network and a supplier what travels is not messages but documents with a state, an author and a history. Every step leaves a record, and the argument about what was promised is replaced by a line in the log.

who this is for

the network, its suppliers and accounting

layer

Network

What is wrong today

“Sent” and “delivered” are different things, yet most systems have one field for both.
A discrepancy at receiving stays in the storekeeper's head and never reaches the buyer.
Documents are assembled by hand from chat threads, and half never reach accounting.

How it works

The order as a document with a state

Draft, sent, confirmed, amended, received, fulfilled. Every transition is stamped with a time and a participant, and any state is one click away.

The supplier's reply becomes a document

A confirmation, a partial confirmation and a per-line refusal are stored line by line: you see exactly what the supplier promised, and how much of it.

Receiving with discrepancies

At receiving, what actually arrived is recorded. The gap between ordered, confirmed and received is computed automatically and becomes the basis for the supplier conversation.

Exchange in the recipient's format

A document travels by the channel and in the shape the counterparty already uses: a file in their format, a message in a messenger, or an API exchange. Neither side has to retrain.

Back into the accounting system

The confirmed order and the receiving record return into the network's accounting, so the books show exactly what the buyer sees, with no manual re-entry.

the working screen

What it looks like in use

Documents on the left; on the right, the path of one of them. The gap between ordered, confirmed and received is computed automatically.

invent.sale · Network · Document floworder, delivery, receipt — one chain

All documents412Discrepancies3Awaiting receipt7

Order 2418 · Distributor Alocation D · 24 linesdiscrepancy

84 200

Order 2417 · Manufacturer Chub · 61 linesreceived in full

41 700

Order 2416 · Distributor Blocation B · 34 linesin transit

9 400

Order assembledTue 06:00 · by the system, from the location's need

ApprovedTue 09:14 · buyer, 2 lines changed

Sent to the supplierTue 09:15 · to the messenger and as a file

Supplier repliedTue 11:02 · toothpaste: 60 instead of 90

Received at the locationThu 08:40 · 23 of 24 lines accepted

Discrepancy closedpending: return or re-invoice

Ordered 90, confirmed 60, delivered 54. The gap is visible on the spot — not a month later at reconciliation.

every step carries a time and a name · a document cannot be changed after the factOpen the discrepancy report

Order, reply and receipt are one documentNo merging an email, a delivery note and an accounting entry. Everything that happened to the delivery sits in one chain.

You see exactly where the 36 units wentOrdered 90, confirmed 60, delivered 54. That used to surface at month-end reconciliation, when nobody was to blame any more.

Every step has a time and a nameThe “I sent it” / “I never got it” argument ends. The log is not rewritten after the fact — not even by us.

An anonymised example: locations are lettered and the dataset is shared across every screen on this site.

Who stays in control

Automatic sending is enabled by the network owner, and large documents can stay on mandatory confirmation. The log cannot be edited from the interface — otherwise it is worthless as evidence.

How it is measured

By documents delivered, documents confirmed, and the number of discrepancies at receiving.

Show us one critical process. We will show how it runs here.

We look at your cycle: how an order is assembled today, who decides, where time leaks and what the system takes over.

Request an architecture review See it running at clients