Launch
How payouts move through Zord

One payout flow.
From payment file to bank confirmation to proof.

System statusSample payout flow
Payout operations

See.
Check.
Match. Prove.

Zord sits next to the systems you already use. Bring in payment instructions, follow batches, match bank confirmations, and export proof - so ops and finance work from the same payout story.

Book DemoBack to landing
Stages4steps
ViewSharedops + finance
ProofExportready
StartTry first
InstructionBatchProviderBankProof
proof status
97.8%
proof pack ready

Operational flow

Every stage is visible, attributable, and designed for action

Scroll through the journey below to see how Zord converts a raw payout request into a fully tracked, confirmed, and defensible outcome.

01 · Instructions
Bring in payment instructions
Bring in the file
02 · Batch
Organize as a batch
Organize the batch
03 · Confirm
Match bank confirmations
Match bank results
04 · Proof
Export proof packs
Export the proof
Stage 01

Bring in payment instructions

Your payment file enters Zord with payees, amounts, and batch context. Teams start from one clear record of what the business meant to pay.

  • Capture amount, payee, and business context in one place
  • Keep the reason for the payout visible for later review
  • Organize instructions before bank confirmations arrive
Input
Payment file
Record
Shared
Ready for
Batching
What this step looks like
Instructions
Payment instructionValidated
beneficiary_id: seller_4821
amount: sample_value
mode: workspace_preview
proof: required
AML clearedPolicy matchedProof required
Stage 02

Organize as a batch

Instructions become a batch so ops can follow one container from intake through confirmation, matching, and proof readiness.

  • Group related payments into one operational batch
  • Track progress without rebuilding status from multiple tools
  • Give finance and ops the same batch story
Container
Batch
Progress
Visible
Ownership
Shared
What this step looks like
Batch
Payment sourcesProduct preview
Cashfree · IMPSStable
Razorpay · WatchCheck
Yes Bank UPIReview
Primary source
Confirmations in
Gap review
CashfreeStable
Selected pathPrimary IMPS
RazorpayCheck
Fallback pathWatch lane
Yes Bank UPIReview
Fallback pathOverflow lane
Stage 03

Match bank confirmations

Settlement and bank files arrive next. Zord matches what was supposed to happen with what was confirmed, and sends unclear items to review.

  • Compare intended payments with bank confirmations
  • Flag gaps and mismatches before month-end pressure builds
  • Send ambiguous matches to a clear review path
Intended
Visible
Confirmed
Matched
Gaps
Reviewable
What this step looks like
Confirm
Dispatched
09:42:12
Provider acknowledged
09:42:18
Bank confirmation
09:42:31
Settlement update
09:43:02
Stage 04

Export proof packs

Assemble the trail finance, compliance, and audit need - from original instruction through confirmation and decisions. No screenshot chase across five tools.

  • Link instructions, confirmations, and review decisions
  • Keep proof packs ready for disputes and audit questions
  • Export one package instead of rebuilding the story by hand
Evidence
Linked
Pack
Ready
Export
One package
What this step looks like
Proof
Proof pack completenessPreview
Ready
Preview
Bank confirmationLinked
Instruction trailLinked
Bank statementPending
Provider timelineIncluded
Bank statement matchIncluded
Bank confirmationIncluded
Operator action logIncluded
Export a proof pack in one click for audit, dispute, or merchant communication.

Same view for every team

Different teams, one payout truth

Zord keeps operations, finance, and engineering aligned without forcing each team to build its own version of payout state.

1

Operations

See where batches stand, which payments still need confirmation, and what needs review right now.

Batch statusPayment gapsNeeds a person
2

Finance

Compare meant-to-pay vs bank-confirmed amounts, reconcile gaps, and keep proof packs ready for close.

Meant to pay vs confirmedProof packsClose
3

Engineering

Keep one shared payout record next to existing payment systems so teams stop rebuilding the same status elsewhere.

Shared recordPayment sourcesIntegrations

From file to proof

One shared place to explain your payouts

Zord helps teams see meant-to-pay vs bank-confirmed money, resolve gaps, and export proof packs - without replacing your bank, gateway, or payment processor.

Back to landingBook Demo