Industries
Deposit return system — IT integration from a business perspective
Maciej Zaleski · Published · Updated · 8 min read
In practice, integrating with a deposit return system means connecting your company to a network carrying three simultaneous streams: packaging data, physical bags of packaging, and money. For a producer, retail chain, or collection point, this means changes to tills, warehousing, ERP, and accounting. This article presents the deposit return system in broad building blocks — who is responsible for what, where information goes, and what to consider when planning integration.
The description is based on our experience working on the deposit return system operator's side (KAUCJA.PL case study). It is not a legal description — detailed obligations depend on the participant's role and current regulations.
Who participates in a deposit return system
A deposit return system connects five participant groups. Each has its own systems, and the operator's system sits at the center.
| Participant | Role in the cycle | What they exchange with the operator |
|---|---|---|
| Parties placing products on the market (producers, importers) | Place beverages on the market in deposit-bearing packaging | Product data (EAN, dimensions, weights, material), volume declarations, initial deposit and producer fee |
| Retail chains and collection points | Charge deposits on sales and accept returns | Voucher verification, bag pickup requests, deposit notes, collection invoices |
| Logistics | Collects sealed bags from stores | Pickup orders, seal numbers |
| Sorting and counting centers | Count the actual number of containers | Count and discrepancy reports |
| Bank and financial systems | Execute money flows | Statements, bulk transfers, accounting documents |
The operator is an intermediary and the single source of truth for vouchers, bags, and balances. This matters for IT: no participant settles “directly” with another — everything passes through the central system.
How data flows in a deposit return system — integration step by step
The easiest way to understand the system is to follow one bottle.
- Product catalog. The party placing the product on the market registers the packaging (EAN, dimensions, weight, material — e.g. PET, aluminum can, reusable glass). The operator makes this catalog available to tills and machines so every point knows whether the packaging carries a deposit and which rate applies.
- Sale. The till adds the deposit to the bill as a separate item.
- Return. The consumer returns the container to a reverse vending machine (RVM) or a store employee. A voucher is printed and immediately registered in the operator's system.
- Voucher redemption. The cashier scans the voucher, and the till asks the operator's system whether it is valid. If so, the system marks it as used, and the customer receives cash or a reduced bill.
- Bag and seal. The store packs containers into a bag, applies a seal with a unique code, and reports it ready for collection. The seal number links the store, transport, and counting center.
- Counting. The counting center scans the seal, counts units and material fractions, and sends the result to the operator along with any discrepancies against the store's declaration.
- Settlement. On this basis, the operator issues documents and orders bank transfers.
Why a voucher must be “burned” in real time
A voucher exists in the system from printing until redemption. Marking it as used once blocks attempts to reuse the same voucher at different tills. For a retail chain, this means tills need a stable, fast connection to the operator's system.
Three money streams
From a financial perspective, a deposit return system involves three separate settlements that are easy to confuse.
Reimbursing the store's deposits
The store refunds customers' deposits from its own till. The operator issues a deposit note for the amount paid to customers and orders a transfer to the chain's account. Illustrative example: a store paid customers a given amount, then receives a note for the same amount and a transfer.
Collection remuneration (handling fee)
The store receives remuneration for every container accepted. The operator issues an invoice on the store's behalf (self-billing), and the document goes to KSeF. Unlike the deposit itself, this stream is subject to VAT.
Counting-center adjustments
When the counting center finds shortages in bags from manual collection — for example, the store declared 100 containers but 90 were counted — the next deposit note is automatically reduced by the difference.
What this means for your company's IT
The scope of changes depends on the role. Below are the most common areas worth planning in advance.
Parties placing products on the market:
- maintaining complete, up-to-date product data in the catalog,
- reporting volumes and handling payments from ERP,
- linking product master data to the data provided to the operator.
Retail chains and collection points:
- integrating tills (POS) with the catalog and voucher verification,
- supporting reverse vending machines and manual collection,
- recording bags and seals in the store's warehouse,
- posting deposit notes, collection invoices, and adjustments in ERP (e.g. Microsoft Dynamics Business Central),
- reconciling transfers with documents.
All participants:
- secure data exchange with the operator (private connections, access control, monitoring),
- clear rules on who in the company is responsible for discrepancies and adjustments.
We discuss connecting ERP to other systems further in the article on ERP system integration.
How to prepare your company for integration — a five-step plan
- Establish your role and obligations. A party placing products on the market has different tasks from a retail chain or collection point. Start with a list of processes the system affects in your company.
- Inventory your systems. Tills, machines, warehouse, ERP, bank — for each, determine what data it sends and receives and who owns it on the business side.
- Organize master data. Product records, sales outlets, and settlement accounts must be complete before transactions start flowing.
- Design reconciliation. Decide how to compare vouchers, bags, notes, invoices, and transfers daily and who responds to discrepancies.
- Test using sample data. A pilot at a few locations helps catch performance and format problems before they affect the whole network.
The most common risks
- Inconsistent product data. An incorrect EAN or material in the catalog leads to incorrect charges at the till.
- Manual document re-entry. Notes, invoices, and adjustments at scale quickly create accounting backlogs.
- No reconciliation. If amounts in notes, transfers, and counting-center reports are not compared automatically, discrepancies only surface at month-end closing.
- Performance. Large numbers of vouchers and bags can strain databases and integrations if they were not designed for that volume.
- Security. Financial data and e-invoices require private, monitored connections, not open interfaces.
FAQ
Does integration with a deposit return system require replacing tills?
Not always. Updating POS software and connecting it to the catalog and voucher verification is often enough. The decision depends on the existing POS system's capabilities and the operator's requirements.
How does a deposit note differ from a collection invoice?
A deposit note concerns reimbursement of deposits the store paid to customers. A collection invoice (handling fee) is remuneration for containers accepted by the store, issued through self-billing and submitted to KSeF.
Where do adjustments come from?
From the difference between the store's declaration and the actual count at the counting center. The bag's seal number is the key linking both sides.
Who is responsible for product data?
The party placing the product on the market — the beverage producer or importer. Correct deposit charging across the entire chain depends on this data's quality.
Can Business Central support a deposit return system?
Yes, ERP can post deposit notes, collection invoices, and adjustments and reconcile them with transfers. This does, however, require integration with the operator's data and adaptation of accounting processes.
Summary
A deposit return system is a network where data, bags, and money must reconcile down to the individual unit. Well-designed integrations make the biggest difference: with tills, warehouses, ERP, and banks, including automatic reconciliation and secure data exchange. If you are preparing your company to participate, see how we work in the circular economy industry and on system integration, or book a 30-minute conversation — we will help put together an integration plan.
Maciej Zaleski
Managing Director, Go2ops