Settlement Value Observed
₹2.41 Cr
Settlement value confirmed by bank or provider
Includes partial matches and linked outcomes. This is not the same as total intended payment value for the batch.
Payout operations
See, check, and proveevery payout
One shared place for the money you meant to pay, what the bank confirmed, the gaps in between, and the proof finance can stand behind.
Overview
Payment integrity from instruction to settlement
Know what was authorised, what moved, what settled, and what can be proven.
₹3.45 Cr
Intended Payment Value
1,248 payment instructions in this period.
This is the value your system intended to pay. Confirmation depends on bank/settlement data.
Month · January 2026
Payment Value: Intended vs Observed
Shows how payment instructions compare with observed settlement outcomes over time. Observed is not matched allocation or bank confirmation.
PAYMENT VALUE · INTENDED VS OBSERVED
Intended Payment ValueObserved Outcome Value
Date: 1
Intended payments: ₹3,19,20,000
Bank-confirmed: ₹2,23,44,000
Needs review: ₹95,76,000
Zord compares your payment instructions with bank/settlement records for this date.
Today's payment health
Current status of payment value, confirmation, and review items across connected systems.
Unmatched Intent Value
₹18.2 L
Payments without a confirmed settlement outcome
Short-settled value₹4.2 L
Over-settled value₹1.1 L
Unlinked settlement₹1.8 L
Reversal exposure₹0.95 L
Covers payments with no confirmed settlement link. Short-settled, over-settled, unlinked, and reversal amounts are broken out below.
Match Confidence
94.2%
Average match confidence
Payments needing review86
Missing reference rate4.2%
Reference completeness95.8%
Multiple match possibility1.4%
Proof Readiness
87.5%
Evidence coverage for audit or export
Proof-ready payments1,092 ready
Incomplete proof156 incomplete
Proof-ready payments have enough linked evidence to support audit or dispute export.
Product preview - sample workspace data
Scroll to explore
For the people who have to explain payouts - ops, finance, and audit.
Three things every payout teamneeds in one place.
One shared place for the money you meant to pay, what the bank confirmed, the gaps in between, and the proof finance can stand behind.
[ 01 ]
See where money stands
See what you meant to pay next to what the bank confirmed. Spot missing amounts before month-end.
Today's payments
Meant to pay
₹0.00 Cr
Bank confirmed
₹0.00 Cr
Still open
₹0 L
RazorpayOK
CashfreeCheck
PayUNeeds help
StripeOK
[ 02 ]
Clear up mismatches
When numbers do not line up, put them on a review list so someone can decide what to do next.
Mismatches to clear
Last week
0.0%
Payments that lined up · last 7 days
What needs attention
See which payments lined up, which are waiting on the bank, and which need a person.
Lined up1,248 payments
Waiting on bankLooking good
Needs a person42 open
Lined up
+0.0%
Gaps
-0.0%
Proof ready
+0.0%
[ 03 ]
Prove what happened
Hand finance one proof pack - from the original payment instruction through bank confirmation.
Proof for finance
Protected0
Proof steps logged
WhoWhatWhen
A. SharmaDownloaded proof pack12 Jan
Finance opsCleared a mismatch11 Jan
SystemMarked proof ready10 Jan
Ready to share
Proof pack ready for finance close or audit questions.
10 Jan 2026 · 14:32 IST
Live signals
Signals surface before money leaks
Live payment health, routing quality, and settlement behavior - scored continuously and acted on before finance feels the impact.
Payment health
A live view of payment health, bank confirmations, and items that need a person.
Settlement healthHealthy
Waiting on bank18
Needs a person41
Lined up this week96%
Suggested next check
18 payments are waiting on bank confirmation longer than usual.
Watching payment health in real time.
How it works
From payment file to proof
[ 01 ]Payment file
Bring in payment instructions
Upload the payment file your business meant to pay - amounts, payees, and batch context in one record.
[ 02 ]Batch
Organize as a batch
Group instructions into a batch so ops can follow progress from intake through confirmation and proof.
[ 03 ]Settlement journal
Match bank confirmations
Add settlement or bank files, then match what was supposed to happen with what was confirmed - and flag what needs review.
[ 04 ]Proof pack
Export proof
Build a proof pack finance and audit can use - not screenshots scattered across tools.
WHY ZORD
Built for payout teams.
Not another payments black box.
See money you meant to pay next to what the bank confirmed, resolve gaps, and keep proof packs ready - in one shared place for ops and finance.
Best for teams evaluating fit
Try first
No commitment
Explore the payout workspace and proof-pack flows with sample data before you commit to production.
- Workspace preview
- Product walkthrough
- Fit review
- Getting-started guides
Best for teams going live
Growth
Annual agreement
Live workspace access, onboarding help, and a regular pricing check-in once payouts are day-to-day work.
- Live workspace
- Setup support
- Pricing check-ins
- Priority onboarding
Best for regulated and high-volume programs
Enterprise
Custom
Flexible pricing for security review, multi-team go-live, tailored proof packs, and a dedicated account contact.
- Volume-based pricing
- Security review help
- Guided go-live
- Dedicated account contact
