Topics: Using features
- Help & docs
- Using features
- Payments, matching and payout reconciliation
Payments, matching and payout reconciliation
Rechnungskit matches every incoming payment to its order and breaks payouts down into their parts. How matching works, what the payment statuses mean, the Belegstart cut-over, rounding differences and the AWV reporting notice.
Updated
On this page 13
- How matching works
- The matching source must fit your shop
- Direct PayPal payments and the order number
- Unzer payments and the order number
- What the statuses mean
- A payment's history
- When something does not fit
- Task reminder by email
- Payout reconciliation
- Belegstart and old data
- Limits, stated plainly
- Notice on the AWV reporting obligation (Bundesbank)
- Where to find it in the app
Rechnungskit matches every incoming payment to the right order automatically. Anything that is not clear never disappears silently; it lands as a task in the clarification list.
This page explains how matching works, what a payment's status means, how to resolve open cases and how Rechnungskit breaks your payment providers' payouts down into their parts.
- Payment referencepassed by the shop or your application
- Order number in the metadatafor example custom_id for PayPal
- Order number in the reference textor in the payment's description
How matching works
Matching tries several routes, in this order:
- Payment reference: the reference the shop or your application passed with the payment.
- Order number from the payment's metadata (for example custom_id for PayPal).
- Order number in the payment reference text or the payment's description.
Under Settings → Connections → Shops and payment providers you see a preview per payment provider of whether matching works with your real data.
The matching source must fit your shop
Per payment provider, under Settings → Connections → Shops and payment providers, you set where the order data comes from, for example Shopify, WooCommerce, Shopware or Stripe subscriptions. Rechnungskit looks for the matching order in this source, and only there.
If it says API there although your orders come from a shop, every payment searches an empty set. Nothing is found and no document is created. Because matching runs through cleanly from a technical point of view, not even an error message appears. The failure only shows in payments piling up unmatched.
That is why Rechnungskit helps in two places:
- Warning: the connection shows a notice when the source is set to API while a shop is connected.
- Preselection: when you add a new provider and exactly one shop is connected, that shop is preselected as the source.
If many payments stay at "Needs review" for no apparent reason, look here first. After switching, "Re-match all" catches up on the stuck payments and creates the missing documents.
Direct PayPal payments and the order number
PayPal payments only carry the order number if the shop checkout writes it into the PayPal field invoice_id (or custom_id). WooCommerce (Invoice Prefix) and Shopware do this by default. Simple PayPal buttons often don't, and then matching works through amount and email.
PayPal with Shopify
With Shopify, the field is filled in different ways. Some payments carry the real order number, while for the rest it holds an internal key of the checkout session, for which there is no order number.
For these payments, Rechnungskit asks Shopify directly for the order and reads the PayPal transaction number stored there. It links order and payment unambiguously. So matching works through the transaction number, not estimated from amount and time. You don't need to set anything up; the existing Shopify connection is enough.
PayPal through another provider
| PayPal runs through | Authoritative source | What happens with the direct PayPal connection |
|---|---|---|
| Mollie or Stripe | the Mollie or Stripe connection | It would record the same payments twice. Rechnungskit detects the duplicates and automatically classifies them as not a sale. Recommendation: disconnect the direct connection |
| Unzer | the Unzer connection | Automatic duplicate detection is technically not possible, because Unzer does not return the PayPal transaction number. Rechnungskit warns and also recommends disconnecting the direct connection |
Unzer payments and the order number
Unzer payments only carry the order number if the shop's Unzer module passes it as the order ID. The Unzer modules for Shopware and WooCommerce do this by default; for other shops, check the module configuration. In addition, the shop must be selected as the matching source of the Unzer connection.
The 4-hour sync covers Unzer too. Known payments from the last 48 hours are fetched again, and recent orders without an Unzer payment are queried directly at Unzer.
What the statuses mean
Every payment under /payments carries exactly one status.
| Status | Meaning | What you do |
|---|---|---|
| Matched | The payment is assigned to an order. | Nothing |
| Needs review | Something is still missing before the invoice can be created. Below the cards you see which reason occurs how often. | Depends on the reason, see below |
| Awaiting sync | The payment is there, the related order is not yet. Payment and order come from different sources and often arrive at different times. The row then shows "Awaiting order", and no task appears under Overview → Tasks. An instalment on a Stripe invoice that is still open at Stripe also waits here. | Nothing. When the order arrives, Rechnungskit matches it. If it is still missing after 24 hours, the payment moves to "Needs review". |
| Refund | A repayment to the customer. If needed, the related correction invoice has already been created. | Nothing |
| Not a sale | Deliberately filed as not revenue-relevant, such as transfers, card verifications of €0.00 or transitory items. | Nothing |
| Historic | The payment dates from before your Belegstart (the date from which Rechnungskit issues your invoices). | Nothing, see below |
| VAT ID check running / decision needed | The qualified check of the customer's VAT ID with the Federal Central Tax Office (BZSt) is still pending or needs your decision before the invoice is created. | Decide when it says "decision needed" |
Under "Needs review", Rechnungskit splits the payments by reason. A click on a reason shows only those payments:
| Reason | What you do |
|---|---|
| decide on VAT | Business customer from another EU country with a VAT ID. The order is found, the invoice waits for your decision. "Decide" leads to the page "With or without VAT?". While the BZSt is still checking, the payment is listed under "Waiting". Until you decide, it does not count as "Matched". |
| without an order | No reference found. "Assign" it to an order or file it as "Not a sale". |
| recipient data missing | Name or billing address missing. "Request details", or add it in the shop or at Stripe. |
| invoice blocked | The order is found, but the invoice cannot be created yet, for example because a tax classification is still open. The row says why. |
| other | No open task. "Re-match" checks the payment again. |
Status in colour
Every status in Orders, Payments and Invoices has a coloured dot in front of the word. Each colour means the same everywhere: lime with a ring means it's your turn, red means an error to fix, amber means take a look (overdue, deadline, mail not delivered), blue waits for the money, grey runs on its own, green is done. Rows that need something from you have a coloured edge on the left. Hover over a status to see what its colour means.
When you click the invoice in an order or payment, it opens in the same side panel and the list stays where it is. "← Order …" or "← Payment …" at the top of the panel (or Esc) takes you back, and "Open in Invoices" shows the same invoice next to the invoice list. A link to an invoice, for example from an email, always opens the invoice list with that invoice in the side panel.
Instalments on Stripe invoices
If a customer pays a Stripe invoice in instalments by bank transfer, Stripe applies each transfer from the customer's balance to the invoice. While the invoice is still open at Stripe, there is no order and no document yet. These instalments wait under "Waiting"; the row names the Stripe invoice and the open amount. Once Stripe reports the invoice as paid, the document is created and all instalments are assigned to it. You don't need to do anything.
If the Stripe invoice dates from before your Belegstart, the old system issued it. Its instalments then show as "Historic", and Rechnungskit issues no second document. For Stripe invoices, the date that counts is when Stripe finalized the invoice.
If a payment names no invoice (neither a link nor an invoice number), it is not automatically an instalment: it can also be a prepayment, a balance top-up or a new sale. It therefore stays under "without an order", and the row lists the customer's open Stripe invoices. Apply the payment to the right invoice in Stripe, assign it here, or choose "Ignore (invoiced externally)" if it belongs to an invoice from the old system.
Matched: invoice or "After shipping"
- If the Invoice column shows a number, the invoice has been created.
- If it says "After shipping", the invoice is only created on shipping (date of supply = shipping date). Whether it has shipped you see on the order. The order number in the row leads straight there.
In both cases there is nothing to do.
Historic
The payment dates from BEFORE your Belegstart. Your previous system already invoiced it. Rechnungskit only loads it so the payouts reconcile: no document, no task, nothing to do.
You can also file an unresolved payment this way yourself, through the payment's menu → Ignore or the link in the assign dialog. That is correct if its order dates from before the system start and was invoiced in the previous system. The task closes, the decision is logged and can be reversed with "Reopen".
A payment's history
Click a payment in the list to open its history. On a computer it slides in from the right, on a phone it opens from the bottom. With the keyboard, use "History" in the row's "…" menu or the clock button at the end of the row. Escape closes it.
The top shows the provider, the amount, the full payment reference and the status. Below that come the steps a payment goes through:
- Received: when the provider took the payment. For Stripe it also says whether the webhook reported it or the sync found it. If the payment reached Rechnungskit hours later, that shows too.
- Matched to order: the order number, and whether it happened automatically or by hand (with the person's name). Since 21 Oct 2026 Rechnungskit stores the exact moment of the match. For older payments the history uses the earliest recorded moment (the resolved "order missing" task or the invoice), or shows no time.
- On hold or Waiting: an open task with its reason, how long it has been open and the button that resolves it. "Resolve" opens the same dialog as in the row.
- Invoice: the number, linked to the document. If there is none yet, the step says when it will be created.
- Refunded and cancellation: each refund with its amount, and the cancellation document if there is one.
- Filed as "not a sale" or historic: when, by whom or automatically, and the note "No invoice".
- Paid out: the payout's date and reference, linked to payout reconciliation. Before that: "with the next payout".
- In the DATEV export: export number and month, locked or still a draft. Otherwise "not exported yet".
A green check means done. A filled orange exclamation mark is an open decision, an orange outline one that has already been taken. Grey circles are steps still to come. The history only shows what is stored, so a step without a known moment has no time.
"All events" adds every task (created, resolved, by whom), the activity log entries for this payment and any handover to the tax advisor, in time order.
When something does not fit
Every open case appears as a task under /payments. Chargebacks and payout differences land there too.
Payment without assignment
Payments without an assignable order appear as the task "Zahlung ohne Zuordnung" (payment without assignment). There you assign it manually or clear up the case.
The most common reason: the payment was faster than the shop sync, and the order simply is not there yet. For WooCommerce:
- Type the order number in the assign dialog.
- Click "Load order … from the shop now", and the order arrives right away.
- The dialog says what it found. An open order with the same amount: it is assigned right away and the invoice is created. A different amount: the order is selected, and you confirm with "Create invoice". Canceled in the shop: the dialog shows how to refund the payment at the provider or reactivate the order in the shop (Match a sale without an order reference, step 6). Already invoiced: the new payment is probably a double payment, so you refund it. Not in the shop: check the number or file the payment without an invoice.
The search in the dialog shows canceled and already invoiced orders in grey with their status. You cannot select them, so no second invoice is created.
Webhook connection silent
If your shop reports orders with a payment provider from which Rechnungskit has not received a single payment since connecting (neither webhook nor fetch), the task "Webhook-Verbindung still" (webhook connection silent) appears. It contains the specific check. For PayPal, for example: enable "Transaction Search" on the REST app, and the app must belong to the account where the shop payments land.
The invoice cannot be created
If something is missing for the invoice, such as a VAT rate, complete recipient details or your company details, the payment is held. The task links directly to the setting that is missing.
Requesting buyer details
For incomplete recipient details, you get the address straight from the buyer.
- "Request details" on the task sends them an email with a link, with you as the sender. Through the link they add their billing address without logging in.
- If no email address is known, copy the link with "Copy link" and send it yourself, by chat for example.
- As soon as the buyer submits the details, the document is created automatically and the task closes.
The link stays valid. Clicking "Request details" again sends the same link once more. The row shows "Requested on" or "Buyer details received on".
- Task createdPayment is heldno document with an incomplete address
- Request detailsEmail with a link to the buyerin your name, or automatically by document rule
- Buyer repliesAddress added, no login"Buyer details received on"
- Right afterDocument created automaticallythe task closes
Send automatically: under Settings → Documents → Document rules, you can have the buyer link sent automatically. The request then goes out in your name as soon as the task is created and the buyer's email address is known. This happens once per payment, never in test mode. The task stays visible until the buyer has replied.
No reply: if the buyer does not reply, nothing happens on its own. The payment stays held, no document is created, the task stays open and appears in the task reminder email. Rechnungskit does not remind the buyer automatically. You can resend the link at any time or add the address yourself in the shop or the Stripe customer profile. The document is then created at the next matching run.
Safety net for lost webhooks
In case a webhook got lost, a safety net syncs with the source regularly:
| Source | Sync |
|---|---|
| Shopify | every 4 hours |
| WooCommerce | every 4 hours, 24-hour window, fully paginated |
| Shopify Payments | every 4 hours |
| Shopware | fetched every 15 minutes anyway |
For goods, the invoice is only created on shipping (date of supply). For shop orders it therefore depends on the status change "Completed" also arriving.
Sync now: The button under Payments fetches payments and payouts from your payment providers right away, so you don't have to wait for the next scheduled run. The sync runs in the background, even if you leave the page or Rechnungskit is installing an update (it then starts again on its own). New payments show up in the list by themselves, and when the sync is done Rechnungskit tells you how many payments it checked and how many are new.
Task reminder by email
You don't have to keep an eye on open tasks yourself. Rechnungskit sends the account owners an overview by email, grouped by project, with the count and the age of the oldest task. For each kind of task it lists up to three cases, each with its reason and a link straight to the case; "and … more" links to the list for the rest. The email only comes if something is actually open.
The Overview does not list single cases. Under "Your turn" it shows the three most urgent tasks; all of them are under Overview → Tasks, one row per cause, such as "payments without an order" or "Tax rates to set", with the number of cases. The rows are grouped by what happens if you wait: "Deadline running" (a deadline ends within the next seven days), "Holds documents back" and "When you have time". Everything that hangs on a tax rate counts only in "Tax rates to set": payments waiting for a rate are listed under Payments at the very bottom under "Waiting for a tax rate", but they don't count towards "Needs review". Click a row and its panel opens next to it with one button to the next step, and "Kit explains it" asks Kit about that task.
The details of each case appear on every task under Payments, under Invoices → Needs you and on the order: why it appeared (with order number, amount, country or rate), "How to solve it" with the next step, a button straight to the case, and under "Options and what follows" every option with what happens next, such as whether an invoice is created and what goes to DATEV. Kit explains tasks with the same sentences.
| Setting | When the email comes |
|---|---|
| Weekly (default) | Fridays at 8 a.m. |
| Daily | every morning at 8 a.m. |
| Off | never |
You change this under Settings → More → Notifications, "Task reminder". The choice applies to the whole account and saves immediately. Every reminder email names its frequency and links to this setting.
Independently of this, Rechnungskit emails you immediately when an invoice is held because a decision is needed, after a failed VAT ID check for example. This immediate email cannot be switched off.
Payout reconciliation
Under /payouts, Rechnungskit breaks your providers' payouts down into their parts, so the bookkeeping adds up. Every item (payment, refund, fee) is shown separately. Fees are never netted against revenue.
Above the list are three tabs: "All", "To reconcile" (payouts with an open task, such as a difference or items without a payment) and "Unresolved" (payouts with at least one unresolved item). The number on "To reconcile" is the same as on the tab Payments → Payouts and on the task under Overview → Tasks. After go-live the list hides payouts from before the Belegstart and those made only of test payments. A note above the list gives their number, and "Show" brings them back.

How payouts come in
| Provider | How Rechnungskit gets the payout |
|---|---|
| Stripe | automatically per payout via webhook |
| Mollie | daily through the Settlements API (organization access token required) |
| PayPal | daily through the transaction history, withdrawals to the bank account as a transfer, itemized into the movements since the previous withdrawal |
| Shopify Payments | automatically through the shop connection |
| Unzer | no payout interface, fees come from the monthly ETN CSV upload |
| Klarna | daily through the Settlements API (no webhooks, Rechnungskit fetches actively), fee per transaction included |
When the fee per payment appears
The fee per payment appears as soon as the provider delivers it. Until then the payment list shows "folgt" (to follow).
| When | Provider |
|---|---|
| right away with the payment | PayPal |
| with the sync around the payout | Mollie, Stripe, GoCardless, Klarna, Shopify Payments |
| only with the monthly ETN import | Unzer |
Missing payments and differences
If the payment for an item is missing, typically for sales before the Belegstart or after a missed webhook, the reconciliation fetches it automatically from the provider for Stripe and Mollie. This happens daily and on "Re-match all". Payments before the Belegstart appear as "Historic" and create no document.
If a difference still remains, you can accept it as resolved with a reason. The decision is recorded immutably in the audit log and is lifted as soon as the payout actually reconciles. How the DATEV export books a difference is explained under Reconciliation difference.
Unresolved items in a payout
Not only the total is checked, but every single item. Unresolved means no payment can be found for this item. The task "items unresolved" therefore appears even when the payout reconciles to the cent.
Rechnungskit resolves two cases itself:
- Refunds with Shopify Payments: Shopify books them under the transaction number of the refund, while the correction invoice hangs on the payment of the original order. Because Shopify includes the order on every booking, Rechnungskit resolves the item through it, provided that order has exactly one payment from the provider. Chargebacks are deliberately left out, because they are a separate process with their own clarification.
- Time before the Belegstart: there are often weeks between purchase and refund. A current payout therefore sometimes contains refunds for orders that were still invoiced in the previous system, and Rechnungskit never saw their payment. Such items show in the payout marked "before Belegstart", do not count as unmatched and do not keep a task open. If the payment turns up later after all, the next reconciliation matches it.
If a task remains, something really is missing, usually the original payment for a refunded order. Then "Re-match all" under /payments helps. If the item is still open afterwards, click "Assign" on it in the payout.
Assigning an item by hand
The "Assign line" dialog starts with what the provider sends along with the item: reference, date and amount, for refunds the original sale (PayPal names it on every refund), and the order number if there is one. Below that are the payments that could fit. Each shows its order number and customer, for refunds the date and amount of the original sale, and the invoice or cancellation number. Payments that already appear in a payout are no longer offered.

- "belongs to this payment according to PayPal" (or Stripe, Mollie): the provider names this payment itself. It is listed first and preselected when there is exactly one such payment.
- "exact": only this payment has exactly the item's amount, and no other open item in the payout has that amount either.
- "same amount": several payments or several open items have exactly this amount, for example five refunds of €15.99 on the same day. Rechnungskit then suggests none of them. The order number, customer and sale date tell you which one fits.
If no payment fits, choose "No matching payment in Rechnungskit" and then one of two options:
- Sale from before the Belegstart: the payment still went through your old system. The item then shows "before Belegstart" in the payout.
- Resolved another way: write a short note on how (at least five characters). The item then shows "Resolved otherwise".
Either way the item is closed. Rechnungskit checks the payout again, and the task closes once nothing is left open. Every decision, including a manual assignment, is recorded in the audit log with its note. "Reopen" or "Remove match" takes it back.
Rounding differences in fees and payouts
Payment providers calculate fees per transaction and internally with fractions of a cent. Mollie and Unzer deliver up to four decimal places. Only whole cents reach the bank account, though. That is why the providers' own settlement reports contain correction items such as rounding differences.
How Rechnungskit handles this:
- Real amounts: Rechnungskit never recalculates fees as a percentage; it takes the provider's real cent amounts per transaction. Internally only whole cents are used, no floating-point numbers.
- Round once: for provider items with decimal places (Mollie costs, for example), the total is formed exactly and rounded only once. The remainder is distributed across the items by the largest remainder method, so the sum of the items always equals the real total. Rechnungskit therefore creates no rounding differences of its own.
- Provider corrections: correction items (rounding, fee corrections, tax on fees, withholdings) are recorded as separate items of the payout.
- Never rounded away: if a payout still does not reconcile to the cent, the difference is shown as a task to clear up. A difference points to a missing, duplicate or wrongly valued transaction.
A rounding cent between shop and invoice
Shops round VAT per line; an e-invoice under EN 16931 rounds it per tax rate. For some gross prices that leaves a one-cent gap. Example: 2 × €19.90 gross. Shopify shows €3.17 + €3.18 VAT, but the sum of the net amounts times 19 % gives €6.36, so the invoice would come to €39.81.
Rechnungskit aligns such rounding cents with the price that was paid: the invoice reads €39.80 with €6.35 VAT. That is the legally correct amount, because the consideration is the gross price minus VAT (§ 10(1) UStG), so 39.80 × 19/119 = €6.35. VAT shown one cent too high would be owed under § 14c(1) UStG. With many items at the same rate, per-line rounding can add up to several cents. Rechnungskit aligns as much as the line rounding can explain: at most half a cent per line. The VAT then equals the sum of the shop's line taxes. Both ways of rounding are allowed for invoices under § 14 UStG, and the EN 16931 rule BR-CO-17 accepts the deviation.
Only pure rounding is aligned. Larger gaps between order and invoice have a reason (a voucher receipt, a refund, shipping added later) and stay as calculated.
Sources: § 10 UStG, § 14c UStG. Not tax advice; your tax advisor decides in the individual case.
Belegstart and old data
Rechnungskit only creates documents for sales from the Belegstart onward. You set it once when going live (Go live page): immediately or scheduled for a cut-over date, such as the first of the month for a system switch. In test mode, the day of setup applies. Under Settings → Documents → Document rules you see the date, but it cannot be changed there.
- Up to 30 days beforePayments are loadedas "Historic", so payouts reconcile
- September 30Order in the shopinvoiced by your previous system, even if paid or shipped in October
- October 1Belegstartset once when going live
- From then onDocuments from Rechnungskitfor every new order
Older payments
Older payments from the last 30 days are still loaded. They appear as "Historic" in the payment list and make sure that payouts reconcile that partly fall before the switch.
They are not invoiced, because the previous system already issued invoices for them. A second, non-identical invoice for the same supply can mean you owe the tax shown on it in addition (§ 14c Abs. 1 UStG, Abschn. 14c.1 Abs. 4 Satz 5 UStAE).
The order date decides
- An order from September 30 that is only paid or shipped in October is still invoiced by your previous system. Rechnungskit files its payment as "Historic".
- Shops connected through the API send the order date in the field
orderedAt. If it is missing, the time the order reached Rechnungskit counts. - If you assign such a payment to an order yourself, a document is still created.
Rechnungskit does not invoice retroactively on its own: set the cut-over date, and from then on everything goes through Rechnungskit. If no invoice exists yet for older sales, you move the Belegstart back when you import older Shopify orders. For other channels, contact support.
Limits, stated plainly
- Bank reconciliation is elsewhere: the basis here is the data from the payment providers and the shop. Reconciling against the bank account (upload a statement or connect the account) is under Payments → Bank.
- €0.00: payments of €0.00 are automatically classified as not a sale and create no document.
- Foreign currency: invoices are created for EUR, CHF, USD, GBP, SEK, DKK, NOK, PLN and CZK. The EUR tax amount is determined with the project's rate method (default for new projects: the BMF monthly rate of the month of supply, with the ECB daily rate as a provisional rate until it is published) and frozen on the document together with the rate date. Other currencies (JPY, for example) and payments whose currency does not match the order create no document but a task to clear up.
Notice on the AWV reporting obligation (Bundesbank)
If a single cross-border payment over €50,000 is matched to an order (German seller, foreign payer), Rechnungskit shows a notice on the Payments page. As a resident, you may have to report it to the Deutsche Bundesbank: a Z4 report under §§ 67 ff. AWV (the German Foreign Trade and Payments Ordinance), due by the 7th working day of the following month (§ 71 Abs. 6 AWV).
To put this in context:
- Statistics only: it is purely a statistical report on foreign trade, not a tax obligation. It changes nothing about your invoice, the VAT or the DATEV export.
- Per payment: the €50,000 limit applies since the reporting month January 2025 (previously €12,500, according to the Bundesbank) and is checked per individual payment, not as a monthly total (§ 67 Abs. 2 Nr. 1 AWV).
- Goods exports: payments for the export or shipment of goods are exempt (§ 67 Abs. 2 Nr. 2 AWV). The notice still appears, because Rechnungskit cannot reliably classify the purpose of the payment.
- Not the ZM: don't confuse it with the €50,000 limit of the EC sales list (ZM). That is a different return to the Federal Central Tax Office through ELSTER, and it only shares the number with the AWV notice.
- You file the report: Rechnungskit only points this out and does not file the Z4 report. The report itself goes through the Bundesbank's reporting portal. The task in the clarification area can be ticked off once done.
Where to find it in the app
Recent changes
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.