Summary

  • AFRINIC’s June 2020 register records a narrow but important corporate control: Resolution 202006.559 required Board approval for bank transactions above USD 100,000. “Above” is a strict boundary. The record does not establish that a transaction of exactly USD 100,000 fell within this particular checkpoint, and it does not establish what counted as one transaction when instructions were related, recurring, staged or divided.
  • Collective review of unusually large bank movements is a reasonable safeguard for a private organization. It can limit unilateral exposure, require a documented purpose and supporting authority, and fix responsibility before funds move. But approval is only one state. It is not a signature, bank release, settlement, ledger reconciliation or audit result, and the public entry does not identify the signatories, combinations, exchange-rate convention, timing rule, exception route or evidence connecting those states.
  • The proportionate answer is not disclosure of accounts, credentials, signatures or counterparties. It is a privacy-safe transaction passport that records the transaction family, aggregation key, original currency, pre-declared conversion basis, approval time and reference, operative signatory mandate, any exception and ratification state, bank acknowledgement, settlement, reconciliation and document custody, with aggregate reporting that allows members to test the control without exposing banking security.

A precise gate with an undefined approach

Imagine a proposed large bank movement arriving at the edge of a corporate control. The amount is known in its original currency. There is a purpose, a payment instruction and some underlying commercial authority. Before anyone asks whether the bank accepted the instruction or whether the entry later appeared in the ledger, one question comes first: does the proposal cross the escalation line at which the Board must approve it?

For Resolution 202006.559, the visible line is unusually crisp. AFRINIC’s register for June 2020 says that Board approval was required for bank transactions above USD 100,000. That sentence makes a real institutional choice public. It tells readers that the Board reserved a class of large movements for collective decision rather than leaving every amount within ordinary delegated handling. It also supplies the first element needed for accountability: an amount and a responsible corporate body.

The most important word is not “Board” or even “USD.” It is “above.” In mathematical terms, the public wording expresses a strict greater-than relation. An amount greater than USD 100,000 crosses the stated line. An amount equal to USD 100,000 is not shown by this resolution entry to cross it. That does not prove how exactly USD 100,000 was treated under some other policy, mandate or authority instrument.

It means only that the available wording cannot honestly be enlarged into “at or above,” “USD 100,000 and above,” or “greater than or equal to.” A control can be weakened by vagueness, but it can also be distorted by well-intentioned paraphrase. Here, verbal precision is part of the control.

That precision does not answer what approaches the gate. “Bank transaction” appears simple until an organization must apply it to real economic activity. Is the relevant unit one payment instruction, one invoice, one contract, one supplier relationship, one project, one Board-approved purpose or a group of instructions that are economically connected? If a recurring obligation produces several payment dates, is each date evaluated alone? If a commercial commitment is settled in stages, is the threshold tested at every stage or against the connected whole? If fees are debited separately, do they belong to the same transaction family?

The June 2020 entry does not establish an answer to any of these questions.

This uncertainty must be handled carefully. It is not evidence that anyone divided a movement to avoid scrutiny. No actual split instruction, avoidance attempt, payment or beneficiary is identified. It is a control-design question: economically similar activity can receive different treatment if its identity depends only on the shape of the bank instruction. Two unrelated movements should not become one merely because they occur on the same day. Conversely, a connected series should not automatically escape collective review merely because a bank displays it as several lines.

A usable threshold therefore needs an aggregation rule that distinguishes genuine independence from economic unity before the amount is tested.

A good rule would define a transaction family in neutral terms. It might use a shared contract authority, purchase purpose, counterparty class, project, invoice series, payment schedule or other stable connection, while allowing documented reasons why superficially similar instructions are separate. The precise choice is for AFRINIC’s private financial governance, not for an outside observer to dictate. The accountability principle is narrower: the organization should be able to reproduce the grouping decision later, using a rule declared before the desired approval route is known.

The same concern applies to foreign exchange. USD 100,000 is a clear unit of account only when the proposed movement is itself denominated in US dollars. A movement in another currency needs conversion. Around the boundary, the chosen rate source, date and time can determine whether the USD equivalent sits below or above the line. Fees can shift the result depending on whether the threshold tests the instructed principal, the account debit or some gross economic amount. Rounding can matter at the margin. None of these fields is established by the public entry.

