The Friday rental total and the money received by the bank need not match. A rental can finish before its payment is captured, an adjustment can belong to an earlier rental, and a bank payout can contain activity from another reporting period. A Romanian operator needs a weekly close that explains those differences rather than hiding them.
The practical deliverable is a small reconciliation pack: the period definition, rental export, payment activity, payout evidence and an owned list of remaining exceptions. It builds on daily checks without pretending that every accounting decision is automated.
Begin with the approved RON deployment
Stripe’s current Romania Terminal page identifies the country integration as Private preview and requires RON with the appropriate Romanian account and reader Location. It lists WisePad 3. Confirm account preview access, local reader purchase and the proposed venue use with Stripe before procurement or a public launch. The operator purchases and registers the reader through its own eligible local account.
CoreCharge already integrates the matched reader through the native Android rental application and Terminal SDK inside the cabinet. The agreed USB data and power arrangement avoids a separate merchant phone. Stripe processes rental payments into the operator’s own account; CoreCharge connects orders, dispensing, returns, pricing and operating records.
The reporting pack does not establish site approval. Confirm whether the actual staffed or fully unattended arrangement is suitable for the selected reader before opening.
Define the week before exporting it
Choose the reporting timezone, start time and cut-off, then use the same definition for each weekly pack. Record which operational view you are reporting: rentals completed during the week, for example, rather than every rental started. Keep open rentals in a separate carry-forward list.
Identify the actual fields available in the CoreCharge Excel export and the authorised Stripe report. Match by confirmed references, not by amount alone. Several rentals can have identical prices, while a single rental can generate an authorisation, final charge and later adjustment.
| Weekly schedule | Basis | Close question |
|---|---|---|
| Completed rentals | Return time and final configured rent | Does each completed order have an explainable payment outcome? |
| Captured activity | Actual Stripe payment records | Which captures relate to this week or earlier orders? |
| Refunds and adjustments | Verified status and original reference | Are approved corrections complete or still pending? |
| Fees and net activity | Actual account records | Are charges and adjustments explained without assumed fee percentages? |
| Bank payouts | Payout record and bank receipt | Which activity funded each payout, and what remains in balance? |
Explain timing differences in a bridge
Start with the week’s operational rental amount. List the items that belong on a different payment basis: an earlier rental captured this week, a completed rental with an unresolved final payment, or a refund against a previous period. Keep these items traceable instead of adding an anonymous adjustment to force equality.
Stripe’s Balance report separates activity from payouts. Its payout reconciliation guidance explains how eligible automatic payouts can be connected to underlying transactions. Confirm which report fits the operator’s actual payout arrangement.
A bank receipt is evidence of that payout arriving, not proof that every rental in the same calendar week was collected. Likewise, a temporary authorisation is not rental revenue simply because the amount is visible in a banking app.
Carry unresolved items forward with owners
Give each exception an order reference, amount and currency, reason, responsible person and next check. Separate a technical missing-return investigation from an approved financial correction. Check the existing request before submitting another refund or capture.
The daily operating manual provides the routine feeding this pack. The authorisation and refund guide helps classify customer payment enquiries.
Sign off reporting and venue settlement separately
Record the preparer, reviewer and pack version. If venues earn a commercial share, calculate it on the agreed basis and retain the approval. An amount earned is distinct from an actual payment to the venue; a dashboard calculation does not automatically create a Stripe split payout.
Review CoreCharge reader-equipped stations or request a Romania reporting and reconciliation walkthrough using your proposed RON tariff and payout arrangement.
References and project scope
Technical references checked on 17 October 2026. The operating procedures above are planning guidance; hardware, account access and payment settings are confirmed for each deployment.