Skip to content
Help support@rechnungskit.de
Topics: Getting started

Test mode (sandbox)

In test mode you try Rechnungskit without risk. Test documents go through the same pipeline as real invoices but count nowhere and never leave the system. How test invoices come about, test payments and go-live.

Updated

In test mode you can try Rechnungskit without risk: documents go through the same pipeline as real invoices, but they count nowhere and never leave the system. Test mode is free and has no time limit. This page shows when you'll see a test invoice, what happens to your real data, what you pay test payments with and what happens at go-live.

When do I see a test invoice?

That depends on what you sell. Test mode follows the same rule as live operation later:

  • Digital products and services (software, courses, consulting, vouchers): the test invoice is created as soon as order and payment match. For an order you create yourself with payment method invoice, it's created right away.
  • Goods you ship: the test invoice is only created at shipment. Until then the order shows as "Awaiting shipment" under Orders, even if it's already paid. The same goes for an order you create yourself "on invoice".

The reason: an invoice has to state the date of supply (§ 14(4) sentence 1 no. 6 UStG). For goods that are shipped, that's when shipping begins, so the shipping day, not the payment day (Section 13.1(2) sentence 2 UStAE). That's why Rechnungskit writes the invoice once the shipment is reported.

When the test invoice is created
For goods, shipping decides
Digital or a serviceOrder and payment match
Right away
Goods, not shipped yetPaid or on invoice, status "Awaiting shipment"
No invoice yet
Goods, reported as shippedThe shipping day becomes the date of supply
Test invoice ready
Test mode works like live operation: goods are invoiced at shipment.

Report the shipment of a test order like this, and the test invoice shows up under Invoices:

  1. Shopify: open the test order in Shopify and fulfill the items ("Fulfill items"). Shopify reports the shipment to Rechnungskit.
  2. WooCommerce: set the test order to "Completed".
  3. Shopware: set the delivery status of the test order to "Shipped". Rechnungskit checks Shopware every 15 minutes, so the invoice can take a moment.
  4. An order you created yourself, Rechnungskit Checkout or a subscription box: click "Mark as shipped" on the order under Orders.

If you only want to see what your invoice looks like, use the live preview under Settings → Documents → Invoice template. It shows a sample invoice with your logo without creating a document.

While a test order with goods waits for shipment and there's no test invoice yet, Rechnungskit also says so under Invoices. Kit gives you the affected order numbers if you ask.

Rechnungskit, Invoices in test mode without a test invoice: note "No test invoice yet? Your goods haven’t shipped." with the text "For goods, the invoice is created when the order ships. Mark the test order as shipped and the test invoice appears.", below it "Waiting for shipment: M-2026-0001, #1001", the button "Go to orders" and the link "How it works"

Connecting real data: what happens and what doesn't

You can connect your real shop and your real payment providers while your current system keeps running. Rechnungskit reads orders and payments and turns them into TEST documents that never leave Rechnungskit. It changes nothing about your orders, sends no invoices, passes nothing to your tax advisor and charges you nothing for test documents.

Real connections in test mode
In test mode, no document leaves Rechnungskit
What happensreading along
Readorders, payments, refunds, payouts
Storein Rechnungskit, marked as test data
Webhookonce when you connect, so events arrive
VAT IDreal check with the BZSt
ResultTEST documents with PDF, only in Rechnungskit
What never happensin test mode
Your shopno change to orders, payments, customer data
Moneyno payment, refund or direct debit on its own, no checkout or subscription charges with live credentials
Invoice emailto your customers strictly blocked
Tax advisorDATEV export only as a test export (TEST_ in the file name), cannot be locked, no ZM
Costtest documents are not billed
Double invoicesyour old system stays in charge
You test Rechnungskit's checkout and subscriptions with test credentials that you add next to your live connection. How that works is explained below.

