This dashboard answers questions like:
"What is my total outstanding voucher liability right now, and which vouchers compose it?"
"How much give-away have I extended on this specific voucher?"
"When was this voucher used, where, and what's left on it?"
"Has this voucher expired, been fully redeemed, or is it still active?"
Voucher overview table
One row per voucher, summarizing its current state.
Column | Meaning |
Voucher code | The unique code customers use to identify their voucher. |
Issuance date | When the voucher was created. |
Expiry date | When the voucher's redeemable period ends. |
Issuance organizer ID | The organizer that issued the voucher. |
Initial value | The face value at issuance — what the customer can spend in total. |
Bonus value | The total give-away on the voucher, including the difference between face value and price paid plus any post-purchase promotional discounts. |
Current status | One of Active, Partially Redeemed, Redeemed, Expired, Cancelled (definitions below). |
Total redeemed | Net face value the customer has used (redemptions minus refunds). |
Remaining balance | Face value the voucher can still be spent for. |
Status definitions
Active — voucher is valid, has its full original face value remaining.
Partially Redeemed — voucher has been used for part of its face value; some still remains.
Redeemed — voucher has been fully consumed (remaining balance is zero).
Expired — voucher reached its expiry date with unredeemed balance, and the remaining face was written off.
Cancelled — voucher was voided. Cancelled vouchers are excluded from the overview by default.
Voucher transaction log table
One row per event in the voucher's life — every issuance, redemption, refund, expiry, etc. Use this table to drill into a specific voucher's history.
Column | Meaning |
Transaction ID | Unique identifier of the event. Matches the journal entry ID so you can cross-reference with your journal entries. |
Synchronization date | When the event was recorded in the system. |
Transaction date | Accounting date of the event (used for filtering and reporting periods). |
Transaction type | One of eight event types — see "Transaction types" below. |
Voucher code | The voucher this event belongs to. |
Issuance organizer ID | The organizer that issued the voucher. |
Transaction organizer (location) | The organizer where this specific event occurred — the redeeming organizer for redemptions, the issuer for issuance. |
Cross-organization flag | Internal (same organizer as issuer) or External (different organizer). |
Transaction amount | Face-value movement at this event (always non-negative; the direction is implied by the type). |
Cash amount | Cost-basis movement at this event — what changed on the merchant's voucher liability books. |
Bonus amount | The give-away (discount) portion of the event. On face-moving events: transaction amount minus cash amount. |
Balance after transaction | Running face balance on the voucher after this event. |
Cumulative bonus | Running in-flight bonus on the voucher — give-away assigned minus give-away realized so far. Closes to zero at end of life. |
Order reference | Customer-facing reference for redemption events. Links a row to the order that used the voucher. |
Transaction types
Each row carries one of eight transaction types, grouped into four lifecycle pairs:
Face-moving events — change the voucher's spendable face value:
Issuance — voucher created.
Cancellation — voucher voided.
Redemption — voucher used to pay for goods or services.
Refund — a redemption reversed.
Expiry — unredeemed face written off at the expiry date.
Expiry reversed — a post-expiry extension restores the voucher.
Bonus-moving events — change the give-away balance on the voucher; the voucher's spendable face is unaffected:
Discount applied — a promotional discount is applied to the voucher (e.g., promo code).
Discount cancelled — that promotional discount is reversed.
How to read each row — the face / cash / bonus split
Three numbers on each face-moving row tell the same event from different angles:
Transaction amount is the customer's view — how much spendable face moved at this event.
Cash amount is the merchant's view — how much real cost moved on the voucher liability books.
Bonus amount is the difference — the give-away portion of the event.
For face-moving events: Transaction amount = Cash amount + Bonus amount.
Example: a CHF 40 redemption of a voucher with face CHF 100 / price paid CHF 80
Transaction amount | Cash amount | Bonus amount |
40 | 32 | 8 |
The customer used CHF 40 of face value. The merchant's voucher liability decreased by CHF 32 (the pro-rated cost basis). The CHF 8 difference is the give-away realized at this redemption.
Bonus-only events (Discount applied / Discount cancelled) sit outside this equation: face = 0, cash = 0, bonus = the discount magnitude.
Cumulative bonus — the lifetime give-away view
Cumulative bonus tracks how much give-away is currently in flight on a voucher: discount assigned, minus discount already realized at redemption (or lost to expiry). It reaches zero by end of life for fully consumed vouchers, exactly like the face balance.
The peak Cumulative bonus value on a voucher equals the total give-away ever assigned to it — useful when you want to compute total give-away per voucher. The Bonus value column on the overview table already does this aggregation for you.
Cross-organizer behavior
For vouchers redeemed at a different organizer than the issuer:
The issuer sees the full lifecycle on this dashboard — issuance, every redemption (regardless of where), refunds, expiry, etc. The transaction organizer column shows where each redemption happened.
The redeemer does not see this voucher on their reconciliation dashboard. The dashboard is anchored to the issuer who owns the voucher liability. Redeemers tracking voucher activity at their own locations should consult their journal entries directly — the 1111 (External voucher) settlement entries and the Voucher redemption discount entries on their books capture this activity.
Anti-backdating
Two date columns work together:
Synchronization date — when the event was recorded in the system.
Transaction date — accounting date of the event, used for period reporting.
Filtering by synchronization date gives you a point-in-time snapshot: the same date filter applied a year later will return the same rows, even if new events have occurred for the voucher since.
Reconciling with your journal entries
Each row in the voucher transaction log corresponds to a row in your journal entries. The transaction ID on the log row matches the journal entry ID on the GL row.
A few things to keep in mind when reconciling:
The transaction amount on the log row shows face value; the journal entry shows cost basis. They differ by the give-away portion at that event.
The cash amount on the log row matches the 2050 movement booked to the journal entries.
The sales and VAT reductions for the give-away portion live in the journal entries directly as "Voucher redemption discount" entries — they're the accounting side of the redemption and do not appear as separate rows in the voucher transaction log.