Summary

  • AFRINIC's live billing timeline says renewal invoices are issued and released on 1 November, payments received through 31 December qualify for a 5% discount, and invoices are due on 31 January. The prose on the same page says the discount applies to payments received before the invoice date.
  • This can be a defensible two-date system: an invoice may be delivered before the date printed on it. The public page does not name that document date or define which event makes a card or bank transfer “received”. No reviewed evidence shows an actual billing error or a member denied a discount.
  • Five per cent ranges from USD 50 to USD 1,920 across AFRINIC's published LIR annual-fee bands. A settlement receipt should join release, invoice date, cutoff, payment event, reference matching and the resulting credit without disclosing a member's private account.

One invoice, two clocks

A billing department can put an invoice in a member's hands before the date printed on the document. There is nothing inherently suspect about that arrangement. It can give the payer time to route a cross-border transfer, complete internal approval and earn a discount before a new service year begins. The difficulty starts when a public rule uses “invoice” to mean both delivery and document date without saying when it changes meanings.

That is what AFRINIC's current public material asks a reader to reconstruct. The Fees & Payment page opens its annual timeline on 1 November with the instruction to issue and release all renewal invoices. The next interval runs from 1 November to 31 December and says payments received qualify for a 5% discount. The invoice due date is 31 January. Farther down the same page, the discount is defined as applying when an LIR member's annual renewal payment is received before the invoice date. Existing members are told that invoices are sent at the beginning of November and that payment is due 30 days after the invoice date.

The live Member Guidebook Reference repeats the essential combination. Invoices are issued at the beginning of November preceding the membership period. The early-settlement discount applies when payment is received before the invoice date. The late-payment account is built around a 31 January due date and a February moratorium.

These statements point towards two clocks. The release clock begins in November. The legal or accounting clock appears to be attached to the date of the invoice and the calendar-year renewal. A document date around the start of January would make the thirty-day path to 31 January intelligible. But the current pages do not state that bridge in the place where they ask a member to act on it. A reader should not have to infer a control date by subtracting thirty days from a deadline.

The strongest defence is operational, not rhetorical

The fair reading comes first. Actual invoices may display every relevant date. MyAFRINIC may calculate eligibility automatically. Billing emails may explain that the document is delivered in November for the coming year, bears a January date and attracts a five-per-cent credit when full payment arrives by 31 December. Staff may reconcile bank transfers with care and correct edge cases. The absence of those private records from this review is not evidence that they are absent in operation.

Nor is there anything improper about an early-payment incentive. A member-funded registry has payroll, infrastructure, security and continuity costs. Earlier cash can improve planning and reduce collection risk. Members receive a measurable benefit for surrendering liquidity sooner. The arrangement can be mutually useful.

AFRINIC's Registration Service Agreement also gives the fee schedule real weight. It requires renewal fees within thirty days after invoicing, permits fee changes with advance publication, and attaches a possible late penalty to the invoice-date boundary. Ordinary renewal follows the calendar year. The membership-agreements page identifies English as the binding text. Together, those instruments make precision more, not less, valuable. A calendar displayed for convenience should reconcile with the agreement that governs consequences.

The narrow finding is therefore documentary. Four public facts are individually visible—November release, a discount through December, a January due date and a rule keyed to the invoice date—but the public join among them is not. The article does not establish an overcharge, a lost discount, a wrongful penalty, a service interruption or an unlawful term.

“Received” is the consequential verb

Even a named invoice date would leave one important control undefined. A card transaction and a cross-border wire do not pass through time in the same way.

A card can be authorised on one day, settled through the acquiring bank on another and posted to the member's registry account later. A wire can leave the member's bank before a cutoff, acquire a value date in an intermediary chain, reach AFRINIC's bank after a weekend and remain unmatched until the payer's reference is identified. The fee page asks members to include a customer number, invoice number or organisation name precisely because matching is a separate operation.

Which event is “received” for the discount? It might be processor authorisation, irrevocable settlement, credit to AFRINIC's account, bank value date or the moment staff match funds to an invoice. Each choice can be reasonable. They do not always produce the same result near 31 December, especially when time zones, public holidays, compliance reviews or an incomplete reference intervene.

