What share of documents matches?

94-99% - measured on twelve closed periods in production, not promised. The reconciliation key is the digit groups of the document number; pairs are built strictly one-to-one with scoring, so one invoice can't close two of the accountant's lines.

A pair was found, but the amounts differ - what then?

The line is visible, but it has no reason class yet, and a person reviews it. This is the largest side of the discrepancy, so we say it plainly: we do not promise to "find every discrepancy". Reason classes exist for the unpaired sides - retail receipt, service instead of goods, credit note, document reached nobody.

Will the system close the month on its own?

No. Closing a period cannot be undone for reporting, so auto-close works only with explicit consent: the system brings the checklist to zero and asks.

How do you tell a shortage from a transfer between stores?

By the signs in the two stores. Minus in the kitchen and plus at the bar on the same item is a transfer, not two shortages. In the demo example there are 24 items with a discrepancy in each store, 16 of them with opposite signs. Pairs are offset as a batch - one document is assembled and sent with one confirmation.

Can the system correct a quantity or a price by itself?

No. The product does not rewrite quantity, multiplier or price: when in doubt, the operator gets a blocker, not a silent edit. A wrong price shows up in reports, a wrong quantity silently goes to the store - the cost of an error is asymmetric, so a person decides.

Does the system build the stock count sheet?

No. The back office does not return prepared items, so the sheet stays with Syrve. We accept the stock export and the count file - and build the review on them.

What about amount-based baskets - staff, household goods, deposit?

We don't break them down by content and don't count them as a discrepancy. Items consumed by amount deliberately collect different products at different prices: that is how they are recorded by design, not an error.

What about negative stock?

It is a signal, not a verdict on the store. It has a known artefact: an invoice that arrives later than its document date produces a minus that is not a store error. So a minus is reviewed together with the document dates for the period.

Product - Reconciliation and month close

Month-end close - a checklist, not a hunt

The month closes on time, and its figures match the accountant's. Discrepancies are worked through as documents arrive - by the first of the month you have a short list with names on it, not an evening of spreadsheets.

How it works

Match against the accountant's exportUnmatched lines by reasonPaired view of two storesAuto-close only with consent

Closing checklistAugust - 4 days to deadline

60%

3 of 5 conditions cleared

you can see exactly which one holds the period

Invoices processed310 of 310

Stock count uploaded31 August

Exceptions resolved30 of 30

Write-offs matched with Syrve4 items

Accountant discrepancies9 lines

Demo data. Your restaurant has the same set of conditions, with its own figures.

The sixth step of the control cycle - the one that sums it up

The full cycle on the home page

01auto

Collect

documents and Syrve data

02auto

Check

prices, units, duplicates

03auto

Detect

deviation from your norm

04auto

Explain

what changed and what it costs

05team

Act

the owner of the task decides

06team

five conditions, total, report

The month's result is built from decisions, not exports

Everything the team worked through during the month - disputed prices, removed duplicates, offset stores - adds up to one figure of protected margin. That is what the owner receives.

A closed month becomes the baseline for the next

Confirmed prices, accepted discrepancy reasons and supplier rules carry over into the new period. The cycle starts again, with fewer questions.

What changes for the finance director and the stock controller

The same work, but now it has a deadline, an owner and a number.

Before

Discrepancies are found on the first of the month, when the period is already closed

Only the accountant knows what is left to do

A shortage in the kitchen and a surplus at the bar are treated as two problems

Reconciliation with the accountant runs on two exports matched by hand

The owner's report is assembled in a spreadsheet - and goes stale at the first edit

After

Discrepancies arrive on the day of the document - while there is still time to fix them

The manager sees the open condition, with a name and an amount

A transfer between stores is called a transfer and closed as a batch

Reconciliation is line by line, the remainder is split into four reasons

The report builds itself once all five conditions are cleared

4 days

before the deadline, not after

closing runs all week, not on the last evening

9 lines

left to review

out of 310 documents this month - instead of a general "doesn't match"

3 140 €

of disputed amounts cleared

resolved discrepancies with the accountant and the stores

18 h

of manual reconciliation a month

no longer spent matching two exports

Demo data - the set of checks is the same, your figures will be your own.

The word "reconciliation" means two different things

They must not be mixed up: each has a different line, period and result.

Document reconciliationStock reconciliation

A line isan invoicean item in the store

What against whatour invoices against the accountant's exportbook stock against the physical count

Periodthe export monththe calendar month

Does it record decisionsyes - a verdict per lineno - it only shows

You can see who is holding the month - and what to bring them

Five conditions, each with its own state. The manager doesn't ask "how is the close going" - they see the open condition, the amount and the person responsible.

Auto-close - only with explicit consent

Closing a period cannot be undone for reporting, so we never do it silently. The system brings the checklist to zero and asks.

