Accounting integrations

“Connect your accounting software to automatically sync paid orders and generate tax-compliant exports.” Done properly this is the single biggest time saving in the product for a restaurant that currently re-types its takings once a month.

Plans

Brasserie, Signature, Enterprise

Can it be switched off?

Yes — an owner or manager can turn it off under Setup → Features.

It lives under Setup

The screen is Setup → Accounting, not Money, even though the topic belongs here. You need tenant.billing.manage.

The six connectors

Connector	How it connects	Where
LexOffice	API key	Germany, Austria
DATEV	File export, no live connection	Germany
Xero	Sign in with Xero	Australia, New Zealand, UK, EU
MYOB	Sign in with MYOB	Australia
QuickBooks Online	Sign in with QuickBooks	—
Sage	Sign in with Sage	UK, EU

The sign-in connectors hand you to the provider’s own login and come back authorised; nobody types a password into RestroManage. LexOffice takes an API key you generate in LexOffice. DATEV is different in kind — it produces files for your tax adviser rather than posting into a cloud ledger.

Account mapping

A connector that posts into a ledger needs to know which accounts to post to. The mapping is split in two:

Revenue accounts, by tax treatment:

• 19% VAT and 7% VAT — Germany and Austria
• 0% / Exempt
• GST 10% and GST-free — Australia

Payment accounts, by how the money arrived: Cash, Card, Online and Tips.

Get the mapping from your accountant before you turn sync on. Everything posted against a wrong account has to be journalled out later, and the sync will happily keep doing it daily.

When it syncs

Three triggers:

Trigger	Behaviour
Manual	Only when you press sync
On payment	Each order posts as it is paid
Scheduled	Posted in batches

There is also a daily catch-up sync at 02:30 UTC, which picks up anything that failed or was missed. That is why an order that did not post at 9pm is usually there the next morning — check before you re-sync it by hand and create a duplicate.

The sync history lists each run as Success, Partial or Failed, with which trigger started it. Partial is the one to read: some orders posted and some did not, and the run tells you which.

Customer data and privacy

How much customer information leaves your system is your choice:

Option	What is sent
Anonymous	No customer identity
Include name & email	Full customer details
Pseudonymized	A hashed email, so the same customer is recognisable without being identified

Sending names is a disclosure

Choosing to include names and emails means “Customer names and emails will be sent to” your accounting provider, and your privacy policy has to say so. Pseudonymized usually gives the accounting side everything it needs — repeat-customer recognition — without the disclosure. Start there unless your accountant asks for real names.

If you change this setting, update your storefront privacy page too — see Legal pages.

DATEV and Lexware formats

DATEV exports in two formats:

• DATEV Buchungsstapel v700 (CP1252) — the standard posting batch for a German tax adviser
• Lexware Native CSV (büro easy) — for Lexware desktop

Pick the one your adviser asks for. They are not interchangeable, and the encoding matters: CP1252 is what DATEV expects, so do not re-save the file as UTF-8 in a spreadsheet before sending it.

Disconnecting

Disconnecting asks you to confirm, and tells you what it does not undo: “Your account data will remain in the accounting software.” Nothing already posted is withdrawn — disconnecting stops future syncs, it does not reverse past ones.