Extensions

E-Invoice Intake

XRechnung, ZUGFeRD and Peppol invoices flow into the same approval rules as your PDF invoices.

More suppliers now send structured e-invoices, and an invoice workflow built for PDFs cannot read them. This add-on lets AI Invoice Intelligence or AI Accounts Payable Agent receive XRechnung, ZUGFeRD/Factur-X and Peppol invoices. Each one is validated, mapped to your accounting system and sent through the approval rules you already use. Approvers see a readable invoice, not raw XML.

  • XRechnung, ZUGFeRD/Factur-X and Peppol BIS 3.0 invoices received
  • Invalid invoices rejected with a clear reason
  • Same approval and coding rules as your PDF invoices
$1,500 10–20 working days
A brass letter tray beside a three-slot sorting frame, showing structured e-invoices sorted into the approval flow.

What it is

E-Invoice Intake adds structured e-invoice handling to AI Invoice Intelligence or AI Accounts Payable Agent. It receives XRechnung, ZUGFeRD/Factur-X and Peppol BIS 3.0 invoices from one inbox or one Peppol access point. Each invoice is validated, mapped to your accounting system and sent through your existing approval and coding rules.

Why businesses buy it

As e-invoicing spreads across the EU, finance teams end up with two invoice processes: one for PDFs and another for XML files. That doubles the work and the risk of missed approvals. This add-on brings e-invoices into the workflow you already trust, with format checks up front. Approvers keep one process and one view. The written scope fixes the formats, the inbox or access point, the testing and the support period before you order.

Problems this solves

Suppliers send XML e-invoices your current workflow cannot read

The add-on receives XRechnung, ZUGFeRD/Factur-X and Peppol BIS 3.0 invoices from one inbox or access point. It maps their fields to the accounting system already connected to your parent product.

Malformed e-invoices slip into approval and cause rework later

Format validation checks every incoming e-invoice and rejects invalid ones with a clear reason. Your team can ask the supplier to resend before anything reaches an approver.

Approvers cannot make sense of raw XML invoice files

A readable invoice view shows supplier, amounts and lines like a normal invoice. The invoice then follows the same approval and coding rules as your PDF invoices.

Scope card SKU UPM-A0059

E-Invoice Intake

Everything this build includes, written down before you pay. Choose how you want it, own the code or license it yearly, then the delivery speed and any add-ons.

$1,500 one-time build price

What is included

Channel
1 inbox or 1 Peppol access point
Integrations
The accounting system already connected to the parent product
Knowledge
3 formats: XRechnung, ZUGFeRD/Factur-X and Peppol BIS 3.0
Workflows
Receive, validate, map and route e-invoices for approval
Languages
As per the parent product
Testing
20 sample invoices tested
Revisions
1 round
Handoff
Written handover report
Support
14 days after launch

A good fit if

Suppliers have started sending XML e-invoices that your current invoice workflow cannot read.
You already run, or are buying, AI Invoice Intelligence, AI Accounts Payable Agent or one of their editions.
You receive e-invoices by email or through a Peppol access point.
Approvers need to read an e-invoice without opening raw XML.

Not the right fit if

You do not yet have an Upmark invoice product. Start with AI Invoice Intelligence or AI Accounts Payable Agent.
You need to send e-invoices to your own customers. Outbound issuing is outside this add-on and needs a Change Quote.
You want the whole finance back office automated together. See AI Finance Ops Stack.
You need archiving under GoBD or other retention rules. Speak to your tax adviser and archive provider about that.

How it works

  1. You share the parent product's order reference and access to one e-invoice inbox or Peppol access point.
  2. Incoming XRechnung, ZUGFeRD/Factur-X and Peppol BIS 3.0 invoices are picked up automatically.
  3. Each invoice is checked against its format rules; invalid ones are rejected with a clear reason.
  4. Valid invoice fields are mapped to the accounting system already connected to your parent product.
  5. Approvers see a readable invoice view, and the invoice follows the same approval and coding rules as your PDF invoices.
  6. We test twenty of your real sample e-invoices, then hand over a test report and a written walkthrough.

What you provide within 72 hours

Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.

  • The order reference of your Upmark invoice or accounts payable product.
  • Access to your Peppol access point or e-invoice inbox, shared by invite or a key you control.
  • Twenty sample e-invoices from your suppliers.
  • Your business information (company basics, hours and brand voice), shared during intake.
  • One decision-maker who approves the field mapping and test results.
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.

Timeline

Start Order reference, inbox or access point, and sample invoices confirmed.
Week 1 Formats reviewed and field mapping agreed.
Week 2 Intake, validation and the readable approver view built.
Week 2 Twenty sample e-invoices tested through your approval rules.
Week 2 Your review and one revision round.
Go-live E-invoice intake live, walkthrough recorded.
Delivery options, in working days (Monday to Friday) from completed intake. They can extend because of national or public holidays, technical issues outside our control (such as platform outages, third-party changes, account approvals or access delays), or natural disasters and other events beyond our control. If a delay happens, we tell you in writing with a new date.
OptionDelivery timePrice
Standard10–20 working days$1,500

