Pay for what you process.

A page is one PDF page that the system OCRs and runs through AI extraction. We meter at upload time using nexus.document_batches.page_count (visible on every batch in the workspace). A typical voucher batch in the GCC is 30-60 pages and contains 10-30 invoice events — so the per-tier page cap maps to far more transactional throughput than the page number alone suggests. A 300-page Solo cap comfortably handles 100-150 invoices per month at typical density. Overage is AED 25 per additional 100 pages, never per-batch — so a single big batch of 500 pages doesn't hit you with a per-batch fee, only the 200-page overage above your cap.

Full Growth-tier access — every available feature, no credit card. We onboard one of your real companies (your own or one of your firm's end-clients) with you and walk your team through the workflow. At day 30 you decide whether to continue. Today we run pilots manually (no automated billing), so there is nothing to auto-charge; if you do not continue we deactivate the workspace and your data is portable as CSV / PDF.

For a single company with a clean chart of accounts: a few days. For a firm or finance team with multiple companies and custom COA mappings: roughly two weeks. The bottleneck is your team's time to map (Type of Expense, Nature of Expense) → GL combinations once. After that the system learns each new mapping permanently.

Yes. CSV templates cover opening trial balance, vendor + customer master, open AP / AR aging, and fixed-asset register — see the full playbook at /docs/migration. Solo and Growth use self-serve CSV upload (with one free assisted session on Growth). Pro and Enterprise include concierge migration: we run the import end-to-end, validate against your previous trial balance, and walk you through period-1 close.

Region-flexible hosting with encrypted-at-rest Postgres, TLS in transit, and a Data Processing Addendum + SCC-equivalent transfer terms. For tenants whose data must remain inside KSA, we offer a KSA-resident self-hosted deployment as an option on Pro and Enterprise tiers. Either path is designed for PDPL alignment — your DPO reviews the structure as part of onboarding before sign-off.

Per-batch hard cap of USD $5 enforced in code. Prompt caching on the system prompt + per-client COA reduces input cost by ~90% on cached calls. Token spend is metered to your account but capped on every invoice — you never get a surprise bill from us based on the underlying model API.

Yes — Growth and above include workflow customisation. Approval-chain depth, role naming, journal-entry templates per (Type of Expense, Nature of Expense) combination, narrative formatting, and Documents archive segregation rules are all configurable. Pro and Enterprise additionally include per-firm rule packages and bespoke report templates. Solo runs the standard default workflow.

On the roadmap. Customers on Pro and Enterprise tiers will be able to upload their accounting-policy document; the AI proposes JE templates, narrative conventions, and approval rules grounded in that policy, with every proposed rule explicitly approved by your team before it goes live. We are deliberately gating this capability until the rule-review and approval workflow is fully audited — it ships when we are confident customers can keep one-click control over what the AI is doing on their books.

Once subscription billing is live, monthly plans will cancel at the end of the current period and annual plans will be pro-rated. Today, during the pilot phase, you can leave at any time with no charge. Either way: every JE, every TB, every source PDF is exportable as CSV / PDF whenever you want, with or without an active subscription.