It means Axosnet Digital Invoice Verifier. It is the solution created by Axosnet to validate electronic invoices on the Concur Expense platform.

Yes, you can validate XML invoices in Concur Invoice.

• Valid invoices that are in conjunction with travel reports and expedite the process.
• Ensure that all invoices that are attached to the report are physically validated.

It is an authorized provider certified by the SAT to add the digital tax stamp node, making the electronic invoice valid by assigning a folio UUID.

No, Axosnet is not a PAC. According to the tax regulations, to validate, you don’t need to be a PAC. You only need a program that reviews and validates the entire structure according to annex 20. Axosnet is based on this structure and validates directly with SAT.

* To issue CFDI, you need to be a PAC. When only performing validations, this isn’t mandatory.

Universal Unique Identifier. It’s a unique code, universal and unrepeatable, that is assigned to each invoice issued, this fiscal folio is given by PAC

The moment the user/traveler clicks on the submit button, the invoices attached to the travel expense report are sent to ADIV, and it goes through validation and returns the result.

No, it’s not possible. Concur only gives access to an API that is to obtain the XMLs that come in the travel expense report at the time it is submitted.

 ADIV cannot take or validate the information from the fields of each expense that the employee fills in the report. ADIV only reads and takes the XML.

Only fiscal validations: structure according to current annex 20 (catalogs, XSD, others) certificate and digital stamps and the validity before the SAT, as well as the payment method.

• Make sure the report has been sent.
• At each expense, position yourself in the blue bracket icon.
• Where two fields with the status and the validation comment will appear.

It’s possible. Concur can add that alert so that the processor has visible if the XML is invalid (Concur does the configuration, not Axosnet).

3 to 5 minutes. There is a process that is running, and this takes the XMLs that arrive from Concur and sends them a result, regardless of the number of XMLs attached to the report.

We can’t change this process since Concur defined it for all its validation providers (partners). The process has not been modified since 2017. Concur intends not to make a bottleneck for validation if it isn’t a continuous flow where travel policies are authorized, their limits, etc. If there is only one error in the validation, it can stop the processor and ask the employee to send the new XML.

Suggestion: they can offer AxosMoney as a beta option to validate before the report is generated, but this option is only via mobile. It can’t be done from the web.

We require you to tell us how many social reasons (RFCs) will receive invoices to validate in Concur, our business scheme is that you will pay an annuity for each RFC that receives invoices regardless of the number of electronic invoices (CFDI) that will be uploaded to the Concur portal.

Suggestion: if the client has many social reasons, this will not be attractive, so it will be necessary to ask him for an estimate of the monthly volume of the XML he receives. Please make sure that you give us the number of XML files, not the number of Concur reports. With this, we can make a package of RFCs.

• If the volume is less than 5,000 XML per month to be validated, then the price of 1 RFC = $3,500 USD is given regardless of how many RFCs are. 
• If the volume is less than 500 XML per month, a much lower price of $2,000 USD per year can be given.

 All this should be reviewed with a business address before giving the price, it’s important to know what volume they have if they see that the customer doesn’t want to pay for RFC.

Our commercial plan is based on a number of factors. The intention is that clients don’t worry about the volume of invoices or how many transactions will be made. You make the annual payment regardless of how many documents will be validated. But we can offer you a package if you tell us the volume.

In order to review this, you would have to know exactly the volume of your transactions on a monthly basis, that is, know how many invoices you receive in Concur per month.

Suggestion: Not how many reports you will have in Concur if not CFDI’s that will be attached to the report. With this, I can go with the business address and review the case.

Yes, we are certified to implement the Concur Expense module and guide the client throughout the implementation, both activities that are the responsibility of the client and Concur's side (Configuration and Project Management). Concur continues to be responsible for the platform (because they sell you the license) – Axosnet configures the platform for each client.

Only expenses that contain a CFDI are valid.

No. Due to Concur’s configuration policy, the authorization flow cannot be stopped.

No, according to the LOA authorization letter, Concur only provides Axosnet (partners) with XMLs, it doesn’t allow obtaining other data such as the employee’s username or email.

No, it’s only until you click on the “send report” button, not when the invoice is attached.

No, they are only shown in Spanish.

No, the SAT requires the XML file, the PDF isn’t a valid document, it’s only a graphic representation of the XML data.

No, the annual prepayment allows for unlimited validations.

It is based on the number of RFCs (Company Codes, Tax ID) that will carry out validations in Concur.

When activating our solutions, you will gain access to our service desk, see reports, and be able to create service tickets.

No, this is included in the annual payment.

New updates are included in the annual payment.