--- title: TSync EVA — the real value of your company, checked two ways description: A friendly guide to TSync EVA (Enterprise Value Analytics). It shows your company's real operational value verified by two independent methods, the impact of currency rates, a control sum, and where a likely error sits — all read-only. It never moves money or changes documents. product: TSync Intelligence 11.3.6 language: en canonical: https://docs.tsync.pro/modules/eva/ source: https://docs.tsync.pro/llms.txt --- # ⚖️ TSync EVA — Enterprise Value Analytics **The real value of your company, verified by two independent methods.** TSync EVA looks at everything your company owns and owes, works out what it is worth **two different ways**, and compares the two answers. If they match, your books are consistent. If they don't, the gap (the **control sum**) tells you something needs checking — and EVA points you at the likely place. EVA is **read-only**. It only looks, calculates and explains. It never makes a payment, changes a document, or touches your accounting. Open **TSync EVA → Dashboard** (`/admin/tsync_eva`). > **Don't see it in the menu?** TSync EVA appears in the sidebar once the **module is activated** in > **Setup → Modules** (activate *TSync EVA*). After that the menu is always visible — even before you turn the > feature on — so you can reach **EVA → Settings**. > > **First time?** Go to **TSync EVA → Settings** and switch it **on**. It starts in **shadow** mode (it computes > and shows everything, but stays quiet — it doesn't send signals to the rest of the system). Switch to **live** > when you want it to raise read-only signals. (Turning EVA off never hides the menu — it only pauses the > calculations.) You can also reach Settings from the **Configuration Center** (the *TSync EVA* card). > > **Settings says "schema incomplete"?** After an upgrade where only some files were uploaded, EVA's data > tables can be missing. **Settings** still opens and shows a **Repair schema** button — click it once and EVA > rebuilds its own tables (it never touches your other data). EVA also tries to repair itself automatically the > next time you open it, so this is just the manual backup. --- ## What's in the EVA menu Once the module is active, **TSync EVA** is a top-level sidebar group with these pages: | Page | What it's for | |------|---------------| | **Dashboard** | The two methods, the control sum, key figures, suspect zones and the components breakdown for the chosen period. | | **Control sum** | The saved history of control sums, with a **Detaliere** (drill-down) per row, and a button to compute one for a chosen period. | | **Snapshots** | The point-in-time pictures of your value (position and flow). View them, or capture one manually. | | **Days to recalculate** | The dates EVA marked as "needs a recalculation" after a change, plus the recalculation log. | | **Periods** | Verify and lock checked months; see the **drift** if a locked period later moves. | | **Settings** | Turn EVA on/off, choose shadow/live mode, set the alert thresholds, repair the schema. | --- ## The two methods and the control sum The dashboard shows three big cards: | Card | What it means | |------|---------------| | **Method 1 — Direct asset valuation** | What the company is worth **right now**: everything you own (stock, cash, bank, money in transit, receivables, fixed assets) **minus** what you owe (suppliers, credits, due obligations). | | **Method 2 — Flow reconstruction** | What the company **should** be worth: the value at the start of the period **plus** the result of the period (sales margin, expenses, salaries, FX differences, and so on). | | **Control sum** | **Method 1 − Method 2.** Near zero = the two views agree (good). A large number = a probable error worth investigating. | ### What the difference is measured against A raw control sum does not by itself say whether it is large or small — that depends on **what you compare it to**. EVA therefore computes **two percentages** and shows both: | Percentage | Divided by | The question it answers | |---|---|---| | **Against the position** | the closing position (Method 1) | "Are the two valuations of the **whole business** roughly consistent?" | | **Against the period** | the **period result** (Method 2 − opening balance) | "Does the reconstruction actually **explain** what moved during the period?" | The second is the one a control sum exists for. The first is always far more forgiving, because a balance sheet is usually many times larger than one month's result — the same difference can read as **0.04 %** against assets and **103 %** against the period. Both are arithmetically correct; only the second answers the question being asked. **The worse verdict wins.** If either percentage crosses its threshold, the card turns yellow or red — a check that reports the flattering number is not a check. The against-the-period percentage has its own thresholds: **10 % warning** and **25 % critical** (both adjustable in Settings). Two situations are handled explicitly: - **The opening balance cannot be established** → the second percentage is simply **absent**. An unanswerable question is left unanswered rather than guessed. - **Nothing moved in the period, yet the methods disagree** → the verdict is **critical** straight away, with no division by near-zero. When the data is incomplete the status stays **incomplete** whatever the percentages say — and the raw difference is still displayed. The number is never hidden. Each card has a short plain-language explanation, and a colour: - 🟢 **green** — the difference is insignificant; - 🟡 **yellow** — worth a check; - 🔴 **red** — a probable error; - ⚪ **grey** — **incomplete data**: EVA is missing something (a rate, or the opening value) and **will not invent a number**. Pick the **period** at the top — day, week, month, quarter, year, or a custom range — and click **Apply**. The dashboard always shows a **live** calculation for that period (nothing is saved just by looking). To save a control sum so it appears in the history and on the Periods page, use **Compute** (Dashboard or Control sum). Below the three cards the dashboard also shows quick figures — **money in transit**, the **FX impact** (whether all currencies could be converted), the **number of snapshots** captured, and how many **days are waiting to be recalculated** — followed by the components breakdown and an **evolution** table of recent periods. --- ## See where every number comes from — "Detaliere" Every row in the control-sum history (on the **Control sum** page) has a **Detaliere** (drill-down) button. It opens a full breakdown so you can verify the figure yourself — nothing is a black box: - **Each component** (stock, cash, bank, card, money in transit, receivables, payables, credits, fixed assets…) shows its **source**, the **original amount and currency**, the **exchange rate applied**, the **base-currency value**, and whether it was **included or excluded** from the total — and **why** (missing rate / incomplete data / no source). - An **FX split** shows the total that **was converted**, the components that **could not be converted**, and the exact **currencies whose rate is missing** — so a partial total is always explained, never hidden. - **Method 2's opening** is shown on the same page: its value, the date it was taken **as of**, which saved snapshot it came **from**, the period result, and whether the opening is complete. - If **Treasury isn't fully configured**, the page warns you that the cash/bank components may be incomplete. > EVA distinguishes a real **0** from **missing data** from a **not-tracked** component — a component with no > source on your install shows "—", never a misleading `0.00`. --- ## Why it sometimes says "incomplete" EVA never guesses. Method 2 needs a real **opening value** — a saved snapshot from the start of the period. On a brand-new install there is no history yet, so Method 2 shows *incomplete* until EVA has been capturing daily snapshots for a while (it does this automatically every day). The same happens when a currency has **no exchange rate** for a date: that amount is shown in its original currency and **left out of the converted total** — never converted at a fake 1:1. > 🔍 **"Zero" and "not measured" are not the same.** In the components breakdown each line is clearly labelled: > **measured** (a real figure, which may genuinely be `0.00`), **not tracked** (there is no source for it on your > install — shown as `—`, never as a fake `0`), or **missing** (a source exists but a rate or figure is unavailable). > So a real zero never hides a gap, and a gap never reads as zero. Method 2 also shows **where its opening came > from** (which saved snapshot, on which date) — it is always a real captured value, never silently recomputed. --- ## When something looks wrong — probable error zones When the control sum is large, EVA lists the **probable error zones** — stocks, payments, reconciliation, receivables, payables, currency rates, money in transit, obligations, and so on. Each zone explains *why* it is suspect and gives you a **drill-down** link straight to the data. EVA never declares the final cause; it points you where to look. --- ## Snapshots, days to recalculate and locking a period - **Snapshots** are point-in-time pictures of your value. EVA captures them automatically each day; you can also capture one yourself from **Snapshots** (a *position* picture, or a *flow* one for the month). - **Days to recalculate** — if you change something in the past (edit an old invoice, fix a rate), EVA marks that date as **needing a recalculation**, so you always know the picture has moved. Click **Recalculate** (for a date range, or all pending) to bring it up to date; you can also **mark a date** manually. The same page keeps a **recalculation log** of what was rebuilt and when. - **Periods** — once you've checked a month, you can **verify** and then **lock** it. A locked month is never changed silently: if the underlying data later moves, the Periods page shows the **drift** between the value you verified and the current value, and only an explicit **reopen** changes it. --- ## Settings — on/off, mode and alert thresholds On **TSync EVA → Settings** you control: - **Enabled** — the master on/off. Off pauses all calculations but keeps the menu. - **Mode** — **shadow** (computes and shows everything, but sends no signals to the rest of the system) or **live** (also raises read-only signals). - **Warning threshold (%)** and **Critical threshold (%)** — how big the control sum's difference must be (as a percentage) before a period turns 🟡 *yellow* (worth a check) or 🔴 *red* (probable error). Defaults are around **0.5%** (warning) and **2.0%** (critical); raise them if your books are noisier, lower them to be stricter. - **Repair schema** — rebuilds EVA's own data tables if an upgrade left them incomplete. Changing a setting needs the EVA *admin* permission; it is saved through the audited settings store. --- ## Export to Excel / Power BI EVA gives you clean CSV exports straight from the buttons on its pages — **Export** on the Dashboard (the EVA summary by period) and **Export** on the Control sum page (the control-sum history). The available datasets are the **EVA summary**, the **components breakdown**, the **FX impact**, the **control-sum history**, the **recalculation log** and the **snapshot lineage**. Every export keeps the **amount, the currency and the base-currency value in separate columns** (never glued together like "1000MDL"), so it drops straight into Excel or Power BI. --- ## What EVA will never do - It will **not** create, change or delete any invoice, payment, or accounting entry. - It will **not** make payments or post corrections. - It only **observes, calculates, explains and flags** — every correction stays in your hands.