SAHRECOSAHRECOSultan Ali Al Hassni Real-Estate Company
My accountالعربية

SAHRECO

Platform release notes

Follow new features and improvements, and see what has changed in the way you use the platform.

Last updated:

Current release

2026.10.24-r392

Published and verified on the live site

Release details

Reconcile printed rent and review its basis

Read rent totals from the correct original column, keep annual and monthly figures separate, and review ambiguous amounts with page evidence.

  • Improvements and fixes

    Original report reconciliation: Distinguish rent aggregates from commission, water-collection captions and merged cells, preserving earlier values and evidence when extraction is corrected.

  • New

    Accountant source review: A scoped review records rent amount, basis and page evidence. An unclear original never means vacancy or zero rent. Changing the basis requires a different supporting original.

Source figures are not bank receipts. No automatic annual-to-monthly conversion or changes to periods, contracts or access. Independent role acceptance and operational reconciliation retain their checks.

Trace printed collection totals to original reports

Read printed totals across source layouts and support corrections bound to original evidence and the previous value,keeping cumulative captions separate from monthly sums.

  • Improvements and fixes

    Report layouts: Distinguish total rows from column headings and occupancy counts,and read final printed collection aggregates before expenses across pages while retaining explicit year-to-date captions.

  • New

    Evidence-bound extraction repair: Internal maintenance distinguishes provenance-only additions,printed-total corrections and cumulative-caption extraction,binding each to the exact prior value and reviewed evidence digest. Earlier values and evidence remain historical;source observations never become bank settlement or cash postings.

This release covers printed collection totals and captions. Other report fields,period conflicts,bank reconciliation and independent native-role acceptance retain their reviews. No fabricated human approval or changes to contracts,originals or account access.

Preserve earlier resolutions and review unextracted report periods

Previously resolved source-period flags stay resolved;when the report period was not machine-readable,a human can document a decision from an original page.

  • Improvements and fixes

    Review history: New review logic preserves older resolutions from earlier extraction. Only an existing structured period decision is invalidated by changed evidence or reopening;history,contract records and original amounts remain intact.

  • New

    Unextracted period review: When no period title was extracted,the Accountant explicitly chooses a report month and records the original page,quotation and reason. The filename is not accepted automatically. Overriding a known printed title still requires a different original.

Actual source decisions are not made on behalf of the Accountant and no money is posted. Interactive and independent-account acceptance remain open. Full-original extraction auditing continues.

Report-period reconciliation with original evidence and review history

A review form reconciles conflicting filename and report-title months,binds the Accountant choice to an original page and refreshes reports and reconciliation while retaining prior readings.

  • New

    Source-period conflicts: A scoped Accountant sees both source months and explicitly chooses a month with an original,page,quotation and reason. Overriding the printed title requires a different supporting original. Same-document report-period flags are resolved together;contract-row flags remain independent.

  • Improvements and fixes

    Report and reconciliation consistency: The reviewed month drives report presentation and available periods. Changed evidence or reopening restores the marker and invalidates prior comparisons. An uncertain save reuses its exact command;raw amounts,contract dates and posted payments are preserved.

Review is a human interpretation of report period,not automatic verification of quotation meaning or receipt approval. The six real report conflicts are not decided on the Accountant behalf. Independent native-role and interactive verification remain open.

Source collection classification linked to bank reconciliation

Resolve collection-basis issues through field and original-page review,retaining the Accountant decision and prior history while invalidating comparisons whose evidence changed.

  • New

    Source field review: A scoped Accountant form records the printed amount classification,page and supporting quotation. Reinterpreting a cumulative caption as report-period collections requires a different original. Status-only closure is refused;original values and periods stay separate from the reviewed interpretation.

  • Improvements and fixes

    Review and comparison consistency: Changed evidence or explicit reopening returns the same review marker to reports,work queue,intake and integrity counts and hides stale bank-comparison results. An uncertain save retries the same command without recording another decision.

Human document classification,not automatic verification of quotation truth,bank settlement or cash posting. Existing Accountant tasks,user access,payment and approval gates remain. Independent native-role and interactive verification are still required.

Recover printed report totals and distinguish cumulative collections

Read totals across merged cells and changing page grids with exact page and source evidence. Cumulative amounts show a basis-review marker instead of an unextracted field or a monthly total.

  • Improvements and fixes

    Original report extraction: Distinguish printed collection totals from annual rent,water charges and expenses;read Arabic numbers and separators without commission inversion or row summation. Preserve source observations and earlier history without replacing existing values.

  • New

    Accountant reconciliation: Year-to-date figures stay outside monthly sums with a red marker explaining that the amount is extracted and its basis requires reconciliation. The task links to its original under current building scope;period conflicts remain separate.

Document observations do not prove bank settlement or an owner transfer. No ledger posting,contract activation or automatic correction of conflicting periods. Independent native-role and interactive live verification remain required.

Building requests and their next action in your account

