# Invoices, receipts and corrections VAT invoices, receipts and corrections in Ritevo: issuing from orders, numbering, VAT rates, OSS, intra-EU supply, PDF and sending to accounting. Ritevo issues sales documents straight from orders: VAT invoices, receipts and invoice corrections. The data comes from the order, and the number, VAT rates, dates and seller details come from the numbering - the set of settings you pick when issuing. You download the finished document as a PDF and send it to an accounting integration. ## Document types - **VAT invoice** (API: "VAT invoice" = `INVOICE`; value in `billingType`) - has a payment due date, GTU codes and procedures. - **Receipt** (API: "Receipt" = `RECEIPT`; value in `billingType`) - has no payment due date. You can also print a receipt on a fiscal printer. - **Invoice correction** (API: "Invoice correction" = `CORRECTION`; value in `billingType`) - fixes an issued invoice: the seller details, the buyer details or the items. You issue it for an invoice only. > **Good to know:** An order can have one invoice and one receipt at a time. To issue a new document of the same type, delete the previous one. You can issue any number of corrections for one invoice. ## Issuing You issue an invoice or a receipt in three ways. Each time you pick the numbering the document is created with: - **In the order** - in the **Issued documents** card click **Create invoice** or **Create receipt** and pick a numbering from the list. - **On the order list** - select orders and click the **Create invoices** or **Create receipts** icon. Up to 1000 orders at once. Orders that already have a document of that type are skipped. - **Automatically** - with the **Generate invoice** or **Generate receipt** step in [order actions](https://ritevo.com/en/docs/automations/order-actions). ![The Issued documents card in an order with the Create invoice button expanded and the list of numberings](https://ritevo.com/docs/orders/en-billing-issue-invoice.webp) The buyer is the company details from the order, i.e. the invoice details (name, tax ID, address). We do not fill in the buyer's personal details - the only exception is the personal ID number, which we take from the buyer's details. If the order has no company details, the document has no buyer - add the details in the order or with the **Update company details with buyer details** step in [order actions](https://ritevo.com/en/docs/automations/order-actions) before issuing. The seller is the company set in the numbering. The items are the order's products with quantity and gross price, and shipping goes on the document according to the numbering settings. The paid amount and the currency come from the order's payment. Invoices and receipts: `POST /orders/billings/batch?billingType=INVOICE|RECEIPT&settingsId={id}` with a list of order ids (1-1000) in the body. It runs in the background - the response is 202, the documents are created shortly after, and failures of single orders are not returned. Skipped: orders with an active document of that type, and orders that do not exist or belong to another company; if none qualifies - 409 `BILLING_ALREADY_EXISTS`. A numbering of another type or another company - 404 `BILLING_SETTINGS_BY_BILLING_TYPE_NOT_FOUND`; `billingType=CORRECTION` - 405. `GET /orders/billing/settings` returns the numberings. In automations the `GENERATE_INVOICE`/`GENERATE_RECEIPT` steps take the numbering id. ## Numberings A numbering is a saved set of document settings: the number pattern, VAT rates, shipping, dates, payment and seller details. You find them in **Orders** → **Billing**, the **Numbering settings** button. You can have up to 50 numberings including the defaults, for example a separate one for cross-border sales. You cannot change a numbering's document type after it is created. ![The Billing page with the document list and the Numbering settings button framed](https://ritevo.com/docs/orders/en-billing-settings-where.webp) ![The numbering list with the default invoice, correction and receipt numberings and the Add new numbering button framed](https://ritevo.com/docs/orders/en-billing-settings-list.webp) You add a new numbering with the **Add new numbering** button - you pick the document type: **VAT invoice**, **Invoice correction** or **Receipt**. The numbering is created with default settings, which you change in its details. ![The expanded Add new numbering button with VAT invoice, Invoice correction and Receipt to choose from](https://ritevo.com/docs/orders/en-billing-settings-add.webp) Every company starts with one default numbering each for invoices, receipts and corrections. You cannot delete a default numbering, nor a numbering that a document already uses. ### Number format In the **Number format** field you enter the number pattern. Plain text is kept as is, and the tokens are replaced with values: | Token | What we insert | Example | | --- | --- | --- | | `#N` | the next number, always 6 digits | 000001 | | `#MM` | month, two digits | 03 | | `#M` | month without a leading zero | 3 | | `#YYYY` | year | 2026 | | `#YY` | year, last two digits | 26 | The pattern `INV/#N/#MM/#YYYY` gives the numbers `INV/000001/03/2026`, `INV/000002/03/2026` and so on. The default patterns are `FV/#N/#MM/#YYYY` for invoices, `P/#N/#MM/#YYYY` for receipts and `K/#N/#MM/#YYYY` for corrections. Tokens are case-sensitive. ![The hint next to the Number format field describing the #N, #MM, #M, #YYYY and #YY tokens](https://ritevo.com/docs/orders/en-billing-settings-format-hint.webp) > **Good to know:** The `#N` counter starts from 1 every month, and the month and year in the number are the issue date of the document. That is why the pattern should have `#N`, the month and the year - without them numbers will repeat. We do not check this when saving. A pattern takes one year token (`#YYYY` or `#YY`) and one month token (`#MM` or `#M`). The counter is shared by all numberings of the same document type. If you have two invoice numberings, for example `INV/...` and `EU/...`, the numbers run in one sequence: `INV/000001`, `EU/000002`, `INV/000003`. ## VAT rates You set the rate for products in the numbering, in the **VAT rate** field: - **Product's assigned VAT rate** (API: "Product's assigned VAT rate" = `LINE_ITEM_ASSIGNED`; value in `taxRateOptions`) - each item gets the rate it has in the order. The default. - **OSS (VAT rate of the delivery country)** (API: "OSS (VAT rate of the delivery country)" = `VAT_OSS`; value in `taxRateOptions`) - the rate of the country the parcel goes to. More in the [OSS](#oss) section. - **Custom VAT rate** (API: "Custom VAT rate" = `CUSTOM`; value in `taxRateOptions`) - one rate for all products, picked in the **Custom VAT rate** field. Shipping has a separate **Shipping VAT rate** field: - **Proportional to products** (API: "Proportional to products" = `PROPORTIONAL_TO_PRODUCTS`; value in `shippingTaxRateOptions`) - shipping gets the VAT rate whose items have the largest share of the gross value of the products on the document (after skipping prices). When there are no products on the document - 0%. The default. - **OSS (VAT rate of the delivery country)** (API: "OSS (VAT rate of the delivery country)" = `VAT_OSS`; value in `shippingTaxRateOptions`) - as for products, by the delivery country. - **Custom VAT rate** (API: "Custom VAT rate" = `CUSTOM`; value in `shippingTaxRateOptions`) - the rate picked in the **Custom shipping VAT rate** field, 23% by default. Besides the regular percentage rates there are three special ones: - **Exempt** (API: "Exempt" = `EXEMPT`; value in `lineItems[].taxRate`) - the exempt rate, "zw." on the document. - **Reverse charge** (API: "Reverse charge" = `BUYER_CHARGED`; value in `lineItems[].taxRate`) - reverse charge, "n.p." on the document. - **Intra-EU supply** (API: "Intra-EU supply" = `ICSG`; value in `lineItems[].taxRate`) - a 0% rate marked as intra-EU supply (WDT). More in the [intra-EU supply](#wdt) section. ## OSS With the OSS setting Ritevo picks the VAT rate by the order's delivery country. This is how you turn it on: 1. In **Orders** → **Billing** click **Numbering settings** and add an invoice or receipt numbering, for example with the pattern `OSS/#N/#MM/#YYYY`. 2. In the **VAT rate** field choose **OSS (VAT rate of the delivery country)**. 3. In the **Shipping VAT rate** field also choose **OSS (VAT rate of the delivery country)**, so shipping has the same rate as the products. 4. You pick this numbering when issuing a document - by hand or in an action step, for example with the **Delivery country is** condition. ![The numbering VAT settings with OSS chosen in the VAT rate and Shipping VAT rate fields](https://ritevo.com/docs/orders/en-billing-settings-oss.webp) We take the rate from the delivery address country, not from the buyer's address. We use the standard VAT rates (not the reduced ones). A document is marked as OSS only when OSS is chosen in the **VAT rate** field for products; the marking itself is not printed on the PDF. Rates as of October 2026: | Country | Code | Rate | | --- | --- | --- | | Austria | AT | 20% | | Belgium | BE | 21% | | Bulgaria | BG | 20% | | Cyprus | CY | 19% | | Czechia | CZ | 21% | | Germany | DE | 19% | | Denmark | DK | 25% | | Estonia | EE | 24% | | Spain | ES | 21% | | Finland | FI | 25.5% | | France | FR | 20% | | Greece | GR | 24% | | Croatia | HR | 25% | | Hungary | HU | 27% | | Ireland | IE | 23% | | Italy | IT | 22% | | Lithuania | LT | 21% | | Luxembourg | LU | 17% | | Latvia | LV | 21% | | Malta | MT | 18% | | Netherlands | NL | 21% | | Poland | PL | 23% | | Portugal | PT | 23% | | Romania | RO | 21% | | Sweden | SE | 25% | | Slovenia | SI | 22% | | Slovakia | SK | 23% | > **Good to know:** If we do not find the delivery country in the table - because the parcel goes outside the European Union or the order has no delivery country - we set the rate to 0%. > **Good to know:** 0% is also the default for orders from sales channels: if a channel does not send an item's VAT rate, the order comes into Ritevo with 0%. That rate goes on the document if **Product's assigned VAT rate** is chosen in the **VAT rate** field of the numbering settings. Numbering with OSS: `taxRateOptions: "VAT_OSS"` and `shippingTaxRateOptions: "VAT_OSS"`. Country: the order's `delivery.address.countryCode`; missing or a country outside the table = `ZERO`. The document then has `oss: true` (only when `taxRateOptions` = `VAT_OSS`). We store the country on the document as `ossCountryCode` - also a country outside the table (e.g. `US`) with the `ZERO` rate, and `null` when the order has no delivery country; documents from before October 2026 have `null`. The wFirma integration sends the OSS rate by `ossCountryCode` and accepts only the countries in the table. The `vatOss` field in the numbering request is not stored - `taxRateOptions` decides. Rate values in the API: `TaxRate`, e.g. `NINETEEN`, `TWENTY_THREE`, `TWENTY_FIVE_AND_A_HALF` (25.5%). ## Intra-EU supply The intra-EU supply rate is 0% marked as intra-EU supply (WDT). Ritevo does not set it by itself - a document gets it from the numbering where you choose it: 1. Add an invoice numbering, for example with the pattern `EU/#N/#MM/#YYYY`. 2. In the **VAT rate** field choose **Custom VAT rate**, and in the **Custom VAT rate** field - **Intra-EU supply**. 3. In the **Shipping VAT rate** field choose **Custom VAT rate**, and in the **Custom shipping VAT rate** field - **Intra-EU supply**. 4. You pick this numbering when issuing an invoice. We take the buyer's VAT number from the company details in the order and do not verify it. ![The numbering VAT settings with the custom intra-EU supply (WDT) rate chosen for products and for shipping](https://ritevo.com/docs/orders/en-billing-settings-wdt.webp) ## Other numbering settings Apart from the number and the rates, the numbering decides what else goes on the document. ![Invoice numbering details: main settings with the number format, dates and payment, company details and VAT settings](https://ritevo.com/docs/orders/en-billing-settings-invoice.webp) ### Shipping - **Do not include shipping** (API: "Do not include shipping" = `NONE`; value in `shippingInclusionType`) - the document has products only. - **Always include shipping** (API: "Always include shipping" = `INCLUDE_ALWAYS`; value in `shippingInclusionType`) - shipping is a separate item, also when it costs 0. The default. - **Include if the shipping cost is above 0** (API: "Include if the shipping cost is above 0" = `INCLUDE_IF_POSITIVE`; value in `shippingInclusionType`) - free shipping does not go on the document. - **Add the shipping cost to the last product** (API: "Add the shipping cost to the last product" = `ADD_TO_LAST_PRODUCT`; value in `shippingInclusionType`) - we spread the shipping cost over the units of the last item instead of adding a separate one: 4 units at 5.00 and 20.00 shipping give 4 units at 10.00. If the cost does not divide evenly into cents, the leftover cents go on one split-off unit (3 units at 5.00 and 20.00 shipping: 2 at 11.66 and 1 at 11.68), so the total always matches the order. Shipping then gets that item's VAT rate - the **Shipping VAT rate** field has no effect. If all products are skipped, there is no shipping on the document. The shipping item is named after the order's delivery method. In the **Delivery prefix** field you can add text in front of it, for example "Delivery: ". ### Skipping products by price - **Include all prices** (API: "Include all prices" = `INCLUDE_ALL`; value in `priceSkipOption`) - all products with a price go on the document. Items without a price are always skipped. The default. - **Skip prices equal to 0** (API: "Skip prices equal to 0" = `SKIP_ZERO`; value in `priceSkipOption`) - no free gifts or items for 0. - **Skip negative prices** (API: "Skip negative prices" = `SKIP_NEGATIVE`; value in `priceSkipOption`) - no discounts saved as separate items with a negative price. - **Skip prices equal to 0 and negative** (API: "Skip prices equal to 0 and negative" = `SKIP_BOTH`; value in `priceSkipOption`) - both at once. ### Dates and payment - **Sale date same as the issue date** (API: "Sale date same as the issue date" = `SAME_AS_ISSUE_DATE`; value in `saleDateTerm`) - the sale date is the day the document is issued. - **Sale date same as the payment date (or today)** (API: "Sale date same as the payment date (or today)" = `SAME_AS_PAYMENT_DATE`; value in `saleDateTerm`) - the day the order was paid, and if it is unpaid - the issue date. - **Sale date same as the order date** (API: "Sale date same as the order date" = `SAME_AS_ORDER_DATE`; value in `saleDateTerm`) - the day the order was placed. The default. The issue date is always the moment the document is created. The **Payment due date** is counted from it - you pick it from a list: **No due date** (the document has no payment due date), **Due on the issue date** or 3 to 120 days (14 days by default). A receipt has no due date. You set the payment method in the **Payment settings** field: - **From the order** (API: "From the order" = `USE_FROM_ORDER`; value in `paymentMethodSettings`) - the order's payment method, and if it has none - **Other**. The default. - **Custom setting** (API: "Custom setting" = `CUSTOM`; value in `paymentMethodSettings`) - a fixed method picked in the **Payment method** field, for example **Bank transfer**. ### Issuer and additional details - **Issuer details** - the **Issuer name** and the **Place of issue**. Empty fields do not show on the document. - **Company details** - the seller details, only in invoice and receipt numberings. A correction takes the seller from the invoice. - **Default unit of measure (e.g. pcs, kg, service)** - the unit of every item. "szt." (pcs) by default. - **GTU codes** and **Procedures** - Polish JPK markings saved in invoices and corrections and passed to the accounting integration. They are not printed on the PDF. - **Additional information on the invoice (if available)** - a fixed text saved in the document and passed to the accounting integration. It does not appear on the PDF generated by Ritevo. Numberings: `GET /orders/billing/settings`, `GET`/`PATCH`/`DELETE /orders/billing/settings/{id}`. `POST /orders/billing/settings?billingType=INVOICE|RECEIPT|CORRECTION` (no body) creates a numbering with default values - 201, and 422 `LIMIT_EXCEPTION` beyond 50 (including the defaults). You set fields with `PATCH`: `name`, `numberFormat` and `defaultUnit` are required, other `null` fields are left unchanged, and boolean fields are always overwritten. Fields: `taxRateOptions` (`LINE_ITEM_ASSIGNED`, `VAT_OSS`, `CUSTOM`), `taxRate` (`TaxRate`, default `TWENTY_THREE`), `shippingInclusionType` (`NONE`, `INCLUDE_ALWAYS`, `INCLUDE_IF_POSITIVE`, `ADD_TO_LAST_PRODUCT`), `shippingTaxRateOptions` (`PROPORTIONAL_TO_PRODUCTS`, `VAT_OSS`, `CUSTOM`; ignored with `ADD_TO_LAST_PRODUCT` - shipping takes the last item's rate), `shippingTaxRate` (default `TWENTY_THREE`), `prefixForDeliveryName`, `priceSkipOption` (`INCLUDE_ALL`, `SKIP_ZERO`, `SKIP_NEGATIVE`, `SKIP_BOTH`), `paymentMethodSettings` (`USE_FROM_ORDER`, `CUSTOM`), `paymentMethod` (`BANK_TRANSFER` default, `CASH`, `CASH_ON_DELIVERY`, `COMPENSATION`, `CARD`, `PAYU`, `PAYPAL`, `P24`, `OTHER`), `saleDateTerm` (`SAME_AS_ISSUE_DATE`, `SAME_AS_PAYMENT_DATE`, `SAME_AS_ORDER_DATE`), `dueDateTerm` (`NONE_DISPLAY`, `ISSUE_DATE`, `DAYS_3`, `DAYS_7`, `DAYS_14`, `DAYS_21`, `DAYS_30`, `DAYS_45`, `DAYS_60`, `DAYS_90`, `DAYS_120`), `issueCity`, `issuerName`, `sellerCompany`, `gtuCodes` (`GTU_01`-`GTU_13`), `taxProcedures` (`TT_WNT`, `TT_D`, `I_42`, `I_63`, `B_SPV`, `B_SPV_DOSTAWA`, `B_MPV_PROWIZJA`, `SW`, `EE`, `WSTO_EE`, `VAT_RR`, `IED`, `TP`, `MR_T`, `MR_UZ`, `MPP`, `IMP`, `WEW`, `RO`, `FP`, `MK`), `additionalInformation`. The fields `recalculateCurrency`, `recalculateToCurrency`, `exchangeRateDate`, `countryCodeLanguage`, `unitPriceDisplay`, `displayVat` are accepted but have no effect. Deleting: the default numbering - 409 `DEFAULT_BILLING_SETTINGS_DELETION`; a numbering used by documents, deleted ones included - 423 `BILLING_SETTINGS_REFERENCE`. ## Editing and deleting - **Editing** - in the document details you change the seller details, the buyer details and the items (add, fix, delete). Net amounts, VAT and totals are recalculated after every change. If the document was issued without buyer details, you add them here. - **Deleting** - a deleted document disappears from the order but stays on the **Billing** list marked as deleted, and you can issue a new one. An invoice with a correction cannot be deleted - delete the corrections first. You delete up to 1000 documents at once; if any of the selected invoices has a correction, none is deleted. ## Corrections You create a correction in the invoice details with the **Create correction** button or with the icon next to the invoice on the **Billing** list - first you pick a correction numbering. A correction has its own numbering and its own counter, and a correction numbering only has the payment, dates, issuer, unit, GTU code and procedure settings. You tick what you correct: - **Seller correction** - new seller details. - **Buyer correction** - new buyer details. - **Order items correction** - a new, full list of items. An item missing from the list is gone from the correction. ![The Create correction window with the Correction reason field, the correction switches and the item list](https://ritevo.com/docs/orders/en-billing-correction-dialog.webp) Seller details, buyer details and items you do not tick are copied from the invoice. Dates, payment method, GTU codes, procedures and issuer details come from the correction numbering. You enter the **Correction reason** (up to 255 characters) when creating it - the field is optional, and the reason is printed on the correction PDF. The currency, the paid amount and the OSS marking come from the invoice. You cannot correct a receipt or another correction, and automations do not create corrections. ![Correction numbering details: main settings, dates and payment, issuer details and GTU codes](https://ritevo.com/docs/orders/en-billing-settings-correction.webp) Correction: `POST /orders/billings/{invoiceId}/correction?settingsId={id}` - only for a non-deleted invoice (`INVOICE`); response 202, and 404 for a deleted or missing invoice and a numbering of another type. Fields: the flags `correctionSeller`, `correctionBuyer`, `correctionLineItems` plus `correctedSellerDetails`, `correctedBuyerDetails`, `correctedLineItems[]` (`name`, `quantity`, `unit`, `amount` - gross per unit, `taxRate`; `quantity`, `amount`, `taxRate` required), `correctionReason` up to 255 characters, optional. A `true` flag without data - data from the invoice; `correctionLineItems: true` with an empty list gives a correction without items. A correction has `originalInvoiceId`, and the invoice a `corrections` list. ## PDF, printing and accounting - **PDF** - you download every document as a PDF generated by Ritevo, also after it is deleted; the file is named after the document number. An items correction shows the items table before and after the correction and the difference in the VAT summary and the amount due. A seller or buyer correction shows those details before and after. - **Printing** - you print a receipt on a printer connected through [Ritevo Printer](https://ritevo.com/en/docs/integrations/ritevo-printer). Invoices and corrections are not printed yet. - **Accounting** - you send a document to an accounting integration in its details, in the **External accounting systems** card, and an invoice or receipt also with an action step. A deleted document cannot be sent. Which document types an integration accepts is on its page in the integrations section. ## Documents in automations Order actions can issue an invoice or a receipt, delete them, send them to accounting and print a receipt. Triggers react to an invoice or receipt being added or deleted and to its successful sending to accounting, and conditions check whether the order has an invoice, receipt or correction, whether a document was sent and whether the customer asks for an invoice. The full list is in [order actions](https://ritevo.com/en/docs/automations/order-actions). ## What it does not do - It does not set the intra-EU supply rate by itself - a document gets it from the numbering where you choose it. - It does not verify the buyer's EU VAT number. - It does not convert amounts to another currency - the document is in the order's payment currency. - It does not generate the PDF in any language other than Polish. - It does not e-mail documents to the customer. - The **Currency conversion**, **Document language**, **Price display** and **Show VAT** options in the numbering settings do not change the document or the PDF yet. ## API Documents: `GET /orders/billings` (paged list with filters), `GET /orders/billings/{id}`, `GET /orders/billings/pdf/{id}` (PDF Ritevo), `GET /orders/billings/{id}/get-external-billing-pdf/{accountingIntegrationId}` (PDF from the accounting integration, after a successful transfer), `PATCH /orders/billings/{id}/buyer` i `/seller` (replace the whole details - `null` clears a field), `PATCH /orders/billings/{id}/paid-amount` with `{paidAmount}`, `POST /orders/billings/{id}/line-items`, `PATCH`/`DELETE /orders/billings/{id}/line-items/{lineItemId}`, `DELETE /orders/billings/batch` (up to 1000, in the background; 422 `BILLING_HAS_CORRECTION` when any invoice has a correction), `POST /orders/billings/{billingId}/transfer-to-external-accounting/{integrationId}` (202; 409 `BILLING_ALREADY_TRANSFERRED` when a transfer to this integration succeeded or is in progress; 404 for a deleted one), `POST /orders/billings/{id}/print/{printerIntegrationId}` (202; 404 when it is not a non-deleted receipt). Editing through the API is not blocked for deleted or sent documents. Document fields: `id`, `orderId`, `billingSettingsId`, `billingType`, `billingNumber`, `sequenceNumber`, `sequenceMonth`, `sequenceYear`, `issueDate`, `saleDate`, `dueDate` (null for a receipt), `paymentMethod`, `issuerName`, `issueCity`, `buyerDetails`, `sellerDetails`, `lineItems[]` (`name`, `quantity`, `unit`, `taxRate` oraz `amount`, `netAmount`, `taxAmount` - values per unit: gross, net, VAT), `totalToPayAmount`, `totalToPayNetAmount`, `totalTaxAmount`, `paidAmount`, `currencyCode`, `oss`, `gtuCodes`, `taxProcedures`, `additionalInformation`, `correctionReason`, `originalInvoiceId`, `corrections[]`, `deleted`, `externalTransfers[]`. The current paths and fields are in Swagger: https://api.ritevo.com/api/v1/api-docs. --- All help in one file: https://ritevo.com/llms-full.txt. Help map with links to every page: https://ritevo.com/llms.txt.