SMETS requirement clause

5.7.5.23 — Payment Debt Register [INFO]

3 technical records havebeen identified at this reference: 3 Section 20 items and 0 explicit clause references. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.

ESMESRV touchpoint
3

Atomic items

Section 20 objects, attributes or methods at this source reference.

3

Documented touchpoints

Typed relationships supported by source mapping rows.

2

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

SMETS5.7.5.23 · item PaymentDebtRegister.method: adjust

PaymentDebtRegister - adjust

SRV touchpoint

PaymentDebtRegister.value is to be adjusted by the amount specified in the adjust method invocation. May be called internally (by prepay credit processing) or externally

Object
PaymentDebtRegister
Attribute / method
method: adjust
Interface disposition
E
Category
Method
Section 20 meaning
PaymentDebtRegister.value is to be adjusted by the amount specified in the adjust method invocation. May be called internally (by prepay credit processing) or externally

Documented touchpoints

Evidence:source paragraph 1602, 1603Section 20 row 1158

SMETS5.7.5.23 · item PaymentDebtRegister.methodInput: adjustmentValue

PaymentDebtRegister - adjustmentValue

SRV touchpoint

The amount of the adjustment

Object
PaymentDebtRegister
Attribute / method
methodInput: adjustmentValue
Interface disposition
E
Category
Method Input
Section 20 meaning
The amount of the adjustment

Documented touchpoints

Evidence:source paragraph 1602, 1603Section 20 row 1161

SMETS5.7.5.23 · item PrepaymentBalanceCollection.PaymentDebtBalance

PrepaymentBalanceCollection - PaymentDebtBalance

SRV touchpoint

See SMETS requirements

Object
PrepaymentBalanceCollection
Attribute / method
PaymentDebtBalance
Interface disposition
E
Category
Operational data
Section 20 meaning
See SMETS requirements

Documented touchpoints

Evidence:source paragraph 1602, 1603Section 20 row 1812

How to read this page

Evidence is kept at record level

A source clause can contain several separately mapped Section 20 items and an explicit alert reference. One item may be read by an SRV, another updated by a different service, and another have only an Alert or local-HAN path. Accordingly, the clause summary does not collapse those distinctions into a single covered or uncovered result.