What Rechnungskit does in test mode

  • Read: Rechnungskit pulls orders, payments, refunds and payouts from your shop and payment provider and stores them marked as test data.
  • Set up a webhook: when you connect, Rechnungskit creates a webhook at Stripe, PayPal, Unzer, the Shopify app and WooCommerce, so new events arrive right away. If you disconnect Shopify or WooCommerce, Rechnungskit removes its webhooks there again.
  • Create TEST documents: with PDF and EN 16931 validation, visible only in Rechnungskit.
  • Check VAT IDs: if a business customer has a VAT ID (USt-IdNr.), Rechnungskit checks it for real with the BZSt (German Federal Central Tax Office), in test mode too. Your own VAT ID and the customer's VAT ID, company name and address go to the BZSt for this.
  • Classify products: in test mode Kit applies its suggestion itself to products without a type of service, including food, books and digital services. The overview then says "Kit classified … products itself". Under Products → "Classified by Kit" you see them and change a type of service right on the product. If everything fits, confirm the classifications with "Looks right", on the Overview or under Products. The notice then disappears. In live mode Kit only applies the standard rate itself and suggests everything else to you.

What never happens in test mode

  • No changes in your shop: Rechnungskit changes no orders, payments or customer data in your shop or at your payment provider.
  • No money on its own: Rechnungskit triggers no payments, refunds or direct debits. In test mode, the checkout and subscriptions do not charge with live credentials.
  • No emails to your customers: invoice emails are strictly blocked for test documents, even to you. Other customer emails such as the data request, payment request and payment reminder come to you instead, so you can see what would go out in live mode. Which ones those are is listed under Customer emails in test mode.
  • Nothing real for your tax advisor: Rechnungskit sends them nothing. In test mode a DATEV export is always a test export: marked (TEST_ in the file name), it cannot be locked and is deleted at go-live. The ZM (EC sales list) stays empty, the OSS return cannot be locked, and there is no BOP file. Your tax advisor sees your test data in their reports, marked "Test data".
  • No cost: test documents do not count toward your billing.
  • No double invoices: until go-live, only your current system issues invoices.

Customer emails in test mode

In test mode Rechnungskit sends no email to your customers. Emails you should check go to you instead: to the contact email from your settings, otherwise to the owner's. Each one has "[TEST]" in front of the subject and a yellow note at the top, for example: "Test mode: in live mode this payment reminder would go to your customer kim@example.com. Rechnungskit sends no emails to customers while test mode is on, so you get it instead." If no address of yours is on file, nothing goes out, and nothing goes to the customer either.

Email In test mode What you see in the app
Invoice email (including "Resend") blocked, even to you on the document, the note "TEST document: it is never emailed …" instead of the send button
Data request ("Request details") to you, the link works "Test mode: sent to you instead of the customer." and "Requested on … (test, sent to you)"
Automatic data request (document rule) off nothing
Payment request (prepayment) to you "Test mode: sent to you instead of the customer." and "Payment request on … (test, sent to you)" on the order
Payment reminder (pay by invoice) to you, text only, without the invoice attached under Open items, "Reminder on … (test, sent to you)"
Subscription notices to you nothing extra

Why is no invoice attached to the test payment reminder? In live mode the original invoice is attached as a PDF. A test document is never emailed, though, not even to you, so that nothing circulates like a real invoice (§ 14c UStG). That is why in test mode you get only the reminder text, and the note at the top says the attachment is missing.

Lots of reminders at once? If several payment reminders are due on the same day, you get a single email: the first one in full, the others as a list with document number, stage and customer address. Each stage comes only once per document, as in live mode. Test documents still open after go-live get no more reminders. Open tasks about test payments, test orders or test documents close by themselves at go-live; tasks about connections and settings stay open, because they apply in live mode too.

Checkout and subscriptions in test mode

Add your provider's test credentials under Settings → Connections → Shops and payment providers. Below the Mollie, Stripe, PayPal and Unzer cards, open "Test credentials (for checkout and subscriptions in test mode)". Checkout and subscriptions use them automatically in test mode. Your live connection stays next to them, so your real payments keep coming in as test documents.

Provider What you enter
Mollie Test API key (test_…)
Stripe Test secret key (sk_test_… or rk_test_…). Rechnungskit creates a separate test webhook in Stripe for it.
PayPal Client ID and secret of your PayPal sandbox app
Unzer Sandbox private key (s-priv-…)

A live key is rejected in this field. "Remove" deletes the test credentials again; your live connection is not affected.

