Receipt validation with AFIP
Who this is for: whoever manages the account.
What it is for
A transactional agent receives an invoice or ticket, extracts its data and checks with AFIP (Argentina's tax authority) that an authorized receipt exists with that data. This is an Argentina-only feature.
What results it gives
| Result | What it means |
|---|---|
| Valid | AFIP confirmed the receipt |
| Data does not match | AFIP found the receipt but some data differs: that field must be read again |
| Rejected | AFIP says no receipt exists with that data |
| Incomplete data | Some data is missing or the paper has no CAE, CAEA or CAI (an ordinary ticket cannot be verified) |
| AFIP error | It could not be queried right now: it is neither verified nor dismissed |
⚠️
Warning:A misread piece of data produces a rejection identical to that of a fake invoice. So, before suspecting anything after a rejection, check the data that was sent.
Things to keep in mind
- CAE or CAEA mode: the paper says which, and querying with the wrong mode returns "does not exist".
- The issue date is not the only date on the paper: avoid picking, for example, the start of activities.
- It is used with the AFIP validator template and consulted from another agent. See Templates.
Common mistakes
- Using it outside Argentina.
- Treating a ticket without a CAE as a fake invoice.