A panel on every screen
1,145 screens explain what they solve and in what order they are used, from inside the screen itself. There is nothing to go looking for.
1,145 screens with their own help panel and 1,416 fields with an explanation right beside them. It is not a manual nobody opens: it is the text that appears exactly where the doubt appears.
What it solves
The real cost of a business system is not the licence: it is the time people take to learn how to use it. When the help is a three-hundred-page PDF, nobody opens it; they ask a colleague, fill the field by eye and the data goes in wrong. And that bad data later shows up in a report someone uses to make a decision.
What is included
1,145 screens explain what they solve and in what order they are used, from inside the screen itself. There is nothing to go looking for.
1,416 fields with what goes there and a real example. That is what prevents the guessed-at value, which is the one that later throws a report off.
The help says what it costs you in money, in time or in access — never how the software works inside. That is what makes it useful.
The traps that show no symptom are flagged: what changes more than it looks, what cannot be undone, what is calculated differently from what you assume.
The tax, the receipt, the authority and the date format in the example are the ones where you operate, not those of another market.
A new screen without its help turns the test suite red the same day. Nothing ships half-done.
How it works
The help panel is there, in the same place, every time.
Its explanation and example appear right beside it, without leaving the screen.
No manual, no course and no calling anyone.
In detail
And the second one shows no symptom: unwired, the panel simply does not render and nothing reports an error. That is why a test checks it, instead of trusting that someone will look.
"October maintenance, contract 42" teaches more than "description of the debt". That is why every field carries a written example, not a repeated label.
What cannot be undone, what changes more than it looks, and which decision drags the next ones with it. That is what a generic manual never tells you.
Help that describes the interface does not help: the user is already looking at it. The useful kind says what a mistake there will cost them.
ITBIS or VAT, DGII or SENIAT, NCF or e-invoice: the text is written once and reads correctly in each country.
Every doubt settled on the screen is a call that never happens. Across more than a thousand screens, that is the difference between using the system and fighting it.
Who it is for
And training each new person takes weeks.
That a good explanation would settle on its own.
Because nobody ever worked out what they were for.
Common questions
No. It is in the platform, across every module, at no extra cost.
No, and that is the whole difference: it is a panel inside each screen and an explanation next to each field, right where the doubt appears.
It is written in Spanish inside the platform, and it uses the terms of your country: your tax, your receipt and your authority.
All 34. And a new screen without its help turns the test suite red, so it never falls behind.
That is its best use: every screen explains what it solves and in what order it is used, so people learn while working.
The help is meant to be read on screen, where the doubt appears. For the structure of the data there is the Data Dictionary, which can be exported.
And also
We will show you Help System running on a case much like yours, with no obligation.