From records to checked outcomes
An expected outcome is a step that should follow another. A trading credit should follow a transfer instruction. An account should follow a paid order. A ledger credit should follow an accepted deposit. PipsClarity checks whether the records support each one.
PipsClarity checks outcomes. It never moves funds or creates trading accounts.
Nine steps, each with a clear owner
Amounts and outcomes come from your rules and the source records. Every assessment keeps the policy, mapping, check time and coverage behind it.
Name the legal entity, sources, account mappings, asset identity, timing rules and the workflow to check.
Records the agreement as versioned policies and mappings.
Confirm each source and asset.
Registers them. Registration alone is not a live feed.
Send the agreed CSV or JSON export with its coverage details.
Shows rejected rows and coverage gaps before anything is accepted.
Review the validation result and confirm it.
Issues a receipt. The same file sent twice does not create duplicate records.
Nothing to do at this step.
Normalizes the records and compares exact references and units against the policy versions in force.
Nothing to do at this step.
States whether the outcome matched, is waiting, differs, is ambiguous, lacks evidence or falls outside the rules.
Nothing to do at this step.
Opens or updates a case. Not every assessment becomes a case.
Read the evidence, assign an owner, add notes and fix the issue in your own systems.
Keeps the evidence, notes and case history together.
Send later records from the source systems.
Checks the outcome again. It may confirm the fix, reopen a concern or keep a separate review case.
Past assessments and case events are kept.
What your team does, and what stays with you
Your team
- Approves the records for the agreed workflow
- Sends exports in the agreed format, with their coverage details
- Confirms account mappings and timing rules
- Investigates and fixes issues in its own systems
- Sends later records so outcomes can be checked again
PipsClarity does not
- Send money
- Place trades
- Create trading accounts
- Hold private keys
Your systems stay the source of truth and the place where fixes are made.
One method, three different rules
Forex brokers
USD 1,000 to the wallet, USD 600 instructed to trading
- Payment received
- USD 1,000
- Wallet credit
- USD 1,000
- Transfer instruction
- USD 600 to trading account A
- Expected trading credit
- USD 600
- Can stay in the wallet
- USD 400
Wallet funding
MatchedThe wallet journal shows the USD 1,000 payment.
Instructed transfer
DiscrepancyNo matching trading credit inside the agreed window and the covered period. USD 600 remaining.
After a later USD 600 credit to account A
Verified resolvedThe new record matches the instruction and can verify the case.
Both assessments stay visible. They are never added into a USD 1,600 deposit total.
See forex deposit checksProp firms
A USD 100 fee for a USD 10,000 simulated evaluation
- Order fee
- USD 100, paid
- Product
- Evaluation account
- Account size
- USD 10,000 simulated notional
- Stage and platform
- As purchased
- Account type and reference
- As the agreed source records give them
Paid order to matching account
DiscrepancyNo account was observed for this purchase. This opens an operational case.
After later account records
Verified resolvedThe observed account matches what was bought.
A USD 100 fee for a USD 10,000 simulated account does not create a USD 9,900 cash gap.
See prop account checksCrypto exchanges
25.000000 units of one synthetic token
- Deposit
- 25.000000 units
- Asset
- Synthetic token on its stated network
- Acceptance rule
- As agreed for this asset
- Customer attribution
- From the exchange’s own records
- Expected ledger credit
- 25.000000 units
While the acceptance rule is not met
Waiting within SLAThe deposit is seen. The agreed acceptance rule is not met yet.
Accepted and attributed, no ledger credit
DiscrepancyA missing credit counts as a discrepancy only when the ledger export covers the period.
After a 25.000000-unit ledger credit
MatchedThe customer ledger shows the matching credit.
If a later reorg changes the evidence
OpenA separate review case opens. The earlier resolution stays on record.
Amounts are never added up across networks or assets.
See crypto deposit checksNot every assessment becomes a case
Matched and waiting outcomes can exist without a case. A case opens only when a rule calls for one.
Assessment
Every checked expectation has one of six outcomes.
Does a rule call for a case?
No. The assessment stands on its own. Matched and waiting outcomes can exist without a case.
Yes. A case opens or updates. A case never exists just to fill a list.
Case
An active case is open, assigned or reopened.
Verified resolved needs later source records. Closed by hand is a team decision. It is not proof that money or account access arrived.
Your team investigates. Later records decide.
Read the records
Open the assessment and read the source records and coverage behind it.
Add a note
Write down what you checked and what you found.
Take ownership
An investigator with permission takes the case.
Fix it at the source
Your team fixes the issue where the record lives. PipsClarity changes nothing there.
Import new records
Later records come in and the outcome is checked again.
Case detail
Instructed transfer to trading account A
AssignedUSD 600 instructed. No matching trading credit in the covered interval.
Transfer instruction
To trading account A
USD 600
Trading credit
No matching record yet
Case history
- Case opened from the discrepancy
- Assigned to the current investigator
- Note added: checked with the platform team
- Waiting for the next import
A missing export does not prove a missing credit
Each source states the accounts and time period it covers, when it was exported and any known gaps. A result can only be as firm as that coverage.
Wallet journal
Registered export source
- Covered interval
- 1 Nov 2026 00:00 to 7 Nov 2026 23:59 UTC
- Exported
- 8 Nov 2026 06:10 UTC
- Known gaps
- None declared
Wallet journal
Registered export source
- Covered interval
- 1 Nov 2026 00:00 to 7 Nov 2026 23:59 UTC
- Exported
- 8 Nov 2026 06:10 UTC
- Known gaps
- 4 Nov 2026 02:00 to 05:00 UTC. A missing export does not prove a missing credit.
Wallet journal
Registered export source
- Covered interval
- None. The source is registered and has never sent records.
- Exported
- Never
- Known gaps
- Not applicable
Guided reviews first, hosted access later
First, a guided pilot
Starting method- Access
- You don’t need a hosted account for the first scoped review.
- Data
- Agreed exports, sent by the transfer method approved in the written scope.
- Delivery
- Agreed reports by a private delivery method, a findings meeting and follow-up checks.
Later, hosted access
Being prepared- Access
- Invited staff sign in with verified identity and MFA, by role, inside their own workspace.
- Data
- Imports are validated, reviewed and committed in the dashboard.
- Delivery
- Assessments, cases, sources and audit history in the dashboard.
Offered only after its sign-in, separation, processing and recovery checks pass.
Questions about the process
How does PipsClarity check an expected outcome?
It takes the agreed exports from each system in the workflow, applies the rules you agreed, and compares exact references and amounts. Each expected outcome gets an assessment with one of six results, and the records behind it stay attached.
Is every assessment a case?
No, matched and waiting outcomes can exist without a case. A case opens or updates only when a rule calls for one.
What if records are missing?
The result shows where the evidence stops. If an export does not cover the period, the outcome is insufficient evidence, not a discrepancy. A missing export does not prove a missing credit.
Does AI decide the outcome?
No, amounts and outcomes come from the agreed rules applied to the source records. AI does not set the outcome.
Do we need a dashboard login to start?
No, the first scoped review doesn’t need a hosted account. Our team guides the first reviews and delivers findings by a private method agreed in the scope.
Walk through it with synthetic data
Request a demo and pick the workflow you want to check.