What you receive at handover

  • Intake of XRechnung, ZUGFeRD/Factur-X and Peppol BIS 3.0 invoices from one inbox or one access point
  • Format validation with rejection reasons
  • Field mapping to the accounting system connected to your parent product
  • A readable invoice view for approvers
  • A test report on twenty sample invoices, a short written walkthrough and 14 days of support

Expected benefits and how to measure them

  • Can bring e-invoices into one approval process with your PDF invoices
  • Helps catch malformed invoices before they reach approvers
E-invoices handled outside the workflow
Count e-invoices processed by hand in the month before launch and in the month after.
Rejected e-invoices and reasons
Review the rejection reasons each month after launch to see which suppliers need to fix their files.
Days from receipt to approval
Compare receipt and approval dates for e-invoices in your accounting system before and after launch.

Before you start: Record how many e-invoices arrive each month, which formats they use and how they are handled today.

These are things to track, not promised results. Outcomes depend on your data, your team and your market.

Running costs

Your Peppol access point subscription, if you use one, is paid to that provider. Otherwise running costs are as per the parent product. We charge once for the add-on and nothing per invoice.

Ask about running costs

Custom requirements

A second inbox or access point, outbound e-invoice issuing or archiving under retention rules is outside this add-on. Add a note at checkout for a written Change Quote.

Request a custom version

Keep it running

E-invoice intake is maintained under the parent product's maintenance, which grows a little to include this add-on. Format updates and field changes come out of its monthly change hours. That suits teams whose suppliers move to e-invoicing in stages.

Adds $75/mo to maintenance

Covered by the main product's maintenance, which grows by this amount.

How maintenance works

How this compares

Do it yourself with a SaaS toolHire a custom agencyUpmark Labs
Price An e-invoice viewer or converter is usually a monthly subscription An integration partner quotes per project Ours is one fixed price, shown before you buy
Approval A separate tool with its own workflow Depends on the build Ours uses your existing approval and coding rules
Validation Format check only Agreed during the project Ours rejects invalid invoices with a clear reason
Readability Depends on the tool Depends on the build Ours gives approvers a readable invoice view

Questions about this product

Which e-invoice formats does E-Invoice Intake handle?

Three: XRechnung, ZUGFeRD/Factur-X and Peppol BIS 3.0. These cover most structured invoices received by businesses in Germany, Belgium and other EU countries. Each invoice is checked against its format rules. If your suppliers send another format, mention it at intake and we confirm whether it can be added through a Change Quote.

Do we need a Peppol access point for e-invoice intake?

Only if your suppliers send through the Peppol network. Many German suppliers send XRechnung or ZUGFeRD files by email, which a dedicated inbox can receive. If you use Peppol, the access point subscription is paid by you to your chosen provider, and we connect one access point.

Will this make our business compliant with e-invoicing rules?

It helps you prepare by letting your invoice workflow receive and validate structured e-invoices. It is not tax or legal advice, and it does not confirm compliance. Archiving under GoBD or other retention rules is not included. Check your full obligations with your tax adviser.

Can we send e-invoices to our own customers with it?

No. This add-on handles incoming supplier invoices only. Issuing outbound e-invoices to your customers is a separate job that usually involves your billing system. If you need it, add a note at checkout and you receive a written Change Quote.

What do approvers see instead of the raw XML file?

A readable invoice view, showing supplier, amounts, tax and line items laid out like a normal invoice. Approvers work in the same approval flow they already use for PDF invoices. They never need to open or understand the underlying XML file to approve or query an invoice.

What happens when an incoming e-invoice fails validation?

It is rejected with a clear reason, such as a missing mandatory field or a format error. Your team can then ask the supplier to resend. Invalid invoices do not enter the approval flow. The test on twenty of your sample invoices shows how your suppliers' files perform before launch.

Read supplier e-invoices the same way you read PDFs.

Add E-Invoice Intake and XRechnung, ZUGFeRD and Peppol invoices are validated, mapped and routed through the approval rules your team already trusts.

Works well with

Brass balance scales above a closed logbook with a green ribbon, showing human-reviewed hiring decisions on record.
Extensions

AI Hiring Compliance Pack

Adds human-review checkpoints, decision logging, draft candidate notices and an auditor-ready data export to AI Resume Screening or AI Interview Intelligence; helps…

From $1,500 Delivery in 10–20 working days
Stacked archive boxes with one open under a brass magnifier, showing past documents processed and sample-checked.
Extensions

Historical Document Backlog Processing

Adds a one-off backlog run to your Upmark document or invoice extraction product: up to 5,000 pages of existing documents processed, sample-checked…

From $1,500 Delivery in 10–20 working days
Half-open ceramic drawer of rolled paper bundles under a closed one, data copied and kept somewhere safe.
Extensions

Offline Export and Backup

Adds scheduled export and backup of an existing product's data. Requires an existing or simultaneously purchased Upmark Labs product.

From $1,500 Delivery in 10–20 working days