Example with explanation per field or paragraph
The obvious fields will not be explained.
<cac:AccountingSupplierParty>
This paragraph records the details of the party that sent the invoice. So for purchase invoices, this is the supplier and for sales invoices, this is the Yuki user. This is a paragraph consisting of the following sections.
<cbc:CustomerAssignedAccountID>xxxxx</cbc:CustomerAssignedAccountID> (is not yet filled)
<cac:Party>
<cbc:WebsiteURI>http://www.company.com</cbc:WebsiteURI>
(The Uniform Resource Identifier (URI) of the Party will not be filled yet)
<cac:PartyIdentification>
<cbc:ID>27124701</cbc:ID>
(This field is filled with the Chamber of Commerce number or trade register number)
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name>KPN BV</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>Maanplein 55</cbc:StreetName>
<cbc:CityName>Den Haag</cbc:CityName>
<cbc:PostalZone>2516 CK</cbc:PostalZone>
<cac:Country>
<cbc:IdentificationCode>NL</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyTaxScheme>
<cbc:RegistrationName>KPN BV</cbc:RegistrationName>
<cac:TaxScheme> (tax code from list of UN)
<cbc:ID>VAT</cbc:ID> (VAT, other TAXSCHEMES will not occur)
<cbc:TaxTypeCode>BTW</cbc:TaxTypeCode>
</cac:TaxScheme>
</cac:PartyTaxScheme>
<cac:PartyLegalEntity>
<cbc:RegistrationName>KPN BV</cbc:RegistrationName>
<cbc:CompanyID>27124701</cbc:CompanyID>
</cac:PartyLegalEntity>
</cac:Party>
<cac:AccountingCustomerParty>
<cac:PaymentMeans>
This refers to the payment condition. Here the list of the UN is referred to once again. There are some example lists:
<cbc:PaymentMeansCode>1</cbc:PaymentMeansCode>
(1 = Instrument not defined 48= Bank Card 49 = Direct Debet >>
<cbc:PaymentDueDate>2014-03-23</cbc:PaymentDueDate>
<cac:PayeeFinancialAccount>
<cbc:Name>Easy Dutch Plus</cbc:Name>
<cbc:CurrencyCode>EUR</cbc:CurrencyCode>
<cac:Country>
<cbc:IdentificationCode>NL</cbc:IdentificationCode>
</cac:Country>
</cac:PayeeFinancialAccount>
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article