Fidelog · Checks business records against your own rules
Hand Fidelog your contracts, invoices, expense claims and emails. It checks every record against the rules you set and finds problems such as overpayments, wrong tax rates or people approving their own claims. Each one points at the source line and shows the calculation. It can run on your own machines, and offline with a local model.
2Why it is a problem
Kestrel Ridge Storage Inc · FK-2026-00127
The rule, in one sentence
Do not pay before the contract is signed.
Turned into logic, worked on this record · click a number for its source
✓ Re-computed independently by a second program: same result
Next step
3Where it is in the source
e-Receipt
e-ReceiptPayer: Kestrel Ridge Storage IncPayee: Larkspur Catering CoTransaction date: 2026-01-13Transaction amount: $56,620.02Purpose: FK-2026-00127 Glacier NVMe ControllerIntro film
Audit as the example: tens of thousands of documents, problems hiding between them, and how Fidelog checks every one against your rules and points each finding back to the source.
Checks in your own words
Large language models are good at answering. Used to check thousands of records, they answer differently from one day to the next, nobody knows which rows they skipped, and when they are wrong they cannot point to the line. Business checking needs something else: a rule that is set once, applied to every record, with evidence for every result.
For example, write
For a single purchase, total payments must not exceed the contract amount.
Describe what to check the way you would say it and give one example. Review the results first; if something is off, change the sentence and run it again. No formulas, no waiting for IT.
Each result lists the rows, the arithmetic and the reasoning steps it used, with the source one click away. Recalculate on the page or change the rule and run it again.
Rules are kept by version, with who changed what. Your team's checking experience accumulates, and a new colleague can use it from day one.
Why you can trust it
The exact source. Figures you can recompute. An independent check. You can follow how a finding was reached before deciding what to do about it.
Go straight to the file, line and original wording that support a finding.
See the source numbers and full formula, recalculated on the page for review.
A separate program retraces the source lines and reasoning, and leaves a record you can inspect.
How one finding is made
Invoice tax rate outside the allowed bands
The rule: an invoice tax rate must be one of 13%, 9%, 6%, 5%, 3%, 1.5%, 1%, 0%.
| Turned into logic | Tax rate = tax ÷ net amount 130.54 ÷ 1,864.91 = 7%, not one of these |
|---|---|
| Source | Invoice scan line 3 “Tax: ¥130.54” line 2 “Amount: ¥1,864.91” |
| Checked again | Re-computed independently by a second program: same result |
The rule, the calculation, the source lines and the second check form one evidence chain you can verify yourself.
Use cases
From business records to customer conversations and compliance reviews, the same principle applies: find the issue, inspect the evidence, decide the next step.
Business records · demo available
For operations, finance and audit teams checking what happened across documents and systems.
Customer experience
For teams who need to understand recurring customer problems and review how they were handled.
Start with your conversations and recordsRun one batch first
Risk & oversight
For teams responsible for checking whether records and processes support the decisions being made.
Checks scoped to your processRun one batch first
Patterns
A single record shows one event. Related records can reveal what keeps recurring, where accounts disagree and which steps are missing.
The same supplier’s invoices show the same error month after month.
The contract price differs from the invoice; one person sits in different departments in two lists.
An expense claim says “approved by manager”, but no approval record can be found.
Paid before the contract was signed; signed off as received before the goods arrived.
What it looks like
An audit example: see how many items need you, open one to read the source, then record how it was handled.
Corporate audit
Next to look at
Tax: ¥130.54
Amount: ¥1,864.91
Invoice tax rate outside the allowed bands3 on this page
Everything in the interface is clickable: tabs, findings, companies, documents.
Security
Run Fidelog on your own machine or inside your network. With local models, document processing and evidence checks can work offline. External model access is optional and under your control.
Deploy locally or on your network, with control over processing, evidence and access.
Each document keeps a fingerprint that no longer matches once its content changes; with the activity log you can see which version was used and who changed what.
Fidelog provides findings, evidence and next steps for your team to review and act on.
Questions
We quote by use case, volume and deployment, listing the software, implementation and support included. You can start with a trial on a representative batch and decide after seeing the results; any trial cost is agreed up front.
Yes. Fidelog supports local and private-network deployment, with offline operation using local models. External model connections and data access follow your requirements.
Pick one use case and a representative batch (say, one month of expense claims). Once we see the volume and formats, we confirm the scope and timing.
One machine inside your network is enough to start; add more as the volume grows. Sized to your document volume.
Bring one batch of your own material. We will show you what needs attention, the evidence behind it and how your team can take the next step.