Confirm the asset register reconciles with the fixed-asset ledger before the schedule is finalised.
For assets acquired during the year, depreciation runs from the date the asset was first put to use, not the invoice date.
RAG‑4i answers questions from the documents in your workspace, citing the passage behind every claim. When the documents don't cover a question, it says so.
Accounts are provisioned by your workspace administrator.
What should we confirm before finalising a client's depreciation schedule?
Confirm the asset register reconciles with the fixed-asset ledger before the schedule is finalised.
For assets acquired during the year, depreciation runs from the date the asset was first put to use, not the invoice date.
Year-End Procedures.pdf· p. 22
Do not finalise a depreciation schedule until the asset register and the fixed-asset ledger reconcile, line by line, for every class of asset.
Fixed Assets Advisory Note.pdf· p. 9
For additions during the year, compute depreciation from the date the asset was first put to use; the invoice date is not the acquisition date for this purpose.
An illustration of the answer surface. Click markers to trace citations to source passages.
Citations open the exact passage a claim was drawn from, with its document and page. You decide whether the evidence holds before you rely on the answer.
And when the retrieved passages don't tell the whole story, RAG‑4i labels the answer instead of smoothing over the gap.
“Do not finalise a depreciation schedule until the asset register and the fixed-asset ledger reconcile, line by line, for every class of asset.”
Cited by: “Confirm the asset register reconciles with the fixed-asset ledger before the schedule is finalised.”
“For additions during the year, compute depreciation from the date the asset was first put to use; the invoice date is not the acquisition date for this purpose.”
Cited by: “Depreciation runs from the date first put to use, not the invoice date.”
Verbatim passage fragments from workspace documents, anchored to cited claims.
RAG‑4i is architected in pure TypeScript on Supabase Edge Functions (Deno) and PostgreSQL with pgvector. Every metric below was empirically measured against frozen enterprise test suites — nothing is estimated.
Hardened systems engineering decisions designed to scale under strict enterprise memory and security constraints.
Runs pure TypeScript unpdf inside Supabase Edge (Deno 2.x). Page-boundary chunking (1,000 chars / 200 overlap) permanently anchors every claim to its statutory legal page provenance without heavy PyMuPDF/Poppler dependencies.
Fuses dense semantic search (Jina v5 embeddings via pgvector HNSW) and sparse lexical search (PostgreSQL FTS GIN) via Reciprocal Rank Fusion (k=60). Repetitive running headers lose weight in BM25 IDF without wasting LLM tokens stripping them.
Eliminates multi-tenant filter starvation under Row-Level Security (RLS) by configuring hnsw.iterative_scan = relaxed_order, guaranteeing full candidate retrieval even when strict workspace partition boundaries are enforced.
H1 router bypasses vector search and LLMs on conversational turns. A deterministic evidence gate checks retrieved passage relevance before calling AWS Bedrock, saving ~4,500 tokens and 400ms while guaranteeing fail-closed refusals on information gaps.
Review full test suites, decisions record (D1–D83), and grey-box penetration reports.
Four steps, no configuration. The same pipeline runs for every question, and it either finds the evidence or tells you it did not.
Upload the PDFs your team works from. Each document is parsed page by page and indexed inside your workspace.
Type the question the way you would ask a colleague. No query syntax, no keywords to guess.
Every question retrieves passages from your workspace's documents, by meaning and by term, and the retrieved evidence is checked before any wording is produced.
Answers arrive with citations attached. Open any marker to read the passage behind it, or get a plain refusal when the documents do not cover the question.
Year-end close
Answering from 3 of 5 sources included
A Space is a set of sources you choose. Ask inside it and retrieval stays inside it, so the answer cannot drift into documents the matter does not touch.
Switching a source on or off changes the scope of every following question; nothing else moves.
Client documents deserve more than a shared drive. These are the boundaries the product is built on, stated as they are implemented.
Tax & advisory
Audit
Sign in to open your workspace: upload a document, ask the first question, and read the answer with its evidence.
Accounts are provisioned by your workspace administrator.