📋 Document sequences

Electronic invoicing sequences in Argentina (ARCA)

In Argentina’s electronic invoicing system, the equivalent concept to a “series” is the combination of Point of Sale (POS) + Voucher Number, which defines the document numbering sequence. Numbering is regulated by ARCA (formerly AFIP).

Voucher number structure

An Argentine electronic voucher is identified as:

POINT OF SALE – VOUCHER NUMBER

Example: 0001-00001234

  • Point of Sale (POS): 4 digits
  • Voucher number: 8 digits

The combination must be unique per taxpayer and voucher type. In the API, the point of sale is represented by document_sequence_code (and, when applicable, branch_office_code); the voucher number is the document number assigned by the sequence.

What is a sequence in Argentina?

The sequence is the incremental voucher number within a specific:

  • Taxpayer (CUIT)
  • Point of Sale (POS)
  • Voucher type

Each combination has an independent counter. So the first Invoice A at POS 0001 gets voucher number 1, and the first Invoice A at POS 0002 also gets voucher number 1, because they are different sequences.

Practical example: independent sequences per POS

A company can define multiple points of sale, each with its own numbering:

POSTypical use
0001ERP invoicing
0002Web store
0003Retail store

Sequences do not overlap:

POSSequence (example)
00010001-00000001, 0001-00000002, …
00020002-00000001, 0002-00000002, …
00030003-00000001, …

So the first voucher at POS 0001 is 0001-00000001, the first at POS 0002 is 0002-00000001, and the first at POS 0003 is 0003-00000001.

Separate sequence per voucher type

Within the same point of sale, each voucher type has its own sequence. Common voucher types include:

  • Invoice A
  • Invoice B
  • Credit Note A
  • Credit Note B
  • Debit Note

Example at POS 0001:

Voucher typeNumbering
Invoice A0001-00000001, 0001-00000002, …
Credit Note A0001-00000001, 0001-00000002, …

So the first Invoice A at POS 0001 is 0001-00000001, and the first Credit Note A at the same POS 0001 is also 0001-00000001, because each voucher type has its own independent counter.

How it works in the API

Sequences are independent per point of sale and per voucher type. Each point of sale uses its own document_sequence_code (and, for Argentina, branch_office_code as required). The document number (voucher number) counter is separate for each combination of document_type_id and document_sequence_code.

Point of saledocument_sequence_codebranch_office_codeFirst invoice document numberSecond invoice document number
111212
221212

When creating a document, send the document_sequence_code that identifies the point of sale (and branch_office_code as required for Argentina). Do not send document_number if you want the voucher number to be assigned automatically from the sequence.

Request example (point of sale 1 – Invoice A)

1{
2 "header": {
3 "account_id": 29240,
4 "document_type_id": "111",
5 "document_sequence_code": "1",
6 "received_issued_flag": 0,
7 "issue_date": "2025-10-24",
8 "issuer_tax_id_code": "20357265992",
9 "issuer_tax_id_type": "AR-CUIT",
10 "issuer_legal_name": "Tecnologias Avanzadas S.A.",
11 "issuer_address": "Av. Corrientes 1234",
12 "issuer_district": "San Nicolas",
13 "issuer_city": "Ciudad Autonoma de Buenos Aires",
14 "issuer_department": "Buenos Aires",
15 "issuer_country_id": "88",
16 "issuer_phone": "011-4321-5678",
17 "issuer_activity": "Servicios de desarrollo de software",
18 "issuer_postalcode": "1043",
19 "receiver_tax_id_code": "30274688781",
20 "receiver_tax_id_type": "AR-CUIT",
21 "receiver_legal_name": "ESCUELA KEMPER URGATES",
22 "receiver_address": "Calle Belgrano 456",
23 "receiver_district": "Centro",
24 "receiver_city": "Cordoba",
25 "receiver_department": "Cordoba",
26 "receiver_country_id": "88",
27 "receiver_phone": "0351-487-2233",
28 "receiver_activity": "Servicios educativos",
29 "receiver_postalcode": "5000",
30 "payment_conditions": "0",
31 "currency_id": 1,
32 "branch_office_code": 12,
33 "additional": {
34 "ar_header": {
35 "invoice_concept": 1,
36 "items_quantity": 1,
37 "service_date_from": "2025-10-14",
38 "service_date_to": "2025-10-14",
39 "service_payment_due_date": "2025-10-10",
40 "receiver_vat_condition_id": 1
41 }
42 }
43 },
44 "details": [ ... ],
45 "totals": { ... }
46}

For a second point of sale, use a different document_sequence_code (e.g. "2"); that point of sale will have its own voucher number sequence starting at 1 for its first document (per voucher type).

For the full request body and all required fields, see Create new documents.

Automatic document number assignment

By default, you should not send the document_number field. The API assigns the next voucher number from the sequence for the given document_type_id and document_sequence_code. Only use document_number when you need to force a specific value (e.g. for special cases or migration). The document types endpoint (PATCH) allows you to set the initial last_sequence_number when configuring or resetting a sequence.