The rule need not publish bank-account details or member transactions. It should name the event. If card authorisation before the cutoff is sufficient, say so. If funds must be credited to AFRINIC's bank, say that. If an unmatched transfer is provisionally protected when the remittance message carries enough evidence, define the cure window. A deadline without an event is only half a clock.

Five per cent is small until the top of the table

The published LIR annual-fee bands run from USD 1,000 for the smallest listed category to USD 38,400 for the largest. Five per cent of those endpoints is USD 50 and USD 1,920. In between, the discount is USD 70 on a USD 1,400 fee, USD 320 on USD 6,400, USD 640 on USD 12,800 and USD 1,125 on USD 22,500.

These are mechanical calculations, not bills. A member's status, resource mix, taxes, currencies, other charges and eligibility can change the amount actually due. The arithmetic matters because it shows why a vague cutoff is not mere copyediting. For a larger LIR, the difference can exceed the service charge attached to several alternative billing arrangements. For a smaller operator, even a smaller dollar amount may compete with local working capital or bank fees.

The distribution is also asymmetric. A well-capitalised member can approve and transmit funds early. A smaller operator may be waiting for its own customers, foreign-currency access or a multi-signature public procurement process. That does not make the discount unfair by definition. It means AFRINIC should make the bargain executable: how early, measured by what event, and credited where?

An Official Receipt is evidence, not the whole rule

The fee page directs members to log in and download an Official Receipt as confirmation that payment has been received. That is a useful control. A receipt can settle the most basic dispute: did AFRINIC record the money?

It may not settle the discount question unless it also records the rule version and relevant timestamps. A receipt generated on 3 January could describe funds credited on 30 December, or it could reflect a transfer only matched on 3 January. A number alone cannot show whether the discount cutoff was satisfied. Likewise, a negative or zero account balance can prove a present accounting state without explaining which discount was applied to which billing year.

The evidence chain needs six joins. First, what billing year is the invoice for? Second, when was it released? Third, what date does the document bear? Fourth, what exact event and timezone determine receipt? Fifth, how was the payment matched? Sixth, where did the five-per-cent benefit appear—on the current invoice, as a credit balance or on a later renewal?

AFRINIC can answer those questions with a compact private receipt for the member and an aggregate public specification. It does not need to publish names, bank references or account balances. It needs to publish the schema of the decision.

What a settlement receipt should contain

The receipt should identify the billing year, invoice release timestamp, document date, due date and early-settlement cutoff with timezone. It should name the eligible membership class and the version of the fee schedule used. It should show the invoice amount and currency, while distinguishing exchange conversion and bank charges from the discount base.

For the payment event, the receipt should record the channel and the operative timestamp. A card record might show authorisation and settlement. A wire record might show bank value date, credit time and reference-match time. If only one of those events controls eligibility, it should be marked as the decision event.

Finally, the receipt should show the calculation: eligible base, five-per-cent amount, final application of the credit and remaining balance. If the payment arrived on time but could not initially be matched, the receipt should preserve the original evidence and the correction. If staff reject eligibility, the member should receive a reason tied to the rule version and a route for correction.

This is deliberately thinner than a billing audit. It does not ask AFRINIC to publish every invoice or expose commercial information. It turns an outcome into a reproducible decision.

The public record has limits

The source set establishes what AFRINIC currently tells the public. It does not show the production billing configuration. It does not show an invoice's printed date, a settlement file, a banking delay, an individual member's status or the accounting destination of the discount. It also does not show that anyone complained.

Those limits matter. Documentation gaps are not operational failures. A page can lag a mature internal process. Equally, a mature internal process should be easy to describe without forcing readers to infer dates. The right remedy is a versioned rule and receipt, not an allegation.

The four reviewed first-party sources are AFRINIC's fee schedule and payment page, Member Guidebook Reference, Registration Service Agreement and membership-agreements index. They were read as distinct instruments: operational timeline, member guidance, contractual frame and authority index.