Check Invoice References Before XML Export

The short answer

Collect the recipient’s current instructions, review seller and buyer data and place each supplied reference in its intended field. Read local check messages, export the requested format and inspect the saved file. This is a data-checking workflow, not tax or legal advice.

Open the free tool

Collect the customer’s instructions before typing

Ask what the recipient needs to identify and receive the invoice. File format, routing reference, order reference and delivery channel are separate questions. Keep their written instructions available rather than interpreting one familiar identifier as the answer to all four. An illustrative customer may supply an order code and a separate department reference. Those example roles are not universal required fields for every transaction.

Create a short working note linking each supplied value to its intended purpose. Preserve spelling and punctuation rather than rewriting a reference into a more attractive form. If a value is missing or ambiguous, clarify it with the recipient. A plausible invented identifier can make a field look filled while making the document impossible to match. The aim is accurate correspondence to the order, not simply removing every empty space in the interface.

Separate seller, buyer and contact information

In “Your company”, check the seller’s details against your own records. “Customer” describes the buyer, which is not necessarily identical to a project nickname or the contact person who arranged the work. Review billing name, address and the person’s contact details separately. Similar names in a customer list can belong to different billing entities.

An “Electronic address” is a structured invoice field; entering it does not mean the tool has delivered the invoice through that route. The form can use email information for electronic address data in supported cases. Inspect the intended value rather than assuming all contact and identifier fields should contain the same text. E-Invoice Studio prepares and reads local files, without automatically submitting them to the recipient’s portal. A correct-looking address inside the data and a successful delivery are different checkpoints.

Give each reference its own meaning

“Buyer reference or Leitweg ID” serves a different purpose from your invoice number. Your own number identifies your document in your records; a reference supplied by the customer supports their matching or routing. Use the recipient’s actual instructions for a Leitweg ID rather than making one up. The official XRechnung references in the sources explain the format context, while the customer provides the values needed for its process.

“Order number”, “Project reference” and “Contract number” are also distinct fields. Do not paste the same value everywhere merely because there is space. For a fictional example, an order code could identify the purchase and a project code its internal activity. Your real case may use fewer fields. Explain uncertain instructions before export. A long description of the service does not replace a reference intended for automated matching, and a correct reference does not replace a clear description of what was supplied.

Recheck values after selecting a saved customer

Saved customers reduce typing but are not proof that all values remain current. After selecting one, read the buyer’s details and reference again. A stored reference can belong to an older arrangement, and changing the customer during a draft deserves another check of the already entered values. Do not assume the entire invoice has been reset just because one part of the form was filled automatically.

Compare dates, currency and items with the agreement as separate facts. A customer can be correct while the invoice still uses the wrong currency or an outdated service period. Use illustrative practice data only in an identified example, not in the real document by default. If the tax treatment is uncertain, resolve that with qualified support and current official guidance before issue. The software cannot establish the business facts or the legal eligibility behind a chosen tax case.

Read check messages in context

The local checks identify implemented field and calculation rules. When a message names a reference, locate that field and understand what the recipient supplied. Do not replace a missing reference with an arbitrary word just to clear the warning. When a message concerns totals, compare quantities, prices and adjustments; editing an unrelated identifier will not fix the arithmetic meaningfully.

A positive local status is not a guarantee that the recipient will accept the file. Profile versions, official validation and delivery requirements can add conditions. The linked official sources were checked on 22 October 2026. Use the current process appropriate to the requested format for formal validation. Preserve the report where your workflow needs it, distinguishing what the tool established from the commercial and administrative questions still to be confirmed.

Export and inspect the real structured file

Choose the requested output and download it. The writer produces supported CII XML and hybrid invoice output; the reader’s ability to read UBL does not imply an unchanged UBL export. Open the saved file in “Open & check” and inspect buyer, seller, dates, currency and references. A correct preview before downloading does not prove you selected the correct final file afterwards.

For a hybrid document, compare the visible page with its structured values. Editing only the printed PDF later can leave embedded data unchanged. Correct the issuing source and regenerate a coherent output through the applicable document procedure. If the recipient wants standalone XML, a printed preview is not a substitute. Keep the actual export with an identifiable version rather than relying on a screenshot of the form as proof of what was sent.

Complete the handover separately

Send the file yourself through the accepted channel and retain any response needed by your own process. The generator does not operate the recipient’s portal or an approved French transmission platform. Confirm receipt according to the customer’s procedure instead of equating a browser download with delivery. Keep the customer’s instructions with the work so a rejection can be investigated against the actual request.

If the file is rejected, identify whether the cause concerns routing, content, format or delivery. Preserve the unchanged rejected version and its report before preparing a correction. Follow the appropriate procedure for issued documents with professional support where required; this guide does not prescribe legal corrections. A concise handover note can identify invoice, export version and unresolved point. Clear record organization makes the next question easier without turning a technical checker into a universal legal approval.

Questions you might still have

Is the buyer reference my invoice number?

They serve different purposes. Use the customer’s instructions rather than substituting your own document number.

Should every reference field contain the same value?

No. Match order, project and contract information to their actual meanings.

Does selecting a customer prove the reference is current?

No. Recheck it after automatic filling and after changing customers during a draft.

Does an electronic address mean the invoice was sent?

No. It is data in the invoice; delivery is a separate action.

Does a clean local check guarantee acceptance?

No. Apply the recipient’s current official validation and submission process.

Can I fix only the visible PDF after export?

That can leave structured data inconsistent. Correct the source and create a coherent output through the appropriate procedure.

Sources & useful details

These guides are written from the current LoschaZ tools and the sources listed above. Examples are illustrations, not tests on every device or promises of an identical result.