Skip to content

Commit

Permalink
Proofreading
Browse files Browse the repository at this point in the history
Rewording, cleaning up TAX generalization and correcting release note by removing reference to a new code list
  • Loading branch information
midran committed Apr 29, 2020
1 parent 156f399 commit 87bbc9a
Show file tree
Hide file tree
Showing 10 changed files with 17 additions and 17 deletions.
2 changes: 1 addition & 1 deletion guides/profiles/28-ordering/principles/scope.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ TAX reporting::
TAX reporting is not a general requirement on orders. In this context the term TAX is used as a generalization of taxes such as VAT, GST or Sales Tax.
The level of support in orders is to

* Enable TAX reporting in invoices by providing TAX number of buyer. As example in case of reverse charges in EU.
* Enable TAX reporting in invoices by providing TAX number of buyer. As an example in case of reverse charges in EU.
* TAX can be stated as an estimate to enable buyers to state expected value of order. +
This can be helpful in automated matching of orders and invoices. +
TAX information is informative and does not affect the terms of trade.
Expand Down
2 changes: 1 addition & 1 deletion guides/profiles/3-order-only/principles/scope.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Invoice Verification:: The buyer may provide some information that the seller is

TAX reporting:: TAX reporting is not a general requirement on orders. In this context the term TAX is used as a generalization of taxes such as VAT, GST or Sales Tax.
The level of support in orders is to
* Enable TAX reporting in invoices by providing TAX number of buyer. As example in case of reverse charges in EU.
* Enable TAX reporting in invoices by providing TAX number of buyer. As an example in case of reverse charges in EU.
* TAX can be stated as an estimate to enable buyers to state expected value of order.
This can be helpful in automated matching of orders and invoices.
TAX information is informative and does not affect the terms of trade.
Expand Down
2 changes: 1 addition & 1 deletion guides/release-notes/v3.0.4.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Release date:: 2020-05-01
** Text in guidelines generalized from VAT to GST
** Element names and descriptions that had VAT in them generalized as TAX
** Rules requesting Tax type ID as VAT removed to allow for GST. VAT now given as example.
** Added new code list for allowed TaxScheme Identifiers. Code list now allows VAT and GST.
** Added new code for allowed TaxScheme Identifiers. Now allows VAT or GST.
* Updated the link “Peppol Identifiers” of all the BIS DOCUMENTS in https://docs.peppol.eu/poacc/upgrade-3/ to reflect the newest version of “Policy for use of identifiers”[POACC-188]

== Changes to syntax
Expand Down
6 changes: 3 additions & 3 deletions guides/shared/files/vat-cat-line.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -3,13 +3,13 @@

TAX information on line level is provided in the class `cac:ClassifiedTaxCategory`.

Each line shall have the item TAX information including category code and percentage rate except when the invoice as whole is not subject to TAX, then percentage shall not be given on line level.
Each line shall have the item TAX information including category code and percentage rate except when the invoice as a whole is not subject to TAX, in which case the percentage shall not be given on line level.

.UBL example of line TAX category, when TAX is VAT
[source, xml, indent=0]
----
include::../snippets/snippet-common.xml[tags=vat-line]
----
<1> TAX category according to codelist {vat-codes}
<2> TAX percentage. For EN must be present unless TAX category code is O (the value "O" means "Out of scope for VAT").
<3> Value must be identify the correct tax type, like VAT, GST or sales tax.
<2> TAX percentage. For EN must be present unless TAX category code is O (the value "O" means "Out of scope for TAX").
<3> Value must identify the correct tax type. For example VAT, GST or sales tax.
2 changes: 1 addition & 1 deletion guides/transactions/01-order/description/attachments.adoc
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
[[attachements]]
= Attachements
= Attachments

