Summary

  • RIPE NCC says a bank transfer can take up to one week to process and that an unclear or missing reference may prevent it from identifying a payment. It asks members to include the customer and invoice numbers and send proof when Billing Details still shows an outstanding invoice after payment.
  • Under current RIPE-858, payment is due 30 days after invoice; at 60 days without received payment, RIPE NCC sends a final reminder, stops open service requests and suspends the member. At 120 days, if payment remains unreceived, its Managing Director issues termination notice and the member account closes.

One reference field can outrank a bank receipt

Money can leave the bank while the registry's invoice stays marked unpaid. RIPE NCC's payment instructions describe the reason: an unclear or missing reference can keep it from identifying which invoice a transfer belongs to. Bank transfers can take up to a week to process. The customer number and invoice number are operational data, not decorative text in a payment box. A finance team can finish its transfer while a network team still has an unpaid account on the registry's screen.

The unpaid-invoice clock reaches the services behind a Local Internet Registry account. Current RIPE-858 makes payment due 30 days from invoice. If RIPE NCC has not received it, the billing contact gets a reminder. At day 60, the registered contacts get a final reminder; the registry stops work on open service requests and suspends the member. The 2026 billing procedure independently says no new or ongoing requests will be processed after that point without payment. A network operator waiting for a resource request now has a deadline set by accounts receivable. The bank receipt cannot move the registry's queue.

The next boundary is much heavier. If payment is still not received after 120 days, RIPE NCC's Managing Director sends notice terminating the Standard Service Agreement and closing the member account. RIPE NCC's payment page says all the member's LIR accounts close and reactivation requires €1,000 plus outstanding fees. RIPE-858 then describes the end of services, including the ability to maintain resource records, LIR Portal access and its RPKI service, and the deregistration and certificate consequences for affected resources.

Day 60 stops requests and suspends membership; deregistration and certificate revocation are addressed under the termination procedure.

The administrative sequence is the market mechanism. The member initiates the transfer and owns the payment reference. The registry controls the billing match, the service-request queue and the account state. A one-line remittance mistake can create a reconciliation problem in front of a hard service boundary. That is why a finance team cannot close the matter on a bank confirmation alone, and a network team should know whether a pending request is exposed to an unresolved invoice.

RIPE NCC offers a direct way to settle the mismatch: check Billing Details through the invoice's secure payment link and send the billing department proof with the bank-account holder, account number, transaction reference, date, amount and invoice number. The missing facts for any particular operator are its invoice date, transfer record, RIPE NCC payment allocation and correspondence. A matched receipt before the boundary changes the operating position; an unexamined bank debit does not.

The registry can pause a member's resource work while the bank and the registry disagree over a line of text. RIPE NCC controls the service switch because it controls the ledger that decides whether the invoice is paid. That makes reconciliation a continuity control with two owners: the member must send an identifiable payment, and the registry must credit the right invoice. A bank debit closes neither side of that loop by itself.

Sources