Examples by country

⚠️ Common errors

This guide lists frequent Argentina errors as returned by the Koywe / FACTO API when issuance is not completed and the result object has status: 2.

---

Common result shape (status 2)

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - <exact error text> - "
}

The text after the fixed prefix Document generated but could not be sent to the Tax bureau - can come from two places:

• FACTO validations (sections 2 to 9): checked before calling ARCA. The document is not sent to ARCA.
• ARCA response (section 1): FACTO sent the document to the WSFE web service and ARCA rejected it or did not respond.

In both cases the document is not authorized (it has no CAE) and ARCA does not register it. Fix the indicated data and issue it again. See the statuses in Invoicing lifecycle.

---

1) ARCA errors

Rejection format

ARCA errors arrive in one of two formats:

• Request rejected (for example, a non-sequential number or a point of sale that is not enabled):

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error code: <code> - description : <description> -"
}

• Document rejected (Result R): each observation includes its code and description. There may be several in the same message:

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: Code : <code> Description : <description> - "
}

In both cases the response returns the draft document (document_status 0) with its document_id. If you sent document_number, the draft keeps that number.

1.1) Error 10016 — non-sequential number

ARCA only accepts the number following the last authorized one for the same point of sale and document type, with a date consistent with that of the last document.

FACTO sets the number as follows:

• If you send document_number, that number is used.
• If you do not send it, FACTO uses the last number issued in FACTO for that point of sale (document_sequence_code) and document type, plus 1.

That is why 10016 appears when documents were already issued for that point of sale outside FACTO (for example, on the ARCA website or with another system), or when you send a document_number that is not the next one.

Check: look up in ARCA the last authorized number for that point of sale and document type, and send document_number with the next number. If you issued documents outside FACTO, do not omit document_number: FACTO's numbering may be behind ARCA's and the error would repeat.

Also check the date: issue_date cannot be earlier than the date of the last authorized document and must be within the date range ARCA accepts for the concept and document type. For example, for a domestic product invoice (invoice_concept 1) the date can be up to 5 days before or after the sending date, without moving into the next month. If the message persists, check the ranges ARCA publishes for your document type.

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error code: 10016 - description : El numero o fecha del comprobante no se corresponde con el proximo a autorizar. Consultar metodo FECompUltimoAutorizado. -"
}

1.2) Point of sale not enabled

The point of sale is sent in document_sequence_code (for example "1"). It must be registered in ARCA as a web service electronic invoicing point of sale (RECE) for the issuer's CUIT. A point of sale created only for ARCA's online invoicing tool ("Comprobantes en línea") cannot be used to issue through the API. For export documents (class E, document_type_id 123 to 125) the point of sale must be of type Comprobantes de Exportación - Web Services.

Check: in ARCA, Administración de puntos de venta y domicilios, that the point of sale exists, is active and its system is web service. Then send that number in document_sequence_code.

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error code: 10004 - description : El punto de venta informado no se encuentra habilitado para usar en el presente WS. Consultar metodo FEParamGetPtosVenta. -"
}

Note: ARCA uses different codes depending on the cause (for example, a point of sale out of range or not registered for web service). Follow the code and description received in error_message. In the homologation (sandbox) environment ARCA may accept a point of sale that is not registered, so this error may not appear in your tests.

1.3) Error 501 — ARCA service unavailable

ARCA could not process the request. It is not an error in the data sent.

Check: retry the issuance later with the same data.

If the issuance ended without a response (for example, due to a timeout), check in ARCA whether the document was authorized before retrying, so it is not issued twice.

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - El servicio de ARCA no está disponible, no fue posible completar la emisión. Intente más tarde. Detalle del Error entregado: 501 - <ARCA detail> - "
}

1.4) Request rejected by the web service

ARCA rejected the whole request before evaluating the document (for example, because of a field with an invalid format).

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: ARCA rejected the request: <code> - <ARCA detail> - "
}

---

2) Issuer data

Seller data uses the issuer_ prefix in the header. If a required value is missing, the message follows the pattern The field '…' is required and cannot be empty. The example uses issuer_tax_id_code, but the same pattern applies to issuer_tax_id_type, issuer_legal_name, issuer_address, issuer_district, issuer_department, issuer_city, issuer_country_id, issuer_phone, issuer_activity and issuer_postalcode.

Check: that no required value is empty or null. If you do not send a value, FACTO takes it from the company settings; in that case, complete the settings.

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error : The field 'issuer_tax_id_code' is required and cannot be empty. - "
}

The issuer CUIT must have 11 digits:

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error : The field 'issuer_tax_id_code' must be a valid 11-digit CUIT. - "
}

---

3) Concept and service dates

Every Argentine invoice must include invoice_concept in header.additional.ar_header: 1 Products, 2 Services or 3 Products and Services.

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: For Argentine invoices you must provide the field invoice_concept (1 Products, 2 Services, 3 Products and Services) - "
}

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: For Argentine invoices you must provide a valid invoice_concept (1 Products, 2 Services, 3 Products and Services). - "
}

