Everything, one box
Transactions, invoices, bills, journal entries, contracts, projects, vendors, customers, employees, documents, and audit events — without choosing a module first.
Platform · platform & data
Finding things is an underrated share of finance work — which invoice, which contract, which approval, which version of the schedule. In most systems that means knowing which module to look in first, which is a piece of institutional knowledge nobody should need.
What it does
Transactions, invoices, bills, journal entries, contracts, projects, vendors, customers, employees, documents, and audit events — without choosing a module first.
Full text within attached PDFs and images, so finding the contract that mentions a specific termination clause does not require having tagged it.
Results are computed within your permissions in the data layer rather than filtered afterwards, so an out-of-scope record does not appear as a hint.
AWS invoices over $5,000 in the last six months. Unbilled projects for one client. A phrase where a filter chain would be slower to construct than to describe.
From any record straight to its audit history, including the agent action that produced it, without navigating there separately.
Save it, schedule it, or export it. A search you run monthly should become a report rather than a habit.
In most ERP systems, finding something requires knowing that vendor bills live here, that attachments are searched separately, that contracts are in a different module, and that the audit history is somewhere else again. That knowledge takes months to acquire and is worth nothing outside the specific product.
It is also the largest hidden cost of onboarding a new person into a finance team, and it is the reason so much institutional memory sits with whoever has been there longest.
This distinction matters more in search than anywhere else. A system that searches broadly and then filters what you may see leaks information through absence and through result counts — you learn that something exists even when you cannot open it.
Scope is applied when the query is composed, in the data layer, so an out-of-scope record is not merely hidden but genuinely not part of the result set. For customer portals and external auditors this is the whole requirement rather than a refinement.
The useful pattern we see is people using search to discover the report they actually wanted. Someone searches for unbilled work on a client three months in a row, and on the third occasion it should become a saved view with a schedule.
Every result set can be pinned, scheduled, or exported for that reason. A recurring search is a report nobody has built yet.
Limits
Search finds records. Large analytical queries across years of history belong in your warehouse, which we export into rather than competing with.
Searching for a dimension that was never coded returns nothing, and it will say so rather than returning a partial set that looks complete.
Document text search depends on extraction. Printed and typed text is solid; a handwritten note photographed at an angle is not.
Questions
A read-only connection and about a week is enough to search your own records from one box.