Invoices, receipts and e-invoices
tebio can generate different billing documents depending on the product configuration, account settings and billing model. The distinction between invoice, receipt and eInvoice is particularly important.
These document types have different technical functions:
- An invoice documents a claim or billing against a customer.
- A receipt confirms that payment has already been made.
- An eInvoice is an electronic invoice in a structured format that can be processed by machine.
The documents that arise depend in particular on whether a product is configured as Prepaid or Postpaid, whether your account is B2B or B2C, and how invoicing, taxes and invoice settings have been set up.
Why is the distinction important?
Section titled “Why is the distinction important?”The distinction is important for:
- Customer communication
- Bookkeeping and financial accounting
- tax audit
- B2B billing processes
- e-invoicing obligations
- Support cases for invoices and payments
- API integrations with ERP, CRM or accounting systems
What is particularly relevant for business users is which document is displayed, provided or sent to a customer.
What is relevant for finance teams is whether a document can be processed and exported as an invoice, receipt, invoice correction or eInvoice.
What is relevant for API users is which resources, document types and status values are created in the background.
Invoice
Section titled “Invoice”An invoice is a billing document for services, products, fees or other items provided or to be billed.
An invoice is typically used when claiming an amount from a customer. The customer should pay the invoice amount or the amount will be collected via a configured payment method.
Typical use cases:
- Postpaid billing of subscriptions
- monthly or annual bill for business customers
- Invoice with payment term
- Billing for multiple subscriptions on a single invoice
- Invoice after an approval process
- Invoice for usage-based services
- Invoice with order number, project reference or contract reference
An invoice typically contains information such as:
- Invoice recipient
- Invoice number
- Invoice date
- Performance period
- Invoice items
- Net and gross amounts
- Taxes
- Payment Information
- legally required information
- optional references such as order number, project reference or contract reference
Receipt
Section titled “Receipt”A receipt confirms that a payment has already been made.
Receipts typically arise in prepaid scenarios where the customer pays before or during the order. Payment is at the beginning of the process here. The document then confirms that the amount has been paid.
Typical use cases:
- Prepaid subscription with direct payment
- Order via a hosted page
- Payment by credit card or PayPal
- digital products with immediate activation after payment
- B2C-oriented ordering processes with immediate payment completion
A receipt typically contains information such as:
- Customer or invoice recipient
- amount paid
- Payment date or receipt date
- purchased service or product position
- Tax information
- payment method used
- Reference for order or subscription
eInvoice
Section titled “eInvoice”An eInvoice is an electronic invoice in a structured format. It is not just a PDF document, but contains invoice data in machine-readable form.
eInvoices are particularly relevant for B2B billing processes because business customers often process structured invoice data in accounting, ERP or document management systems.
Typical use cases:
- B2B invoices
- Invoices to business customers with structured further processing
- Invoices with project reference, order number or contract reference
- Financial accounting processes with automated processing
- Sending invoices to companies or public clients
In tebio, the creation of e-invoices depends in particular on the account configuration and the billing model.
B2B, B2C and e-invoices
Section titled “B2B, B2C and e-invoices”When registering, it is determined whether the products are primarily aimed at private customers (B2C) or business customers (B2B).
This selection affects pricing logic, tax calculation and e-invoices.
Private customers (B2C)
Section titled “Private customers (B2C)”If you select Private customers (B2C), prices are managed and displayed gross, i.e. including taxes.
The tax calculation is from gross to net. This logic can cause rounding differences because the included tax and the net amount are mathematically derived from a gross amount.
For this reason, no e-invoices are created with this approach.
Typical documents in B2C scenarios are:
- Receipts
- Invoices without eInvoice format
- Payment confirmations
- Invoice corrections if necessary
Business customers (B2B)
Section titled “Business customers (B2B)”If you select Business customers (B2B), prices are managed and displayed net, i.e. excluding taxes.
The tax calculation is from net to gross. This logic avoids the rounding differences typical of gross-to-net calculations.
With this approach, e-invoices can be created provided the other requirements and settings are met.
Typical documents in B2B scenarios are:
- Bills
- eInvoices
- Invoice corrections
- structured billing documents
- Documents with order numbers, project references or contract references
Comparison: invoice, receipt and e-invoice
Section titled “Comparison: invoice, receipt and e-invoice”| topic | Invoice | Receipt | eInvoice |
|---|---|---|---|
| Main function | Document the claim or billing | Confirm payment | Provide invoices in a structured and machine-readable manner |
| Typical timing | Before or with payment request | After successful payment | When creating a B2B invoice |
| Common model | Postpaid | Prepaid | B2B postpaid |
| Typical target group | B2B and B2C | Especially B2C and self-service | Especially B2B |
| reference | Service, product, subscription, period | amount already paid | Invoice with structured invoice data |
| Open amount possible | Yes | Usually no | Yes |
| Machine readability | Not necessarily | Not necessarily | Yes |
| Typical usage | Invoice process, accounting, open items | Payment confirmation | Accounting, ERP, compliance, automated processing |
Connection with prepaid and postpaid
Section titled “Connection with prepaid and postpaid”The payment strategy of a product influences which documents are typically created.
Prepaid
Section titled “Prepaid”With Prepaid, the customer pays in advance for a service period or service. Payment is often made directly at checkout.
This model often creates:
- Receipts
- Payment confirmations
- Invoices without downstream payment collection, depending on the configuration
Prepaid is particularly relevant if the customer should only have access to the service after successful payment.
Example:
A customer books a digital subscription via a hosted page and pays directly by credit card. After successful payment, the customer receives a confirmation and, depending on the configuration, a receipt or another billing document.
Postpaid
Section titled “Postpaid”With Postpaid, the service is provided initially or billed collectively for a period of time. Billing takes place subsequently or at a defined billing time.
This model often creates:
- Bills
- eInvoices for B2B configuration
- Invoice corrections
- Documents for payment collection or payment terms
Postpaid is particularly relevant for business customers, usage-based billing, invoice runs and payment terms.
Example:
A business customer uses multiple subscriptions. At the end of the month, tebio generates an invoice for the services to be billed. With the appropriate B2B configuration, this can also result in an e-invoice.
Invoice corrections and credits
Section titled “Invoice corrections and credits”In addition to invoices, receipts and e-invoices, invoice corrections or credits can also arise.
An invoice correction is used when an invoice that has already been created needs to be corrected in whole or in part.
Typical cases:
- Invoice was canceled
- Invoice amount was incorrect
- Incorrect billing address or incorrect invoice recipient
- incorrect tax treatment
- subsequent correction of a position
- Goodwill credit
In the documentation, the term invoice correction should preferably be used when it comes to correcting an existing invoice.
The term credit can also be used depending on the technical context, for example in the case of goodwill or other amounts in favor of the customer.
Effects on open items
Section titled “Effects on open items”An invoice can create an open item if the amount has not yet been paid.
A receipt, on the other hand, typically only arises when a payment has already been made. As a rule, it does not document any outstanding amounts.
An e-invoice is technically still an invoice. It can therefore also create an open item if the invoice amount has not yet been paid.
It is therefore important for finance teams to not only check the document itself, but also:
- Payment status
- Payment transaction
- Journal entry
- Invoice corrections
- Export status for financial accounting or DATEV
Impact on customer communication
Section titled “Impact on customer communication”Depending on the configuration, tebio can automatically inform customers about new documents.
Examples:
- Invoice has been created
- Receipt has been created
- e-invoicing has been provided
- Payment was successful
- Payment failed
- Invoice was canceled
- Invoice correction was created
In order for such notifications to be sent, communication channels, event selection and message templates must be configured appropriately.
Where can I find the documents in the business portal?
Section titled “Where can I find the documents in the business portal?”Billing documents can be viewed in different places depending on the context:
- in the area of Finance
- in the customer view in the Invoices tab
- in the detailed view of an invoice
- in the detailed view of an order
- in the detailed view of a subscription
- in the Documents tab, if a document is linked to an entity
- in the events or message history when a document was sent
Which view is relevant depends on whether you want to check a specific document, the payment process, the order, the subscription or the customer context.
Avoid typical mistakes
Section titled “Avoid typical mistakes”Do not equate invoice and receipt
Section titled “Do not equate invoice and receipt”An invoice requests or documents an accounting. A receipt confirms a payment.
If a customer has already paid, a receipt is often more appropriate than another invoice.
Do not confuse e-invoice with PDF invoice
Section titled “Do not confuse e-invoice with PDF invoice”A PDF invoice is a visual document. An e-invoice contains structured invoice data that can be processed automatically.
Depending on the configuration, both forms of representation can appear together, but they are not technically the same.
Pay attention to B2B and B2C logic
Section titled “Pay attention to B2B and B2C logic”Whether e-invoices can be created depends largely on the account configuration.
For B2C accounts, prices are managed gross and tax calculation is from gross to net. Due to possible rounding differences, no e-invoices are created using this approach.
For B2B accounts, prices are managed net and tax calculation is from net to gross. This approach is the basis for e-invoices.
Additionally check payment status
Section titled “Additionally check payment status”A document alone does not always say whether a payment has been successfully completed.
If you have payment questions, always check the payment status, the payment transaction and, if necessary, the journal entry.
Use invoice correction instead of manual workaround
Section titled “Use invoice correction instead of manual workaround”If a final invoice is incorrect, it should not be corrected manually outside of the system.
Instead, use the designated processes for cancellation, invoice correction or credit note so that accounting, event history and documentation remain traceable.
API notice
Section titled “API notice”For API users, invoices, receipts, and eInvoices are part of multiple professional resources.
| area | Meaning |
|---|---|
| Invoice | Billing documents such as invoices, e-invoices or invoice corrections |
| Payment | Payment transactions, payment status and refunds |
| Order | Origin of many billing-relevant processes |
| Subscription | Ongoing service that is billed |
| Document | Documents created or uploaded |
| Event history | Document creation, shipping, payment or cancellation events |
| Journal | Accounting entries and traceability |
The API technical reference describes the available endpoints, parameters and response formats.