What ReconDoc sees and does in your iiko

You're giving the service access to the restaurant's accounting system. It's worth knowing the exact boundaries of that access.

What the service reads#

• The catalog of products, dishes, and preparations, including containers.
• The supplier directory.
• The list of stores.
• Tax categories.
• Previously created incoming invoices — to find duplicates and show the last-delivery price.

All of this is only ever read and kept as a copy on our side, so products can be filled in without a round trip to your server on every click.

What the service creates#

Only incoming invoices. One button, one action, always on your command.

Every document it creates carries a comment, so BackOffice shows which invoices the service created and which a person did.

What the service never does#

If an item is missing from your catalog, you add it in iiko yourself — the service only reads it at the next sync.

The iiko password#

Stored encrypted and never shown anywhere: not in the interface, not in emails, not in logs. Even we can't read it.

ReconDoc support access#

Support access isn't turned on by itself — you grant it with a single button under Settings → Team members whenever you need our help, and revoke it the same way, with one button, at any time. See ReconDoc support access for details.

Auto-posting#

By default, invoices are created unposted — meaning they don't affect stock until a person posts them. You can turn on posting right away, but that's your explicit choice, not the default behavior.

Data retention and deletion#

While a restaurant is active, its data is kept and backed up daily.

If payment stops for a long time, a retention policy kicks in: first the iiko password gets erased, later the restaurant's data entirely. Every step comes with an email in advance.

Didn't find an answer?#

If you need formal documents, the privacy policy and the offer are published on the site. For anything else, contact support.