User guide

Contracts, real-estate brokerage and the data room form an interconnected workflow.

A contract records its owning client company, parties, type, term, currency and document text. A Hungarian title is mandatory.

Persons can be assigned to parties with roles. Marking a broker contact for the data room initiates access assignment.

Each property has a separate brokerage row with transaction types, commission, access period and shared folder.

Access can originate from a contract, manual folder sharing or an accepted registration. Invitation emails must be sent separately…

A registration has a header and independently decidable advertisement rows. The system flags duplicates and produces rejection doc…

An offer requires an accepted registration row. Acceptance, rejection, withdrawal and expiry are supported.

A transaction requires an active underlying contract of the appropriate type. Sales record instalments; leases record fulfilment o…

A performance certificate is linked to a transaction. Fees and VAT are calculated server-side; leases require prior confirmation o…

One incoming invoice draft can be created from a performance certificate; the actual invoice number is entered later.

An amendment requires its date, effective date and text. A changed end date also updates related brokerage and access periods.

Ordinary, immediate and mutual termination are supported. A request submitted through the portal does not itself terminate the con…

Annexes are numbered per contract, can be created from templates and are linked to the document repository.

For automatic expiry, the system sends one notice at the configured number of days before the end date.

Templates are defined by document type and language. Non-Hungarian PDFs require Hungarian text and use a two-column layout.

Template text can be loaded into the editor. The PDF is generated from saved document text and stored in the document repository.

Click-to-accept and email one-time-code acceptance are supported. SMS and DÁP integration are unavailable.

Termination reasons, registration rejection reasons and brokerage activities are managed as separate reference data.

The portal supports login, terms acceptance, watermarked viewing and downloads, search and access to own contracts.

Administrators manage folder and user permissions, the issuance log and the activity timeline.

NDA functionality is not implemented. Templates, mandatory acceptance and evidence PDFs are planned.

Use requires route permission, feature permission and content scope. Missing authorization blocks the operation.

Common errors include missing storage rules, unaccepted registration and expired access.

The client company owns the contract; a brokerage row represents one property; an offer folder is a virtual shared folder.