Connect building drafts and requests to personal history,dashboard and company queue,with one next step and responsible role derived from current reviews.

  • New

    Owner request journey: The original draft and request appear in the account without another ticket. Exact links show missing items and the current completion,review or decision step. Search includes both saved languages.

  • Improvements and fixes

    Follow-up responsibility: Request detail,account and company queue share the current next step. Changed review evidence or agreement expiry returns it to review;an unavailable assigned Accountant shows CEO fallback. Corrections wait for the applicant,and terminal outcomes remain in history.

A read-only projection over the original request;no duplicated record,assignment,activation,access,fee or message change. No invented processing deadline or native acceptance from isolated tests;independent-role verification remains required.

Evidence upload authority and safe retries

Bind owner-team evidence to its native identity,delegation and source;retain originals and reconcile uncertain saves without duplicate proposals.

  • Improvements and fixes

    Documents and access: An upload stops when identity or membership changes during storage. Earlier files cannot silently acquire fresh submission authority;red review reasons preserve the original and history.

  • Improvements and fixes

    Receipt evidence: Retries retain the same file,fields and command;late results are discarded after account changes. Reuploading identical evidence under revised delegation cannot duplicate a pending receipt for the same installment.

Evidence remains review-only;owner confirmation and Accountant posting stay separate. No ownership transfer,access grant,subscription activation or message. Isolated checks and deployment verification do not establish independent native-browser acceptance.

Complaint response targets and extension notices

Initial response within two business days and target resolution within five,with dated receipts,responsible-staff deadlines and reasoned extension notices.

  • New

    Approved service targets: New complaints retain original targets calculated for Sunday–Thursday in Riyadh time. Targets appear to complainant and staff;ordinary follow-up edits cannot erase or postpone them.

  • New

    Initial response and extensions: Authorised staff can explicitly publish an initial response or clarification. An extension requires a reason and later dated target while preserving the original. Final-response review remains separate;elapsed time never closes a complaint.

These are human-approved company targets,not statutory periods or regulator acceptance. No retroactive rewrite of older complaints and no Nafath,licensing or hosting proof is implied. Interactive live lifecycle acceptance remains required.

Intellectual property policy and public complaints

A standalone policy and public complaint form with a saved reference,date and private tracking in the existing ticket centre.

  • New

    Platform information: Publish a standalone Arabic/English intellectual property policy and link both policy and complaints through shared public navigation.

  • New

    Complaints and follow-up: Save complaints in the same ticket centre with a reference,date and Customer Service or CEO assignment. Private tracking excludes staff notes and unapproved replies;retrying the same save does not duplicate the complaint.

This does not establish platform licence completion. Complaint timeframe,Nafath,REGA integration,hosting,authentication,advertisements and legal-edition identity matching remain. Save tests are isolated and synthetic;interactive live acceptance remains open.

Recheck owner-team invitations and pending proposals

Pending invitations and proposal approvals stop when issuer identity,delegation or management evidence changes. A red marker explains the review reason and required next action.

  • Improvements and fixes

    Owner-team invitations: Invitations retain their issuer identity,role and scope binding,rechecked at preview and joining. Legacy invitations without that binding stay retained and require cancellation and replacement.

  • Improvements and fixes

    Reviewing unit proposals: Approval is bound to the submitting membership,identity,building and management evidence. Changed authority blocks the old proposal from updating the unit;reviewers can decline with a reason and request a fresh submission.

This release creates no production invitation,membership,charge or operating approval,and does not change accepted memberships or earlier history. Independent native-role acceptance remains required.

Protect records when account access changes

Delayed requests cannot restore records from an earlier owner,team or permission context. Ordinary display-name updates keep current work intact.

  • Improvements and fixes

    Session and requests: Old responses are discarded before interpretation and after body loading. A stale sign-in error cannot expire a newer session,and an unconfirmed write is never automatically replayed.

  • Improvements and fixes

    Workspace and private files: Workspace records and file previews clear when account authority changes,and delayed downloads stop. Cosmetic profile and equivalent permission-order updates preserve current forms.

Server permissions and operating approvals remain authoritative. Operational data and liabilities are unchanged;independent native-role and browser acceptance remain open.

Use the linked owner in service requests and quotes

Property ownership uses the reviewed landlord record;service requests and quotes use its linked customer account. The two identifiers are kept distinct and owner choices are deduplicated.

  • Improvements and fixes

    Owner and customer choices: Property choices list each canonical landlord once. Scoped company forms list actual linked customer accounts; a private landlord record without a login is not treated as a service actor.

  • Improvements and fixes

    Requests and service quotes: A linked owner can request a repair within current property access. Quote payer choices use the correct customer account,retaining customer approval and separate payment verification.

This does not create accounts,invitations,permissions,ownership or payments,or alter saved operational records. Independent native sign-in acceptance remains separate.

Preserve rent entitlement when ownership changes

Changing a building owner no longer exposes obligations or receipts assigned to a former beneficiary. Records are preserved and beneficiary fields needing Accountant review are marked.

  • Access protection

    Owner and team rent scope: Lists,details,exports,statements,contract/building views and reminder context check the recorded beneficiary. Payment proof requires matching entitlement on both proof and obligation.

  • Improvements and fixes

    Review and unconfirmed balances: The Accountant sees a red field marker when a beneficiary is missing or differs from the current owner,with instructions to retain the original liability. An unresolved financial scope is not displayed as a zero balance.

