I like how WithLess is built around European small‑business finance workflows, which fits our small food‑and‑beverages team's reality without forcing us into bulky enterprise‑grade finance tools. We don’t have a dedicated finance specialist on staff at Stuttgart Gastro Handel UG, so being able to handle our catering reconciliation work all by myself matters a lot in day‑to‑day operations. The tagging and grouping capabilities stand out most for me. After I export sanitized CSV transaction files from payever and upload them, I can tag every entry to separate regular shop walk‑in sales, small private bookings and large corporate catering events. Last month we were swamped, handling five separate catering gigs within one single week. One of them was a big wedding booking for 110 guests, with three separate payments: initial deposit, mid‑event partial transfer and final settlement. All three transactions appeared as disconnected lines inside payever. Using WithLess tagging, I bundled all three payments under that wedding event name. I could immediately check total invoiced value against total money we actually got, no messy manual spreadsheet summing required. I didn’t need to click through dozens of transaction records one‑by‑one. I also appreciate the simple high‑level finance dashboard. Every time I finish uploading monthly data, I open it and can quickly spot fully‑closed catering jobs, clients still holding outstanding balances, and compare how much money we earned from shop sales versus event business. Before I started using WithLess, I had to jump back and forth between payever raw exports and multiple spreadsheet tabs just to get that basic overview. This feature really keeps high‑priority unpaid cases from slipping through the cracks amid our busy catering season. Even with its obvious flaws around manual file imports, this practical grouping and overview functionality is what makes WithLess genuinely valuable for our German F&B operation. Review collected by and hosted on G2.com.
First of all, there is zero native integration with our core payment platform payever, so every batch of transaction data has to be exported manually as a CSV, cleaned to strip customer private information for GDPR, and then uploaded into WithLess. This whole manual import workflow brings real human‑error risks that we have experienced firsthand. Not long ago, I was processing finance records for a big company catering order for 90 guests. I accidentally selected a partial CSV export file that omitted two late client instalments. The incomplete dataset loaded into WithLess, and our part‑time finance assistant was about to use those numbers for our monthly revenue check before I caught those missing payment entries. That close call really showed me how risky this lack of direct system sync can be. Also, WithLess lacks pre‑built templates for catering and food‑service businesses. There are no ready‑to‑go tag sets for deposits, partial event payments or final settlement transactions, so I have to build every tagging structure completely from scratch. There is no rule‑based auto‑tagging feature either. During our busiest months with many parallel bookings, I must apply tags line‑by‑line. I once mis‑tagged a large wedding deposit as regular shop income, which distorted our project‑level revenue figures until I fixed it. Setting up WithLess to properly fit our catering business took far more effort than I expected. The onboarding material offered zero practical guidance on GDPR requirements for German hospitality companies, so I had to research data‑protection rules independently and write internal team usage rules on my own. All these shortcomings add substantial repetitive administrative overhead that could easily be reduced with better out‑of‑box tool design. Review collected by and hosted on G2.com.