Submitting your mileage to Concur is easy with MileIQ!
First, authorize Concur with your MileIQ account and you can then begin posting transactions to new or un-submitted reports in Concur.
If you experience any issues, please review the troubleshooting questions below.
#1. Did you delete or submit the report in Concur before the MileIQ transactions had fully posted?
Occasionally, we'll see users create a report in MileIQ, then make changes to expense reports before the MileIQ transactions have fully posted to Concur. If a report is deleted or submitted before the mileage appears within Concur, the mileage report will not go through. For a large amount of drives, submissions can take up to 10 minutes.
Be sure to refresh the list of reports in MileIQ before attempting the submission again. You can refresh the list of reports by clicking on 'Email' in the "Enter Report Details" window and then clicking on 'Concur' again. This will ensure you're submitting to an available report within Concur.
#2. Does your mileage expense type form in Concur contain non-default fields?
MileIQ is built to support only the standard default mileage form in Concur. If your company has added additional fields that must be filled in before a transaction can be saved, then MileIQ will be unable to post your transactions. To confirm, login to Concur and create a test report and a test expense selecting the “Expense Type” used for submitting mileage. Don’t worry, you can delete the report and transaction later.
Then, look for each of the fields listed below. If there are fields other than the ones listed below, check to see if they have a red line on the left hand side. If the field has a red line it means it is required in order for the transaction to be saved. Since MileIQ doesn’t post data to that field, the transactions created via the MileIQ integration won’t be able to be saved.
Default Fields Supported by MileIQ integration to Concur:
- Expense Type
- Transaction Date
- Purpose of the Trip
- From Location
- To Location
- Distance
- Amount
- Payment Type
If you identify that there are required fields preventing the MileIQ integration from functioning, please contact your Concur Administrator. The following paragraph may be helpful in explaining your request:
“MileIQ is a Concur App Center partner and widely used mobile application for tracking and submitting mileage expenses. I would like to use the integration with Concur as it makes it easier for me to post mileage transactions. However, the integration has been built to support Concur’s default configuration for mileage expenses. Our company has additional required fields on the mileage expense type form that mean MileIQ’s integration is unable to post transactions to Concur. According to Concur and MileIQ, in order to avoid confusion for employees, we should either amend this expense type form to only require the default fields (Expense Type, Transaction Date, Purpose of the Trip, From Location, To Location, Distance, Amount and Payment Type) if possible or we should disable MileIQ and other mileage apps in the Concur App Center. To do this in Concur, go to Administration >> Web Services >> Manage User Applications.”
#3. Did you use a mileage expense type other than "MILEG"?
A common issue stems from trying to send mileage to a Concur Policy that excludes the expense type for mileage. The standard US Expense Policy includes this field by default under the label of "MILEG".
To confirm, do you have an expense type for mileage in the policy you are submitting to? If not, then your Concur Administrator needs to create a new expense type labeled MILEG, and this expense type will need to be active for all policies. Once this has been completed, MileIQ can then report your mileage expenses to the newly created MILEG expense type in Concur.
If the mileage expense type is already active, please ensure that it shows up as MILEG, as we are not able to support any non-default settings to this field at this time.
#4. Did you use a payment type other than “Cash”?
All mileage transactions should be created with a payment type of cash which indicates that you should be reimbursed for the cost (rather than your credit card provider).
#5. Is your Concur account set up with variable mileage rates?
Unfortunately, MileIQ is unable to submit any reports to Concur for users that have multiple mileage rate options. If you identify that there are multiple mileage rates available to you but you only use one rate, please contact your Concur Administrator. The following paragraph may be helpful in explaining your request:
“MileIQ is a Concur App Center partner and widely used mobile application for tracking and submitting mileage expenses. I would like to use the integration to Concur as it makes it easier for me to track and submit mileage expenses. The integration has been built to support Concur’s default configuration for mileage expenses. Our company has variable mileage rates configured which means MileIQ’s integration is unable to post transactions to Concur. According to Concur and MileIQ, in order to avoid confusion for employees, we should determine if multiple mileage rates are required for US employees and if so, we should disable MileIQ and other mileage apps in the Concur App Center. To do this in Concur, go to Administration >> Web Services >> Manage User Applications. Note that the MileIQ and other mileage apps only appear for users in the US so if variable rates are required for other countries, it is not necessary to disable the app listing as long as US employees are all set up with a single rate car configuration.”
#6. Did you have more than 64 characters in the notes field?
MileIQ is unable to submit your report if your drives have more than 64 characters (the maximum characters allowed by Concur) in the notes field. Please reduce the number of characters in the notes field for each of your drives
#7. Did you have two separate location fields for drives?
Unfortunately, we do not support combining the location fields into one. Please reach out to your Concur administrator about changing these fields in your Concur policy so the fields are separated as ToLocation and EndLocation.
#8. Did you have more than 48 characters in the location field?
MileIQ is unable to submit your report if your drives have more than 48 characters (the maximum characters allowed by Concur) in the location field. Please reduce the number of characters in the location field for your drives.
#9. Did you include the expense type for tolls?
MileIQ is unable to submit your mileage to a Concur Policy that excludes the expense type for tolls. The standard US Expense Policy includes this field by default under the label of "TOLLS". Please enable the expense type for tolls in your policy.
Additional Information
If, after following the above troubleshooting steps, you continue to experience issues please fill out the form at support.mileiq.com with the email account on file with MileIQ.