Calculation Methodology Licensing

Commercial licence · figures stay on your infrastructure

What the specification covers in practice

Methodology licensing fails most often in the boring places: a rounding rule that looks equivalent but accumulates error over a long schedule, a boundary condition that silently produces a negative payment, or a currency conversion applied at the wrong point in the sequence. The specification this site uses is written to make those decisions explicit rather than implicit in code.

Concretely, the licensed material specifies, for each published calculator:

• Inputs, units and permitted ranges. Every field, its unit, and the values the calculator will and will not accept, so an implementation can reject bad input the same way this one does rather than producing a plausible-looking wrong answer.
• The closed-form expression. The actual mathematics, not a description of it, so an auditor can reproduce any published result in a spreadsheet and confirm it.
• Rounding order and precision. At which step rounding occurs, to what precision, and whether intermediate values are rounded at all. On amortisation schedules this is the difference between a total that is off by a few units and one that drifts visibly over thirty years.
• Failure behaviour. What the tool does when an assumption is impossible — a negative term, a rate of zero, a term of zero months — rather than returning an undefined or infinite result.
• Known limitations. What the calculation does not capture. This site states these on the tool itself; a licensed implementation inherits the same obligation, because an undisclosed limitation is what turns a calculation into a false claim.

This is the same material already published on the site’s methodology page and applied across its calculators — documented transparently because a finance figure that cannot be checked is not worth using.

What you get

• 1
  The calculation specification. Every formula, every rounding rule and every boundary condition, written so an engineer can implement it and a reviewer can audit it. The same methodology already published on this site’s methodology page.
• 2
  Reference test vectors. Published inputs with their exact outputs, so an independent implementation can be checked against a known-good baseline rather than trusted.
• 3
  Provenance rules. How a figure earns the right to appear on a page: the primary-source requirement, the retrieval-date discipline, and the classification scheme this site applies to its own banking data.
• 4
  Correction and update path. How a changed figure or a revised formula is published and dated, so your readers can see what moved and when.

What this is deliberately not

This licence covers how a number is calculated and how it is evidenced. It does not transfer, and must not be read as transferring:

• Financial, legal or tax advice. A licensed implementation is a calculation tool. The licence does not make the licensee’s product advice, and no part of it should be presented as a recommendation to take or avoid any financial action.
• Any regulated permission. Nothing here authorises a licensee to operate under any regulator’s rules. Regulatory permissions are obtained from the regulator, independently.
• Product endorsement. The licensee’s product, brand and editorial judgement remain entirely their own.
• The trust promise. The privacy position described on this site — calculations run locally and nothing is transmitted — is a property of the reference implementation, not a licence obligation. If you change where computation happens, you own that change.

Licensing tiers

• Reference — $12,000 / year. One named publication or product. Full specification, test vectors and provenance rules. Annual renewal; updates included.
• Organisation — $36,000 / year. Unlimited properties within one legal entity, with a named technical contact and a scheduled methodology review.
• Network — quoted. White-label distribution across third-party sites. Priced on distribution scope and support commitment.

Why the provenance rules travel with the licence

A calculator that is arithmetically perfect but cannot say where its inputs came from has the same problem this site spent 2026 fixing. When this site audited its own banking dataset it found 175 published figures with zero verified retrieval dates. The licence therefore includes the classification scheme, so a licensee can measure the same thing about their own data instead of assuming it is fine.

That measurement is published in full on the site’s editorial policy and methodology pages.

The rest of the licensing surface

This licence covers the method — how a number is calculated and evidenced. Two adjacent products license the artefacts themselves, and they are usually bought together:

• Embeddable calculator engine — from $400 / month. The calculation code itself, licensed to run inside your own product. You can verify it before buying: it is the same interface this site runs.
• Banking data API — from $750 / month. The regulator-linked country and division dataset behind this site’s banking directories, as JSON with a provenance classification per field.

How to start

Commercial enquiries are handled directly. Describe the product, the audience and the jurisdictions you cover, and the specification will be shared before any commercial discussion — so you can decide whether it is useful before there is anything to buy.

Contact AINext Growth