ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

PaymentNotice — Payment notification

"Payment was issued on 14 May 2026 for 1,250 USD." A simple notification, without line-by-line allocation detail — to point the recipient to the associated PaymentReconciliation.

Purpose

PaymentNotice is a short notification: the insurer informs the provider (or vice versa) that a payment has been issued for a given Claim. It is light, does not carry the line-by-line details — see PaymentReconciliation for that.

Key fields

FieldTypeCardinalityRole
identifierIdentifier[]0..*External identifiers.
statuscode1..1Mandatory. active, cancelled, draft, entered-in-error.
requestReference(Any)0..1Original Claim or request.
responseReference(Any)0..1Corresponding response (ClaimResponse).
createddateTime1..1Mandatory. Notice date.
reporterReference(Organization | Practitioner | PractitionerRole)0..1Notice issuer.
paymentReference(PaymentReconciliation)0..1Detailed reconciliation.
paymentDatedate0..1Effective payment date.
payeeReference(Organization | Practitioner | PractitionerRole)0..1Payment beneficiary.
recipientReference(Organization)1..1Mandatory. Notification recipient.
amountMoney1..1Mandatory. Paid amount.
paymentStatusCodeableConcept0..1Payment status (paid, cleared, returned).

JSON example

Notification of 1250 USD payment to the hospital:

json paymentnotice-001.json
{
  "resourceType": "PaymentNotice",
  "id": "pn-2026-001",
  "identifier": [{
    "system": "urn:oid:1.2.34",
    "value": "PN-2026-001"
  }],
  "status": "active",
  "request": { "reference": "Claim/claim-2026-001" },
  "response": { "reference": "ClaimResponse/claimresponse-2026-001" },
  "created": "2026-05-15T11:00:00+02:00",
  "reporter": { "reference": "Organization/insurer-x" },
  "payment": { "reference": "PaymentReconciliation/pr-2026-005" },
  "paymentDate": "2026-05-14",
  "payee": { "reference": "Organization/hospital-1" },
  "recipient": { "reference": "Organization/hospital-1" },
  "amount": {
    "value": 1250.00,
    "currency": "USD"
  },
  "paymentStatus": {
    "coding": [{
      "system": "http://terminology.hl7.org/CodeSystem/paymentstatus",
      "code": "paid"
    }]
  }
}

Common pitfalls

  • Including line-by-line detail — PaymentNotice is a short message. Detail goes in PaymentReconciliation.
  • No payment link — without a referenced reconciliation, the notice is blind: what does the amount correspond to?
  • Missing currency in amount — EUR vs USD: costly ambiguity.
  • Confusing payee and recipient — payee = who gets the money, recipient = who gets the notification (could be a third party, intermediary or office).
  • active status without actual payment — creating a PaymentNotice before effective payment creates accounting noise.