- Create orderdoneWien → Hamburg · 8
I prepared the transport details. Review the route, cargo and missing information before approval.
Billing & e-invoicing
Invoice right after the POD.
As an e-invoice. With accounting export.
As soon as the proof of delivery arrives, the billing agent creates the invoice – single or collective, with correct VAT logic, as an e-invoice and with a posting batch for your accounting.
LogCon · Transport file
Invoice R-2026-001187
Total€1,480.00
E-invoice (ZUGFeRD)XRechnungPeppol
- BMD posting batch
Transport workflow illustration
Billing without rework
Outgoing invoices
Single and collective invoices from orders, price from rate card, surcharges included.
Self-billing for carriers
Self-billing credit notes for subcontractors straight from the order.
Incoming invoice checks
Compared with the agreed price, duplicate detection, deviations as proposals.
E-invoicing
ZUGFeRD 2.3 (PDF/A-3), XRechnung, Peppol BIS 3, ebInterface, FatturaPA and KSeF – validated against EN 16931.
BMD & DATEV
Posting batches for BMD NTCS and DATEV EXTF – for you or your tax adviser.
VAT logic
Standard, reverse charge and tax-exempt export per country and customer.
From delivery to posting batch
- 01
Receive POD
Driver app or document agent report the delivery.
- 02
Create invoice
The billing agent prepares the invoice for approval.
- 03
Send
The ZUGFeRD invoice (PDF with embedded XML) goes to the customer by e-mail – or as an e-invoice via Peppol, e-rechnung.gv.at, KSeF or SDI.
- 04
Export
The posting batch for BMD or DATEV is ready.
Ready for e-invoicing mandates
- EN 16931 compliant formats
- Country-specific obligations stored in the country packs
- Invoice number ranges per tenant
- Invoices are never deleted, only cancelled
- Pallet account considered in billing
- Peppol sending and receiving via an access point (Storecove, ecosio or Tickstar) – interface built, contract with the access point required
Frequently asked questions
Which e-invoice formats are supported?
ZUGFeRD 2.3/Factur-X as PDF/A-3 with embedded XML, XRechnung (UBL and CII), Peppol BIS 3, ebInterface 6.1, FatturaPA and KSeF FA(3). Every e-invoice is validated against the official rules (EN 16931, XRechnung, Peppol) before sending.
Can we send invoices via Peppol?
The interface to Peppol access points (Storecove, ecosio, Tickstar) is built. For sending you need a contract with an access point; the recipient’s Peppol ID is checked in the Peppol directory (SML/SMP) beforehand. The route has not yet been accepted in live operation.
Does the export work with our tax adviser?
Yes. BMD and DATEV posting batches are the standard formats for tax advisers in Austria and Germany.
Copilot
Your transport-file Copilot
Find orders, understand operations and prepare changes using the context of your current page and tools available to your role.
Relevant workflows: Review invoice details and prepare proposals within your accounting permissions.
Interactive simulation · no customer data, no sending
Demo · Dispatch
Copilot
Prepare an order Vienna → Hamburg for 8 pallets.
Prepare a change
PendingMail agentCreate orderL2 – Approve
86%
Reasoning: Route and cargo come from this fictional request. Loading time, customer and price still require review.
RouteAT Wien → DE Hamburg2 stops
Shipments1 shipment
Transport workflow illustration
Available tools depend on role, plan and configuration. Copilot mutations prepare proposals. Background agents separately follow configured autonomy levels.