@getpeppr/cli 0.8.2 → 0.8.4

package/CHANGELOG.md

@@ -4,6 +4,30 @@ All notable changes to `@getpeppr/cli` are documented here.
 
 The CLI bundles `@getpeppr/sdk` into its published artifact (tsup `noExternal`), so `validate`, `convert` and `init` run the SDK's validators, country rules and UBL builder locally — an SDK release only reaches CLI users once the CLI is rebundled. Rebundle-only releases are listed with the SDK version they ship.
 
+## [0.8.4] — 2026-08-22
+
+`getpeppr init` now scaffolds an invoice that a fresh sandbox account can send:
+the SPF Economie test receiver plus out-of-scope `O/0` lines. The previous
+template targeted the correct receiver but still carried VAT-bearing and
+reverse-charge lines, so a new sender with no VAT identifier received 422.
+
+Every generated `O` line includes the builder-only exemption reason required by
+the SDK's local validator. The quick `getpeppr send --to …` payload remains on
+the same contract. This release bundles SDK 4.7.0.
+
+## [0.8.3] — 2026-08-21
+
+Rebundles `@getpeppr/sdk` **4.6.0** (was 4.5.0), so `getpeppr validate` and
+`getpeppr convert` understand exempt VAT breakdowns instead of accepting XML
+that the Peppol rulebook rejects. Category `O` omits the VAT rate; `E`, `AE`,
+`G`, `O`, and `K` require an exemption reason; `S` and `Z` never render one.
+
+The built-in `getpeppr send` sandbox payload now supplies its category `O`
+reason so the stricter local pre-validation does not stop the command before
+the network call. The field is builder-only and is stripped from the JSON
+request; Storecove continues to derive its own provider-specific exemption
+text on the send path (GPR-1068).
+
 ## [0.8.2] — 2026-08-21
 
 **`getpeppr lookup` accepts both spellings of a scheme** (GPR-1116). A Peppol

package/README.md

@@ -241,7 +241,7 @@ Scaffolding (`init`), validation, and conversion run fully offline — no API ke
 
 ## Invoice format
 
-The input file must be a JSON object matching the getpeppr `InvoiceInput` type. `number`, `to`, and `lines` are required for API sends. The `from` party is included in the scaffold because offline validation and UBL conversion need seller metadata; API sends use the legal entity linked to your key.
+The input file must be a JSON object matching the getpeppr `InvoiceInput` type. `number`, `to`, and `lines` are required for API sends. The `from` party is included in the scaffold because offline validation and UBL conversion need seller metadata; API sends use the legal entity linked to your key. The generated file is an integration fixture: a fresh sandbox sender has no VAT identifier, so every line uses category `O` at rate `0`.
 
 ```json
 {
@@ -271,14 +271,17 @@ The input file must be a JSON object matching the getpeppr `InvoiceInput` type.
       "description": "Conseil en transformation numérique",
       "quantity": 10,
       "unitPrice": 950,
-      "vatRate": 21
+      "vatRate": 0,
+      "vatCategory": "O",
+      "taxExemptReason": "Integration test"
     },
     {
       "description": "Software license — annual subscription",
       "quantity": 1,
       "unitPrice": 2400,
       "vatRate": 0,
-      "vatCategory": "AE"
+      "vatCategory": "O",
+      "taxExemptReason": "Integration test"
     }
   ],
   "paymentTerms": "Net 30 days",