Understanding bundled payments
Some payments arrive in Unisoft as bundled batches: a single bank transaction that brings together several logically distinct payments. This page explains what a batch is, how to identify it in the list, and why a payment belonging to a batch cannot be refunded individually.
What is a batch?
A batch (technically called paymentGroup) is a single bank transaction that corresponds to multiple Unisoft payments. The donor made a single debit on their card or account, but it covers multiple lines in Unisoft.
Concrete examples
| Situation | Batch created |
|---|---|
| A family registers as a block for an event with 5 participants at 50 € | 1 transaction of 250 € = 1 batch of 5 payments of 50 € |
| A donor pays 3 different annual fees in a single transaction | 1 transaction = 1 batch of 3 payments |
| A multi-item basket on the site (campaign donation + course registration + boutique book) | 1 transaction = 1 batch |
| Multiple donation pledges paid in a single transfer | 1 batch grouping the payments |
Why this structure
The batch preserves functional readability on the Unisoft side (one payment per reason, one tax receipt per payment if eligible) while respecting the bank reality (a single transaction on the platform side).
This is essential for:
- Bank reconciliation: a single credit = an identifiable batch
- Tracking by campaign / fund: each payment counts in its own category
- Tax receipts: issued per individual payment, not per batch
Identify a batch payment
In the detail panel of a payment belonging to a batch, Unisoft displays:
| Clue | Detail |
|---|---|
| "Payment from a batch" mention | Visible at the top of the panel |
| Batch identifier | Unique reference of the parent batch |
| Link to other payments in the batch | See all payments linked to the same transaction |
| Total batch amount | Sum of all payments in the batch |
Why a batch payment is not individually refundable
The payment platform (Stripe, PayGreen…) doesn't know that Unisoft has split the transaction into multiple payments. For it, there is a single transaction of 250 € on the donor's card.
| Action | Possible on platform side? |
|---|---|
| Refund 250 € (entire batch) | Yes — full refund |
| Refund a portion, for example 50 € | Technically possible (partial refund) but complex to coordinate with Unisoft payments |
| Refund a specific payment from the batch | No equivalent notion on platform side |
This is why Unisoft disables the "Refund" action on individual batch payments, and proposes instead the refund of the entire batch.
Refund a complete batch
- 1
Open one of the payments in the batch
The detail panel is displayed.
- 2
Click on See other payments in the batch
You access the batch view with all grouped payments.
- 3
Click on Refund the entire batch
The action is centralized at the batch level, not the payment.
- 4
Confirm the total amount to refund
Unisoft displays the total and the list of concerned payments.
- 5
Validate
All payments in the batch go to Refund in progress status, then Refunded upon platform confirmation.
Manage a dispute on part of the batch
If the donor disputes only a portion of a batch (for example, on 250 € of family registrations, they dispute the 50 € registration for a child who finally won't come):
Solution 1: Refund the entire batch then re-enter
- 1
Refund the complete batch
Procedure above.
- 2
Manually enter the payments to keep
For the remaining 200 €, make a new payment (check, transfer, re-entered card depending on the available method).
- 3
Communicate with the donor
Explain the procedure and confirm the arrangement.
Solution 2: Compensation outside the batch
If refunding the batch is too heavy, propose to the donor:
- A credit on a future payment (registration to an upcoming event)
- A credit note materialized in comment on their profile
It is a less clean accounting solution but operationally simpler.
Special cases
Mixed batch (multiple reasons)
A batch can contain payments with different reasons: a donation to a campaign + a registration to an event + a membership fee. Each individual payment keeps its own reason, its own tax receipt (if eligible), its own link to the concerned entity. Only the refund is grouped.
Batch with eligible and non-eligible tax receipt payments
Typical case: 100 € for a campaign (deductible) + 50 € for a boutique book (non-deductible). The tax receipt is issued only on the 100 € deductible. The overall batch is worth 150 €.
Batch from a multi-reason subscription
When a subscription is multi-reason (50 €/month allocated to 3 reasons), each due date creates a batch in Unisoft. See Multi-reason subscription.
Failure of part of the batch
If a platform accepts the overall transaction but fails to allocate a specific payment of the batch, the batch is marked as partially validated. Admin action required to resolve — contact support.
Go further
- Understanding a payment
- Refund a payment — standard procedure
- Add a multi-reason payment — different from a batch