How to Check Your POS Data Exports Before an Audit or Handover

Define the exact purpose of the handover first

If you want to check your POS data exports before an audit or a handover, clarify the purpose first and only then look at the file. That determines what you actually need to verify. Accounting usually needs something different from an internal handover to a new office, a location change, or a review by an auditing party. If you separate those cases cleanly at the start, you avoid the most common mistake: a technically correct file that is still the wrong one for the recipient.

In BonZumo, that distinction is built into the workflow because closing documents, the receipt archive, period exports, and DATEV EXTF CSV each serve different purposes. Depending on the purpose, you can use different documents and export types, such as Z-reports, period exports, archive records and DATEV preparation. That makes one decision much easier: do you need a condensed daily or period view, individual receipts for follow-up questions, or prepared posting data for import into the office system? Only once that question is answered does the actual verification make sense.

Keep accounting files and audit records deliberately separate

In day-to-day operations, many operators simply say “the export,” but they often mean very different things. An accounting file is usually meant to transfer figures into another system. Records for an audit or an operational handover often need to make the path from sale to payment to receipt and closing understandable. That is why a DATEV file is not automatically the full answer to every question, even if it may be exactly right for accounting.

BonZumo supports a DATEV posting batch export as EXTF CSV for preparatory accounting work. It also provides a preview and guidance notes so you do not discover obvious issues only after the recipient opens the file. In practical terms, that means you should never confuse a successfully created accounting export with a fully checked handover package. Always ask the recipient specifically whether they also expect Z reports, receipts, closing documents, or a defined period to be included. That saves you from rushed follow-up deliveries later.

Anchor the date range to your actual closing rhythm

The second basic decision is this: what exact period is being handed over? Not “roughly May” and not “the last few weeks,” but a clear start and a clear end based on how your business really runs. In hospitality, errors often happen at the boundary between two closings. An evening service may stretch organisationally past midnight, a month change may land on a very busy weekend, or a late correction may end up in the wrong folder. Under time pressure, those edges are easy to miss.

With period exports and stored Z reports, BonZumo lets you prepare exactly that slice. A good habit is to check the operating boundary first every time: first day in the period, last day in the period, first matching Z report, and last matching Z report. For example, if you expect sales on the 31st but the export only shows closing documents up to the 30th, that is not a minor detail. It points to a handover boundary set incorrectly. You will find those breaks much faster by checking the closing framework than by spending hours searching through individual rows.

Start with known transactions instead of starting with volume

A reliable export check does not begin with thousands of records. It begins with a few deliberately chosen transactions. Pick five to ten cases that represent your business well: a simple cash payment, a card payment with tip, a split bill, a voided transaction, and ideally a receipt with invoice details. That mix covers typical weak points because it brings together sales, payment method, correction, and receipt output. If those small test cases run cleanly through the selected period, you gain confidence in the rest much faster.

Use the receipt archive in BonZumo to find known transactions, then compare their dates and amounts yourself with the selected period and closing documents. That makes the task concrete for your team. They are not just checking whether some receipt exists, but whether date, amount, payment method, and the link to the transaction all make sense together. That approach is especially helpful before a handover. If even known cases do not show up properly, it is better to stop the handover immediately and clarify the cause instead of sending a large data folder onward and trying to explain a discrepancy later.

Read sales, payments, and tips as separate figures

A large share of misunderstandings in exports happens because sales, payments, and tips get mixed together. For your check, take a very sober view: what was sold, what was paid, and what amount was additionally recorded as a tip? These levels belong to the same transaction, but they do not mean the same thing. If 100 euros in sales and 5 euros in tip suddenly become 105 euros in revenue, the interpretation is already wrong, even if the guest did pay 105 euros in total.

BonZumo keeps those meanings separate within the transaction. That makes comparison with Z reports, the payment view, and receipts much easier. A hypothetical example: one table has 100 euros in sales, 5 euros in tip, and 105 euros in card payment. Your team should be able to see which amount belongs to which context, rather than staring only at one grand total. This separation matters before an audit or handover because it helps you narrow down discrepancies much more precisely. Is the difference in the sale, in the payment method, or only in the way the tip was interpreted? Without that distinction, you can end up searching in the wrong place.

