La Table Management

The business and the pain

A restaurant group’s head office settles accounts with three worlds at once: suppliers paying commission on the purchases of some 20 franchisees, meal-card and delivery platforms (Cibus, Tenbis, Wolt and others) sending commission invoices by email, and the franchisees’ own bookkeeping reports. Each party sends a differently-shaped file, and each calls the same branch by a different name. Until the system, all of it was closed in Excel: a full quarter of ant work, where every mistake multiplies across dozens of branches and lands on an invoice.

What the system does

Runs the entire settlement cycle end to end. Report requests go out automatically to suppliers and franchisees, each with a secure upload link and reminders for whoever is late. Every file is parsed by its own mapping, names are resolved by a Hebrew matching engine, and supplier reports are cross-checked against franchisee bookkeeping: small gaps close automatically, the rest enters a review queue with a documented reason. Commission invoices from the meal-card platforms flow in straight from inbound email into the same pipeline. And at the end of each cycle, the system produces the invoice reports, grouped by the collecting management company.

The details that prove deep specification

• Franchisee reporting is read from the Israeli Tax Authority uniform file, the one they already produce for bookkeeping. Nobody is asked to do new work.
• Report requests go out on the first business day of the month by the Hebrew calendar. There is no point chasing a supplier on Rosh Hashana.
• Every supplier has its own parser (41 of them), each encoding a trap discovered in a real file: commission already baked in that must not be multiplied again, negative credit lines, one supplier shipping two files for two brands.
• Only a 100% name match is accepted automatically. Everything else gets a human eye. Trust is earned slowly.