Skip to main content
Resources

ICANN Billing and Payments

Instructions for Payments to ICANN

Tax Residency Certificate and Other Tax Related Documents

ICANN ccTLD Contribution Billing

ccTLD ICANN Billing Overview & Frequently Asked Questions (FAQ) – This document provides an overview of the billing process and provides answers to commonly asked questions related to ccTLD contributions.

ICANN Registrar Billing

Registrar Fees Overview

Registrar Billing Frequently Asked Questions (FAQ) - This document provides answers to commonly asked questions regarding Registrar billing and payments processes.

ICANN Registry Billing

Registry Fees Overview

Registry Operators Billing Frequently Asked Questions (FAQ) - This document provides answers to commonly asked questions regarding Registry Operators billing and payments processes.

Billing Changes and Improvements

This section provide visibility into the ICANN Billing process enhancements which are focused on improving the quality and timeliness of invoices it issues to contracted parties. ICANN Billing will provide regular updates on the progress of billing improvements. The updates will be the month following each calendar quarter end. The next update will be in October 2018.

ICANN Billing is committed to providing its contracted parties with accurate and timely invoicing and payment services.

  • ICANN Billing has established high standards of excellence for itself and is continuously working towards achieving them.
  • Ongoing improvements to invoicing and payment services
  • Prompt and centralized responses to inquiries thru ICANN's Global Support ticketing system
  • Continued team development and process improvement

Process Improvements:

  1. The ICANN org created a cross-functional billing process improvement project team that reviews the resources, systems and processes used to produce invoices, collect payments and support requests from contracted parties (May 2017).
    1. The team includes representatives from Finance, Registry Services, Registrar Services, Operations, Contractual Compliance, and Information Technology. The inclusion of all responsible contributors to the process in a cross-functional team better enables us to identify and solve the root cause of problems, rather than only symptoms of issues.
  2. The ICANN org implemented a robust and scalable enterprise-wide resource planning system that is able to provide automation for improved accuracy and timeliness of invoicing (Dec 2016).
  3. The size and capabilities of the finance department personnel was increased by hiring a dedicated billing manager (Cecibel Izaguirre, Dec 2017).
  4. The implementation of quality reviews for the manual processes for updating contact information and emailing invoices was implemented (Jan 2018).
  5. The development of process documentation for training and development of personnel in areas of billing (ongoing).
  6. ICANN Billing has established a policy to ensure that contracted parties' email inquiries to [email protected] are acknowledged or responded to within 3 business days. Automation of the tracking of these targets has been included in the roadmap below.
  7. ICANN Billing implemented automation for the emailing of invoices. This automation reduces the potential for errors in emailing invoices.(July 2018).
  8. ICANN Billing is working on implementing the automation of customer contact information between all internal systems. This automation will reduce the potential for errors in updating changes to the customer contact information
  9. ICANN Billing is working on implementing the automation of customer contact information between all internal systems. This automation will reduce the potential for errors in updating changes to the customer contact information,
    1. NSp to Oracle integration automated on the NSP platform (Jan 2019)
    2. Oracle ERP testing continues through June 2019.
  10. The roadmap table below provides expected timing of these projects along with an estimated go live date.

Roadmap for Improvements:

Billing Process Improvement Roadmap

Updated as of November 1, 2019

A note about our terms of service:

We have updated our electronic terms of service to provide greater transparency and align with laws applicable to us. Learn more.

This site uses cookies to deliver an efficient user experience and to help us see how the site is used. Learn more.OK

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."