Restaurants

Part of today's sales will arrive next week, minus a commission nobody checked.

A Pantera digital worker reconciles every location every day — the card terminal, the cash, the delivery payouts and what the ERP recorded — and escalates only the differences that are real.

Written for CFOs, controllers and administrative managers at multi-location restaurant groups in Colombia and Mexico.

Why this breaks

A restaurant does not have one cash register. It has four channels.

Dining room, takeaway, delivery apps and corporate accounts all end up as one line in the books, but each arrives at a different moment, through a different intermediary, with a different deduction taken out of it.

Delivery pays you net, and days later

The platform keeps its commission, bundles several days of orders into one transfer and sends it when its own cycle closes. Matching that single deposit back to the orders it covers is a job nobody has time for every week.

Suppliers invoice faster than anyone can check

Perishables arrive several times a week at every location, at prices that move. By the time an overcharge is noticed, the product has been served and the invoice has been paid.

Cash still has to be proven

What a location closed with, what it deposited and what the bank credited are three different numbers that only agree if somebody checks them that same week.

By the time it surfaces, the month is closed

A difference found three weeks later is no longer an operational problem. It is an accounting adjustment, and nobody remembers what happened on that shift.

What it runs

Four processes, running in every location at once

The work does not get harder as you open locations. It gets longer, and it falls on the same two people. That is the part a digital worker takes.

Daily reconciliation, location by location

The digital worker pulls each account's movements, matches them against what the ERP recorded for that location, and leaves a short list of real differences with the evidence attached — the morning after, not the month after.

Delivery payouts against the orders behind them

Each platform's settlement report is read the same way a bank statement is read: the payout is broken back down into the orders, the commission and the adjustments it contains, and anything that does not reconcile is escalated with the evidence attached.

Supplier invoices, at kitchen frequency

Every invoice is checked against its order before it is posted: amounts, line items, tax details, duplicates. A price that moved or a quantity that does not match the delivery note reaches a person; the rest does not.

Electronic invoicing compliance

Supplier documents are validated against the tax authority before they enter the books — CFDI against the SAT in Mexico, electronic invoices under DIAN rules in Colombia — so a bad document does not surface during the close.

Every location stays visible on its own

Differences are reported per location, not as one consolidated number, so a kitchen that is drifting shows up as itself rather than disappearing into the group total.

On your own systems

Nothing migrates and nothing gets replaced

Restaurant groups in Colombia and Mexico run on Siesa, SAP Business One, Siigo, Contpaqi and Aspel. The digital worker works inside the system you already have, the way your team already works.

Your rules, not ours

The matching criteria are the ones your controller already applies by hand. You show them once and the digital worker runs them from then on, the same way every day.

Everything it does is evidence

Every action, every rule applied and every approval is recorded with its audit trail, so a difference can be explained months later without reconstructing it from memory.

Next step

Bring one location and we will show you it running

Thirty minutes, on an ERP like yours. Pick the location that takes your team the longest to reconcile and we will show you what it looks like when a digital worker owns it.