Table views for every role

§ 1

In brief

One record

The payments

every fact of every payment

Payments manager
Routing and cost
- instrument
- acquiring
- fee
Finance controller
Settlement and ledger
- batch
- net
- posting
Auditor
Everything, read only
- all columns
- export

Every figure in every table traces back to the record it came from.

Fig. 14.1 — one record of the payments, read into a table for each role.

One source: Orders, invoices, payments, settlements and the ledger are read from one record, so they never disagree.
Sections by permission: A section opens for a role that holds its permission; a role’s menu shows only its own sections.
Columns by role: An operator sees instrument, acquiring and stage; a finance controller sees fee, batch and posting.
Exports with sources: A table is exported with references to its records, for accounting, a data warehouse or an auditor.

§ 2

In detail

2.1

One record, several views

Each fact of a payment names the views it forms. A capture marks the invoice paid and the order paid, forms the payment’s view and writes balanced entries in the ledger — in one step, from one fact. Orders, invoices, attempts, payments, settlement batches and the ledger are all read from the same record.

Demo scene 1

The views of the retail stand

How many entities each view holds now; the ledger counts its entries.

Order
2,452
Invoice
2,452
Session
2,858
Payment
2,615
Settlement
1,889
Ledger
7,921

2.2

The sections a role sees

A section opens for a role that holds its permission; a role’s menu lists the sections it works with, in its own order. A stand may name a section in its own words: the retail group calls a provider’s tariffs its acquiring terms.

Demo scene 2

Which role opens which sections

Groups of sections, the permission each checks, and the roles that hold it on the demo stand. A filled square: the role sees the group.

Sections	Operator	Payments manager: routing and costs	Finance controller: reconciliation	AML and compliance officer	Contracts and access manager	Integrator	Auditor
Orders · invoices · sessions · paymentsflows.read
Routing · costscosts.read
Settlements · ledger · payoutspayouts.read
Held payments · alerts · onboardingaml.read
Access · requests · audit trailgrants.read
API log · webhooks · event cataloguelogs.read

2.3

Columns by role, the same figures under every table

An operator sees a payment by its instrument, acquiring and stage; a finance controller by its fee, batch and posting; an auditor sees everything and changes nothing. Each table is a declared set of columns over the same view, and its figures are computed by the same functions that routing and reconciliation use, so a number in a list, on a dashboard and on a payment’s page never disagree.

2.4

Rebuilt and exported with sources

Every view can be rebuilt from the record at any moment and comes out the same; the demo stand builds all of them this way when it starts. The same views feed the exports — a settlement batch to accounting, the stream of facts to a data warehouse — each row with its unit, source and time, traceable to its fact and, for a bank’s report, to its line.

§ 3