Non-XML documents can be sent as attachments to the PEPPOL BIS Order.
This could be drawings or time sheets or other documents relevant for the order.
Expand Down
2 changes: 1 addition & 1 deletion structure/syntax/ubl-catalogue.xml
Original file line number Diff line number Diff line change
Expand Up @@ -1683,7 +1683,7 @@
<Element>
<Term>cbc:ID</Term>
<Description>Tax scheme. E.g. “VAT” or “GST”</Description>
<Value type="EXAMPLE">VAT</Value>
<Value type="EXAMPLE">VAT or GST</Value>
</Element>
</Element>
</Element>
Expand Down
2 changes: 1 addition & 1 deletion structure/syntax/ubl-order-response.xml
Original file line number Diff line number Diff line change
Expand Up @@ -587,7 +587,7 @@
<Description>Tax scheme. E.g. “VAT” or “GST”</Description>
<DataType>Identifier</DataType>
<Reference type="BUSINESS_TERM">tir76-p003</Reference>
<Value type="EXAMPLE">VAT</Value>
<Value type="EXAMPLE">VAT or GST</Value>
</Element>
</Element>
</Element>
Expand Down
8 changes: 4 additions & 4 deletions structure/syntax/ubl-order.xml
Original file line number Diff line number Diff line change
Expand Up @@ -388,7 +388,7 @@
<Description>Mandatory element. E.g. "VAT" or "GST"</Description>
<DataType>Identifier</DataType>
<Reference type="BUSINESS_TERM">tir01-p004</Reference>
<Value type="EXAMPLE">VAT</Value>
<Value type="EXAMPLE">VAT or GST</Value>
</Element>
</Element>
</Element>
Expand Down Expand Up @@ -932,7 +932,7 @@
<Description>Tax scheme identifier. E.g. "VAT" or "GST"</Description>
<DataType>Identifier</DataType>
<Reference type="BUSINESS_TERM">tir01-p003</Reference>
<Value type="EXAMPLE">VAT</Value>
<Value type="EXAMPLE">VAT or GST</Value>
</Element>
</Element>
</Element>
Expand Down Expand Up @@ -1469,7 +1469,7 @@
<Description>Tax scheme identifier. E.g. “VAT” or “GST”</Description>
<DataType>Identifier</DataType>
<Reference type="BUSINESS_TERM">tir01-p013</Reference>
<Value type="EXAMPLE">VAT</Value>
<Value type="EXAMPLE">VAT or GST</Value>
</Element>
</Element>
</Element>
Expand Down Expand Up @@ -2141,7 +2141,7 @@
<Description>Tax scheme. E.g. “VAT” or “GST”</Description>
<DataType>Identifier</DataType>
<Reference type="BUSINESS_TERM">tir01-p021</Reference>
<Value type="EXAMPLE">VAT</Value>
<Value type="EXAMPLE">VAT or GST</Value>
</Element>
</Element>
</Element>
Expand Down
6 changes: 3 additions & 3 deletions structure/syntax/ubl-orderagreement.xml
Original file line number Diff line number Diff line change
Expand Up @@ -978,7 +978,7 @@
<Term>cbc:ID</Term>
<Description>Tax scheme. E.g. “VAT” or “GST”</Description>
<DataType>Identifier</DataType>
<Value type="EXAMPLE">VAT</Value>
<Value type="EXAMPLE">VAT or GST</Value>
</Element>
</Element>
</Element>
Expand Down Expand Up @@ -1082,7 +1082,7 @@
<Term>cbc:ID</Term>
<Description>Tax scheme. E.g. “VAT” or “GST”</Description>
<DataType>Identifier</DataType>
<Value type="EXAMPLE">VAT</Value>
<Value type="EXAMPLE">VAT or GST</Value>
</Element>
</Element>
</Element>
Expand Down Expand Up @@ -1654,7 +1654,7 @@
<Term>cbc:ID</Term>
<Description>Tax scheme. E.g. “VAT” or “GST”</Description>
<DataType>Identifier</DataType>
<Value type="EXAMPLE">VAT</Value>
<Value type="EXAMPLE">VAT or GST</Value>
</Element>
</Element>
</Element>
Expand Down
2 changes: 1 addition & 1 deletion structure/syntax/ubl-shoppingcart.xml
Original file line number Diff line number Diff line change
Expand Up @@ -693,7 +693,7 @@
<Element>
<Term>cbc:ID</Term>
<Description>Tax scheme. E.g. “VAT” or “GST”</Description>
<Value type="EXAMPLE">VAT</Value>
<Value type="EXAMPLE">VAT or GST</Value>
</Element>
</Element>
</Element>
Expand Down

0 comments on commit 87bbc9a

Please sign in to comment.