Use Z reports as the guardrail for the overall comparison

Before you dive into individual receipts, check the big picture first. Z reports are the best guardrail for that. They help you judge whether a day or a period looks plausible as a whole: what sales were closed, which payment methods appear, and how many closing days the period actually contains. If that condensed view already does not make sense, perfectly matching individual receipts will not help much, because the handover frame itself is wrong.

In practice, that means comparing the stored Z reports for the selected period with what your export and archive documents show overall. If one closing day is missing, a payment method is unexpectedly empty, or the period is clearly outside the agreed monthly or weekly window, the handover should not go out yet. A typical example in a hypothetical office handover is this: the imported file looks tidy at first, but later someone notices that one daily closing from the start of the month ended up in a different period. If you check via Z reports first, you detect those shifts early and avoid a lot of rework.

Align the DATEV parameters with the recipient in advance

If you are handing data over to a tax office or accounting team, it is not enough for the figures to be roughly right. The file also has to be prepared the way that specialist team expects. In BonZumo, that includes adviser and client parameters as well as the preparation of the DATEV EXTF CSV export with preview. This is never something to guess. Even small formal deviations can mean that the recipient receives a file but still cannot use it in their intended process.

So do not only check whether the file can be created. Check whether the period, parameters, and handover logic were agreed in advance. One simple organisational rule helps a lot: have the recipient state clearly which details are needed, who maintains them in your business, and when they must be reviewed again after changes. That turns month-end stress into a repeatable process. BonZumo helps you prepare the posting batch, but you should still confirm directly with the recipient which format they expect in your case and when they plan to import it.

Turn preview notes into real work tasks

If the export preview or its check notes show something, that is neither automatically a disaster nor something to click away. The sensible approach is to turn each note into a concrete question. Is an assignment missing? Is some master data incomplete? Was the wrong period chosen? Or is a quick clarification with accounting enough because a special case is expected differently there? This calm classification prevents the familiar pattern of exporting the same data again and again without a plan.

It also helps to assign clear roles in your team. One person checks the period and closing boundaries, a second reviews known sample transactions, and a third checks the export parameters for the office handover if needed. That turns a technical note into something your team can actually work through. BonZumo supports you with preview and guidance notes, but the practical value only appears when your business turns that into decisions. A note is not just a warning light. It is the starting point for a focused clarification before files leave the business.

Store unchanged original files and add readable supporting records

Once the export content looks plausible, an often underestimated step begins: clean filing. Save export files unchanged in a clearly named handover folder with period, creation date, and purpose of the handover. Add the matching Z reports and the records you may need immediately for follow-up questions. Do not quickly open and alter CSV files in a spreadsheet program just to make them easier to read. That kind of editing can shift columns, separators, or formats and later create exactly the problems you were trying to avoid.

It also makes sense to add a short cover note for the recipient, whether in your internal documentation or in the handover record itself. Note which period is included, what type of export was attached, and which totals you checked roughly in advance. That is not a legal statement. It is simply good order. If a discrepancy appears later, you immediately know which file was originally handed over. BonZumo makes that order easier because Z reports, the receipt archive, and export preparation are connected. Careful storage and naming are still organisational tasks on your side.

Get the recipient to confirm the import and any open points before the actual review

The final check does not end when you click export. It ends when the recipient confirms what was successfully imported or reviewed and what may still be missing. Especially when handing data over to accounting, tax advisers, successors, or internal administrative teams, ask for a short confirmation. That protects you from the typical situation where someone only notices shortly before an audit that a file did arrive, but the expected period or supporting records were not included.

For a truly reliable preparation before an audit or handover, keep the same order every time: clarify the purpose, distinguish the format, define the period cleanly, check known transactions, separate the totals, mirror them against Z reports, align the handover parameters, and store the original files unchanged. If you also clarify which details on fiscalisation, technical closing boundaries, or country-specific requirements your actual recipient wants to see, you remove a lot of deadline pressure from the appointment. BonZumo helps you structure the records and the path through the data. Whether your business also needs special audit formats or additional documents beyond that should be agreed in advance with your office, technical contact, or specialist advisor.