Invoices processed

All documents for the period are recognised, matched and posted. Open ones stay on the list.

cleared

310 of 310

Stock count uploaded

The count per store is in the system - without it there is nothing to compare book stock with.

cleared

31 August

Exceptions resolved

Purchasing and stock control exceptions are closed with a decision: disputed, accepted, corrected.

cleared

30 of 30

Write-offs matched with Syrve

Write-off records in our system match those posted in the back office.

borderline

4 items

Accountant discrepancies resolved

The reconciliation tail is closed: every line has a reason class or a verdict.

holds the period

9 lines

Stock count uploaded - the review is ready in a minute

Not "upload and look at the table". The system itself tells you what to recount, which invoices are missing and what to ask the accountant.

Count uploadreviewed in 48 s

Count accepted

2 stores, 486 items

31 August

Book stock reconciled

receipts, consumption and recipes for the period

done

Discrepancies found

30 items out of 486

1 240 €

Reasons suggested

78% of the amount explained without a write-off

3 actions

We accept the Syrve export and the count file. The stock count sheet stays with the back office - we don't build it.

Recount 4 items

store

The discrepancy exceeds the tolerance and is explained neither by a transfer nor by a recipe. Most often it is an error in the count itself - cheaper to check than to write off.

salmon, French fries, cheese, syrupSend for recount

4 invoices missing

purchasing

The shortfall matches deliveries that are not in the books: the emails arrived, the documents were not posted. Until they are, book stock is bound to be lower than the actual stock.

2 suppliers - 2 840 €Open documents

Request to the accountant

accountant

On nine lines the discrepancy comes from the back office, not the store: a credit note, a service instead of goods, a retail receipt. The request is drafted as text - it only needs sending.

email and export attachedSend request

For the stock controller: this is not a shortage, it is a transfer

Minus in the kitchen and plus at the bar on the same item. It used to be written off as two separate problems - and both were wrong.

Item pairs - kitchen and bar16 pairs to offset

ItemKitchenBarOffset

Bottled beer 0.33

received to kitchen, consumed from bar

Kitchen-48 pcsBar+48 pcsOffset48 pcs

Orange juice 1 l

the item name says bar

Kitchen-24 lBar+24 lOffset24 l

Lemon

shared purchase for two stores

Kitchen-6.2 kgBar+6.4 kgOffset6.2 kg

Vanilla syrup

received to kitchen, consumed from bar

Kitchen-9 pcsBar+9 pcsOffset9 pcs

Mineral water 0.25

the item name says bar

Kitchen-72 pcsBar+72 pcsOffset72 pcs

The batch is assembled in full and sent with one confirmation. Nothing reaches the back office silently.

Offset as a batch

Demo example

24items with a discrepancy in each of the two stores

16of them with opposite signs - a transfer, not a shortage

11 and 4items negative in one store with no line in the other

Why as a batch, not line by line

Sixteen pairs are sixteen transfers. One by one it is the same manual work, just in a different window.

First release. Offsetting pairs as a batch is available now. The other review actions - write off, recount, investigate - are in progress.

The month's figure matches the accountant's by 94-99%

Measured over twelve closed periods, not promised. The remainder is not dumped into "doesn't match": every line has a reason class, so settling it with the accountant takes minutes.

The key is the digit groups of the number

Pairs are built strictly one-to-one with scoring, so one invoice can't close two lines.

The tail is split into classes

Not a general "doesn't match" list, but four reasons, each with a clear next step.

The reason lives with the supplier

Document numbers never repeat, suppliers do all the time. So the rule is remembered per supplier.

Reconciliation with the accountant's export - August

310 documents, 97% matched

one-to-one pairs

Matched line by line302

Retail receipt - no invoice will come4

Service instead of goods2

Credit note1

Document reached nobody1

The reason is remembered per supplier, not per document. The tail holds 52 lines over four months and not a single repeated number: suppliers repeat, documents never do.

Reconciliation with the accountant, no integration

The accountant sends an export of their postings - we match it against the invoices in the system by supplier, number and amount, one to one. There is no need to connect the accounting software or negotiate with its vendor.

What we accept

xlsxcsvJumis PDF registerany period length

Any period length. We don't ask you to change the export format - we take the one the accountant already produces.

We have it, the accountant doesn't

5 lines

The document is posted in the system but did not make it into the postings. Until the accountant has it, the month's costs are understated.

The accountant has it, we don't

4 lines

The invoice never reached us - the intake channel missed it. So it was not part of the price checks either.

Pair found, amounts differ

no reason class

The largest side of the discrepancy, and it has no reason class yet: the line is visible in the reconciliation and a person reviews it. We do not promise to "find every discrepancy".

There is no automatic export to Jumis, 1C or DATEV yet - reconciliation doesn't need it.