Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Our Spanish customer switched from SII version 1.0 to 1.1. I used the functionality from the last NAV 2016 cumulative update (33). We are able to transmit without problems, but I see that for intracommunautary documents, the system does no longer create a "Regular" and "Intracommunautary" entry (see below). Is this correct or is there still a bug in the system?
Thanks for any help,
I´m not an expert on the Microsoft SII Solution, since when they released the first version (shortly before it became mandatory), I studied the code and found it totally unacceptable for my customer, as it only managed basic things and contained a lot of bugs.
After looking into other partners offerings, I realized that none covered the complex needs and ended up designing my own module.
However, one of the many things that shocked me about MS (and many others) design, was the fact how they misinterpreted AEAT's Intracommunitary Documents requirement:
The ledger name is "SPECIFIC intracommunitary operations", and regular invoices to EU-customers or from EU-vendors should not generate an Intracommunitary SII Document. Instead, they are just regular invoices with IDType=IDOtro (Key 02=VIES-VAT) - of course Liable & Exempt (sujeta exenta) with cause E5 (sales) or Liable Type S2 with ISP (purchases). The only exceptions are Invoices that comply with AEAT's definition (in English):
That way, the only operations my customer declares in the DOIC Ledger are stock transfers between their own warehouses in other EU countries outside of Spain. On the other hand, regular EU sales and purchases are only declared as LRFE/LRFR.
I'd recommend you make sure that your customer's EU-Invoices do not fall under the SPECIFIC definition as above.
If they don't, then declaring them as "Regular" is correct. If not: you'll need to resolve that (and it might indeed be a bug).
Please bear in mind that entries should not be duplicated: either you have a normal LRFE/LRFR or you have a DOIC.
Hope this answer helps,
Thank you Bleika. Your answer helps a lot. Implementing the Microsofts SII solution has indeed been a hard job;-). I don’t think my customer falls under the “specific” definition. So a “regular” entry will be fine.
Business Applications communities