Billing
8 TopicsUpcoming Price Adjustments - Cross Connects
Hi Community - Just wanted to share a copy of this announcement incase you missed it. Deutsch (German) • Español (Spanish - Latin America) • Español (Spanish - Spain) • Français (French - Canada) • Français (French - France) • Italiano (Italian) • Polszcyzna (Polish) • Português (Portuguese - Brazil) • Português (Portuguese - Portugal) • Türkçe (Turkish) • български (Bulgarian) • 日本語 (Japanese) • 中文 (Chinese Simplified) • 한국어 (Korean) Due to global macroeconomic conditions, including rising energy, construction, and labor costs, we are increasing rates for Cross Connects. This adjustment ensures that we can continue to invest in the digital infrastructure and ecosystems that you depend on for your business. Cross Connects Effective 1 August 2022, standard pricing for new Cross Connects will increase. Price adjustments for new Cross Connects vary by media type and country. Existing Cross Connects are not impacted; new rates will apply to new Cross Connects orders placed on or after 1 August 2022. Cross Connects orders placed prior to 1 August 2022 will be charged the current rate, even if the order is fulfilled after 1 August 2022. If you have questions or would like to review your options, please contact your account manager. Thank you, Equinix Product Management The world's digital infrastructure company5.3KViews0likes0CommentsImproving Expedite Smart Hands Process and Flexibility
I am an Equinix customer who has experienced the Expedite Smart Hands service on several occasions. While I appreciate the overall service and response times, I have encountered some challenges related to scheduling and billing that I believe could be improved. Currently, when a customer raises an Expedite Smart Hands request, the ticket goes to OPS for approval, and the customer is informed that the request will be reviewed within 2-6 hours. However, there have been instances when OPS is unable to accommodate the expedited request, and the only option they have is to ask the customer if an alternative date and time are suitable. In such cases, if the customer agrees to the rescheduled time, they are still charged the extra expedite fee, even though the request was not fulfilled as initially planned. Additionally, many tickets end up being auto-canceled if the customer doesn't make a decision, leading to frustration and the need to submit a new ticket. To enhance the customer experience and improve flexibility, I suggest providing OPS with the option to arrange a new time with the customer and "un-tick" the expedite charges on the ticket. This way, the ticket can remain active and transition to a "standard smart hand" with a new commit date that OPS can handle without the need for the customer to resubmit their request. I believe this improvement would streamline the Expedite Smart Hands process and result in greater customer satisfaction. Thank you for considering my suggestion.1.9KViews1like1CommentBilling v2 API deprecation?
Hello, today I noticed that on the API documentation overview page it says that the Billing_v2 API is Deprecated. I can't find any further information on that and also noticed that, in contrast to the WorkVists_v1 API which is marked in the same way, no deprecation information can be found on the actual documentation page. Would you be able to provide some more information on the deprecation or links to where I can find it? I'm especially interested in whether this API is actually going to be disabled in the future and if there's any alternative to obtain invoice information programmatically and machine-readable. Thanks, JonasSolved49Views1like3CommentsInconsistent monetary information for Japan via Billing v2 API
Hi, we have a presence in different Equinix data centers and retrieve billing information via the Billing v2 API. We observed that the information we obtain for the Japan invoice (and that one only) has inconsistent (dare I say wrong?) tax amount values across time: For invoices from 2024-02 (oldest I have) until 2024-05 (which is not downloadable anymore due to the 12 month limit but I have a local copy) the Japanese line items behave exactly like all others we can observe, namely: non-zero taxAmount (10% of recurringAmount) and recurringAmount + taxAmount = totalAmount. For invoices from 2024-06 until 2024-08 (both in the snapshot I had from a few months ago and the one I just took now) the Japanese line items now still has a non-zero taxAmount (10% of recurringAmount) but totalAmount = recurringAmount. Checking a few entries we saw that the netAmount is the same as in previous entries which makes me assume that the totalAmount does not include any tax amount. For invoices from 2024-09 onward the Japanese line items now all have taxAmount = 0 and totalAmount = recurringAmount. This means that we are unable to obtain any tax information from the invoice other than assuming that the 10% applies to all line items. Furthermore, this data is inconsistent with the reality that there is tax to be paid. Could you explain why the data is so inconsistent, changing multiple times withing a few months? Could you also explain why the data for invoices since 2024-06 is inconsistent with the reality? Is there any resource where changes in the API are documented and where I could have learned about these changes? What can we expect moving forward? Should we expect the data to change again, hopefully to be correct again as it was pre 2024-06? Thanks JonasSolved20Views0likes3Comments