Balance report
Opening and closing balances, itemised activity and separate payout details. Include every relevant currency and the agreed month-end cutoff.
What changed in Stripe, and what remains?
Payments & accounting
The bank statement tells you what arrived. Your books also need the customer sale, fees, refunds and the money still held by Stripe.
Follow the worked example01 / Reports & records
For standard Stripe Payments, your company sells to the customer. Start with the full account and period, then connect the payments to the sales documents and bank.
Opening and closing balances, itemised activity and separate payout details. Include every relevant currency and the agreed month-end cutoff.
What changed in Stripe, and what remains?
For automatic payouts, use the report that assigns transactions to each payout. Manual and instant payouts need the balance history and a separate bank match.
Which movements explain the transfer?
Invoices, credit notes, service periods, customer details and fee invoices where issued. A Fees-report CSV is a reconciliation report, not an invoice.
What was sold, when, and at what cost?
The posted receipt, reference, currency and any conversion or bank charge. A Stripe status or expected arrival date does not establish the bank posting.
What actually reached the bank?
Each CSV contains only the section where you start the export. Check that the full reporting period is available before treating the month as complete.
Stripe report dates, timezones and availability ↗Stripe Managed Payments is a merchant-of-record product. Connect and marketplace arrangements can involve different sellers, accounts and funds flows. We check the agreement and account structure before applying a reconciliation model.
Stripe Managed Payments ↗02 / Worked example · September · EUR
Two customer payments, a partial refund and one manual payout. Follow the records through the balance, bank and sales documents.
Every movement stays in its original settlement currency.
| Record / UTC date | Gross | Fee | Net |
|---|---|---|---|
| Payment A 2 Sep · txn_example_01 | 1,000 | 30 | 970 |
| Partial refund of A 18 Sep · txn_example_02 | −200 | 0 | −200 |
| Payment B 29 Sep · txn_example_03 | 500 | 15 | 485 |
| Net activity | 1,300 | 45 | 1,255 |
The provider record and bank statement are two sides of the same transfer.
po_example_01po_example_01The payout settles part of the Stripe balance. It does not create another customer invoice or another EUR 800 of revenue.
A bank reference may differ from Stripe’s payout ID. Use the actual statement reference, amount, currency, destination and dates to document the match.
The payout was initiated on 25 September. Payment B was collected on 29 September and becomes available on 2 October. It remains in the September closing Stripe balance. This example uses a manual payout; no automatic payout assignment is claimed.
The charge reference links the cash movement to the customer document. The contract establishes the service period.
ch_example_01 → in_example_01
EUR 200 is refunded against this payment. The sales worksheet includes the corresponding credit note, cn_example_01.
ch_example_02 → in_example_02
The September service is invoiced and paid. The net EUR 485 remains pending at Stripe at month end.
All services in this example belong to September. An annual subscription or an advance payment needs its own period schedule; the payment CSV does not decide when that income is earned.
Synthetic records for one standard Stripe Payments account, manual payouts and EUR settlement. Fees are embedded in the charge rows. Opening EUR 100 is fully available. The September cutoff is 30 September at 23:59:59 UTC. Fee amounts are chosen for this example, not a Stripe price quotation.
The example excludes VAT, FX, disputes, reserves and other adjustments. Both sales and the credit note relate to September services. This does not establish a VAT exemption or an accounting currency. The download contains report-column examples and separate ORNEVIO sales and bank worksheets; it is not a bookkeeping import template.
From CSV to records
Descriptions and amounts can repeat. Use stable identifiers, retain the source files and make the link to each supporting document visible.
balance_transaction_idIdentifies a Stripe balance movement. Use it to check duplicate imports and retain the original record.
charge_id / source_idLinks a payment, refund or dispute to the underlying Stripe object. Follow refunds back to the original charge.
invoice_idLinks to a Stripe Billing invoice where available. External invoices need their own matching reference.
payout_idIdentifies the transfer to match with the bank. Automatic allocation uses automatic_payout_id in the relevant activity report.
A payment can be collected in September and settle in October. Keep the report timezone, creation date, availability date and period boundary explicit.
The documented financial CSV columns use major currency units. Stripe API balance-transaction amounts use minor units. Read each source’s schema before converting.
Some accounts use standalone fee transactions. Summing only charge-row fees can miss costs; booking both an embedded fee and a duplicate fee entry can count them twice.
Reconcile each account and settlement currency separately. Keep presentment, settlement, bank and accounting currency identifiable where they differ.
03 / Czech accounting
Customer records establish the sale. Stripe records establish the provider movements. The bank confirms the receipt. The company’s accounting and tax policies connect them.
Keep the sales document, original payment, fee record and any credit or correction document linked. A refund records a cash movement; the reason for the refund and supporting documents determine the sales adjustment.
Czech accounting-document requirements can be supported by linked records. A CSV alone does not establish the customer, service period and complete tax treatment.
Financial Administration: accounting records ↗One illustrative company chart: 311 customer receivables, 315 Stripe clearing, 602 service revenue, 568 processing costs, 261 money in transit and 221 bank. Amounts below are source EUR.
| Event | Debit | Credit | EUR |
|---|---|---|---|
| Sales invoices | 311 | 602 | 1,500 |
| Payments collected | 315 | 311 | 1,500 |
| Credit note | 602 | 311 | 200 |
| Customer refund | 311 | 315 | 200 |
| Processing fees | 568 | 315 | 45 |
| Payout initiated · 25 Sep | 261 | 315 | 800 |
| Bank receipt · 28 Sep | 221 | 261 | 800 |
The closing Stripe clearing balance is EUR 555, including opening EUR 100. Account numbers illustrate one chart; actual ledger amounts follow the company’s accounting currency, VAT and exchange-rate policy.
Accounting Act: §§ 3, 11 and 14 ↗An EUR Stripe balance does not automatically mean EUR statutory books. Czech rules permit CZK, or EUR, USD or GBP when the chosen foreign currency is the company’s functional currency.
We establish the accounting currency and rate policy, retain source and settlement amounts, and account for conversion and exchange differences. Management reporting and Czech tax-return amounts need separate consideration.
Financial Administration: accounting currency ↗For sales, establish the product, customer status and location, relevant registrations and place-of-supply rules. EU business, consumer and non-EU sales can have different treatment. Electronic services may require additional location evidence and an applicable local or OSS route.
For Stripe costs, use the actual invoicing entity, product and fee document. Payment services and separately billed software can have different VAT treatment. Neither a payout deduction nor an invoice with no VAT shown determines an identified-person or reverse-charge obligation by itself.
We assess these from your company’s records. An accounting revenue schedule is not a VAT schedule.
04 / Month-end checks
A payout match is one check. The monthly close also has to explain the Stripe balance, sales records, deductions and anything crossing the period boundary.
Start from the previous reconciled close, per account and currency. Do not insert the opening balance as a new sale.
Check payments, refunds, separate fees, disputes, reversals and other adjustments. Retain unique references and resolve missing sales documents.
Explain available and pending funds and any other relevant balance components. Keep movements in transit separate from bank cash.
Match references, posted dates, amounts and currencies. Investigate failed payouts, bank charges and conversions.
Record the amount, evidence missing, person responsible and next action. A balancing entry is not an explanation.
Missing invoice referenceKeep the payment and obtain the sales document.
Dispute debitTrack the case and outcome; do not automatically cancel revenue.
Fee differenceCheck standalone fees, taxes, product scope and timing.
Unmatched payoutCheck status, bank receipt, currency and transfer timing.
Stripe with ORNEVIO
We agree the Stripe accounts, currencies, documents and reporting scope in your proposal. You receive the closing provider balance, bank matches and unresolved items alongside your accounts.
Changing accountants? With your authorisation, we request the prior Stripe records and opening reconciliation directly. Routine handover is included in every ongoing accounting package.
Your company
Tell us what you need help with. We will reply by email.
hello@ornevio.comSources checked 20 October 2026. This guide covers standard Stripe Payments for a company selling directly.
Contact ORNEVIO