How to fix XML parse errors

1. Keep a copy and find the first error

Save an untouched copy before editing. Open the document locally and note the parser’s line and column, then inspect a few lines around that location. Fix the earliest error and parse again before chasing later messages.

For example, an invoice export may report a failure on a closing tag when the real mistake is an unclosed attribute quote above it. Reformatting is useful after parsing succeeds; indentation alone cannot repair broken syntax.

2. Match tags and close them in order

Opening and closing names must match, including case. Nested elements close from the inside out. In this example the amount belongs inside the invoice, so close amount first.

<!-- Broken -->
<invoice><amount>42</invoice></amount>

<!-- Corrected -->
<invoice><amount>42</amount></invoice>

3. Escape text and quote attributes

A literal ampersand in ordinary text must be written as &. Attribute values need matching quotation marks. Do not globally replace every ampersand: that can double-escape references that were already correct.

<!-- Broken -->
<vendor id=7>Parts & Service</vendor>

<!-- Corrected -->
<vendor id="7">Parts &amp; Service</vendor>

• Check literal less-than signs in text; write them as <.
• Look for duplicate attributes on the same element.
• If the error mentions encoding, check the saved file encoding against its XML declaration.

4. Check the document boundary

A document needs a single root element. Two invoice elements placed side by side are not a complete XML document. A containing invoices element makes this example well-formed, but the receiving system must also accept that structure.

<invoices>
  <invoice id="7"/>
  <invoice id="8"/>
</invoices>

5. Parse again, then check the receiving system

In XML Lens, reopen or paste the corrected source, inspect its structure, and check well-formedness. If you have the expected XSD, validate against that schema next. A file that parses can still contain an invalid date, a missing required field, or the wrong namespace.

Keep the original and corrected versions until the destination accepts the file. Compare them to confirm that you changed only the intended values or markup.

Common questions

Try the workflow in XML Lens

Explore the relevant Mac workspaces and their capabilities.