Supplier Bank Change
External identity, internal authority, dual approval and evidence before any payment detail changes.
Engineered product direction
Trust turns authority into accountable action.
TrustMand is a mandate-to-action control layer for critical business actions across people, systems and AI.
Identity, authority, control, compliance, auditability — one chain from mandate to evidence.
Control Chain
From Authority To Accountable Execution.
Six stages, each answering one precise question. Together they connect identity, authority, policy, approval, execution and evidence.
Stage 1
Actor
Who is acting?
People, AI agents, suppliers, companies.
Stage 2
Mandate
On whose behalf?
Role, scope, validity, context.
Stage 3
Policy
What are the rules?
Policies, compliance, risk controls, limits.
Stage 4
Approval
Who must approve?
Single or multi, hierarchies, human or AI, exceptions.
Stage 5
Action
Execute or block?
ERP, banking, procurement, data systems.
Stage 6
Evidence
What is recorded?
Audit trail, proof of action, traceability, accountability.
Ecosystem Architecture
TrustMand Sits Between Actors And Systems Of Record.
It does not replace ERP, banking, procurement, identity, contract or compliance systems. It orchestrates authority, policy, approvals, execution control and evidence across them.
Actors
People
Employees and authorised representatives acting inside defined limits.
Suppliers
External parties requesting changes that carry financial consequence.
Companies
Legal entities acting through delegated organisational authority.
AI Agents
Automated initiators that must hold an explicit mandate to act.
Mandate-to-Action Layer
Authority orchestration and evidence
Mandates, policy, approvals, execution control, evidence packages.
Systems of record
ERP systems
Master data, purchase orders, vendor records.
Banking and payments
Payment release, account changes, settlement.
Procurement systems
Requests, sourcing, ordering, receipting.
Data and documents
Sensitive records, exports, controlled disclosure.
Contract systems
Signature, release, amendments, obligations.
Key Use Cases
Critical Actions Worth Controlling.
TrustMand Approvals is the initial validation focus. These illustrative use cases combine external identity, internal authority, financial or legal consequence, policy and inspectable evidence.
High-Value Payment
Threshold-based mandates and approval hierarchies before release.
Contract Release
Verified authority to sign, release or amend on behalf of the entity.
Sensitive Data Release
Purpose, scope and validity checked before controlled disclosure.
AI-Initiated Procurement
Machine actors act only inside an explicit, limited and revocable mandate.
First pilot concept
Supplier bank changes come first: dual approval, execution gating and evidence in a workflow where the cost of a wrong action is immediate and measurable.
Maturity and background
Current proposition. Clear limits. Documented origins.
TrustMand’s current commercial proposition is the mandate-to-action control layer described above. Earlier infrastructure work provides provenance, but it is not presented here as a parallel product history.
Maturity, stated plainly
An engineered product direction requiring engineering, security validation and controlled pilots; not presented as deployed or production-proven. Its underlying authority and permission concepts have documented VPLedger-era provenance from 2019 onwards; that historical record is not evidence that TrustMand itself was deployed then.
What is not claimed
Not production-proven everywhere. No universal regulatory compliance and no guaranteed elimination of fraud. It does not replace IAM, ERP, banking or GRC systems, and it does not imply complete technical reuse of every historical component.
The deeper exchange, distributed-ledger and governance chronology belongs to Ronny Boesing’s full journey on Boesing.dk.
PRODUCT MATCH
Test the fit before discussing implementation.
Five specific questions turn the initial recommendation into a bounded next step — including when the product is not the right next step.
Question 1 of 5