Weaselior
commented
7 years ago Ask: I would like the Journal for corporate wallets to include, in the reason field on any tax transaction, the isk value used to calculate the tax - even if the tax was 0 isk. In other words, each tax is calculated by CCP creating some isk value, X, and multiplying it by a tax rate (say, 1%), and calculating the end tax - here, .001*X. I want "X Isk" included in the "reason" field.
Goal: To allow alliances to effectively tax corporate structures. Currently only the end tax is visible - that a corporation collected Y isk from a taxed event. This change would allow alliances to set their own tax rate and charge it to the corporation. E.g. the alliance could demand 0.5% of the initial amount, and the corporation would be free to charge 2% (via the in-game taxation methods) and pocket 1.5%, or charge 0% and pay the 0.5% out of pocket. Alliance tax collection and calculation would be done via external taxation systems reading the API information.
Currently, all an alliance can do is demand a percentage of the amounts charged (so if a corporation earns 100 isk, the alliance demands 50 isk - but doesn't know what tax rate was charged to create that 100 isk). A corporation could charge its members (or a select group of people) much lower rates than other people pay and so the alliance isn't able to enforce consistent taxation. Fixing this would require exposing and tracking ACLs, the associated tax values, and add much more overhead on the CCP side and the user side.
By making the raw isk value visible, you allow an alliance to simply read off the isk amounts and calculate any taxes it wishes to charge off the raw isk value. The raw isk value should already be computed by EVE so the issue is merely exposing it to the journal entry (and then externally via API). This would apply to ALL taxable events: refining taxes, broker taxes, industry taxes, etc.
So in my example, we would have our alliance set a 1% industry tax. We would use our api system to read the isk value of each industry job that created a tax journal entry. We would then calculate 1% of that amount, and add it to our internal ledger for the corporation. That corporation, at the end of the month, would pay the alliance the appropriate amount, funded through the corporation setting whatever taxes it wished on its industry structures.
Currently, alliances like mine simply have to ban any corporations owning structures we seek to tax, except our executor corporations which charge the taxes we want to impose. Making this change would allow us to let any corporation drop structures while the alliance is still able to know what tax it is looking to charge each corporation.
joelhousman
Ask: Would like Journal for corporate/alliance wallet(s) to include refTypeIDs for:
Goal: Looking for greater granular visibility into source of corporation wallet income from structure services. It would be nice to see how much is is coming from each service in each citadel, and who is consuming the services. Presently all structure services income aggregates into corporate wallet with no ability to see which corporately owned structures its coming from.