Structured invoices

Create e-invoices and reuse their data.

An e-invoice contains structured invoice data. Accounting Scalable uses these data from invoice export through to posting suggestions for incoming documents.

E-invoice checks in your daily bookkeeping run

Your AI checks the invoice. You decide unresolved cases.

In your configured MCP agent workflow, your assistant considers e-invoice requirements before creating an entry. If suitable structured invoice data is missing, it checks the information available for an applicable transition rule or exception.5

  1. Identify the format

    Consider both ZUGFeRD embedded in a PDF and standalone XML invoices. Missing embedded XML alone does not establish a breach of the requirements.

  2. Assess the requirements

    Consider the supply period, the transaction concerned and known transition rules or exceptions together. An unknown supplier turnover remains unknown.

  3. Ask a focused question

    If an e-invoice is required, or the decisive assessment remains unresolved, the agent holds that receipt for clarification with you. It can continue processing other resolved receipts.

Example clarification request
This invoice is missing suitable structured data. The information available indicates that an e-invoice is required; no applicable exception is documented. Is it available separately, or can you add information about the transaction? The proposed entry remains open until this is clarified.

You remain responsible for the legal assessment. The agent does not replace an unknown value with zero or treat input VAT as lost solely because an invoice is a PDF.

Make time and cost tangible

What two fewer minutes of review could mean.

Assume you process 100 invoices per month. If your active time for format review and clarification falls from three minutes to one minute per invoice on average, the worked example is:

Manual review
5 h 0 min
With agent assistance
1 h 40 min
Illustrative time saving
3 h 20 min
At an hourly time value of €60
€200Time value per month

Assumptions: 100 invoices × (3 − 1) minutes = 200 minutes. 200 ÷ 60 × €60 = €200 of time value per month.

Illustrative model, not a measured customer saving. The one-minute assumption includes the average human review and clarification effort assumed in this example.6

Analysis of a structured incoming document with invoice data and review notes
Structured incoming document analysis using a synthetic example.

The feature scope

What you can do with it.

Create XRechnung and ZUGFeRD, analyze structured incoming documents and import invoice data without retyping.

Include e-invoice requirements in the review

Your configured MCP agent assesses missing structured invoice data in the context of the supply period, transition rules and exceptions. If a required e-invoice is missing or the case remains unresolved, it asks you and leaves the receipt open.

One document version, suitable formats

Generate PDF, ZUGFeRD/Factur-X or XRechnung from the same invoice version. Validations help identify missing or contradictory details before final export.12

Recognize incoming documents

The application analyzes existing UBL, CII and ZUGFeRD documents by content. Recognized invoice data appears with notes and possible blockers.3

Data instead of retyping

Transfer recognized invoice data into the posting form. Check accounts, amounts and taxes before posting.4

Preserve the original and posting link

The original document stays linked to the entry. Preview and download help you understand the invoice and structured data.

How to work with it

A clear workflow.

  1. Choose a format or store a document

    Choose PDF, ZUGFeRD or XRechnung for export or upload a structured incoming document.

  2. Review the result

    Check required details, totals, tax groups and accounting notes.

  3. Continue with control

    Finalize the outgoing invoice or complete the suggestion for the incoming invoice in the posting form.

Your questions

Brief answers.

Which output formats can I create?

Create PDF invoices, ZUGFeRD/Factur-X and XRechnung from your invoice version.

How do I use incoming e-invoices?

Store the document, review recognized invoice data and transfer the posting suggestion into the posting form.

Notes and requirements

  1. The profiles and versions supported in the application are available. Not every e-invoicing profile is fully covered.

  2. Creating an XRechnung does not include general submission to all public invoicing portals.

  3. Incoming document recognition is part of general journal bookkeeping; it is not a complete purchasing or accounts payable workflow.

  4. Unclear account allocation, warnings and blockers require professional review.

  5. The check requires the current e-invoice review workflow in your app instance, suitable MCP tools and a configured agent. It is not individual tax advice or a guarantee of input VAT deduction. Correction, objective evidence and a justified assumption of transitional eligibility may be relevant separately.

  6. The times and hourly rate are illustrative assumptions, not product measurements. Actual effort depends on invoices, clarification, setup and your review. App and AI costs have not been deducted. The time value is not a promised cash saving or tax saving.

  7. The offering is exclusively for businesses within the meaning of section 14 BGB.