Again, the gap proves no manipulation. Exchange rates move, institutions use different legitimate sources and banks may calculate debits differently from accounting systems. The safeguard is a stable convention: name the rate source, choose the relevant timestamp or reference period, decide how fees and rounding are treated, and apply that convention before knowing which result is more convenient. A pre-declared convention makes equivalent decisions comparable. A rate selected after the approval path is apparent turns a numerical rule into a discretionary one even when each selected rate could be defended in isolation.

Time creates a third approach problem. A bank movement has many potentially relevant moments: commercial commitment, budget authorization, contract signing, invoice approval, preparation of a payment instruction, Board decision, authorized signature, release to the bank, value date, settlement and reconciliation. Resolution 202006.559 exposes the need for Board approval but does not establish which moment the approval had to precede. It does not show whether the control attached only to the outgoing bank instruction or also required collective consideration before AFRINIC became commercially committed. It does not show whether a later ratification path existed.

The cleanest reading is not to invent an answer but to keep the verbs separate. A Board can approve a proposed transaction. An authorized person or combination can sign an instruction. A bank can accept and release it. The movement can settle. Finance staff can reconcile the settlement to the approved purpose and the ledger. Reviewers can later test the chain. Each verb names a different fact, supported by different evidence. A minute showing approval cannot prove that the operative bank mandate was followed. A signature cannot prove that the bank released the instruction. A bank acknowledgement cannot prove settlement.

A ledger entry cannot retroactively create authority that was required earlier.

This separation also clarifies why the threshold’s benign case is strong. A private Board may reasonably reserve unusually large movements for collective scrutiny. The point need not be suspicion. Large movements can create concentrated exposure even when they are entirely proper. Requiring a Board decision can compel management to identify the purpose, budget, commercial basis, amount, currency and risks before execution. It can distribute responsibility across a corporate body and create a contemporaneous record that protects the organization as well as its members.

It may also protect staff by ensuring they are not left to carry an exceptional decision under a routine delegation.

Nothing in the available record shows that this safeguard failed. Nothing identifies a delayed payment, rejected instruction, unauthorized transaction, loss or service consequence. The constructive question is therefore not whether Board approval was too demanding. It is what minimum bridge would allow a later reviewer to connect the numerical gate to the economic activity and to the successive acts that followed.

That bridge begins with a small set of boundary fields. The proposed movement needs a stable identifier and a transaction-family or aggregation key. It needs an original amount and currency, a named conversion source and timestamp where conversion is necessary, treatment of fees, and a rounded USD equivalent. It needs a statement of which moment the calculation governs and an approval reference dated before the relevant execution point. These fields do not expose an account number or confidential commercial detail. They establish why the transaction did or did not cross the line and allow the organization to repeat the decision later.

One can see the stakes by comparing two kinds of clarity. Resolution 202006.559 gives rule clarity at the highest level: above a named amount, the Board is responsible for approval. Operational replay requires application clarity: this was the transaction unit; these connected instructions were aggregated, or were not, for a recorded reason; this was the conversion convention; this was the controlling moment; and this was the approval state at that moment. The first is valuable. The second is what makes the first verifiable without turning private banking into public spectacle.

The distinction matters especially for a membership institution. Members do not need online access to sensitive payment files to ask whether a large-transaction rule has meaning. They need confidence that the rule is applied consistently and that corporate records can answer a bounded question after the event. NRS’s transaction-by-transaction authority perspective is useful here: authority should be traceable for the particular act under consideration, rather than inferred from a title, a general reputation or a later outcome.

That is an accountability test, not evidence that NRS approved, signed, banked or reviewed any movement under the resolution.

The strict line therefore deserves neither exaggeration nor dismissal. It is not merely decorative language; it allocates responsibility for an important private act. Nor is it a complete account of control. Its meaning depends on the transaction brought to it, the currency basis used to value that transaction and the time at which approval is tested. Those are the questions on the approach to the gate. The next layer is the bridge beyond it: who may carry an approved instruction forward, and what record proves each handoff?