Rexfin Product Tour: Every Number Traceable

Most finance software asks you to trust it. Rexfin asks you to click a cell.

Every actual figure in the product opens onto the page it came from, the extraction that produced it, and the check that confirmed it agrees with the printed total. That is not a slogan bolted onto a demo. It is the reason the product exists: a stack of GCC filings and ledgers turned into a model where every number is either defensible or refused, with nothing in between. This page walks the surface of that product, top to bottom, so you can see what you’d actually be buying.

Where the trust comes from

Start with the part that is easy to skip past: how a number gets into the model in the first place. Rexfin never seeds an actual figure from a single guess. Documents move through intake and classification, get tagged against an IFRS taxonomy, and then get extracted by more than one independent engine. A figure only becomes citable once two backends agree on it: multi-backend extraction agreement is the cheapest defense there is against one engine’s silent misread. Agreement alone isn’t proof the right cell was read, so every candidate is also checked against the printed subtotal it’s supposed to roll up into. Only figures that clear both hurdles earn a citation, and Rexfin ranks and surfaces that evidence rather than hiding it: see how the trust chain evaluates evidence.

That chain is what sits behind the cited financial statements themselves and the provenance drawer you open on any cell: click, and you see the source page, not a promise. Before that page renders, Rexfin re-hashes the served file and compares it to what was originally ingested, which is what a tamper-evident integrity scan is for: if a document has been altered since it was filed, you see a warning instead of a clean render. And when a company re-files or corrects a prior period, Rexfin flags the conflict instead of quietly overwriting history: that’s restatement detection doing its job.

The gate that says no

The single feature that makes the rest of this credible is the one that blocks output. Before any board pack or export leaves the system, Rexfin runs the model against its identity checks. If an accounting identity breaks on real, actual-anchored numbers, the export gate refuses to produce the file. Not a warning banner: a blocked export. What does clear the gate becomes a cited PDF or XLSX, a full board pack, or, for GCC teams that report in both languages, a bilingual board pack that carries the same citations in Arabic and English. Every version is versioned with an audit trail, so you can show exactly what changed between the pack you sent last quarter and the one you’re sending now.

Talking to the model without it lying to you

Rexfin’s AI layer is built on a rule that sounds obvious until you watch a competitor break it: cite or refuse. Ask it a question in the AI chat and you get an answer with a citation attached, or you get an honest “I can’t verify that,” never a confident guess. The same underlying answer can be reframed for different audiences: analyst, board, auditor, without changing a single number, because voice is presentation, not a second opinion. And the commentary that ends up in your reports is generated the same way: narratives that cite their source, plus a running insights feed that flags what moved and why.

Modeling, not guessing

Underneath the reporting is a real modeling engine. Ask what if in plain language and the AI translates the question into driver changes that a three-statement projection engine recomputes deterministically: the same driver modeling discipline covers everything from a 13-week cash forecast to a full budget cycle to a rolling forecast that carries closed periods forward untouched. Save comparisons as scenario packs, start from a regional template instead of a blank grid, and pull in classical statistical baselines where they’re useful, clearly labeled as forecast baselines, never dressed up as fact.

Reporting depth and who gets to see what

Above the model sits the analysis layer teams actually live in day to day: KPI and variance analysis, segment reporting, quarterly, interim, and TTM views, multi-currency statements, EPS metrics, and fast comparables against peer filings. Statements render in the IFRS-18 presentation shape by default. None of it means anything if the wrong person can see it, so access runs on role-based control, teams work inside shared workspaces with comments and review threads attached to real cells, and an external auditor gets a scoped share link instead of a copy of your whole tenant. Documents live in one searchable library, and other systems can reach in through an API and webhooks or an MCP surface for teams running their own AI operators, with the same access rules enforced at every door.

Built for the region, not translated for it

Rexfin was designed GCC-first, not localized after the fact. Reporting is Arabic-first, the data model is built on a ZATCA-aligned foundation, and a standing compliance calendar tracks the filing and e-invoicing deadlines that actually apply to you.

That’s the tour. Each linked page goes deeper into one piece; this page exists so you can see how they fit together before you dive in.