With concept 2 or 3, service_date_from, service_date_to and service_payment_due_date are also required. The message names the missing field:

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: If invoice_concept is 2 (Services) or 3 (Products and Services), you must provide the field service_date_from - "
}

---

4) Receiver

4.1) VAT condition (receiver_vat_condition_id)

receiver_vat_condition_id (in header.additional.ar_header) is required and its value must match the document class. See the codes in Table of codes.

Class	Allowed values
A and A subject to withholding	1, 6, 13, 16
B	4, 5, 7, 8, 9, 10, 15
C	1, 4, 5, 6, 7, 8, 9, 10, 13, 15, 16
E (export)	8, 9

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: The field receiver_vat_condition_id is required and must be included in the request. - "
}

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: For invoices of type A, the field receiver_vat_condition_id is invalid. Allowed values are: 1 (VAT Registered), 6 (Monotax), 13 (Social Monotax), and 16 (Promoted Independent Worker Monotax). - "
}

The same message exists for the other classes (type B, type C, type E, type R and type A subject to withholding), with their list of values.

4.2) Receiver identification (Invoice B)

An unidentified final consumer is invoiced by omitting receiver_tax_id_type and receiver_tax_id_code, or with receiver_tax_id_type AR-XXX. If you send the type, you must also send the number:

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: The field receiver_tax_id_code is required when receiver_tax_id_type is provided. To invoice an unidentified final consumer, omit both fields or use AR-XXX. - "
}

From ARS 10,000,000 (ARCA RG 5700/2025) the final consumer must be identified:

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: The final consumer must be identified (receiver_tax_id_type and receiver_tax_id_code) when the total is ARS 10,000,000 or more (ARCA RG 5700/2025). - "
}

With a passport (AR-PP), the number must contain only digits:

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: For receiver_tax_id_type AR-PP, receiver_tax_id_code must contain only digits (ARCA does not accept letters in the document number). - "
}

---

5) Point of sale and numbering

In Argentina, document_sequence_code is the ARCA point of sale.

5.1) Several points of sale without document_sequence_code

The account has more than one point of sale for that document_type_id and the request does not say which one to use.

Check: always send document_sequence_code when you issue from more than one point of sale.

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error : There is more than one sequence for this document type and no document_sequence_code was provided. - "
}

5.2) New point of sale (informational alert)

The document_sequence_code sent did not exist in FACTO for that document type and it was created. It may appear together with other texts in error_message. The number "5" is only an example.

If the point of sale already had documents authorized in ARCA, send document_number on the first issuance to avoid error 10016.

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - The sequence code 5 did not exist for this document type. It was created with document_number 1 - "
}

---

6) Amounts, currency and taxes

net_amount, total_amount and currency_id are required. currency_id must be a valid ARCA currency code.

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: The field total_amount is required and must be provided in the request. - "
}

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: The provided currency_id  does not match any valid ARCA currency code.. - "
}

Each tax in the taxes block must include tax_type_id, tax_percentage, tax_amount and tax_base_amount. The message names the missing field:

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: The field tax_amount is required in the taxes section and must be included in the request. - "
}

---

7) Credit and debit notes (references)

Credit and debit notes must reference the related document in references, with reference_branch_office_code (point of sale), document_type_id and reference_document_id or reference_number. The referenced document must have been issued in FACTO by the same company.

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: Either reference_number or reference_document_id is required for each reference. - "
}

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: The referenced document (reference_number 15) was not found among the documents issued by the company. References to third-party documents are not allowed. - "
}

---

8) Export (class E)

Export invoices and notes (document_type_id 123, 124 and 125) require receiver_country_id, receiver_tax_id_code, receiver_address and language_code (1 Spanish, 2 English, 3 Portuguese), and existing_permission (S or N) in header.additional.ar_header. The message names the missing field:

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: If the invoice type is 'E' (export), the field 'receiver_country_id' must be provided. - "
}

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: Invalid value for field 'existing_permission'. Only 'S' or 'N' are accepted - "
}

---

9) Informed CBU and optionals

informed_cbu is only accepted on class A documents (document_type_id 111 to 114). It must have 22 digits with valid check digits. informed_alias requires informed_cbu and must have between 6 and 20 characters.

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: The field informed_cbu is invalid: its check digits do not match. - "
}

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: The field informed_alias requires the field informed_cbu. - "
}

optionals must be a list of objects with a numeric id and a non-empty value, without repeated ids. ARCA validates which optionals each document accepts and rejects them with its own code (section 1).

"result": {
  "status": 2,
  "error_message": "Document generated but could not be sent to the Tax bureau - Error: The field optionals cannot contain repeated ids. - "
}

---

Useful references

• Invoicing lifecycle
• Create documents
• Recommended practices
• Table of codes