UUltraTechGermany

ERP & CRM · remote, across Germany

SAP Interfaces — Connect the Systems Instead of Retyping

We build interfaces between SAP and the systems around it — shop, CRM, warehouse, carriers, bank, tax adviser — using OData services, BAPI and RFC, IDoc, and, where middleware earns its place, SAP Integration Suite (Cloud Integration, formerly CPI). Every interface gets error handling with a restart point, not a silent failure.

Most duplicate data entry in a mid-sized company is not a process problem but a missing interface: orders retyped from the shop, delivery notes carried over from the warehouse system, incoming payments reconciled by hand from the bank portal. An interface takes that work over — provided it is built so that somebody notices when it stops. That is where most of them fail: not on the format, on the error handling.

  • Reply the same working day
  • Written quote
  • Anywhere in Germany
  • Payment after handover
Technology
IDoc, RFC/BAPI, OData, REST
Error path
Named per interface
E-invoicing
XRechnung, ZUGFeRD
Way of working
Remote
Service area
Anywhere in Germany
Reply
The same working day
Payment
After handover

Use cases

Typical jobs

Usually one of these:

Services

What we take on

  • OData services (SEGW or RAP) for web and app access to SAP data
  • Integration via BAPI and RFC, including custom function modules where the standard offers nothing
  • IDoc channels set up and extended: partner profiles, ports, processing, monitoring
  • Integration flows in SAP Integration Suite (Cloud Integration, formerly CPI)
  • Shop and marketplace integration: articles, stock, prices, orders, delivery status
  • Logistics integration: shipping orders, tracking, label printing
  • Payments: importing statement formats, producing payment runs, preparing reconciliation
  • Accounting export for the tax adviser, including DATEV-readable formats
  • E-invoicing to EN 16931 — output as XRechnung (pure XML) or ZUGFeRD 2.x (PDF with embedded XML), plus inbound processing
  • Monitoring and error handling per channel: restart point, notification, reprocessing

Cost

What does an interface cost?

A defined analysis comes before the work; then a written quote.

ItemHow it is charged
Specification per interfaceFixed price in the quote
Build and testTime and materials, estimated in the quote
Working time for analysis and deliveryTime and materials, amount stated in the quote
BillingAt least 1 hour, then in full hours
PaymentAfter the work and handover: SEPA bank transfer, invoice or PayPal

What drives the price

  • Number of interfaces
  • Technology on the other side
  • Data volume and frequency

Extra work that only shows up on site is agreed with you first – nothing is charged without your consent.

  • SEPATransfer
  • Invoice
  • PayPal

For your purchasing department

  • Quote

    In writing, up front: labour, material and travel are stated before any work starts.

  • Payment

    After the work and handover: SEPA bank transfer, invoice or PayPal. No prepayment.

  • Contact

    We reply the same working day, in English or German.

  • Supplier details

    UltraTech Germany · Leipziger Straße 40, 10117 Berlin, Germany · VAT ID DE463530263 · Legal notice

Quote

For an accurate quote

A few facts are enough.

  • Which systems should be connected?
  • Which data, how often?
  • Documentation of the other side
  • Who looks after the other side?

Process

How a job runs

  1. 1

    Agree the channel and its trigger

    Which data, in which direction, how often, and who notices a failure. That last question decides the build — an interface with no named owner eventually fails silently.

  2. 2

    Choose the technology

    OData, RFC, IDoc or file, with or without middleware. We recommend the simplest option that will hold. An Integration Suite earns its cost above a certain number of channels, not for the first one.

  3. 3

    Build and test the failures

    Tested with your data and explicitly with the failure cases: incomplete record, duplicate delivery, counterparty unreachable. What happens then has to be decided in advance.

  4. 4

    Hand over with an operating note

    You get a description of the channel, its error messages and its reprocessing — written for whoever has to look at it on a Monday morning.

FAQ

Frequently asked questions

When does German B2B e-invoicing become mandatory, and what does it mean for SAP?

German businesses have had to be able to receive structured e-invoices since 1 January 2025. Issuing is phased: from 1 January 2027 for businesses with more than 800,000 euros of prior-year turnover, and from 1 January 2028 for all domestic B2B supplies. The legal basis is the Wachstumschancengesetz, via section 14 of the German VAT Act. Technically it is EN 16931, which both XRechnung and ZUGFeRD 2.x satisfy. In SAP it touches outbound, inbound processing and archiving — not a project for the December before.

Do we need SAP Integration Suite for this?

Not necessarily. A single channel can be built directly, as an OData service, an IDoc channel or a file handover. Middleware earns its place when several systems share several channels, when mappings should be maintained centrally, or when you need monitoring across all of them. It is a licensing and operations question that should be settled before development starts — and we will tell you plainly if you do not need it.

What happens if the counterparty is unreachable?

Whatever you decided. By default we build retries with a wait, a restart point, and a notification to a named address if the channel still is not running after several attempts. What matters is that an outage is noticed — not discovered at the month-end close.

Can you take over an existing interface?

Usually yes, documentation or not. It then starts with a survey: what runs, how often, with which errors. Often the conclusion is that the channel itself is sound and only the monitoring is missing.

Can you connect to DATEV?

We deliver the accounting data in a format your tax adviser can import, and agree the field and account mapping with them beforehand. That agreement is the real work; the format is the easy part.

Sources

Standards and sources

Where a standard or a law gives a number, this page states it with its source. Where sources disagree, we give no number – your specification decides.

Show sources
  1. [1]§ 14 German VAT Act – issuing invoices, e-invoicing (German)
  2. [2]§ 27(38) German VAT Act – transition rules 2025 to 2027 (German)
  3. [3]XRechnung – the EN 16931 standard (KoSIT / xeinkauf.de)
  4. [4]SAP News, 4 Feb 2020: mainstream maintenance for SAP Business Suite 7 to end of 2027

Enquiry about SAP Integration and Interface Development

  • Free initial consultation
  • Reply the same working day
  • Work by appointment
  • across Germany
Request a quote+49 30 50930365

For an accurate quote

  • Which systems should be connected?
  • Which data, how often?
  • Documentation of the other side
  • Who looks after the other side?
  • SEPATransfer
  • Invoice
  • PayPal