Accountants

Align supplier accounts between Hans and DATEV

A known supplier should continue on the accounting firm's existing account after the move to Hans. Verify that the legal supplier is the same, then save the target-account mapping before the first export. This solves a numbering problem; it does not recreate the detail behind an opening balance. The example below reconciles old invoices, a new invoice and a combined payment to the exact remaining supplier balance.

Author: DeinHans Team

Updated: 4 min read
In this article

Key takeaways

  • Verify supplier identity before assigning the target account.
  • Keep opening balances separate from historical invoice detail.
  • Check the remaining items and account balance after import.

Same supplier, two account numbers

In this fictional example, the firm already uses DATEV account 70042 for a supplier. Hans has created the same verified supplier under 70088. Both numbers are illustrative.

ItemCorrect mapping result
Supplier identity in HansRemains the same legal supplier
Target supplier accountDATEV 70042
New invoice for €357Exported to 70042
Payment allocation against that invoiceUses the same target supplier account and invoice reference
Future exportsReuse the saved mapping

The client does not need a second DATEV supplier account simply because the source system uses another number. Inspect the export preview to confirm the mapped result.

Verify identity before saving the mapping

Compare the invoice issuer with the existing master record: legal name, address and available registration or VAT identifiers. Check whether a changed name is only a spelling variation, a legal name change or a different company.

A familiar brand, identical amount or shared collection IBAN is insufficient. If target account 70042 already belongs to another entity, resolve that collision rather than using the occupied number.

The supplier-identity guide covers two legal suppliers trading under a similar name.

Reconcile the opening balance and current work

At the 1 September cutover, this supplier is owed €2,400. The old ledger's retained detail contains two unpaid invoices of €1,200 each. A new September invoice adds €357.

The client pays €1,057. Its remittance advice allocates €357 to the new invoice and €700 to the first old invoice.

Supplier positionBefore paymentPayment allocatedRemaining
Old invoice A€1,200€700€500
Old invoice B€1,200€0€1,200
New September invoice€357€357€0
Total€2,757€1,057€1,700

The account-level reconciliation is €2,400 opening liability + €357 new invoice − €1,057 payment = €1,700 closing liability.

In the continuing DATEV ledger, the two old invoices already exist. Import the agreed new activity without importing the €2,400 opening position again. Otherwise the historic liability would be duplicated.

In Hans, use the agreed opening-balance setup to establish the account-level starting position. Retain the old invoice detail needed for allocation and reconciliation. An aggregate €2,400 balance does not itself import invoices A and B.

Know what the supported imports contain

Hans supports master data, accounts and opening balances. Keep the three concepts separate:

  • Master data: who the supplier is and which account identifies it.
  • Opening balance: the amount owed at the cutover date.
  • Open-item detail: invoices, credits, due dates and previous allocations explaining that balance.

Do not treat a balance import as an OPOS-history import. If historical invoice-level processing is needed, agree how that detail is retained and handled before the first payment. The old ledger or archive remains evidence for the illustrated €700 allocation.

Correct the mapping at the right stage

StageAction
Not exportedSave the mapping and inspect the preview
Exported, not importedMark the old package as superseded and issue the agreed replacement
Partly importedIdentify accepted rows before deciding the correction
Fully importedCoordinate the correction in the receiving ledger; a new mapping does not rewrite old postings

DATEV's booking-batch specification defines the receiving fields. The firm's import check establishes that the actual package used the correct account and references.

Accept the first month with three checks

  1. Identity: one known supplier, one genuinely new supplier and one numbering conflict end up on the intended accounts.
  2. Settlement: invoice and payment references produce the intended remaining items, including a payment against an earlier balance.
  3. Totals: the supplier subledger and control account reconcile, and bank movements appear once.

For the worked example, acceptance means target account 70042 carries €1,700: €500 on invoice A and €1,200 on invoice B. The new €357 invoice is cleared. That outcome proves more than a successful CSV upload.

Use the first-month setup guide to agree the cutover and the export guide to check the complete package.

Sources

Sources were checked on 06 October 2026. This article provides orientation and is not tax, legal, or accounting advice.

  1. German Commercial Code section 238 – bookkeeping duty
  2. DATEV Developer Portal – booking batch format

Related resources

  1. Open-item reconciliation: connect invoices, payments and account balances
  2. Start with Hans alongside DATEV, Agenda or Lexware
  3. Same brand, different supplier: check identity before matching invoices

Start with your first free mandate

One named mandate stays free for your firm, with all features and personal setup help. No card or automatic paid subscription.

Start freeBook a demo
Back to resources