Skip to main content

dgii-rejected

HTTP 422 · Possibly tenant fixable.

DGII rejected the document but did not return a structured rejection code that ERPly Pro can map. This generic entry appears in the following cases:

  • DGII returned an HTTP 4xx response without a parseable XML/JSON payload.
  • The DGII engine was in a transition and returned an undocumented code.
  • The client reached a newer version of the DGII API than we have catalogued.

When DGII does return a numeric code, the Problem.type points to the specific entry (e.g. dgii-17-totales-inconsistentes) and the dgii.code field contains the original code.

How to fix​

  1. Inspect the detail field — it usually contains the raw body returned by DGII.
  2. Review the dgii.trackId in the DGII virtual office to see the rejection.
  3. If the rejection is reproducible, open a ticket with the correlationId so we can update the mapping catalogue.