SShortSingh.
Back to feed

Restaurant bookkeeping as double-entry data: prime cost, tip liabilities and delivery gross-up

0
·1 views

The article treats a restaurant's books as structured data, identifying a few rules that carry most of the accounting logic. Prime cost is defined as food cost plus beverage cost plus all labor, divided by sales. Card tips and sales tax are recorded as liabilities that should trend back toward zero once paid out, and delivery app payouts are net figures that must be grossed up into sales and expense lines. The author, who builds the ZeraBooks AI-native general ledger, supplies Python examples using Decimal arithmetic, a balance check on each entry, and a sample card deposit that splits revenue, sales tax and tips. The piece argues that persistent residuals in tip or tax liability accounts signal data errors worth catching early, and that a ledger's handling of restaurant books is a useful test of its data model.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Cloudflare's Clairic Model Returns Null Values Rather Than Guesses, Developer Warns

A developer's hands-on review of Cloudflare's Clairic, a preview extraction model on Workers AI released October 19, found that it correctly returns null when an input lacks a requested field. However, its response also includes a 'guess' key that can contain a plausible but wrong value, such as an invoice number placed in a purchase order field. Clairic is described as a single-pass model that produces field values without generating text and costs $0.10 per million input tokens. The author notes that Cloudflare has not documented what the confidence score means when the value is null, and that the weights are not yet public and the model is offered 'AS IS'. The article recommends gating each scalar field with thresholds on null probability and confidence before using the output in data pipelines.

0
ProgrammingDEV Community ·

Domain loss after a registrar account freeze exposes the limits of digital asset ownership

A widely discussed post reported that a registrar disabled every domain under one account even though invoices were paid, showing how quickly access can be removed. The commentary argues that customers typically hold a revocable license and login access rather than true title to domains, app listings, payment accounts, and cloud projects. Unilateral abuse flags, trademark complaints, or fraud heuristics can freeze assets with little notice, leaving the burden of proof on the account holder. Because registrar, DNS, email, and hosting often sit in one account, a single action can cascade into loss of identity and recovery channels. The piece recommends keeping exportable backups, separate credentials, and independent DNS providers so control can be relocated without the cooperation of the party that might freeze access.

0
ProgrammingHacker News ·

French Supermarket Fridges Left Exposed Online for Months, Report Finds

A security analysis published on the ipinfo.io blog reports that refrigerators used in French supermarkets were accessible over the internet for an extended period. The vulnerability reportedly persisted for months before being identified. The write-up is discussed on Hacker News, where it has drawn a modest amount of attention. The original article text was not included in the source material, so the specific technical details, affected vendors, and remediation steps cannot be confirmed here. Readers are directed to the original blog post for full findings.

0
ProgrammingDEV Community ·

Why AI transcripts need an acceptance pipeline before anyone relies on them

A guide argues that automatic speech recognition can look convincing in demos while still failing in production on overlapping speech, noise, domain terms, names, and numbers. It recommends asking what evidence a transcript must provide before people or systems depend on it, rather than asking how accurate a model is in general. The author frames local processing versus managed APIs as a choice driven by the actual data flow, security posture, and operational capacity, not a generic privacy-versus-convenience trade-off. A comparison table lists the evidence each option requires, including data-flow diagrams, runbooks, regression suites, and deletion proof. The core principle is keeping audio, transcript, speaker structure, uncertainty, corrections, and downstream actions linked in one traceable record.