Data safety and quality

Data you can trustMistakes stopped at entry, access only for those entitled, history kept, other people's work never overwritten.

A report is only as good as the data behind it. HQSFlow checks data in the browser and again on the server, enforces uniqueness, won't let records in use be deleted and protects against overwritten changes. Only signed-in operators get to the data, and the server checks every operation against their permissions — and records who changed what.

Two-level validationServer-side permissionsAccount lockoutChange historyDuplicate blockingArchivingAutomated tests

How HQSFlow looks after your data

Check digits wherever they exist

NIP, REGON, PESEL, NRB/IBAN account numbers, EAN-13, EAN-8 and UPC-A codes. A wrong digit is caught on save, with a message next to the field concerned.

Rules that make business sense

VAT deregistration no earlier than registration, a maximum payment term no shorter than the regular one, gross weight no less than net, non-overlapping limit periods, a country that matches the customer type.

No duplicates

Customer and item codes are unique. Tax IDs are checked against archived records too, with a block or a warning — depending on the setting. An own barcode cannot repeat anywhere in the database.

The server checks permissions, not just the screen

A hidden button is a convenience, not security. Every operation — reading a list, saving a record, deleting an attachment — is checked on the server against the operator's permissions and company access, wherever the request came from.

Accounts under control

A password policy, a forced password change at first sign-in, lockout after failed attempts. Blocking an account takes effect at once, open sessions included, and the administrator sees active sessions and can end them.

Employees' personal data for authorised users only

An employee's PESEL number and bank account are visible only to those with a separate permission — in the change history too, where these values are masked.

You know who changed what

Record change history with operator, date and values before and after — switched on for selected record types, with a retention period. The sign-in log records successful and failed attempts. On top of that, customer addresses are versioned with validity dates and consents carry grant and withdrawal dates.

Simultaneous editing without losses

If someone saved the same record a moment earlier, HQSFlow won't overwrite their changes — it shows a message and asks you to refresh.

A delete you won't regret

A record in use goes to the archive instead of disappearing. Archived records are hidden from lists, but one switch away and restorable.

Screenshots from the working system

Validation and access control in screenshots

A new customer with an invalid tax ID and REGON — fields highlighted in red with an error description and a message that the form contains errors
An invalid NIP and REGON check digit — the save is stopped, an explanation sits next to each field, and the tab with the error is marked with a dot.
An operator's effective-permissions table — the source of each right (role or exception) and whether it applies
An operator's effective permissions with the source of each right — role, exception, substitution.
An operator's active sessions with Sign out buttons and the sign-in log with successful and failed attempts
Active sessions with remote sign-out, and the sign-in log.
A customer's change history — who changed which fields and when, with values before and after
Record change history — who, when, what before and after.
The question shown when the main address changes — a new address version or a correction of the current one
An address change doesn't overwrite history — unless you deliberately fix a typo.
A customer's credit limits by period, with a limit that is no longer valid greyed out
Limit periods in the same currency cannot overlap.
The customer list showing an archived customer labelled Archived
A customer used as an item's manufacturer was archived instead of deleted.
Settings — blocking customers whose tax ID already exists, attachment limits and the sign-in log retention period
Duplicate tax ID blocking, attachment limits and sign-in log retention — the administrator's decision.

Click a screenshot to see it at full resolution. All data in the screenshots is fictional. The application interface is in Polish.

Validation in two places

Every rule is checked in the browser — so users see straight away what to fix — and again on the server, before anything reaches the database. That way data correctness can’t be bypassed, even when data arrives by some route other than the application screen.

Access only for those who need it

Operators sign in to HQSFlow with a password or a Windows domain account. Every request to the server is checked: is the operator signed in, do they have access to the given company, and do they have the permission for this particular operation. Permissions come from roles and exceptions set on the operator; a change takes effect without signing in again. View as operator mode, which the administrator uses to check what a person sees, is locked to read-only on the server side. More: Companies, operators and permissions.

A trail in the system

  • Record change history — who, when, which fields, values before and after; switched on per record type, with a retention period.
  • Sign-in log — successful and failed sign-ins with the reason for refusal, IP address and browser; older entries are removed after a period set by the administrator.
  • Audit on the record — date and author of creation and of the last change.

Quality built into the process

  • Automated tests — server-side business rules and the application screens are covered by automated tests.
  • Versioned database migrations — every change to the structure is recorded and repeatable; updating the database is not a manual operation.
  • Code in Git — every change has an author, a description and a history.
  • Event log — errors are recorded on the server with full details, while users see a clear message.

Attachments in the backup

Files attached to records are stored in the database, so a database backup covers them as well. The administrator sets the maximum file size and blocks dangerous extensions (e.g. .exe, .bat, .js).

Let's talk about your company

Tell us how many companies, customers and items you have and what you use today. We will show HQSFlow on examples close to yours and tell you honestly what it already handles — and what it doesn't yet.

Book a demo

We answer every request personally, usually within one working day.

Please enter your name.
Please enter a valid e-mail address.
Please check the phone number or leave the field empty.
Please tell us briefly what the demo should cover.
How we handle your data

The controller of your data is HQS Systems. We use what you send here only to answer your request and to carry on the resulting conversation, and we keep it no longer than that requires. You can ask us at any time to show, correct or delete your data by writing to office@hqs.cloud.