bseddon

Yes. The version I have seems to work. As soon as I can find time to do a bit more testing I’ll update the plugin.

The free Simba version does not collect the information needed for MOSS reporting so you must follow the directions offered.

I knew that, just a typo in the readme, fixed now. At least I got it right in the admin notices.

Regards

Bill

Just a short note to let you know that version 1.0.10 has been updated to add support for VAT and rate information recorded by the Aelio EU VAT Assistant plugin.

OK, I can see tax classes in WooCommerce but since a user is able to create any number of classes, how it is possible to map one user defined class to ‘standard’ and another to ‘reduced’?

<<the peak of idiocy for data exchange>>

Agreed.

Have you implemented (or is there an existing WooCommerce) facility for users to specify a rate type for a product? The MOSS plugin will add an option to a product page but it would be better to allow a site administrator to use an existing feature if it exists.

See this page for information about how to content the [SDS team](https://www.hmrc.gov.uk/emcs/software-developers.htm)

The UK output is an ODS or XLSX file formatted by HMRC. Any variation from the prescribed format will not be accepted. I do have a copy of the spreadsheets but I have been asked by the Software Developer Support team not to let out. Apparently the information will be on the HMRC web site ‘soon’. You can contact them to see if they are willing to release a copy to you.

The information required while broadly similar across the EU member states is not the same. None of the Xml formats, or CSV formats or spreadsheets is the same. It might have been nice if they could at least agree a format. It’s interesting to me to note that they have got their act together on a format for auditing where there is one format to be used by all countries but not for MOSS. Maybe it says something about priorities.

ALL the formats require that the registrant identify the VAT rate type as STANDARD or REDUCED on their returns. While it may seem arbitrary, these classes are available for every type of sale (product) on the EC commission web site. It is expected that registrants will apply the rate types on the EC commission web site when completing their returns.

In my VAT plugin for EDD we allow the user to specify, by product, the rate type and the MOSS plugin adds a meta box to the WooCommerce product and EDD download definition pages so the registrant is able to specify the expected rate type.

Of course it conceivable that product ‘A’ is ‘standard’ in France but ‘reduced’ in the UK. So my VAT plugin allows the user to specify VAT rate type by country for each tax class. It’s not really necessary yet because at the moment everything reported through MOSS will be ‘reduced’. However next year, if the idea of applying VAT in the MSCON is applied to all products, it will become more important.

Hi Diego

Thanks for your comments. This is a useful piece of information and will save me hunting around for it later. If there’s nothing reported for VAT then it is likely to be a B2B transaction and not required in a MOSS return. However I will make sure any necessary adjustments are made to the EC Sales List plugin to support EUVA. This way if any EUVA users are in the UK they are able to generate the report as well.

In the meantime, maybe you can help me a little bit further. In the MOSS return required by most countries (Sweden is the exception) VAT and the taxable amount must be aggregated by the member state of the consumer (MSCON) and the VAT rate used. It is usual that each line will be annotated as either ‘Standard’ or ‘Reduced’.

All digital service sales are ‘Reduced’ but in the future this may change, for example if taxing using the rate applicable in the MSCON is extended to sales of physical goods. Is it the purpose of the field ‘tax_rate_class’ to hold this type of information? Or is this field recording the WooCommerce tax class assigned to a product?

Bill

Though I will take a look, it may just work. The MOSS report plugin assumes the VAT applied is stored in the usual place in the meta data of any WooCommerce ‘product’ post and that there is a meta data record keyed by the name ‘vat_number’ if there is a vat number (sales with VAT numbers are not reported though the MOSS of an EU member state).

After a very quick look, it seems that the plugin EU VAT Assistant plugin does meet these criteria.

Another thing I have to check is that the tax rate is stored in the same place as the plugin by David Anderson. But even if not it is likely to be a small change to accommodate this difference.

When I’ve verified this plugin will work with the data stored by the EVA plugin I’ll post an update here.

Bill

Hi

An option to export as a CSV file the same information that would be sent to HMRC based on an ECSL report definition has been added to the plugin.

The new option is available on the edit definition page. That is, it’s available once an ECSL report definition has been created.

Regards

Bill

Sorry for the delay in replying. We’ve been working on releasing our MOSS support plugin.

https://www.ads-software.com/plugins/vat-moss/

The functionality you mention will be available before the end of the quarter.

OK, that wp_localize_script was a bad example. Here’s how it should be and in the flags() function:

wp_localize_script("flags", 'glt_vars', array(
  'translate_text' => apply_filters('glt_translate', 'Translate')
));

Answering my own question. It would be great if you can add a call to wp_localize_script in the plugin’s init function so the translated ‘translate’ can appear in the page to be used in load-toolbar.js:

wp_localize_script("glt", 'glt_vars', array(
  'translate_text' => apply_filter('glt_translate', 'Translate')
));

Then in the JavaScript the translated text to use can be applied:

$('#glt-translate-trigger span').text(glt_vars.translate_text + ' ? ');

And the same for the other trigger.

That’s great. Are you able to share the revised function here so I can remove the messages from my log?

Thanks