No ownership,liability,financial posting or permission is transferred or changed. Independent native sign-in and role acceptance remain separate.

Reopen delivery when its verified scope changes

Changed criteria, dependencies or newly outstanding work reopen delivery, retain earlier evidence and require fresh proof for the current scope.

  • Improvements and fixes

    Completion integrity: An item cannot carry completion into changed criteria or dependencies. Earlier scope and evidence remain in history; new evidence binds to the current scope epoch. Display, responsibility and priority edits that do not change scope preserve valid delivery.

  • Improvements and fixes

    Confirmed delivery policy: Open records reflect direct deployment and documented verification without an extra CEO engineering acceptance step. Independent-role criteria and operational/financial approvals remain.

Correcting policy text does not complete other work or establish independent native-role acceptance.

Remember language and reconcile verified delivery during release

Returning visitors retain their chosen language. The release process requires reconciliation and saved readback of its tracked items.

  • Improvements and fixes

    Website language: The homepage respects a remembered language when the URL has no explicit choice. Explicit Arabic/English URLs take precedence; new visitors default to Arabic.

  • Improvements and fixes

    Development delivery: Publication requires a tracked-item plan bound to the source and verifier. After live verification, item outcomes are saved and read back before delivery finishes. Partial verification cannot close an item.

Employee and operational approvals remain separate. This batch does not establish whole-platform or independent-role completion.

Fixzit product areas in the progress register

Nine product areas link existing work, verified delivery, open items and planned expansion.

  • New

    Product roadmap: The dashboard adds ERP, CRM, HR and payroll, stock, billing and accounting, industry solutions, school and hospital facilities, optional websites and e-commerce, and web/mobile applications. Counts open existing work filtered by area and status.

  • New

    Progress scope: Planned expansion is distinct from current tracked delivery. Existing categories, delivery order and records remain. Areas overlap and their counts do not imply a complete standalone product.

Progress taxonomy does not activate payroll, stock or other industry modules or change access or commercial settings. Patient and student data are not specified scope.

Announcements follow their captured current audience

Replacement owners and relinked accounts cannot inherit earlier announcements. The composer lists eligible linked tenants, and queued email stops if its publisher loses authority.

  • Improvements and fixes

    Announcement history and current audience: New announcements capture selected current tenant accounts and existing authorised building owners. An unchanged recipient keeps posted history after an ownership change; later owners or rebound accounts receive no automatic historical access. Current company scope retains the original history. Earlier announcements without recipient evidence show the common red Accountant review marker.

  • Improvements and fixes

    Eligible recipients and queued delivery: Recipients require a linked member account, current readable contract and message access. The composer explains who can read an announcement and stops with guidance when no eligible account exists. Inbox and queued email use the same source and recipient checks; new external delivery also rechecks the original publisher. No production announcement is migrated, published or sent by deployment.

Populated transfer, recipient and legacy paths are verified with isolated synthetic records, separately from native Wix role acceptance. Original history, financial parties, access grants and provider configuration are preserved. Accepted external sends cannot be recalled by later authority checks.

Private conversations follow current participants

Replacement owners, providers and rebound accounts no longer inherit earlier private messages. Maintenance access follows the exact tenant contract, including private files and notices.

  • Improvements and fixes

    Message audience and attribution: New private messages capture current recipient identities and parent context. Conversations, inbox notices and email preparation use the same current checks. Original author attribution is captured instead of inferred from later account edits. Current company scope retains history; legacy messages without recipient evidence show a red Accountant marker and are not automatically shared with replacement parties.

  • Improvements and fixes

    Exact maintenance contract: Relinking a customer to another tenant in the same unit no longer grants the old maintenance job, invoices, tickets, exports or private file bytes. Existing scoped company and assigned-provider access remain separate. No financial party or historical liability is changed.

  • Improvements and fixes

    Final email recipient check: After claiming a queued notice, the worker rereads authority and compares the recipient and message context immediately before transport. Changed authority/address/context suppresses stale mail; a failed current read holds it without sending or claiming delivery. Provider setup and sending policies remain unchanged.

No production conversation is migrated, shared or sent by deployment. Legacy context requires authorised company review and explicit relevant communication. Populated ownership/message paths are tested with isolated synthetic records; independent native role acceptance remains separate. Already accepted external sends cannot be recalled by a later access check.

Latest release references on this page (20)

The full history is retained. Browse updates, search a version, or open the reference pages within each update to reach every original.

Release reference and technical verification
Verified — Riyadh time
24 Oct 2026, 04:42
Automated checks
3,867 passed · 0 failed
Build reference
20261024-navigation-context-4
Source fingerprint
7271bc7812b64dd86eba5c7110053af9d2ff400586ab3181af01ff3d3cee09ba
View release JSON

For signed-in accounts, New lasts seven days from the first visit after release, capped at thirty days from release. Visitors see it for seven days from release.