You don't need a live connection to test. If you connected a provider with test credentials only, you can still select it for checkout or subscriptions in test mode. The card then shows the note "Connected with test credentials only". Before go-live, connect the live credentials. If they are missing, the go-live check warns you, and after go-live payment with this provider is unavailable until you have connected the live credentials. A live account never falls back to the test credentials.

Without test credentials, Rechnungskit blocks the payment in test mode as soon as a provider with live credentials is selected for the checkout or for subscriptions. Otherwise your customer would pay real money and only get a test document.

  • Checkout and shop: buyers see "Test mode: payment not possible. The seller is currently testing this checkout." Invoice purchase and prepayment stay available, since no money runs through a provider there.
  • Subscriptions: new subscriptions don't start. Due follow-up payments wait, with no failed attempt, no dunning step and no email.
  • Stripe bank transfer via the API: for orders with paymentGateway stripe_transfer, Rechnungskit creates no payment request in Stripe. The order waits, and a task tells you why. With Stripe test credentials, Rechnungskit creates the customer and the payment request in your Stripe test account.

You pay with your provider's test data (see What do you pay a test payment with?). Otherwise a test purchase works like a real one, with these differences:

  • Emails to buyers go only to your own address (the contact email from your settings, otherwise the owner's), with "[TEST]" in front of the subject and a note at the top. That applies to the payment request for prepayment and to all subscription notices, such as subscription active, failed payment, cancellation or withdrawal. The invoice email stays blocked for test documents.
  • Integrations and webhooks run as in live operation, such as access in Ghost or Memberspot and your own webhooks. The webhook payload then carries "test": true.
  • Ad tracking: conversion events to Meta are not sent for test purchases and test subscriptions. The purchase pixel of Meta, Google and TikTok on the thank-you page stays off too. That keeps test purchases out of your ad reports.
  • Payments through test credentials are always test payments. They never turn into a real document, not even after go-live.

At go-live, the test credentials are switched off and running test subscriptions end immediately, with no email to buyers and no charge. Access that test purchases and test subscriptions unlocked in Ghost or Memberspot is revoked at the same time, the same way as after a full refund. Checkout links, the shop and subscription plans stay and run through your live connection from then on.

Common worries

Worry Answer
Does my customer get the data request if I click "Request details" in test mode? No. The email goes to your own address, with "[TEST]" in the subject and a note that in live mode it would go to the customer. The row shows "Requested on … (test, sent to you)".
Does my customer get payment reminders or a payment request in test mode? No. Both go to your own address, with "[TEST]" in the subject and a note saying who would get them in live mode. The payment reminder comes as text without the invoice attached. The order and Open items show "(test, sent to you)".
Will my customers get a second invoice? No. Invoice emails are strictly blocked for test documents, even after go-live. Rechnungskit never invoices orders from before the Belegstart on its own.
Does Rechnungskit charge or refund money? Never for your shop sales. Your shop and your payment provider collect the money as usual, Rechnungskit only reads along. Rechnungskit's checkout and subscriptions don't charge with live credentials in test mode. With the test credentials you add under Settings → Connections → Shops and payment providers, only test money moves.
Does Rechnungskit change anything in my shop? Nothing about orders, payments or customer data. When you connect, it creates a webhook.
Does my tax advisor get test data? Only if you give them access. Then they see your test documents in the DATEV preview and your test exports in their advisor access. They can also create a test export themselves (TEST_ in the file name), which cannot be locked. Rechnungskit sends them nothing on its own.
Does testing cost anything? No. Test mode is free and has no time limit, and test documents are never billed. Billing starts at go-live, and on the current plan the base fee is prorated from the go-live day in the first month. Accounts on the previous €9 plan follow that plan's rule (Pricing and billing).
How long can I test? As long as you like. Only an account that has never been live and where nobody logs in for 90 days gets an email. If nobody logs in within the next 30 days, Rechnungskit deletes the account.
Can I test the bank and expenses? Yes, with test data. In test mode the bank only connects the demo banks of our technical provider YAXI, and you can add up to 10 test expenses. None of this is carried over at go-live. Real bank accounts and real expenses come after go-live.
Where is the data stored? At Hetzner in Falkenstein (Germany).
Does the AI see my customer data? Kit gets no customer names, email addresses or postal addresses, only sums and counts. Kit processes whatever you type into the chat yourself.
What if I don't continue? Disconnecting deletes the credentials, "Reset sandbox" the test PDFs. Orders, payments and customer data stay stored until you delete your test account. As an admin you do that yourself under Settings → Company → Plan and billing, section "Cancel or delete your account" (Cancelling and deleting your account).

How a test invoice comes about

An invoice comes about in Rechnungskit in two ways, in test mode just as in live operation:

  • Automatically from an order and a payment: an order comes from your shop or via API, the matching payment from your connected payment provider. As soon as both are there and match, Rechnungskit creates the document itself.
  • From an order you create yourself: under Orders → "Create order". With the payment method invoice, the invoice comes about in the same step; for goods that haven't shipped yet, only with "Mark as shipped". With prepayment it comes about as soon as you confirm "Payment received". Details are in Manual orders and invoices.

In test mode both ways produce a TEST document with its own TEST number. No email goes out to your customers.

Automatic route · three steps
Test invoice from an order and a payment
  1. Shop or APIOrdertest order in the shop or POST /v1/orders, shows up under "Orders"
  2. Payment providerPaymentmatched by order number or transaction ID (paymentRef)
  3. RechnungskitTest documentTEST number range, with PDF and EN 16931 validation
If the order for a payment is missing, Rechnungskit reports "Payment without an order" in the tasks under /payments.

This is how you get a test invoice the automatic way:

  1. Connect a data source and create an order. Either connect a shop (Shopify, WooCommerce, Shopware) and place a test order there. Or, as a SaaS or your own application, report an order via API (POST /v1/orders with your API key). The order then shows up under "Orders".
  2. Connect a payment provider and make a payment for the order (Stripe, Mollie, PayPal, Unzer, GoCardless, Klarna). The easiest way is to connect your live credentials, as described below under Test mode and payment providers. Your real payments then run through as test documents. For checkout and subscriptions you also add test credentials, and then you pay with the provider's test data. Matching works through the order number or the transaction ID (paymentRef).
  3. Rechnungskit creates the test document. If the payment matches the order, the test document comes about automatically (TEST number range), including the PDF and EN 16931 validation. If a payment arrives without a matching order, Rechnungskit reports "Payment without an order" in the tasks under /payments. In that case the order is still missing.

The quickest way to see a test invoice is an order you create yourself: payment method invoice and a service or product that isn't shipped, and the TEST document comes about right away. For goods, click "Mark as shipped" afterwards (see When do I see a test invoice?). You need an IBAN in your settings for this. If you just want to see the layout, use the live preview of the invoice template under Settings → Documents → Invoice template. It shows a sample invoice with your logo and your texts, without creating a document.

What do you pay a test payment with?

With your payment provider's test data, not with data from Rechnungskit. We do not process payments: the money runs through your own account with the provider, and its sandbox supplies the test cards and test IBANs. As long as a test key is stored there, no real money moves.

Provider Test data
Stripe test cards, test IBANs for SEPA direct debit and scenarios such as declined or 3-D Secure at docs.stripe.com/testing
Mollie test cards and a dedicated test payment screen where you choose the outcome yourself (paid, failed, expired) at docs.mollie.com/docs/testing. Mollie does not document its own test data for SEPA direct debit there. For a direct debit test, use Stripe or ask Mollie support.
PayPal, Unzer, GoCardless, Klarna through each provider's sandbox (Klarna calls it the Playground)

Which payment methods appear

Your provider account decides which payment methods appear in the checkout. For Mollie and Unzer, Rechnungskit reads the enabled methods and shows them under Settings → Connections → Shops and payment providers. "Refresh" reads them again. If you enable another payment method with the provider, it then shows up in the checkout too.

The Rechnungskit Checkout works with Mollie, Stripe, PayPal and Unzer. For subscriptions it is Mollie and Stripe, because recurring collection needs a mandate.

What applies in test mode

Same account · two states
Test mode and live operation compared
Test modeSandbox
NumberTEST-2026-0001
In the document"Testbeleg, keine Rechnung, kein Steuerausweis"
Costnot metered
Invoice emailstrictly blocked
DATEV, OSS, ZMno real export, OSS only as a preview
Archivecan be reset at any time
After go-liveLive
Numberyour format, e.g. RE-2026-0001
In the documentreal invoice with VAT statement
Costcounts toward your billing
Invoice emailautomatic, can be turned off
DATEV, OSS, ZMincluded
Numberingno gaps, can no longer be changed
Connections and settings stay the same at go-live. You don't set anything up again.
  • Separate number range: test documents are called TEST-2026-0001 and so on, and your real number range stays untouched.
  • Notice in the document: every test document carries a clear notice in the document itself ("Testbeleg, keine Rechnung, kein Steuerausweis": test document, not an invoice, no VAT statement).
  • Not metered: test documents cost nothing and do not count toward your billing.
  • No invoice emails: a test document is never emailed, not even to you. The block is tied to the test document itself, so it still applies after go-live. In test mode you get payment reminders for test documents yourself, as text without an attachment (Customer emails in test mode).
  • No effect on reports: test documents appear neither in real DATEV exports nor in the ZM (the EC sales list). In the OSS overview they only show as a preview while the project is in test mode, and no longer after go-live. For a trial import, you (or your tax advisor) can create a marked test export. It has TEST_ in the file name, cannot be locked and is deleted at go-live or when you reset the sandbox.
  • Archive: the archive is not write-protected in test mode, and you can reset test data at any time.
  • Bank and expenses with test data only: in test mode the bank only connects the demo banks of our technical provider YAXI. Under Expenses you can add up to 10 test expenses. Real bank accounts and real expenses come after go-live, and nothing from test mode is carried over.
  • No time limit: test mode doesn't end on its own. Only an account that has never been live and where nobody logs in for 90 days gets an email, and it is deleted 30 days later if nobody logs in by then.

After go-live it is the other way round: real invoices with a VAT statement come about in your number format. They count toward your billing, go to your customers by email by default (you can turn this off) and end up in DATEV, OSS and ZM.

Enabling and resetting test mode

Every new account starts in test mode. For a project without real documents, you switch it on under Settings → Company → Company details, in the project management ("Test mode (sandbox)").

"Reset sandbox" deletes the test PDFs from the archive, the test DATEV exports and the test payout documents. Orders, payments and customer data stay stored. The project, connections and settings stay the same, and real documents only come about with go-live.

API keys in test mode

The API integration has a single key type (prefix rk_key_). In test mode it creates only test documents. So you can run through your whole integration, including EN 16931 validation and PDF creation, before any real documents are created.

At go-live the same key stays valid and creates real documents from then on. You do not need to swap the key or touch your integration. Older keys with the rk_test_ prefix keep working unchanged. API details are in Connect your own application via API.

Test mode and payment providers

Important for all payment providers (Stripe, Mollie, PayPal, Unzer, GoCardless, Klarna): connect your live credentials, not the provider's sandbox or test credentials.

Credentials at the payment provider
Which credentials you connect in test mode
Live credentials plus Rechnungskit test modeYour real payments run through as TEST documents, no invoice is sent or exported
Recommended
Test credentials added on topsk_test_, test_, PayPal sandbox or s-priv-: in the separate "Test credentials" field below the live connection, only for checkout and subscriptions in test mode
test payments only
Test keys as the main connection at go-liveblock go-live, so that test payments never turn into real documents. The additional test credentials don't block; they are switched off.
Blocked

Why? A provider sandbox is an empty parallel world where your real payments never appear, so no data reaches Rechnungskit either.

So the risk-free way to test is Rechnungskit's test mode with real credentials. Rechnungskit does not trigger payments on its own, and in test mode the checkout and subscriptions don't charge with live credentials. What else happens and what doesn't is explained above under Connecting real data. How you test the checkout and subscriptions is under Checkout and subscriptions in test mode.

Test credentials (for example Stripe sk_test_, Mollie test_, Unzer s-priv-) are recognized by their prefix. As the main connection they only deliver test payments from the provider's sandbox; for live operation, replace them with your live credentials under Settings → Connections → Shops and payment providers. For checkout and subscriptions they belong in the separate "Test credentials" field below the live connection, see Checkout and subscriptions in test mode.

Testing alongside your old system

Because Rechnungskit changes nothing about orders, payments or customer data in test mode and sends no invoices, your current system keeps running as usual. No duplicate invoices come about. This lets you see with real numbers how matching, the fee split and the DATEV preview would look for you.

Running in parallel
Your old system invoices, Rechnungskit does a trial run
Your shop and payment provider
Real ordersstay unchanged
Real paymentsRechnungskit triggers none
Rechnungskit in test mode
  1. Reads alongorders, payments, refunds
  2. Matchesas it will in live operation
  3. Creates TEST documentsno VAT statement, no sending
Invoices to customers
Until go-liveonly from your current system
From the Belegstartonly from Rechnungskit

Only when everything fits do you go live with a Belegstart date (the cut-over date from which Rechnungskit issues your documents). From then on, only Rechnungskit creates the documents. Orders and payments from before the Belegstart count as historic, and Rechnungskit never invoices them on its own; your current system keeps handling those.

Go-live: what you decide

At go-live (under "Go live"), Rechnungskit checks a few points and asks for three things that get decided right then.

From go-live you pay the base fee, and on the current plan it is prorated from the go-live day in the first month (the previous €9 plan keeps its own rule, see Previous plan). That is why the 1st of a month is the recommended date: invoice numbers, the DATEV month and billing then all start on the same day. The go-live page preselects "On a set date". If your company is no more than 12 months old and your account is on the current plan, apply for the founder discount before go-live if you can. You then pay no base fee for 6 months from go-live.

Going live · in place
From test mode to live operation
  1. CheckPayment method and keysno go-live without a payment method for the fees or with test keys
  2. DecideNumber range and sendingformat, first invoice number, email sending on or off
  3. BelegstartNow or scheduledto the minute, from then on only Rechnungskit creates documents
  4. After thatTest data disappearshidden, test PDFs deleted, confirmation by email
Connections and settings stay as they are. You do not need to reconnect anything.

Company name and address

Your company name and address appear on every invoice (§ 14(4) UStG). The go-live checks them and stays blocked while the name is a placeholder (such as "Mein Unternehmen") or the address is incomplete. In Germany that means street with house number, a five-digit postcode and the city. You enter both under Settings → Company → Company details, which already refuses a placeholder when you save.

Register details

If your company name contains a registered legal form, the register court and register number belong on every invoice and every invoice email. For a GmbH, UG, AG or eG, all managing directors or board members are added (§ 35a GmbHG, § 80 AktG, § 25a GenG); for a GmbH & Co. KG, those of the general partner GmbH (§ 125a HGB). For a KG, OHG or e. K., the register court and number are enough (§ 125a HGB, § 37a HGB). Rechnungskit reads the legal form from your company name. The checklist checks everything the invoice email requires: company name, address, VAT ID or tax number and the register details. If something is missing, it shows a "Mandatory details for invoice emails" item naming the fields, with a link straight to the field in Settings. With automatic email sending on, that item blocks the go-live, because Rechnungskit would otherwise have to hold back every invoice email. With automatic sending off, it is a warning, and after the go-live you can only turn sending on once the details are complete. In Settings, the fields are marked as required for these legal forms.

Imprint, privacy policy and review

You can go live once your imprint (§ 5 DDG) and privacy policy (Art. 13 GDPR) both load: each link must point to a real web address and the page must open. A Shopify development store (a test shop without real payments) can't go live, so connect your real shop.

If something stands out at go-live, such as an imprint that doesn't name your company, Rechnungskit takes a quick look at the account. Until it's approved everything stays in test mode, and you'll get an email as soon as you can go live. Without approval within 14 days, the account ends.

Payment method for your fees

Before you go live, a payment method for your Rechnungskit fees must be on file so the first real invoice can be billed. There are two ways:

  • SEPA direct debit: you set it up right in the go-live window.
  • Shopify bill: if you came through the Shopify App Store. You approve the Rechnungskit subscription in the go-live window with "Approve subscription in Shopify". Shopify only charges from your document start, it is free until then. If you schedule the go-live later than approved, the window asks again. If you cancel a scheduled go-live, Rechnungskit cancels the still free subscription.

Without a payment method, go-live is blocked.

Invoice number range and next invoice number

You set your number format: JJJJ stands for the year, #### for the sequential number. RE-JJJJ-#### gives RE-2026-0001, for example. You also pick the number the first real invoice starts with.

This lets you continue your previous numbering seamlessly (from 1043, say) or start at 1. From the first real document on, the numbering has no gaps and the counter can't be reset. You can change the format later (a different prefix, say) under Settings → Documents → Document rules, section "Document start and numbers"; the counter carries on and issued invoices keep their numbers.

Send invoices automatically by email

This is on by default. As soon as you are live, Rechnungskit sends every finished invoice to your customers automatically, in your name and with your template. You can untick this in the go-live window and change it at any time under Settings → Documents → Invoice e-mails.

Test keys and Belegstart

An active connection with a test key also blocks go-live, so that test payments never turn into real documents. The additional test credentials for checkout and subscriptions don't count; go-live switches them off itself. After that you choose the Belegstart date, immediately or scheduled to the minute. From that moment on, only Rechnungskit creates the documents. When you schedule it, Rechnungskit suggests "Tonight at midnight" and the next first of the month and names the moment with its weekday. Note: 00:00 is the start of a day, so for documents from 1 November you choose 1 November, 00:00.

If test subscriptions are still running, the checklist shows "N test subscriptions will end".

Check the Mollie connection

With a live Mollie connection, the checklist shows two points that would otherwise only surface after go-live. Neither blocks the go-live:

  • No payment method active: in Mollie's test mode every method is available, in live mode only the ones you activated in your website profile. Without a single one, every checkout payment fails. See Activate payment methods for live payments.
  • Advanced access token missing: payments arrive, but the payout reconciliation and the Mollie fee per payment stay paused until you add the token on the Mollie card.

What happens to your test data at go-live

Go-live switches your account to live operation in place: the same environment, the same connections, the same settings. Your test data is handled like this:

  • Test documents, test orders and test payments are hidden immediately from all lists, reports and exports (DATEV, OSS, ZM). They never count toward your real numbers.
  • The archived test PDFs are deleted from storage.
  • Test expenses and transactions from the demo banks are not carried over. You connect real bank accounts and record real expenses after go-live.
  • The test number range (TEST-…) is retired. Your first real invoice uses the number range you set at go-live.
  • Test subscriptions end immediately. Buyers get no email, and nothing is charged.
  • Access from test purchases and test subscriptions in Ghost or Memberspot is revoked, the same way as after a full refund. The go-live check shows beforehand whether there is any. If you switched off automatic revocation in the integration, that access stays.
  • The test credentials for checkout and subscriptions are switched off. Checkout links, the shop and subscription plans run through your live connection from then on. If a provider connected with test credentials only was selected for checkout or subscriptions, payment there is unavailable until you connect its live credentials.
  • Your connections and settings stay as they are, and you do not need to reconnect anything.

Confirming Kit's classifications

If Kit gave products a type of service itself in test mode, the go-live page shows them counted by category, for example "Digital services · 214". From go-live they apply to real documents. "View classifications" takes you to Products, where you check them and change one right on the product if needed. You can only go live once you tick "I have checked Kit's classifications".

Scheduling go-live for later

If you schedule go-live for a future time, everything stays in test mode until then.

You can change the number range and email sending until then: adjust them and click "Save changes", and the scheduled time stays. As soon as you are live, owners and admins get an email confirmation with the Belegstart, the first invoice number and the sending setting.

At the scheduled time, Rechnungskit checks the test keys once more. If an active connection runs on a test key at that point, the switch does not happen. Your account stays in test mode, the schedule is cleared, and owners and admins get an email explaining why.

Limits

  • Test mode is meant for trying out features, not for load tests (fair use).
  • At go-live your account goes live in place: connections and settings remain, and test data is hidden and removed from the archive. You do not set anything up again.

Where to find it in the app

Still have a question? Ask Kit in the app or write to support@rechnungskit.de
No tax or legal advice

Rechnungskit is not a tax advisory or law firm. This article explains general principles and does not replace advice from a tax advisor (Steuerberater, § 5 StBerG) or a lawyer (§ 3 RDG). Rechnungskit is built for businesses based in Germany and prepares documents, tax rates and bookings automatically. How your specific case is treated remains your decision, ideally together with your tax advisor or a lawyer.

de en