Is BT-10 the same as a PO number or Leitweg-ID?
It depends on what the buyer expects. The app maps common buyer reference, PO, routing reference, and Leitweg-ID messages to the supported reference field, but the buyer should provide the exact value.
BT-10 BuyerReference rejection
If a buyer ERP says BT-10, BuyerReference, Leitweg-ID, routing reference, or PO number is missing, use the rejection helper to map the message to supported invoice fields before regenerating the file.
Use it when the buyer gives an exact buyer reference, Leitweg-ID, purchase order, or routing reference that must appear in structured invoice XML.
Manual one-at-a-time XRechnung-oriented invoice creation and field inspection is free where supported. Bulk spreadsheet generation, saved mappings, reusable presets, and advanced design tools require Monthly or Lifetime access.
It depends on what the buyer expects. The app maps common buyer reference, PO, routing reference, and Leitweg-ID messages to the supported reference field, but the buyer should provide the exact value.
Ask the buyer for the exact BT or BR rule ID, missing field name, required profile, endpoint or buyer reference, and one accepted sample if available. Do not invent unsupported XML fields from a vague message.
No. It can address one supported field, but the final file still needs validation and buyer-side acceptance. This is not legal, tax, accounting, filing, or compliance certification advice.