Search articles

    All Gastrokompass articles →

    Details

    Agree DATEV import requirements and test a sample file

    How do you agree DATEV import details and verify the export works for your accountant?

    Agree period boundaries, posting rules, account mappings, document links and file format with your adviser, then produce a representative sample period (cash, card, cash movement, split bill). Have the recipient perform a trial import and sign off before regular handovers; BonZumo availability of specific DATEV options depends on your configuration.

    Guide overview: Prepare DATEV requirements and accounting exports for a restaurant: Start with the recipient workflow; Keep documents connected to figures; Agree on a sample period before the first export

    Start with the recipient workflow

    An export is useful only when the accounting team knows what it receives and how to process it. Ask first about the period, posting rules, accounts, document references and preferred file format. Bonzumo provides accounting preparation and closing information; the availability of a particular DATEV requirement must be checked for the actual configuration. A downloadable file does not prove that the recipient imported it successfully or that a live integration exists.

    Prepare payment methods carefully

    Cash, card, vouchers and unpaid invoices can take different paths in accounting. If a payment method was selected incorrectly during service, an export cannot magically recreate the truth. Explain to the team why the choice at checkout matters. Review the related figures at daily closing. Only then decide how records move into accounting. With card payments, the individual confirmed transaction and a later grouped provider payout may fall on different dates.

    Check period boundaries and completeness

    Exporting one month sounds simple, but a restaurant may work across midnight and distinguish operating day from calendar day. Agree with the adviser what period is needed and which documents belong to it. Check that relevant closes are present and whether open or cancelled transactions need separate attention. Bonzumo can provide closing and archive information. Verify how a proposed export selects it and what preflight checks exist by using a sample file.

    Keep documents connected to figures

    Numbers without a traceable source lead to questions. A useful handover connects each required figure to its origin: sale, payment, cash movement or correction. Not every detail must be in one file, but the accounting team needs to know where to investigate. Use anonymous sample transactions and compare the displayed totals with the available documents. Data protection and retention duties still require business-specific professional review.

    Test an import, not just an Export button

    A successful download proves only that a file was produced. The next step is a trial import by the actual recipient or in its test environment. Check encoding, separators, periods, account assignment, error messages and document links. Record what remains open. Describe a Bonzumo connection as ready only when the agreed route has been tested with your adviser and configuration. A blanket claim about DATEV support would not answer the practical questions. For the system export step, see DATEV export in Bonzumo: preflight and handover.

    Set a repeatable monthly handover

    Once a test works, your venue needs a rhythm. Who checks the closes, who creates the transfer, where is its version stored and who reports import errors? A short checklist with named roles is better than a ritual known to one person. Include an exception: what happens when a transaction for one day is still under review? The result is not merely a technical export but a dependable working process between restaurant, accountant and adviser.

    Agree on a sample period before the first export

    Do not test only an empty day with one cash sale. A useful sample period contains cash and card payments, a cash movement, a split bill and at least one document with recipient details. The accounting office can then check whether the data answers its actual questions. Note whether your venue uses an operating day that crosses midnight. If the export period is cut differently, a correct daily result may appear to be missing from the month. Resolve that boundary before making the transfer routine.

    Agree what a failed test means. A field format may be wrong, an account mapping may be absent or a document may not link to its sale. That is not a reason to replace source records with uncontrolled manual values. Record the feedback, adjust the agreed configuration and test the same cases again. The routine is ready for repeated use only when sender and recipient understand the result. Bonzumo can provide operational data; the receiving system and accounting mappings belong in the conversation with your adviser.

    Before calling the test complete, ask the adviser to describe one imported sale and one cash movement using only the received data and agreed document access. If the explanation requires a phone call to somebody who remembers the shift, identify the missing reference. Keep the original sample and the feedback together so the next export can be compared against the same cases. This avoids changing the period, mappings and example transactions all at once when a problem appears.

    Technical source for the file format: DATEV format – posting batch. Agree the specific import process with your accountant.

    Next step

    See how the workflow fits your operation.

    Request a demo