Open table of contents
Key takeaways
- Keep payroll calculation in the established process.
- Give each bank payment one posting owner.
- Confirm the actual liability accounts, not just the chart-of-accounts name.
- Investigate a remaining balance rather than forcing it to zero.
€6,000 owed, €6,000 paid
This fictional example follows net wages only. A complete payroll journal contains other components.
| Step | Work performed | Effect |
|---|---|---|
| Payroll in the existing system | Calculate and record payroll | The full journal includes €6,000 credited to net wages payable |
| Payment assigned to Hans | Record the bank movement | Debit net wages payable €6,000; credit bank €6,000 |
| Firm checks the combined books | Compare liability and payment | With no opening balance or other movements, this liability is zero |
The bank payment reduces what is owed. It must not create wage expense again. Likewise, if DATEV has already recorded this payment, importing it again from Hans would duplicate the bank movement.
DATEV describes payroll-to-accounting interfaces in its Lohn und Gehalt documentation. That existing process can remain in place.
Check three payment relationships during setup
Net wages, wage tax and social-insurance payments have different counterparties and liability relationships. Confirm each relevant account and the period covered. Both systems using SKR03 does not prove that their account assignments agree.
Hans includes supported payment rules in its configured setup. The firm can inspect, adjust or disable applicable rules. Automatic processing depends on the enabled rule, authorization and available evidence. An unfamiliar correction or refund can still need review even when the recipient is familiar.
If the liability does not clear
| Situation | What to check |
|---|---|
| Payroll recorded, cash not paid yet | Is the payment still pending? |
| One amount paid in two transfers | Do both references support the same liability? |
| Payment for an earlier period | Is the earlier liability still open? |
| Different amount paid | Is there a settlement or correction explaining it? |
| Bank movement recorded twice | Which system owned the posting and which package was imported? |
A zero balance is useful only when the underlying entries are correct. It does not certify the payroll calculation, taxes or social-insurance amounts.
Accept the first month with the firm
Check that the payroll entry exists in the receiving books, the payment uses the agreed liability account and the bank movement appears once. Explain remaining balances and inspect the actual import result, not just the export file.
During evaluation, both systems may process the same sample for comparison. Keep that comparison output out of the accepted books. The benefit of parallel operation comes from dividing the work, not posting the same work twice.
Use the DATEV setup guide to agree the first period. The monthly-close checklist covers the rest of the month.
Sources
Sources were checked on 27 September 2026. This article provides orientation and is not tax, legal, or accounting advice.
Related resources
See how your firm would review a month
Inspect a monthly package with us: evidence, payments and remaining decisions. Establish what stays in your existing workflow and what DeinHans takes on.
Inspect a monthly package in a demo