Payment

A monetary payment between two parties.

Relations to other schemata

Payment has the following relations to other schemata in the model:

Relation	Schemata
Properties inherited from:	Value Interval
More precise schemata:	-

Payment has multiple properties to describe its data. Some properties are inherited from its parent schemata.

Icon legend

This property is used to compute a caption for the entity.

This property is a featured property, which means in UI applications it should be shown with higher information hierarchy.

This property is a matchable property and can be used in matching systems to find similar entities.

This property is a hidden property and should not be rendered in UI applications.

Name	Label	Type
Value:amount	Amount	number
Payment:payer	Payer	entity
Payment:beneficiary	Beneficiary	entity
Interval:date	Date	date
Payment:purpose	Payment purpose	text
Payment:sequenceNumber	Sequence number	string
Payment:transactionNumber	Transaction number	string
Payment:programme	Payment programme Programme name, funding code, category identifier, etc.	string
Payment:payerAccount	Payer bank account	entity
Payment:beneficiaryAccount	Beneficiary bank account	entity
Payment:contract	Contract	entity
Payment:project	Project	entity
Interval:startDate	Start date	date
Interval:endDate	End date	date
Interval:summary	Summary	text
Interval:description	Description	text
Interval:recordId	Record ID	string
Interval:sourceUrl	Source link	url
Interval:proof	Source document	entity
Interval:publisher	Publishing source	string
Interval:publisherUrl	Publishing source URL	url
Interval:alephUrl	Aleph URL	url
Interval:namesMentioned	Detected names	name
Interval:indexText	Index text	text
Interval:modifiedAt	Modified on	date
Interval:retrievedAt	Retrieved on	date
Value:currency	Currency	string
Value:amountUsd	Amount in USD	number
Value:amountEur	Amount in EUR	number

How to use it in a graph or timeline

FtM has well-defined semantics for different representations of entities, for example in a network graph or in a timeline.

When using this schema in a graph representation, it should be represented as an edge.

Semantic	Property
Temporal start	Interval:startDate Interval:date
Temporal end	Interval:endDate
Edge source	Payment:payer
Edge target	Payment:beneficiary