The Consultant in Your Channel — Canias ERP

THE FLOW

Same job, two flows

In the flow on top, every gap between the boxes is a wait: the user explaining, the consultant getting to it, the trace being requested. In the lower flow those gaps are gone — but the release still passes through the consultant approval gate. The scale is illustrative.

IN PRACTICE

These are your own sentences

All of them exactly as users wrote them in Slack. The line underneath says what happened that same day.

“The withholding tax columns come up empty”

The definition said 03; it should have been O3. A three-year-old root cause, fixed in two companies at once.

“The system is calculating it wrong”

The calculation was right. The tax authority asked for a different scope; the report was filtered without touching the standard.

“I can't issue an invoice”

The posting key was undefined in the second ledger. Definition completed, closed the same day.

“I can't post a goods receipt”

The order validity date was blocking it. Data correction plus a permanent safeguard.

“Where does this line come from?”

Document found, the report's code opened, the condition read, the total verified — no guessing.

“I can't print the dispatch note”

The file name had become .xls.xlsx. Nobody told the user to “save it differently”; the code was fixed.

“A column is missing from the list”

Added to two views. No queue, same conversation.

“I keep getting a warning when posting”

Unnecessary warning switched off for 137 document types. Before and after reported with numbers.

WHAT YOU GAIN

Consulting spend goes down

The same work, the same consultant, in a fraction of the time. The information-gathering step that eats most of it disappears.

Your users aren't worn out

No screenshots, no trace requests, no mail threads. They write the problem in their own words and get the answer in their own words.

Root cause, not symptom

The error message isn't guessed at. The line of code that produced it is opened, the condition read, the result measured against the data.

Production stays safe

Development happens in an inherited object; the standard is untouched. Anything written to production is measured, backed up and approved first.

EVIDENCE

Three cases, in the open

0 linesOF CODE WRITTEN

A rejected dispatch note — the fault wasn't in the system

The customer had rejected the note and the response couldn't be taken in. Checked against live data: goods had left stock, no reversing entry. The trace showed the error was in the document itself — the counterparty had written the same goods as both accepted and rejected: accepted 2,700 + rejected 2,700 > shipped 2,700. Patches scanned, system current. Before sitting down to write code we asked Canias support; the answer: under the regulation this response is an invalid document, the correct path is a return dispatch note — which the customer had already issued. No code fix was needed.

3 yearsOF MANUAL WORK

Withholding tax was being split by hand

When VAT went from 18% to 20% the withholding keys became unusable; the company had last used the mechanism two days before the change, and for three years nobody asked why. The trace showed a single character: the definition held 03 where it should have been O3. The user's reply: “IT WORKS, THANK YOU”

SLACK CHANNEL · 26.08.2026

AC

Accounting09:12

The withholding tax columns come up empty, I can't issue the invoice.

CN

Consultant09:26

The trace says the VAT key can't be found. The definition has 03 (zero-three) where it should be O3 (letter O). Fixed it in both companies and added the missing accounting line. Could you try again?

AC

Accounting09:41

IT WORKS, THANK YOU

THE TRACE BEHIND THAT ANSWERE155

MESSAGE BAS E155 : "K.D.V. 01 T 03 1 not found!"
IASFINITEM_VATKEY[03]← zero. should be: O3

The definition field held 03; it should have been O3.
That is why the withholding key never worked — for three years.

7/1067FILTERED / KEPT

“The system is calculating it wrong” — no, a difference of scope

The unexplained -3.610.060,52 line in the tax authority's list was the reversing entry of the month-end VAT closing voucher. Canias was calculating correctly. The filter was built by reading Canias's own VAT definition rather than hard-coding an account number: in 2026, 7 documents are filtered out and 1,067 remain.

GUARANTEES

01Nothing reaches production without approval. A script is written, its effect is measured, approval is taken, then it runs.

02The standard is never broken. Development happens in an inherited object with your own prefix. Nothing is lost on a version upgrade.

03Every change is reported with numbers. Not “fixed” but “137 rows updated, before 0, after 1.” The way back is written down.

