How to Issue E-Invoices to Retail Customers at a Cafe
A practical counter workflow for issuing e-invoices to walk-in cafe customers: what to ask, handling refusals and late requests, fixing errors.

It is 8:40 on a Monday morning and the queue is out of the door. A customer pays for an americano and a croissant, then adds, "Could I get an invoice for that?" Your cashier has already moved the order to "paid", the next customer is stepping forward, and nobody is sure whether the invoice should have been started before payment or after it. What does a cafe actually need in place so that this ten-second moment goes smoothly every time?
In short, you need a fixed routine of four moves: close the order in the point-of-sale system, ask one standard question about invoicing, collect only the details the invoice type needs, and issue and deliver the invoice before touching the next order. Everything else, including error handling, late requests and end-of-shift checks, exists to protect that routine. This article builds the routine for a Vietnamese cafe and shows how to test it, without arguing about whether your cafe is required to issue invoices in the first place.
Important: this is general information about process, not legal or tax advice. Invoicing rules in Vietnam change and differ by business type. Check the current documents published by the tax authority, or ask your accountant or a tax adviser, before you apply any step below.
What makes a retail customer different from a business buyer
A retail customer buys for personal consumption: a drink, a pastry, a loaf to take home. They pay on the spot, they rarely want to give personal details, and they want the whole thing to take seconds. A business buyer behaves differently. They want the company name and tax code on the invoice, often ask after the fact, and may combine several purchases.
That difference shapes the counter design. The transaction content (items, quantities, unit prices, total, payment method) always exists in your sales system. The buyer details may or may not exist. How your cafe treats a customer who gives no details is a question for current rules and for the tax office that manages your business, so confirm it with your accountant before writing it into your routine.
| Aspect | Walk-in retail customer | Customer buying for a company |
|---|---|---|
| Buyer details | Often minimal or none | Company name, tax code, address |
| When the request comes | At payment, or never | Before payment, or days later |
| Typical failure | Missed orders, slow queue | Wrong tax code or company name |
| Delivery channel | QR code, text message, email, or none | Email, mostly |
| Who checks | Cashier and shift lead | Cashier and accountant |
What to prepare before the first customer asks
Most counter chaos is really a setup problem. If the cashier has to improvise, the queue grows and mistakes multiply. Before you start, check the following.
- You and your accountant have agreed how invoices are created for your business, including whether they come directly from the cash register or are made in a separate tool.
- Your sales system can connect to the invoicing channel you chose. To see what invoices generated straight from a sale look like at solution level, read the page on e-invoicing from the cash register and compare it with your setup.
- Your menu items and tax categories have been confirmed by your accountant. A wrongly categorized item produces a wrong invoice, and correcting invoices costs far more time than correcting the menu.
- Cashiers can read the invoice status on screen: issued, pending, failed.
- There is a fallback device or procedure for internet loss or register failure.
- One person per shift is authorized to handle exceptions and knows how to reach the accountant.
If you run several outlets, give them the same routine and the same item naming so that reconciliation does not drift. Browsing how software for this model is organized, for instance the page on multi-branch cafe and bubble-tea management, can give you a checklist of what to expect from any system you evaluate.
The counter routine, move by move
The sequence below is a template. Adjust it once your accountant confirms the invoice type your cafe uses.
- Close the order. Confirm items and quantities with the customer, take payment, and record the payment method. Do not start anything invoice-related while the order can still change.
- Ask one question. For example: "Would you like an invoice?" Keep it to that. A single, identical question from every cashier keeps the queue moving and the experience consistent.
- Branch on the answer. If the answer is no, finish the order in the way agreed with your accountant. If yes, continue.
- Collect only what the system needs. Depending on the invoice type, that might be an email address or phone number for delivery, plus a tax code and company name if the customer wants the invoice in a business name. Read the details back before confirming.
- Issue and deliver. Press issue, wait for a success status, then send the invoice through the channel the customer picked. Do not hand over the drink and move on while the status still says pending.
- Record exceptions. Failed invoice, changed mind, bank transfer not yet confirmed: tell the shift lead, who logs it in the notebook or the system notes.
Why one question beats a menu of options
New cashiers tend to over-explain. They offer paper, email, text and QR in one breath, and the customer, who just wanted a coffee, sighs. Limiting the opening to a yes-or-no question pushes the decision where it belongs. Only customers who say yes face further choices, and by then they are motivated.
Delivery channels worth offering
Customers who linger may be happy to scan a code on the screen. Customers in a hurry want a message or email. Some will not leave contact details at all. List two or three channels at the counter, limited to the ones your system supports reliably, and ask your accountant which channels count as valid proof that the invoice reached the customer.
Three common situations and how to handle them
The customer asks at the moment of payment
This is the easy case because the order is still on screen. Run moves four and five. The main risk is a mistyped email or phone number, so read-back confirmation should be mandatory.
The customer declines
Most customers just want their drink. The cashier should not push or ask twice. What matters is that the sale is still recorded correctly, in the way agreed with your accountant, so that end-of-day totals reconcile under the rules that apply to you. How such sales are treated for invoicing purposes depends on the current regulations and your business type, so ask rather than assume.
The customer comes back later
People remember they need an invoice after they leave, particularly business travelers and anyone claiming an expense. Decide in advance how long after the sale you will accept requests, what proof you need (a receipt, a payment confirmation, an approximate time), and who approves. The limits depend on current rules about when invoices must be created, so get them from your accountant and write one short internal policy. Otherwise every shift will improvise differently.
A worked example: reconciling one shift
The figures below are assumptions for illustrating the arithmetic, not real sales data or market benchmarks. Replace them with your own numbers.
Suppose the afternoon shift at a cafe near a business park handled 84 paid orders. At closing, the shift lead builds this table.
| Category | Orders | Note |
|---|---|---|
| Total paid orders in the system | 84 | From the shift report |
| Customer declined an invoice | 61 | Handled per the agreed rule |
| Invoice requested and issued | 18 | Status: issued |
| Invoice requested but failed or pending | 3 | Must be resolved before closing |
| Voided or refunded order | 2 | Reason recorded |
Check the arithmetic: 61 + 18 + 3 + 2 = 84, which matches the total. If it did not, you would look for a missing order before closing, usually a merged or split table that was never recorded, or a test order that leaked into revenue.
Next, the request rate: (18 + 3) / 84 = 25 percent. That figure is only a reference for your own cafe. If it spikes in one time window, for example the hour after office lunch, consider adding a second register or a second cashier for that window. The three unresolved invoices are handled by the shift lead, who checks the status, resends, or contacts the customer using the details collected.
The principle behind the example is that every order has a "home". No order is left in limbo when the shift ends, which is the simplest way to keep the day's data clean.
Mistakes at the counter and what to do about them
No counter issues invoices flawlessly every time. What matters is knowing what type of mistake occurred, who decides how to fix it, and where it is logged. The specific correction method (cancel, replace, adjust) depends on current rules, so have your accountant confirm it before it goes into the routine.
| Mistake | Usual cause | Direction (confirm with your accountant) |
|---|---|---|
| Wrong email or phone number | Misheard, typed too fast | Resend to the correct channel and note it on the order |
| Wrong tax code or company name | Customer misread it, handwritten copy | Ask the customer to confirm and follow the procedure for incorrect buyer details |
| Wrong item or quantity | Order changed after issuing | Escalate to the shift lead and follow the agreed adjustment procedure |
| Same order invoiced twice | Double press during a slow connection | Report it; never delete on your own |
| Returned item or refund | Wrong or unsatisfactory drink | Record the reason and handle the related invoice per procedure |
| Connection lost while issuing | Network failure | Use the fallback and process the backlog when service returns |
The golden rule for cashiers is simple: never edit or delete on your own. An issued invoice is a document, so every change needs approval and a trail. That protects the employee as much as the owner.
End-of-shift and end-of-day checks
The counter routine covers half the job. The other half is checking afterwards that the system, the cash drawer and the invoices agree.
- Compare the total orders on the sales report with the count in each status group, as in the example.
- Compare totals by payment method (cash, transfer, card, e-wallet) with what was actually received.
- List failed, pending or voided orders and assign an owner to each.
- Check orders with discounts, vouchers or promotions: does the invoice value equal what the customer really paid?
- Save the shift summary (a screenshot or exported file) so the accountant can reconcile at period end.
Multi-outlet owners should add a comparison between branches. A branch with an unusually high failure rate needs a closer look at training or equipment. If you are choosing or reviewing a till system, the page on the point of sale application shows the kind of functions a POS typically consolidates, which you can use as a yardstick.
Training cashiers with a script, not a manual
Cafe teams are often part-time and rotate quickly, and nobody reads a thick manual. Three lightweight tools work better.
- A one-page card next to the register with the standard question, the two branches, the details to collect and the shift lead's phone number.
- A ten-minute rehearsal in a new hire's first shift: one person plays a customer who wants an invoice, one plays a customer who declines, one plays a fast talker who spells an email wrongly.
- An exception log template with time, order number, problem, owner and outcome, so information does not live only in people's heads.
Name one person as the invoice process owner. When the rules or the software change, this person updates the card and briefs every shift. Without an owner, the routine will be out of date within a few months.
Common implementation mistakes
- Asking for too much information. Collect only what the invoice type needs.
- Letting each cashier decide how to correct an invoice. Mixed practices make period-end reconciliation painful.
- Copying another cafe's setup without checking. Business type, filing method and current rules can differ.
- No fallback for outages. Rush hour is when connections strain, and when the counter cannot stop.
- Forgetting evening staff and seasonal hires. Most errors come from newer or less supervised shifts.
- Skipping daily reconciliation. Errors that pile up until month end are hard to trace.
- Accepting late requests with no limit. Agree a rule with your accountant.
Frequently asked questions
Does a cafe have to ask every customer about an invoice?
Whether you must, and how a declined invoice is recorded, depends on the current rules for your business type. Operationally, one short question keeps staff consistent. Confirm the specifics with your accountant or the tax office that manages your cafe.
What if the customer will not give an email or phone number?
Do not press them. Ask your accountant which details your invoice type requires at minimum and which may be left blank under current rules, then put the answer on the counter card.
A customer has left and wants an invoice now. What should we do?
Follow the internal policy agreed with your accountant: the allowed time window, the proof needed and who approves. If you do not have a policy yet, this situation will repeat, so write one.
Can a cashier correct a wrong invoice alone?
No. Corrections need approval and a trail. The method (cancel, replace, adjust) follows current guidance that your accountant confirms.
What do we do if the internet drops at rush hour?
Have a fallback your accountant has approved, such as recording customer details to process once connectivity returns. The key point is that every interrupted order is listed and resolved before the shift closes.
Is this much process needed for a single small cafe?
Yes, at least three parts: a standard question, an exception owner and a closing check. You can simplify the rest according to volume, but do not drop those three.
Next steps
- Sit down with your accountant, confirm the invoice type your cafe uses and the current rules for retail customers, and write down each requirement.
- Draw the six-move counter routine, adjust it to your system and print it as a card.
- Run ten simulated orders, including a decline, a misspelled email and one failure, and watch how staff cope.
- Fix a shift report template and name the person who reconciles every day.
- Review the routine regularly, especially when your software or the rules change.
To repeat the caution: this article is general information about how to organize a process, not legal or tax advice. The numbers in the example are assumptions for illustration. Rules change, so verify them against current official documents or with a professional before you apply anything.



