How FeeVerify handles your data and decisions

FeeVerify keeps each client's data in its own ringfenced environment and never uses it to train a model. Every action by an agent or a person is logged, every rule is graded for confidence, every analysis runs under a spend ceiling, and a named reviewer signs off each material finding before anyone acts on it.

Questions procurement and audit teams ask

Procurement, infosec and internal audit teams usually ask the same nine questions about FeeVerify: whether it is independent, where data is stored, whether it trains models, who can see it, who signs off a finding, what is logged, how spend is capped, what happens at the end of an engagement and how agents are approved. Each answer below matches the privacy policy where the two overlap.

Is FeeVerify independent of our providers?

Yes. FeeVerify processes and routes nothing, and sells no acquiring, processing or routing, so its findings carry no commercial agenda. It sits as an independent control layer between what your providers and the schemes bill you and what you agreed, owned by your Finance team rather than by a provider. That independence is why its evidence can be put to an acquirer, processor or scheme, and why internal audit can rely on it.

Where is our data stored?

Each tenant's data sits in a ringfenced environment. There is no co-mingling and no shared fine-tuning layer between tenants by design. Bulk transaction, reconciliation and cost data are held in a per-tenant data store, separate from the system that manages accounts and permissions. Where you require a specific data-residency region, we agree it with you as part of onboarding. Where data is transferred outside the region you operate in, we put appropriate safeguards in place, such as standard contractual clauses, and agree the arrangement with you in advance.

Is our data used to train AI models?

Your commercial data is never used to train, fine-tune or improve any machine-learning model, ours or a third party's. Where the platform uses model providers to read documents or reconcile data, it does so under agreements that prohibit training on, or retention of, your content beyond what is needed to return a result.

Who can see our data?

Your organisation's users see your tenant, and your org admins manage who those users are. Tenant isolation is enforced in the database, so one tenant's users cannot reach another tenant's data. The browser has read-only access, and every change passes through a server-side gate. Inside FeeVerify, we apply least-privilege access controls and log access for review. Files containing full card numbers (PANs) are rejected at upload, so they never enter the environment.

Who signs off a finding?

A named reviewer. Material outputs, and any output graded Low for confidence, land in needs review and wait for a named sign-off before they reach a decision-maker. AI does the high-volume analysis, and experienced payments specialists steer each investigation and sign off every material finding, so you need no new headcount to run it. The sign-off, with the reviewer's name and the time, is recorded in the worklog alongside the finding.

What is logged?

Every action, by an agent or a person, is recorded in the worklog with the operator, the source, the output and its status. That covers uploads, data dictionary approvals, each agent step, each rule and its confidence grade, and every sign-off. We also log platform activity for audit and security: actions taken, by whom, when, and the outcome.

How is spend controlled?

Every analysis carries a spend and time ceiling, so an investigation cannot run up an open-ended cost and finance can predict what an answer will cost before it is asked. Commercial terms are set out in your contract: a risk-aligned pilot, then a success fee on the value you accept, with no ongoing commitment. Pilot fees and success-fee percentages are subject to contract.

What happens to our data at the end of an engagement?

We retain your commercial data only for as long as your tenancy is active or as you instruct. When you delete a tenant, or at the end of your engagement, the associated data is deleted from our systems within the period set out in your agreement. Audit-log metadata may be retained for a limited period where we are required to keep it. You keep the rulebook, variance maps and reports: you own the findings drawn from your data.

How are agents approved before they run on our data?

Every agent moves through draft, shadow, live and promoted. A draft runs in shadow, alongside live work and without affecting it, until a person reviews it at the human gate and promotes it. Your org admins approve promotions within your tenant, and FeeVerify's platform operators gate anything shared across tenants. The Orchestrator can draft a new skill when it finds a gap, but it never promotes one itself.

Which controls are on by default?

Six controls are on by default for every tenant from the first upload. Together they mean every figure FeeVerify produces can be followed back to its clause or data row, the person who approved it, and the spend it consumed.

ControlWhat it doesWhere you see it
WorklogRecords every action by an agent or a person, with operator, source, output and statusOn every investigation and every finding
Confidence gradingGrades every rule High, Medium or Low against named sources; Low-graded rules go to a person firstOn every rule and finding
Human gateHolds material outputs in needs review until a named reviewer signs them offIn the needs review queue
Budget capsSets a spend and time ceiling on every analysisOn each investigation
Per-tenant boundaryKeeps your data in its own environment, with no co-mingling and no shared fine-tuningIn your agreement
Residency and deletionHolds data in the residency region agreed at onboarding where you require one, and deletes it when you delete the tenantIn your agreement

What can we review before we sign?

Before signing, your team can review the data-processing terms, the list of sub-processors and the residency arrangement, and put its own security questionnaire to us. For commercial data you upload, FeeVerify acts as a data processor on your behalf and you remain the controller.

We use a small set of sub-processors to run the service, including cloud infrastructure and authentication providers, and model providers used to read and reconcile data. Each is bound by a data-processing agreement with confidentiality and security obligations consistent with our privacy policy. We keep an up-to-date list available to customers on request. Where you have a signed agreement with us, that agreement governs how we handle your data.

Start with one month of your own data.

A pilot begins with the agreements that protect both sides, then your contracts and one month of settlement data, scoped with a payments specialist on the first call. The 30-day diagnostic re-costs every transaction against them and shows each variance with its clause, before any recurring fee.