DH-310 Examples

The following examples aim to describe how reports of close-proximity or overlapping sales agreements are processed in Datahub to prevent the creation of overlapping agreements.

Example 1: Accounting point agreements reported with different start dates come into effect consecutively, regardless of whether the supplier reports them on the same day or on different days.

Example 2: An accounting point agreement previously reported with the same start date as a new agreement prevents the new agreement from coming into effect on the same day. Datahub rejects the latter notification (B) from the supplier.

Example 3: An upcoming agreement reported for the accounting point prevents the creation of an agreement that would be valid until further notice and would begin before the upcoming agreement. This situation may occur when, e.g., a lessor wishes to renovate an apartment before a new tenant moves in, and the tenant has already made an upcoming agreement for the accounting point. In this case, it is only possible to make agreement (B) for the ”in-between” period in Datahub, and the agreement will end before the start date of the earlier agreement (A). The notification for the new agreement (B) must include the agreement end date. The supplier is made aware of agreement A’s start date when it requests preliminary accounting point data before reporting a new agreement. The notification informs the supplier of the date on which agreement B must end.

Example 4: A reported moving in to an accounting point cancels all previously reported upcoming changes of supplier or agreement.

Situation before agreement B is reported:

Situation after agreement B is reported: