Payments Ontology: Reference

Dave Reynolds, Epimorphics Ltd

The payments ontology enables linked-data publication of information on payments to suppliers. For help on using the ontology see guide.

Vocabulary index

Classes: payment:ExpenditureCategory payment:ExpenditureLine payment:Payment payment:PaymentDataset payment:Purchase payment:Redaction

Properties: payment:contract payment:date payment:expenditureCategory payment:expenditureCode payment:expenditureLine payment:grossAmount payment:invoice payment:narrative payment:netAmount payment:order payment:payee payment:payer payment:payment payment:procurementCategory payment:purchase payment:reference payment:totalGrossAmount payment:totalNetAmount payment:unit

Vocabulary Reference

Core classes

Class: payment:PaymentDataset Sub class of: qb:DataSet [ stable ]
A set of payments or expenditures, laid out as a cube of data
Class: payment:ExpenditureLine Sub class of: qb:Observation [ stable ]
An item of expenditure that can be classified or assigned to a cost centre
Class: payment:Payment Sub class of: qb:Slice [] [] [] [ stable ]
A payment to a supplier for some goods or services, may correspond to one or more expenditure lines
Class: payment:Purchase [ stable ]
The overall goods or service for which the payment was made

Property aliases to clarify structure for non-cube viewpoints

Property: payment:expenditureLine ( payment:Payment -> payment:ExpenditureLine ; sub property of: qb:observation ) [ stable ]
Links a payment to the individual expenditure lines associated with it.

Dimensions - which can be used to structure the cube

Property: payment:payer ( payment:Payment -> foaf:Agent ) [ stable ]
The entity which made the payment.
Property: payment:payee ( payment:Payment -> foaf:Agent ) [ stable ]
The entity to which the payment was made.
Property: payment:date ( payment:Payment -> interval:Interval ) [ stable ]
The date the payment is deemed to have occurred.
Property: payment:expenditureCategory ( payment:ExpenditureLine -> skos:Concept ) [ stable ]
The category of expenditure in some appropriate categorization scheme (such as the Best Value Account Code of Practice categories). If the scheme is hierarchical then this should at least designate the narrowest (most fine grain) applicable code and can additionally designate the broader codes. Multiple code schemes can be used within the same dataset and consuming applications can use the skos:inScheme (and the rdf:type) of the code to determine the scheme.
Property: payment:expenditureCode ( payment:ExpenditureLine -> ) [ stable ]
An (optional) internal code for the expenditure category. Such codes may not be useful across organizations but retaining them in a dataset may aid comparability of datasets within an organization and help with tracing back requests for further information. The internal code may actually be an amalgam of multiple different categories (e.g. may denote both the subjective and objective classifications of an expenditure).
Property: payment:payment ( payment:ExpenditureLine -> payment:Payment ) [ stable ]
Indicates the payment of which this expenditure line is a part.

Measures - values that can be associated with a single observation in the cube

Property: payment:grossAmount ( payment:ExpenditureLine -> xsd:decimal ) [ stable ]
The amount paid, inclusive of any tax (whether reclaimable or not)
Property: payment:netAmount ( payment:ExpenditureLine -> xsd:decimal ) [ stable ]
The net amount of the payment. This is the effective cost to the payer after any reclaimable tax has been deducted.

Attributes - qualify the measured value

Descriptive properties for Payments and Expenditure lines

Property: payment:order ( payment:Payment -> ) [ stable ]
Indicates an order associated with this payment (optional).
Property: payment:invoice ( payment:Payment -> ) [ stable ]
Indicates an invoice associated with this payment (optional).
Property: payment:contract ( payment:Payment -> ) [ stable ]
Indicates a contract associated with this payment (optional).
Property: payment:reference ( payment:Payment -> ) [ stable ]
A reference number, code or label which identifies the payment. Not unique across different suppliers.
Property: payment:totalNetAmount ( qb:Slice -> xsd:decimal ) [ stable ]
total net amount
Property: payment:totalGrossAmount ( qb:Slice -> xsd:decimal ) [ stable ]
total gross amount
Property: payment:purchase ( payment:Payment -> payment:Purchase ) [ stable ]
Indicates the overall goods or service for which the payment was made.
Property: payment:procurementCategory ( payment:Purchase -> skos:Concept ) [ stable ]
A classification for the goods or services for which the payment was made.
Property: payment:narrative ( payment:Purchase -> ) [ stable ]
A narrative description of the goods or services that were supplied.

Structure relationships

Property: payment:unit ( payment:Payment -> org:OrganizationalUnit ) [ stable ]
Optionally indicates a particular organizational unit (Department, Directorate etc) of the payer organization associated with the payment. Use org:classification to link the unit to a categorization of types of units to support cross-comparison. For example, in the UK Local Authority spend application then the ESDToolkit-maintained list of Department Types may be a suitable code list.

Data structure definitions

Individual (expenditure structure): payment:payments-with-expenditure-structure
The structure of a cube containing expenditure level information along with payments.
Individual (payment slice): payment:payment-slice
The definition of a slice through an expenditure cube that corresponds to all the expenditures in a single payment.

Expenditure codes for capital/revenue

Class: payment:ExpenditureCategory Sub class of: skos:Concept [ stable ]
The set of expenditure categories in the expenditure-category scheme for capital/revenue.
Individual (Exenditure category scheme): payment:expenditure-category [ stable ]
A code scheme for classifying expenditures as capital/revenue.
Individual (Capital): payment:capital [ stable ]
Indicates a capital expenditure.
Individual (Revenue): payment:revenue [ stable ]
Indicates a revenue expenditure.

Support for recording redaction

Class: payment:Redaction [ proposed ]
An instance of Redaction can be used in place of the actual value in a dataset to indicate that this is a replacement for the true data value which has been redacted. Typically the Redaction resource will be a blank note. It is recommended that it have an appropriate rdfs:label (e.g. REDACTED). If further information on the reaction is available then dcterms properties should be used to carry those, in partcular dct:description can be used to convey a description of the redaction and reasons