Documentation

Buying by invoice

For organisations that need a purchase order. Keys are issued against your organisation ID.

If your organisation cannot buy by card, or needs a purchase order and a conventional invoice, Meridian Software invoices you directly and issues a licence key by hand.

What we need from you

Your Azure DevOps organisation ID. This is a GUID, and it is what the key is bound to.

Find it in Organisation settings → Charter → License, in the Organisation section, with a Copy button next to it. That is the only place in the product it is readable, which is deliberate — it is the one value that must be exactly right.

Send the organisation ID, not the organisation name. A key issued against the wrong GUID will not activate, and the error names both organisations so the mistake is at least obvious. If the ID given at purchase was wrong, we reissue the key at no charge.

How these keys differ

An invoiced key is verified offline. It is cryptographically signed, Charter checks the signature in your browser, and no network call is made. It works in a collection with no outbound internet access, which is the usual reason organisations ask for one.

An online subscription, by contrast, is confirmed by calling Polar.

Everything else is the same: the same tiers, the same per-organisation licensing, the same behaviour at the Standard project limit.

Renewal

An invoiced key carries an expiry date. After it passes, Charter continues to work for a grace period of seven days and tells you a renewal is overdue — every feature stays enabled during grace, it warns rather than restricting.

After grace it drops to view-only, naming the date it expired.

Getting one

Contact Meridian Software with your organisation ID, the tier you need, and your purchase order details.