import { Callout } from "zudoku/ui/Callout";

# End-to-End Reference for Batch Payments

## Business Value

With a **SEPA collective credit transfer** or a **SEPA collective direct debit**, several journal lines are handed over to the bank together. The bank then usually reports the operation back as **one** bank transaction. Without a shared reference, that single transaction can no longer be assigned to the original payment lines – reconciling your own collective payment becomes manual work.

With the **end-to-end reference for batch payments**, all lines of a batch payment carry the same end-to-end reference. The bank transaction that is reported back can therefore be assigned to its batch payment unambiguously.

## Feature Description

When a payment or a direct debit collection is carried out, 365 business Banking aligns the **end-to-end reference** across all lines of the respective batch:

1. If one line of the group already carries a reference and that reference is not used outside the group, it applies to the entire group.
2. Otherwise a new reference is drawn and written to all lines of the group.

This shared reference is passed to the bank as `endToEndId` with the payment order and at the same time serves as the identifier of the batch booking.

How the group is formed depends on the payment type:

- **SEPA collective credit transfer:** lines of the same journal with the same execution date.
- **SEPA collective direct debit:** lines with the same mandate reference and the same collection date.

Lines that originate from [customer-vendor netting](extended-payment-suggestion.mdx) are excluded – they are not paid through the bank and therefore do not belong to the batch payment.

<Callout type="info" title="Only batch payments share a reference">
Only the lines of a batch payment are given a shared reference. Lines with the payment type **SEPA credit transfer** or **SEPA instant credit transfer** are handed to the bank as single payments and therefore keep a reference of their own – even when they carry the same posting date and the same document no. and are carried out together.
</Callout>

### When the bank books a batch payment singly

Whether the bank actually books a batch payment as one collective transaction is the bank's decision. If it books the payments singly, one bank transaction comes back per payment, and every one of them quotes the reference of the **entire** group. The reference then no longer names a single payment but the whole batch.

365 business Banking handles both:

- **One collective transaction:** the transaction is assigned to the batch payment and settles all bank ledger entries of the group together.
- **Single transactions:** because the reference names several bank ledger entries, the amount additionally decides which entry belongs to which transaction. Every transaction therefore settles the bank ledger entry of its own payment.

### Where the reference comes from

In the **End-to-End Reference Nos.** field of the **General Ledger Setup** you define a number series for the references. This keeps the references meaningful and traceable within your own numbering logic.

If no number series is set up, 365 business Banking generates a technical reference from a GUID in the form `E2E…`. It is unique across companies, sessions and time, and at 35 characters uses exactly the length permitted by SEPA.

<Callout type="info" title="Set automatically when the payment is carried out">
The reference is assigned when the payment or direct debit collection is carried out – it does not have to be entered and cannot be edited in the journal.
</Callout>

For more information, see [Payments](../../bank-payment.mdx) and [Payment Journal](../../payment-journal.mdx).