A-Cube Transfer
A-Cube Transfer sends the files your ERP already exports. It converts them to XRechnung or ZUGFeRD when needed and delivers them through A-Cube's e-invoicing service for Germany. Upload through SFTP without writing an invoicing integration, or use the file upload API from your application.
For onboarding, uploads, tracking and receiving, see the complete Transfer documentation. This page covers the formats, connection details and outcomes for Germany.
Before your first upload, A-Cube activates your account and agrees the file format with you. You can use the standard layout or have A-Cube build a conversion for your CSV, JSON or XML export.
In Germany, Transfer sends your invoices as XRechnung, the German standard based on the European norm EN 16931. A-Cube's German invoicing service delivers them to your customer over Peppol or by email. By email, your customer gets the XML and a PDF of the invoice generated by A-Cube.
How it works
- Your ERP exports the documents as files, for example a CSV spreadsheet or XRechnung or ZUGFeRD XML.
- You upload the files to the SFTP folder A-Cube provides. Your application can also upload a file with an HTTP call to the file upload API, after A-Cube confirms access for your destination.
- A-Cube reads each file and, if it is not XRechnung or ZUGFeRD yet, converts it. A CSV file can contain several documents: each one becomes a separate electronic document.
- A-Cube delivers each document through its e-invoicing service for Germany.
- You check processing and delivery separately. The tracking API reports file processing and gives you each document's identifier. Use that identifier in the invoicing API to check the later delivery outcome.
When to use it
| Use | When |
|---|---|
| A-Cube Transfer | Your system can export invoice information, and you want to send it as it is, without writing code that builds each document. |
| Invoices API | Your application creates each document in XRechnung or ZUGFeRD and sends it to A-Cube with an API call. |
Availability describes how A-Cube sets up each capability:
- Available: ask A-Cube and it is enabled for you, with no development.
- Custom: A-Cube builds it for you, for example the conversion of your own CSV layout.
Get started
- Contact A-Cube with your destination, a sample export with test data, and your preferred channel (SFTP or file upload API). Request sandbox access to try the integration.
- A-Cube confirms your format, credentials, connection details and where to read the delivery outcome. See Onboarding and access.
- Upload a first file with the Quickstart SFTP. Use the sample and sandbox username for your destination.
The shared guides cover SFTP uploads, file upload API requests, processing statuses and errors and corrections.
Formats for Germany
| File | What A-Cube does | Availability |
|---|---|---|
| UBL XML in Peppol BIS Billing 3.0 or XRechnung | Sends it as XRechnung. Several files can travel in one ZIP archive. | Available |
ZIP archives, End-to-end IDs and the other features shared by every destination are described in the A-Cube Transfer documentation.
What you get back
| What | Where | Availability |
|---|---|---|
The status of every invoice, for example sent | German invoicing API | Available |
| Errors found in your files, and the reasons the German invoicing service rejected an invoice | A-Cube dashboard and API | Available |
| A webhook for each invoice with an End-to-end ID, when it is accepted or fails | Your notification URL | On request |
Connect
During onboarding, A-Cube enables your account in sandbox, a test environment, in production, or in both.
| Item | Value |
|---|---|
| SFTP host | transfer.acubeapi.com, port 22, the same for sandbox and production |
| SFTP username | <your-email>--de.api.acubeapi.com, where <your-email> is the email of your A-Cube account |
| SFTP username, sandbox | <your-email>--de.api.acubeapi.com-sandbox |
| REST API base URL | https://transfer.api.acubeapi.com |
| REST API base URL, sandbox | https://transfer-sandbox.api.acubeapi.com |
| REST API | country is DE. See Upload a file for the full request |
| Size limit | 5 MiB per XML file, otherwise the file fails with FILE_TOO_LARGE |
Before your first upload, register the seller as a Legal Entity in the German invoicing API, in the same environment. See SFTP and REST API for how to connect.
Format details
UBL invoices
Send one UBL invoice in each XML file. A-Cube sends it to the German invoicing service as XRechnung 3.0: when its cbc:CustomizationID is the Peppol BIS Billing 3.0 one, A-Cube replaces it with the XRechnung one, and it changes nothing else. See the UBL XML to XRechnung mapping reference.
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>
The German invoicing service validates the invoice and chooses the delivery channel from the buyer's electronic address: a Peppol participant ID, or an email address with schemeID="EM". For email delivery, the seller must carry the German VAT ID of its Legal Entity. See Delivery channels.
Outcome in the German invoicing service
Every invoice you send goes through two stages, and each stage has its own status:
- A-Cube reads your file and hands each invoice to A-Cube's German invoicing service. You follow this stage with the processing status.
- The German invoicing service validates the invoice and delivers it to your customer. Its status tells you how delivery went.
transmitted during file processing means that the German invoicing service accepted the invoice. Delivery can still fail later, and the processing status does not change when it does: always check the invoice status.
The document's transmission_uuid is the invoice UUID in the German invoicing API. Use your sandbox token and replace <transmission-uuid> with the value from the tracking API:
curl --fail-with-body -sS 'https://de-sandbox.api.acubeapi.com/invoices/<transmission-uuid>' \
-H 'Authorization: Bearer <your-sandbox-token>' \
-H 'Accept: application/json'
For email delivery, sent means that the email was handed over for delivery: it becomes delivered once it reaches the recipient's mail server, or delivery_error if it bounces. To be notified of every change, configure the German invoicing webhooks.
Contact A-Cube to activate it for your account, in sandbox, in production or in both.