04AI makes mistakes; the consultant verifies. No finding is applied unverified. Accounting decisions are yours; technical responsibility is the consultant's.

CASE · 30.08.2026

A button on a screen, without ever connecting the IDE

The customer said “let's put a button on this account screen”. The classic path means IDE, VPN, licence and an available consultant. We did the same job end to end with web services — without connecting to the database even once.

EVERY STEP THROUGH THE CANIAS SERVICE LAYER · NO DIRECT DATABASE CONNECTION

~~ReadQuery~~is it locked?0 — clear ~~RunSql~~inherit the screenPRTFINT01F002 ← FINT01F002 ~~AddControl~~add the button659 378 168 22 ~~RunSql~~write the click codeevent=2 · 860 bytes ~~ConvertDialog~~compile32 inherited + 1 own ~~ActivateObject~~activatetest environment only

customer asks→inherit screen→add button→ write code→compile→activate→ working in test

Production did not change at the same time. Activation lives in the business database, so it is environment-scoped — what runs in test does not appear in production by itself.

BEFORE — FINT01F002 STANDARD · IAS

The screen as IAS wrote it. Never touched.

AFTER — PRTFINT01F002 INHERITED · PRT

121 inherited + 1 own. The orange frame marks the single control added to the inherited object: the button.

DEVELOPMENT VIEW · IN THE INHERITED OBJECT

The Bakiye Getir button inside PRTFINT01F002 in the TROIA IDE

The IDE was opened only to verify the result.

TEST ENVIRONMENT · RUNNING

The button running in the test environment

At the same moment this button did not exist in production.

Both drawings are wireframes, not screenshots — they are generated from the screen's own geometry (the labels are in Turkish because the system is). Because the standard object never changed, there is no customisation to be overwritten on a version upgrade. The service refuses to write to an object you don't own; that rule comes from Canias's own code.

Read the full case →

PRICING

First week free, monthly after that

All three plans are unlimited — no counter per question, per hour or per day. The only thing separating them is what the consultant is allowed to do in your system. Pay monthly or yearly; two months free on annual prepayment.

TRIAL First 7 days free Full access, no credit card. The trial runs on the Development plan — you see what comes out of it before committing.

FOUNDING CUSTOMER 12-month price lock for the first 10 You lock today's price for a year and are unaffected by interim increases. Once the places are gone, list price applies.

ANALYSIS

700 €/ mo

annual prepay 7,000 € — 2 months free

unlimited questions · analysis and resolution

Unlimited questions in the Slack channel, continuous follow-up
Trace analysis, 30 MB files included
Analysis over business data and TROIA source code
Root cause report — document, line, amount
Resolution of anything that doesn't need code — process, usage and definition issues
A written record of every piece of work

If the fix requires a code or data change, you move up to Development.

DEVELOPMENTRECOMMENDED

1.400 €/ mo

annual prepay 14,000 € — 2 months free

unlimited questions · analysis + development

Everything in Analysis, with the same no-limits terms
Development in inherited objects — under your own prefix
Report and list adaptations — statutory formats, e-documents
Definition and parameter corrections
Data correction scripts — backed up, measured, reversible

Every change that reaches production passes through consultant approval.

ENTERPRISE

2.800 €/ mo

annual prepay 28,000 € — 2 months free

unlimited questions · multi-company · process ownership

Everything in Development, with the same no-limits terms
More than one company and database
Priority response, out-of-hours support for critical work
Monthly written report — what changed, before, after
Quarterly review, a named consultant

For groups where the same fault repeats in every company.

The subscription covers ongoing work — questions, analysis, root cause, development and corrections within your existing setup. New module rollouts, data migrations and large projects are quoted separately. Prices exclude VAT. Cancel any month, no commitment. Canias 8.03 and 9.03 are supported. Setup takes half a day: a Slack channel, read access to the database and access to the trace folder is enough. Access can be restricted; write operations run through scripts, backed up and approved.

Book a call →

Goes to the Heartecon booking form — name, email and a time that suits you, nothing else.