Skip to main content

Legal

Tax & Accounting

Trade & Supply

Risk & Fraud

News & Media

Books

Developers

e-file Help and Support

Tips for troubleshooting modernized e-file (MeF) rejections

Here are some ideas to help you understand XML validation errors.

Tips for troubleshooting modernized e-file (MeF) rejections

Keywords used in reject codes
Explanation
Resolution
Database validation error
If this is the only error you receive, these keywords essentially indicate a Master File rejection and don’t indicate a calculation error. The reject code indicates a difference between the client information on the form and the information that the IRS has on record (such as the taxpayer's tax year, entity type, and/or name).
In addition, this can indicate that the ERO didn’t apply to e-file the return type in the initial application to participate in the IRS e-file application.
Make sure that all data is correct. For example, if the error states that the taxpayer's Employee Identification Number (EIN) and name control don’t match, verify the EIN and name control.
If necessary, call the IRS to determine what information was entered incorrectly and to determine if the IRS can revise the Master File.
For non-1040 clients, call the IRS at 800.829.4933.
If you didn’t prepare the prior-year return, an officer or partnership representative needs to call the IRS.
If the error indicates that the ERO's “EFIN needs to be valid and in accepted status,” the ERO needs to contact the IRS at 866.255.0654 to add the return type to the electronic registration.
Unexpected [child element…] / Expected: { }
These keywords indicate the IRS or state's e-file processor found a missing entry or out-of-sequence entry. The error lists the expected or missing items.
Expected and unexpected items have field descriptions that indicate the items that are out of sequence.
Review the return diagnostic messages and the form location of the unexpected items to determine where the expected items should be entered, identify the correct sequence, and determine the missing item based on the sequence.
These keywords are often triggered by an invalid address entry or a statement line-item amount that doesn’t have a corresponding description, or vice versa; note that this may include entering a zero.
Element data is incomplete / Expected: { }
These keywords are usually synonymous with the previous unexpected items rejection; the expected items are missing and need to be entered.
Review the return diagnostic messages and locate the description for the expected field.  Verify that an entry exists in the field. Note that this may include entering a zero.
Violates MinInclusive constraint: 0
These keywords indicate that the tax authority-established rules about the data that can be entered in a field on a return; the lowest value that the tax authority accepts is zero or positive values.
This is generally triggered when the tax authority expects a gross number in a field (such as apportionment factors) but a negative number is entered.
Replace the negative number with a positive number; note that this may include entering a zero.
Violates enumeration constraint of…
These keywords indicate that the tax authority specified a group of values that can be entered in the field.
For example, in a field that requires the state in which corporate books are located, the accepted list of entries would include only the list of standard state ZIP Codes.
The list of acceptable values is generally included in the rejection text.
Verify that all values were entered correctly. For example, verify that "IN" for Indiana was not incorrectly entered as "IK."
Returns with noncalculating forms are especially vulnerable to this type of rejection.
Value failed to parse / error parsing element with value { }
Similar to the previous error, these keywords indicate that the entry in the field doesn’t match the tax authority's prescribed data type.
For example, this error triggers if a decimal number is required for an apportionment percentage field, but a word is entered instead.
Identify and locate the referenced field, and verify that the type of entry is correct. For example, verify that letters are not entered in the ZIP Code field.
Element { } can't be empty according to the Schema
The tax authority determines the schema, which is the standard for e-filing.
These keywords indicate that a specific field needs to contain data to e-file the return.
Use the field description to locate the field that is missing data, and enter data in the corresponding input screen field; note that this may include entering a zero.
Chat now

error-icon

Triva isn't available right now.

Check out the support page for our phone number and hours

error-close