
Accounting begins during service
An accountant needs more than the final number at the end of a day. They need a traceable path from what was sold, through payment methods and receipts, to the close of a period. In a restaurant, that information is created at tables, at a counter, on card terminals, with vouchers, and sometimes through corrections. If those steps are reconstructed only at month-end, even a small question can consume hours. Bonzumo brings checkout, closing, and reporting preparation into a common operational context.
Begin an export plan with a clear question: What information does the person receiving your figures need, in what grouping and for which period? That person might work in-house or at an external accounting firm. Bonzumo includes daily-closing, accounting-preparation, and a DATEV-related export interface. Whether the format, account mapping, and handover meet your particular needs has to be confirmed during setup. An export button alone cannot replace professional agreement on the data.
Define business periods deliberately
Hospitality operating days do not always end at midnight. A bar may close in the early morning while the next day's preparation starts shortly afterwards. Closing therefore needs a clear rule for which transactions belong to which period. An unsuitable cut-off can make a correct payment appear to be a discrepancy. Agree the business logic before sending a file to an accountant or making a comparison across several shifts.
A repeatable routine is valuable: Who checks a shift, when is a day closed, and how are unresolved cases recorded? Closing should not depend on notes stored only in one manager's notebook. Bonzumo provides closing and reporting context; the responsibility for acting on it belongs to your team. Test a shift that crosses midnight and a day handled by two different teams. If both can explain the period in the same way, later handovers become easier to trust.
Separate payment methods clearly
Cash and card payments may look equally straightforward to guests, but they follow different internal review paths. Add vouchers, tips, and partial payments, and the accounting handover becomes more detailed. Staff need to know which amount belongs to which method and what remains unpaid. A wrong choice made during a busy checkout can reappear later as an apparent closing difference. That is why accounting quality starts at the point of sale.
Bonzumo supports payment workflows and presents them in payment and closing contexts. What matters is not an endless list of theoretical methods; it is a clear description of the methods you actually use. For each one, decide which receipt or external confirmation the team can expect and who investigates an uncertain outcome. This helps staff explore a difference without restarting a charge that may already have succeeded.
Put receipts and invoice details in context
A receipt explains what was billed; a payment confirmation may add another part of the evidence. Split bills, business meals, and events require those pieces to belong to the correct partial transaction. Bonzumo can collect invoice-recipient details within the payment flow. Ask for such details early and make the checking responsibility clear. An after-the-fact spreadsheet is a weak substitute once the table context has disappeared.
For useful filing, an accountant needs a way to relate a question back to a transaction. Period, amount, payment method, and receipt relationship are practical reference points. Personal guest data should be used only where relevant to the purpose. Retention and invoicing requirements depend on the legal setting and your business; Bonzumo can support an organised process but does not replace tax or legal assessment for an individual case.
Explain cash movements, not just the cash balance
Beyond sales, a venue may record deposits, withdrawals, or other cash movements. These affect the money counted in the drawer but are not automatically sales revenue. A useful cash book distinguishes the type of movement from the closing cash balance. Bonzumo includes cash-book and closing areas. The entries, supporting documents, and responsibilities needed in your business should be agreed with the accounting team. A blanket claim of compliance would be too vague to help.
A short daily check is practical: Does the counted cash match the movements expected? Is there a difference whose cause should be recorded immediately? A shift lead should be able to tell whether a payout was entered or merely written on a loose note. Questions identified while the shift is fresh are much easier to resolve than those reconstructed weeks later. Software can create a shared record; consistent operational habits make that record useful.
Agree accounts and revenue categories with a specialist
Financial accounting often requires sales and payments to be grouped into particular categories. Those groups should not be guessed from product names or device labels. Different services, tax treatments, and voucher models may raise distinct questions. Bonzumo has accounting-preparation capabilities, but the correct mapping for your business needs agreement with the responsible professional. Only then does a technical handover become meaningful.
Bring a small selection of real but anonymised examples to the setup conversation: a standard table bill, takeaway, a voucher, a split invoice, and a correction. The accountant can explain which information they need and which cases should remain separate. This turns an abstract discussion about interfaces into a concrete description of your transactions. It reduces later questions without claiming that software automatically makes every accounting judgment.
Treat an export as a controlled handover
An accounting export is more than downloading a file. It needs an agreed period, an owner, a recipient, and a check that the contents are complete and readable. The DATEV-related export area in Bonzumo is one part of such a process. Delivery to a particular firm or another application depends on format, configuration, and the agreed route. Do not assume live synchronisation with any third-party service simply because an export exists.
Before the first real transfer, decide who creates the file, how it is handed over securely, and how both sides recognise the version of the period. If something is corrected, it should be clear whether a new file replaces an earlier one or adds further information. A trial export with sample data is a valuable rehearsal. Ask the receiving accountant to review the totals and structure before the exercise becomes a regular monthly routine.
Expose differences instead of covering them up
A good closing process makes open questions visible. If a terminal result is uncertain, a voucher does not match the expected remainder, or the drawer is short, a shift lead needs a method for investigation. Posting an extra adjustment just to make the total look right can hide the actual cause. Record which transaction is involved, which evidence exists, and who will take the next step.
Bonzumo offers reports and closing views for examining numbers in an operational context. They do not remove the need to verify an external terminal status or ask an accountant to decide the treatment of a case. A helpful handover question is simple: Which items are resolved, and which remain deliberately open? When that distinction is made during the shift, the month-end accountant does not have to guess whether a difference was noticed.
Make multiple sites comparable
A restaurant, café, and bar may all follow different opening hours, device routines, and staffing models. Central reporting still benefits from common definitions. Decide which measures and closing information mean the same thing across locations and where local exceptions need explanation. Bonzumo has location-related operational context. Whether a particular export combines several sites in the form you want must be checked against your configuration.
Start with a small comparison using the same period, named sites, and consistently defined payment methods. If totals differ, the report should help you ask whether the cause is actual trading, different hours, or a different allocation. The aim is not to force unlike venues into an artificial mould. It is to give managers enough context to make decisions without spending the first hour explaining unclear column headings.
Run a trial with the accountant who receives the data
The most useful test is a small end-to-end monthly rehearsal. Choose typical days covering cash, cards, a split bill, tips, and vouchers. Follow each example from its original sale through closing to the exported structure and the recipient's view. Ask the accountant to trace an unusual transaction instead of merely approving one grand total. Can they explain where the amount came from and whether anything remains unresolved?
Bonzumo should make this route easier to understand for your business. The final fields, formats, permissions, and delivery method emerge from your actual workflow. That is a better way to assess an integration than spotting a familiar logo on a partner page. Your staff and accountant should be able to discuss the same period and the same transactions without rebuilding their meaning from scratch.