Receipt Types

According to your company's fiscal configuration and customer type, Sarah can issue different types of receipts, for example:

• Invoice A
• Invoice B
• Invoice C
• Invoice X (internal / non-fiscal, according to regulation)
• Credit notes and debit notes

Emit validations

Sarah blocks invalid combinations before sending to AFIP:

• Invoice A → Registered VAT (RI) customers with CUIT only. Monotax and VAT-exempt customers cannot receive Invoice A.
• Invoice B → not allowed when the customer is RI (use Invoice A). Monotax and exempt customers can receive Invoice B.
• Invoice C → only monotax or VAT-exempt issuers can emit it. Registered VAT businesses do not issue C receipts.

These rules apply in POS, sales invoice generation, and advanced invoicing.

Receiver VAT condition (ARCA)

When requesting a CAE, Sarah sends CondicionIVAReceptorId from contacts.tax_condition:

Sarah sends the mapped id when it is valid for that letter (mirrors AFIP FEParamGetCondicionIvaReceptor: 1/6/13/16 → A/M/C; 4/5/7/8/9/10/15 → B/C). If the id is not valid for the letter (monotax, social monotax, promoted monotax, or RI on Invoice B), Sarah sends 5 (final consumer) — what ARCA already accepts — and does not throw. POS shows a non-blocking hint that Invoice A is the correct voucher. Invoice B to an RI customer with CUIT is still blocked by the older emit check (use Invoice A).

Exempt customers

By default (and when the company value is empty), an IVA-exempt receiver on Invoice B / NC-B / ND-B is filed as an exempt operation: ImpOpEx = total minus other tributes, VAT 0, no AlicIva, CondicionIVAReceptorId 4. Invoice C keeps today’s amounts (ImpNeto = total, ImpOpEx = 0) and only sends id 4. In Company → Tax, “Bill exempt customers as exempt operations” (companies.invoice_exempt_customers_as_exempt) can be turned off to keep the previous 21% taxable split on B; id 4 is still sent. POS shows the exempt notice only on B receipts.

If another contact in the same company shares the CUIT, POS warns. When the selected contact has no condition and a sibling does, that condition is used without editing contacts. Conflicting conditions are not guessed.

Territorial regime Law 19.640 (Tierra del Fuego)

In Company → Tax, “Law 19.640 regime (Tierra del Fuego)” (companies.iva_territorial_regime = ley_19640) is opt-in. Off or empty = today’s continental split. It does not turn on just because the province, city, or ZIP says Tierra del Fuego.

When the regime is on (island operations):

• Invoice A and B (and their NC/ND) are filed as VAT-exempt: ImpOpEx = total, ImpNeto = 0, ImpIVA = 0, no AlicIva. AlicIva Id 3 (0% taxable) is not exempt.
• The letter still follows the customer (RI → A, CF / exempt → B). The territorial benefit does not force Invoice C.
• The receiver VAT condition does not change: CF = 5, RI = 1, Exempt = 4, Monotax = 6. Id 10 (VAT Liberated – Law 19.640) is a receiver id, never the issuer for being on the island.
• The ticket may print “VAT exempt – Law 19.640”.
• If the exempt-customer switch also applies on B, the result is still ImpOpEx (idempotent).

Credit and debit notes

CAE credit/debit notes are stored as their own invoices rows (NC-A, NC-B, NC-C, ND-A, ND-B, ND-C) and linked to the original voucher. The fiscal month attributes VAT to the note’s month.

How VAT is shown on the receipt

The printed footer follows the receipt type:

• Invoice A (registered VAT to registered VAT): the footer breaks out taxable net and VAT per rate. The VAT-included total is not shown as a pre-tax subtotal. Example: NETO GRAVADO 21% / IVA 21% / TOTAL. Extra rates get their own net + VAT pair. Untaxed, exempt, other taxes, and withholdings print only when they have an amount. Credit/debit notes A use the same footer.
• Invoice B (final consumer or other non-RI): the total is the final price. The VAT included / Law 27.743 legend prints only when the receiver is a final consumer and the voucher has VAT. An exempt receiver prints their stored condition and the exempt amount, without that legend. A4 lists net, VAT, and exempt as on the electronic voucher. B credit/debit notes print as credit/debit notes (not “INVOICE”), with the associated voucher.
• Invoice C and X: no VAT breakdown.

Footer VAT amounts come from the stored voucher (invoices.tax_aggregates or the ARCA request/response in metadata). If no stored split exists, print still uses the historical sale-line calculation (default 21% on the total).

80 mm ticket

On the 80 mm thermal ticket, each product with a barcode shows the last 4 digits next to the name. Use it to identify the item and find it in POS. 57 mm and A4 do not add them.

Automatic receipt type selection

When you generate an invoice from POS or the sales module:

• The system takes into account:
  • The company's fiscal condition.
  • Customer type (Registered Taxpayer, Monotax, Final Consumer, etc.).
• According to those rules, it suggests the most appropriate receipt type.

You can manually adjust the type in special cases, as long as it's valid according to regulations.

Internal receipts (X)

Invoice X are usually used for:

• Internal receipts.
• Preliminary sales where you don't want to generate a definitive fiscal receipt yet.

In your company's configuration you can define when to use this type of receipts and how to migrate later to final fiscal receipts.