Uploads
On the Uploads page (/uploads) you upload the exports from your sales and payment sources. KanzleiSynchron auto-detects the source from the column headers and parses the file immediately.
Supported sources
Section titled “Supported sources”Live (production-ready): Stripe, Shopify, Amazon, PayPal, Klarna, e-Rechnung (XRechnung/ZUGFeRD), and DATEV-EXTF.
Beta / in development: Silverflow and a direct bank connection. These sources are not yet cleared for the production month-end close. A full overview is on Supported sources.
Upload a file
Section titled “Upload a file”- Open Uploads in the navigation.
- Click Upload file or drag the CSV onto the drop zone.
- KanzleiSynchron reads the column headers and shows the detected source (e.g. “Stripe”). If the detection is wrong, pick the source manually.
- Click Upload. The file is parsed immediately.
- After parsing you see the number of imported rows and any skipped rows.
What to upload
Section titled “What to upload”For a complete reconciliation you need, per period, at least:
- one sales source (e.g. Shopify orders), and
- the matching payment/payout source (e.g. Stripe payouts or PayPal transactions).
Only then can the matcher reconcile orders against actual money received.
Format requirements
Section titled “Format requirements”- File type: CSV (UTF-8 recommended).
- Column headers: leave them exactly as exported — KanzleiSynchron uses them to detect the source.
- Amounts: in each provider’s own format; KanzleiSynchron converts to the DIN 5008 format (
1.234,56 €). - Date range: upload the export for exactly the period you are reconciling.
When something goes wrong
Section titled “When something goes wrong”| What you see | Cause | What to do |
|---|---|---|
| Source not detected | Column headers were changed, or the source is unsupported | Re-export the original without edits; pick the source manually if needed |
| Skipped rows | Individual rows are incomplete or malformed | Check the row numbers in the report, fix them in the source export, re-upload |
| 0 rows imported | Wrong file or empty date range | Verify the correct file/period |
| Wrong format | File is not a CSV (e.g. XLSX) | Export as CSV from the provider’s tool |
You can re-upload a faulty file at any time — the last successful import per source and period is the one that counts.
Download the per-row error report
Section titled “Download the per-row error report”For any upload you can download a per-row error report as CSV (endpoint /uploads/<file>/errors?format=csv). It lists exactly which row was skipped and why — ideal for targeted fixes in the source export.
Needs counterpart (NEEDS_COUNTERPART)
Section titled “Needs counterpart (NEEDS_COUNTERPART)”If you upload a source whose matching counterpart is still missing (e.g. Shopify orders without the corresponding payment/bank source), the Exceptions page shows an amber notice card with status NEEDS_COUNTERPART. Upload the missing counterpart source — then the matcher can pair them. If the notice does not apply (e.g. a PayPal-only client), you can dismiss it.
PDF documents
Section titled “PDF documents”PDF files are stored but not parsed (source_type='PDF', parse_status='SKIPPED'). They serve as supporting attachments and do not enter the reconciliation.
Next step
Section titled “Next step”After the upload the reconciliation runs automatically. Continue to resolving exceptions.