[members-discuss] billing problem on multiple lir accounts.

Hi.

Also the NCC could make agreement by means of check box on web site and
don't spend so much time and human resources for the SSA or Additional LIR
Agreement printing and sending by DHL.

Another question: the DHL post wants 100 euro for it's services one way
from Amsterdam to Moscow. Total 200 euro for round trip. To  account
creation, the invoice price cannot be more than 500 euro. So we have 700
euro, but it is not 2000 euro. More over some members from EU pay
additional VAT 20%.

Also the NCC could cancel the membership payment for the quarter, when the
new member account was created. But the non commercial organization cares
about IPv4 pool for new business and takes all efforts for it.

вт, 8 янв. 2019 г., 14:18 Juri hostmaster at ntx.ru:

> Hello,
>
> Any case I hope that a lot of members read. Unfortunately mailing lists
> are not the best way for discussions but we have to follow it because of
> no choice.
>
> I've heard a lot of voices was just about IPv4 stuff. But I am talking
> about bugs in billing and bad algorithms.
>
> For those who think just in "v4" reality I am ready to give another
> fresh example about IPv6.
>
> Example:
> It was request form my LIR to make transfer of v6 range at the end of
> 2018. As far as everybody knows IPv6 and 32bit ASNs doesn't have any
> limitation for transfers (!). RIPE NCC was glad to get ticket for
> processing and billing department suggested to issue extra invoices for
> ~6kEUR to make this transfer happen because of bad rules inside the
> billing department. Here we can see how RIPE NCC stepped on their own tail.
>
> What I can see here? RIPE NCC cry that they have a lot of extra work
> with invoicing and they cancel billing per 3 month. But this example
> shows how they make useless work by themselves. Of course there is no
> any economical reason to pay extra invoices to RIPE NCC and it was
> better to wait 2 extra weeks till 2019 and let this transfer happen. But
> RIPE NCC stuff spend there time on request.
>
> Here I show that RIPE NCC is not optimal and it's too bureaucratic. I am
> talking here about useless issues that RIPE NCC invented by themselves.
>
> I want and I suggest to improve RIPE NCC to make there work easier and
> make members feel more comfortable.
>
> I don't understand people who are not agree that RIPE NCC should fix
> issues. Ideas I suggest do no harm anyone. They give clear and correct
> and easy way for RIPE NCC to bill members and members get clear and
> understandable billing.
>
> RIPE NCC has 20,693 right now. This amount of customers is very small
> for IT company. RIPE NCC doest do any extra services for customers, they
> just keep database. I don't see any problem to make pdf/website invoices
> for companies and program clear and suitable way for payments.
> I don't understand why RIPE NCC spend so much human resources (and let a
> lot of human mistakes!) for billing services.
>
>
> Happy New 2019 Year everybody!
>
> Juri
>
>
>
> On 07.01.2019 10:45, Sebastian Wiesinger wrote:
> > * CloudHost <nikoladavv at yandex.ru> [2018-12-27 13:13]:
> >>    This question discussed earlier, 2 - 3 weeks ago. However nobody did
> >>    support it until they didn't have the same situation. I hope the NCC
> >>    will notice that there are many members, who don't agree with the
> >>    current charging scheme, and will discuss it on the next General
> >>    Meeting from 20-24 May 2019.
> >
> > I don't see many members complaining.
> >
> > Regards
> >
> > Sebastian
> >
> > _______________________________________________
> > members-discuss mailing list
> > members-discuss at ripe.net
> > https://mailman.ripe.net/
> > Unsubscribe:
> https://lists.ripe.net/mailman/options/members-discuss/hostmaster%40ntx.ru
> >
>
>
> --
> Juri
> +7 (499) 346-76-29
>
> _______________________________________________
> members-discuss mailing list
> members-discuss at ripe.net
> https://mailman.ripe.net/
> Unsubscribe:
> https://lists.ripe.net/mailman/options/members-discuss/aleksbulgakov%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20190108/34758174/attachment.html>