Summary

  • RIPE NCC’s archived business-applications plan marks the work needed for yearly invoicing 2027 as completed in Q3 2026, but the adopted scheme says member fees will be determined from data gathered on 31 December 2026 and invoices sent in January.
  • The missing bridge is not another debate about fee fairness. It is a privacy-safe calculation trace that shows which rule, snapshot, charge classes, software version and exceptions produced each bill.

The finished system and the unfinished evidence

There are two clocks inside RIPE NCC’s new charging year. The first belongs to software delivery. In its archived Q3 2026 Business Applications plan, RIPE NCC says that the May vote required work in internal and external applications to comply with the principles for yearly invoicing 2027. The status is “Completed in Q3 2026.” Curiously, the paragraph sits beneath a heading called “New Navigation Framework”; the body, not that stray label, is the useful evidence.

The second clock belongs to the bill. The charging scheme adopted as Resolution 3 at the May 2026 General Meeting says fees per LIR account will be determined from data gathered on 31 December 2026. Invoices go out in January 2027. On 9 September, therefore, the software can be complete while the decisive input population is necessarily unfinished.

That is not a contradiction. A registry should implement a charging decision before the cutoff, test its integrations and leave time for operational preparation. But a completed implementation is not yet a reconciled billing run. The latter requires a particular snapshot of member, LIR-account, ASN, independent-resource, sponsorship and Legacy-resource state; a particular interpretation of the adopted text; and a particular version of the calculation engine.

The distinction matters because Model A is simple only from a distance. The annual fee is EUR 1,894 per LIR account, up from EUR 1,800 in 2026. The first ASN assignment registered to an LIR account is included; additional ASN assignments cost EUR 50 each. Independent Internet number resource assignment registrations cost EUR 75, covering IPv4 and IPv6 PI, Anycast, and IPv4 and IPv6 IXP assignments. Sponsored Legacy IPv4 registrations remain EUR 75, and direct-contract Legacy IPv4 registrations acquire the same EUR 75 charge from 2027. The one-time sign-up fee remains EUR 1,000 per new LIR account.

Each sentence is clear. Their application can still turn on state and classification. Which ASN is treated as the included first assignment? Which records belonged to an LIR account at the cutoff? Was a Legacy registration sponsored or held under a direct contract? Did a new account trigger the sign-up fee, and under which of the scheme’s Legacy-holder exceptions? A price list cannot answer those questions without a dated input record.

A vote approves the rule, not the output

The General Meeting results say 3,049 votes were cast and that Resolution 3 adopted Model A. The 3,049 figure is the total number of votes cast at the meeting, not the number of votes in favour of that resolution. More importantly, a valid vote authorises the charging rule; it does not verify the later extraction, classification, calculation, invoice delivery or correction process.

This is where governance often loses sight of evidence. Institutions publish the decision and then publish the bill, leaving the transformation between them inside an application. If the amount is challenged in January, support staff and members must reconstruct the transformation after account or resource state may already have changed. A correct result can then become expensive to prove. An incorrect result can take longer to isolate because the dispute mixes source data, business rules and software behaviour.

RIPE NCC does not need to expose member data to fix that. Before 31 December it can publish the calculation schema, the rule-version policy and anonymised worked examples for edge cases. With each January invoice it can provide the authenticated member with a compact trace: the charging-scheme version; cutoff timestamp and snapshot identifier; number of billed LIR accounts; the included first ASN and count of additional ASNs; independent-resource counts by charge class; sponsored and direct Legacy counts; sign-up-fee state; exceptions; calculation-engine version; line-item totals; and a correction route.

Such a trace is not an accusation disguised as compliance. It is the ordinary receipt for an automated institutional decision. It lets a member ask a narrow question—wrong snapshot, wrong classification, wrong rule or wrong arithmetic—rather than opening a general dispute about the invoice. It also lets RIPE NCC aggregate exception and correction rates without publishing confidential accounts.

The strongest objection is practical. A quarterly plan can reasonably call work complete when code, integrations and procedures have shipped. No one can freeze 31 December data in September, and no responsible registry should publish member-specific billing records. That objection is right about both timing and privacy. It is not an argument against evidence; it is an argument for separating implementation completion from billing reconciliation. The public schema can exist before the cutoff. The private trace can arrive with the bill.

No source reviewed for this article establishes a wrong invoice, a software defect, an outage, member harm or a support failure. The completion label is RIPE NCC’s own project-status statement, not an independent audit. Nor does the published price table prove what any particular member will owe. The claim is narrower: the first live bills are the first moment at which the completed system can be tested against the final population it was built to charge.

Sources