An archive should answer questions
A guest calls a week later about a receipt. A shift lead looks for a card payment from the previous evening, while accounting asks about a cash movement. These cases need different information, but they share one principle: a document must lead back to its transaction. Bonzumo has archive and reporting contexts. For your venue, decide who may search, which periods matter and how a result is checked before anything is reissued or changed.
Start with a few reliable search clues
Time, table or sales area, approximate amount and payment method are often the first clues. A split bill can produce several documents for the same table. The team should not hand over the first search result without checking it. Compare the linked sale and confirmed payment. When the information is still ambiguous, ask for another detail. Careful matching protects a guest from receiving somebody else’s record and saves the team from later corrections.
Read closing records separately from guest receipts
A daily close, a Z report and an individual receipt serve different purposes. Closing supports totals and handover; a receipt relates to a specific sale. Teams sometimes mix up these names in conversation. Training and navigation should make clear which record answers each question. Bonzumo can provide several views of transactions. Your business should have the content, retention and delivery duties for each document reviewed by qualified advisers.
Treat corrections and cancellations as events
If a sale is corrected or cancelled later, its history should not disappear through silent overwriting. The original sale, later change, time and responsible person can all matter when a question arrives. The team needs suitable permissions and a known review sequence. An old receipt must not be confused with a new payment. Practise with an anonymous case where an item was entered incorrectly and then handled using the agreed correction route. The relationship between documents is the essential part.
Include access and privacy in the routine
Not every server needs the same view into older transactions or invoice recipient details. Assign roles to the task: a quick guest question, shift review and accounting handover may require different permissions. A receipt search is not a reason to leave unrelated guest data visible on a shared device. Bonzumo provides team and access contexts. Configure the exact rights and review retention periods for your venue with appropriate professional support.
Search all the way to a verified result
In a demo, try three requests: a simple counter receipt, a partial invoice from a group table and a question about a cash withdrawal on closing night. Ask a different colleague to find each one without knowing the case in advance. They should explain why the result is correct and what they may share with the guest or accountant. That makes the archive a working tool rather than a folder that merely stores files.
Handle a later guest request step by step
A guest remembers visiting on Saturday evening and paying a card total, but no longer knows the table number. The person answering should not send several possible receipts immediately. They gather the available clues, search for matching confirmed transactions and consider whether a tip or split payment changed the amount described. Several similar results call for one more question. An authorised colleague then releases only the document linked to the actual visit through the intended delivery route.
This is easier for the team when roles are agreed in advance. Who may view older payments? Who checks invoice recipient details? Who answers a question outside opening hours? In a Bonzumo demo, have one colleague search an anonymous example while another plays the guest. Judge not only how quickly a result appears, but whether the match can be explained without exposing somebody else’s data. A useful archive saves time precisely because it does not encourage careless answers when records look similar.
Also practise a case with two similar card amounts on the same evening. A date and value alone may not uniquely identify a guest receipt, especially when separate parties pay the same menu price. Ask for another safe identifying clue and compare the underlying sale before release. If no confident match is possible, the correct next step is a review by someone with suitable access, not a guess. This careful routine makes archive search useful even during a busy service.
