Know what applies. Prove when it’s done.
Helimux evaluates versioned jurisdiction rules against each entity’s facts and turns the ones that apply into a single compliance calendar, with every obligation traced to its source.
From rule to evidence,
one explainable path.
Every obligation in Helimux can answer three questions: which rule created it, why that rule applies to this entity, and what proves it was met.
- 01
Entity facts
Jurisdiction, entity type, status, formation date and the other facts rules depend on.
- 02
Current rules
Versioned rules from the jurisdiction packs that cover your entity, each tied to its official source.
- 03
Applicability
Each rule’s conditions are checked against the facts. You can see why a rule applies, or why it doesn’t.
- 04
Obligations and deadlines
Applicable rules become obligations for a period, with a due date calculated from the rule’s deadline logic.
- 05
Work and review
Required inputs and documents, an assignee and a reviewer. Consequential steps wait for approval.
- 06
Submission and evidence
The submission is recorded with its external reference, and the evidence is attached before completion.
Enough context to answer
an auditor, or your future self.
Obligations carry their source and their history, so you never have to reconstruct why something was due or how it was handled.
Confirmation statement
What and why
When
Who
Proof
Example obligation shown for illustration.
A status that means something.
Across every entity at once.
Obligations move through explicit states. Some can also be overdue, blocked, deferred, not applicable or cancelled. One calendar shows them all, by day, week, month, quarter or year, and by entity, jurisdiction, obligation type or assignee.
- 01
Upcoming
- 02
Due
- 03
In progress
- 04
Awaiting review
- 05
Submitted
- 06
Verified
- 07
Completed
Completed is only reachable once the evidence is attached, so the last step on the rail always has proof behind it.
What Helimux
will not do.
Compliance mistakes are expensive, so these limits are part of the product, not settings.
No invented requirements
Helimux does not create filing requirements or deadlines that aren’t backed by a rule and its source.
Prepared is not filed
Helimux never records a document as filed when it has only prepared it.
Outdated rules are flagged
A rule under review or past its effective dates is shown as such, never presented as current.
Complete means evidenced
Opening a page or generating a draft doesn’t complete anything. Completion is an explicit step with evidence.
Compliance, answered.
How rules are sourced and versioned is covered in detail in our methodology.
- How does Helimux decide which obligations apply to my company?
- Each rule in a jurisdiction pack has explicit applicability conditions, such as entity type, status and formation date. Helimux evaluates those conditions against the facts recorded for your entity. The evaluation is deterministic: an AI model does not decide whether a rule applies.
- What happens when a rule changes?
- Rules are versioned with effective dates. A new version is added alongside the old one rather than overwriting it, so obligations already worked on keep the version they were based on, and upcoming obligations use the version in effect for their period.
- Does Helimux file for me?
- Helimux prepares the work and tracks it. Consequential actions such as filings wait for your explicit approval, and an obligation is marked complete only after its evidence, such as a filing receipt, is attached.
- Can I track companies in more than one country?
- Yes. Every entity in a workspace shares one compliance calendar, which you can view by entity, jurisdiction, obligation type, assignee or time period.
Helimux manages operations and workflows from source-backed rules. It is not a law firm, does not give legal advice and does not replace licensed legal counsel.
Run your company with clarity.
Bring your company information, obligations, documents, and workflows into one connected system.