What RestoAudit.ai works with: Syrve, PEPPOL, ZUGFeRD, email, Telegram
An integration is the matching, not the PDF reading.
You change neither your back office nor your suppliers’ habits: we fit into what is already there. «Chicken fillet chld.» at the supplier and «Chicken fillet chilled, kg» at your place are one product, and a case of 12 has to become kilograms in the warehouse. That work is the integration.
Three exits from one stream
Once the document is parsed and checked, it goes wherever it suits you to receive it. The paths are equal and work at the same time.
Straight into Syrve
A posted invoice in your back office: incoming, return or credit note, each in its own document type. Nothing is posted without your confirmation.
As a file to the bookkeeper
Reconciliation runs on their export in xlsx, csv or PDF. There is no accounting software to connect and no vendor to negotiate with.
Through the API
An accounting system or an integrator pulls invoices ready to post itself, by key. The data is already matched and verified.
What connects to what
- POS and back office
- Syrve - reads the item list, recipes, warehouses and sales; writes incoming invoices, returns and credit notes
- Platform
- RestoAudit.ai is an app in the NEXX App Market; supplier exchange and EDI live at platform level
- Intake channels
- Email (forwarding; Email Agent on your mailbox - soon), Telegram, manual upload
- Document formats
- PDF, photos and scans, XML, PEPPOL BIS Billing 3.0, ZUGFeRD
- Document languages
- LV, DE, EN, RU and 46 more - the language is detected automatically
- Reconciliation
- Your bookkeeper’s export in xlsx, csv or PDF - no integration needed
- Partner API
- Read-only REST: invoices, suppliers, warehouses, categories and VAT rates, by key
- Not available today
- Automatic export into Jumis, 1C and DATEV
- Time to connect
- Email forwarding - the same day; matching your item list - the first week
How to automate invoice entry into Syrve
Syrve - a two-way exchange
WorksWe read your reference data before parsing a document and return the finished invoice after your confirmation. A supplier line is tied to your product, and the decision is remembered for that supplier and article - the next document like it goes through without asking.
- The item list and units of measure
- Recipes - the version valid on the date
- Warehouses and their structure
- Sales for the period
- The incoming invoice
- Return and credit note - each in its own type
- A new supplier and a new product - on confirmation
- Nothing is posted without your consent
PEPPOL, ZUGFeRD and XML: receiving incoming invoices
Incoming documents from suppliers
WorksThis is about incoming invoices from your suppliers, not about issuing invoices to guests. XML is parsed line by line: items, units, prices, VAT rates and discounts enter the books without typing, and a mismatch in the document total shows before posting.
- PEPPOL BIS Billing 3.0
- ZUGFeRD - PDF with embedded XML
- A supplier’s own XML
- PDF, photos and scans - through recognition
- We do not issue your outgoing invoices
- We do not replace your POS
- We do not connect EDI operators (Telema, Edisoft) - that is NEXX’s domain
Reconciliation without an integration
Your bookkeeper’s export is enough
WorksYour bookkeeper sends an export of their entries in xlsx, csv or PDF - we match it against the invoices in the system by supplier, number and amount, one to one. There is no accounting software to connect and no vendor to negotiate with.
The document is posted in the system but never reached their entries.
The invoice never got to us - an intake channel missed it.
Number and supplier match, the sum does not: price, discount or VAT.
Exchange API: pull the data programmatically
RestoAudit Partner API v1
WorksA read-only REST API for accounting systems and integrators: the partner pulls verified invoices ready to post itself, together with your back office structure - warehouses, categories and VAT rates. Only documents that passed the readiness gate are served; drafts and unapproved documents are never exposed.
- The key travels in the Authorization: Bearer header
- One key - one restaurant
- Keys are stored hashed and can be revoked
- A disabled partner stops receiving data immediately
- The accounting system pulls invoices without files or email
- The data is already matched to your item list and verified
- Read-only: your documents cannot be changed through the API
RestoAudit.ai lives in the NEXX App Market
RestoAudit.ai is an app in the NEXX App Market: the product is built on top of the platform, and part of the exchange lives at platform level. Supplier connectivity, EDI and orders belong to NEXX; an invoice received there comes back into RestoAudit through the usual stream and is parsed like any other.
- RestoAudit.ai is an app in the NEXX App Market
- Supplier connectivity, EDI and electronic exchange - at platform level
- Orders to suppliers - from the same place the conversation happens
- The document returns to RestoAudit and is parsed as usual
A separate partner product - opens on nexx.business
What is not available today
Automatic export into accounting systems
In progressFinished documents do not yet flow into Jumis, 1C and DATEV on their own. We are building the export at NEXX platform level, where it is currently in pilots; we will build it inside RestoAudit separately if that suits customers better. Today the data is pulled through the partner API or exchanged as a file.
Write to us. If the same need turns up at several restaurants, it goes into the shared plan and comes with your subscription - there is nothing extra to pay. If the integration is yours alone and cannot be reused elsewhere, the work is quoted separately: the price depends on the setup and the complexity.