ERP and Power BI consultant, Lithuania

Two systems show two numbers. Both are wrong.

I find out why the numbers disagree, then build a report that holds up when someone checks it. Dynamics 365 F&O, production management systems, Microsoft Fabric, Power BI.

Tell me what you are trying to find out → What I actually do

ExampleQuestion: how much did we sell in August?

ERP, finance

318 400 €

Too low

Misses the invoices still sitting in the production system. They reach the accounts next month.

Production system

329 750 €

Too high

Credit notes counted as a plus, and one customer sitting there twice under two codes.

After reconciliation

324 180 €

The real one

Both systems joined on a shared key, credit notes subtracted, duplicates merged. Every line traces back to a document.

The gap between the first two is 11 350 €. One of them goes into the board slides year after year, until someone asks where the number came from.

Four jobs I take on

Reports you can trust

A Power BI or Fabric report built straight on your ERP data, with a written definition of exactly what each number means. So nobody has to guess six months later.

report and definitions

Reconciling data across systems

For when the same customer, invoice or order lives in two systems. I find the key that joins them, catch the duplicates and write down which system owns which fact.

map of sources

An AI assistant that knows your ERP

Not a generic chatbot. An agent loaded with your schema, what the fields mean and your business rules: you ask in plain language and get the answer together with the query, so you can check it.

agent and queries

A diagnostic before the project

One week. I go through what you already have and tell you what is worth doing and what is not. Fixed price, told in the first call. The write-up is yours, even if we go no further together.

1 week, fixed price

From the first call to something that works, no slide deck stage

I work alone. The person you talk to in the first call is the person who does the work. No sales people, no handover to somebody else.

The call

45 minutes, free. What you are trying to find out, and why the answer you get today does not do the job.

Access to the data

Read only. I change nothing in your system and install nothing in it.

A prototype, not a presentation

A working report on your real data. We agree the deadline after the call. That is where it becomes clear whether this is worth continuing.

Handover

The code, the definitions and the documentation stay with you. Nothing ties you to me.

Get in touch if

you have an ERP and data, but you do not trust it

you asked three people the same question and got three answers

an ERP migration is under way and you need to know what is really in the data

somebody rebuilds the same report by hand in Excel every month

Do not get in touch if

you need an ERP implemented from scratch: that takes a team, not one person

you need a website, an online shop or a mobile app

you need on-call support, I work project by project

the decision is already made and you only need hands to carry it out

Tadas Stačiokas

ERP and data consultant, Kaunas

LinkedIn · info@ttech.lt

More than ten years in IT and ERP with manufacturers, trade companies and online shops, from consultant to head of an IT team. In practice that means migrations between systems, reports that have to agree with the accounts, integrations between applications, and lately AI agents loaded with a company's data schema, so that the answer to a business question can be checked.

One rule: if a report cannot work something out, it has to say so, instead of showing a tidy number.

Receivables reportA Power BI report on customer debt that matches the ERP auditor report line for line. Until then three people had three versions and argued every month about which one was right.
Two systemsSales sat in the production system and in the accounts at the same time, and the numbers differed. Joined on a shared key, credit notes subtracted, duplicates merged. One number left, plus a list of which system answers for which fact.
Agent on the ERPA question about ERP data used to mean waiting until somebody had time to write a query. Now the team asks in plain language and gets the answer together with the query, which anyone can check.

Tell me what you are trying to find out

No technical brief needed. A question that nobody answers the same way twice is enough.

First call 45 min, free

Diagnostic 1 week, fixed price

Email info@ttech.lt

LinkedIn LinkedIn profile