One operational record
Provider, bank, ledger and billing events are held in one normalized record. Totals can be traced to the events behind them.
PulseControl
Financial operations, under control.
PulseControl compares what should have happened with what did, event by event, under rules your team sets. It raises exceptions when the two disagree and keeps the evidence together.
01 · Overview
A control layer, not a report.
Reports describe the past after the fact. PulseControl runs alongside operations, so a settlement that is short is flagged while the batch is still open.
Continuous matching
Matching runs as events arrive, not at month-end. Expected records come from your own systems and from provider reports.
Exceptions with context
An exception is never just a number. It arrives with its transaction, settlement, bank event and provider response linked.
Demo workspace · SandboxDemo state only. Actions never leave this page.
Processed₹24.8MLast 30 days · 3 gateways
Matched98.7%By value · 118 of 130 raised exceptions closed
At risk₹42.8KVariance on 12 unresolved
Transaction volume · reconciliation trend
30 days Daily processed Reconciliation rate
Exception summary
Raised · 30 daysHIGH121 open
MEDIUM373 open
LOW818 open
130 raised · 118 resolved · 12 open now.
System status
Critical systems operational- Gateway ALast event 2s ago
- Gateway BLast event 4s ago
- Gateway CLast event 3s ago
- Bank A feedStatement 09:14
- Bank B feedStatement 09:14
- ERP ledgerPosted 09:00
- Billing eventsLast event 6s ago
- Payout feedDelayed 2m
Recent activity
Today- 09:14:09Mismatch detected · PX-48291 · Gateway B · ₹42,580
- 09:02:41Batch STL-20931 evaluated · 1 of 4,812 events unmatched
- 08:47:12Payout feed delayed 2m · non-critical · monitoring
- 08:31:55PX-48243 resolved · rounding tolerance applied
- 08:12:03Rule "Provider hold ≥ ₹10,000 → HIGH" matched 1 event
- 08:00:00ERP ledger sync completed · 4,790 postings
Every figure in this interface is synthetic. No real customers, accounts or payment data.
Interactive demonstration. All figures are synthetic and actions affect this page only.
02 · Operational control loop
A closed loop, not a report.
Every event moves through the same eight stages, and resolved exceptions feed back into the controls. Select a stage.
Stage 05 · PulseControl
Detect
PulseControl identifies transactions that do not reconcile with expected settlement records.
Expected₹542,580
Actual₹500,000
Variance₹42,580
Illustrative · synthetic data
03 · Reconciliation
Expected against actual, by source.
Every source has an expected figure and an actual figure. Variances are computed, linked to events and routed to a case.
- One-to-one, one-to-many and many-to-one matching across provider, bank and ledger records.
- Tolerance rules for rounding and fees, set per source and per record type.
- Timing windows, so a credit that is a day late is treated differently from a credit that is wrong.
| Bank ABank | ₹12,400,000 | ₹12,400,000 | ₹0 | Matched |
| Bank BBank | ₹12,400,000 | ₹12,357,420 | −₹42,580 | Variance |
| Billing systemBilling | ₹3,184,200 | ₹3,184,200 | ₹0 | Matched |
| ERP ledgerLedger | ₹24,800,000 | ₹24,757,420 | −₹42,580 | Variance |
| Gateway AGateway | ₹8,200,000 | ₹8,200,000 | ₹0 | Matched |
| Gateway BGateway | ₹5,742,580 | ₹5,700,000 | −₹42,580 | Variance |
| Gateway CGateway | ₹10,857,420 | ₹10,857,420 | ₹0 | Matched |
| Marketplace payoutsPayouts | ₹1,926,400 | — | — | Pending |
Showing 8 of 8 sourcesAmounts in ₹ · synthetic data
Gateway B
Batch STL-20931 settled ₹42,580 below expected.
04 · Exception management
A queue ordered by risk.
Exceptions are ranked by severity and amount. Filter by status, search by reference and open any item for its full evidence.
| Exception | Amount | Severity | Status |
|---|---|---|---|
| PX-48291Settlement mismatch | ₹42,580 | HIGH | Open |
| PX-48284Settlement timing deviation | no amount impact | MEDIUM | Open |
| PX-48279Missing bank reference | no amount impact | MEDIUM | Open |
| PX-48276Duplicate provider event | no amount impact | MEDIUM | Open |
| PX-48274Fee rounding difference | ₹40 | LOW | Open |
| PX-48272Fee rounding difference | ₹35 | LOW | Open |
| PX-48269Fee rounding difference | ₹30 | LOW | Open |
| PX-48266Invoice rounding difference | ₹30 | LOW | Open |
| PX-48263Fee rounding difference | ₹25 | LOW | Open |
| PX-48260Ledger posting rounding | ₹25 | LOW | Open |
| PX-48257Fee rounding difference | ₹20 | LOW | Open |
| PX-48254Fee rounding difference | ₹15 | LOW | Open |
12 shown · 12 openSelect a row to investigate
Exception #PX-48291
Settlement mismatch
Gateway B · opened 2h 14m ago · owner Unassigned
HIGHOPEN
Expected₹542,580
Actual₹500,000
Variance₹42,580
The provider settled less than the transaction total and flagged a partial hold. The bank credit and the ERP receivable both reflect the lower amount.
Timeline
- Payment received14:02:11Captured via Gateway B · ₹542,580
- Provider settlement18:30:00Batch STL-20931 closed · ₹500,000 · status PARTIAL
- Bank record09:14:07Credit ₹500,000 posted · next day (T+1)
- Mismatch detected09:14:09Settlement mismatch · severity HIGH
Evidence
Transaction
- ref
- TXN-48291
- amount
- ₹542,580
- captured
- 14:02:11
- source
- Gateway B
Settlement
- batch
- STL-20931
- amount
- ₹500,000
- closed
- 18:30:00
- fee basis
- batch
Bank event
- credit
- ₹500,000
- posted
- 09:14:07 (T+1)
- reference
- BNK-48291
- account
- Operating ••42 (demo)
Provider response
- status
- PARTIAL
- reason
- HOLD
- held_amount
- ₹42,580
- release
- pending review
Suggested next step: Request hold release from the provider, then re-evaluate batch STL-20931.
Actions change this demo only. Nothing is sent anywhere.
Actions change this demo only. Nothing is sent anywhere.
05 · Investigation
Evidence assembled before anyone asks.
Opening an exception shows a timeline across systems and the four pieces of evidence that explain it. Actions are recorded as they happen.
Timeline across systems
Payment received, provider settlement, bank record and mismatch detection on one axis, each with its source and time.
Four evidence types
Transaction, settlement, bank event and provider response, shown side by side so the cause is visible without opening four systems.
Recorded actions
Investigate, escalate or resolve. Each action carries the actor, the time and the reason, and is added to the audit trail.
06 · Controls
Rules that operations can read.
Matching tolerances, severity thresholds and approvals are explicit settings. Turn a rule off and the behavior changes visibly.
Controls · demo workspace4 of 5 rules active
- Rounding toleranceMatched · no exception
Auto-match when |variance| ≤ ₹10 and the source is a fee line. - Provider hold escalationSeverity HIGH · notify
When provider status = PARTIAL and reason = HOLD, set severity HIGH and notify Finance Ops. - Settlement timing windowSeverity MEDIUM
Raise MEDIUM when the credit is later than T+1 by more than one business day. - Resolution approvalApproval required
Require a second approver to resolve any variance above ₹25,000. - Duplicate event suppressionPaused
Suppress the second event when provider reference and amount are identical.
Rules are explicit settings. Changes are recorded in the audit trail.
07 · Analytics
One chart that matters.
Volume and reconciliation rate share one axis of time, so a dip in match rate can be read against the day it happened.
Volume and reconciliation rate · 30 daysSynthetic data
Daily processed Reconciliation rate
Open exceptions by sourceSynthetic data
08 · Integrations
Fed by every system you run.
PulseConnect supplies PulseControl with normalized events from six categories of system.
PulseControlOne operational view
- Exceptions
- Alerts
- Reports
- API
01 · PaymentsDemo connector model
- Supplies
- Authorizations, captures, refunds, settlement batches and provider responses.
- Connection methods
- API · webhooks · settlement files
- Typical source
- Payment gateway · acquirer · payout provider
09 · Security
Controls that behave as a finance team expects.
Access, audit and isolation are part of how the product works, not an add-on.
ControlBehaviorWhere you see it
EncryptionData is encrypted in transit and at rest.Platform-wide
Role-based accessPermissions are granted by role and by connected source.Settings · Access
AuditabilityEvery action is recorded with actor, time and before-and-after state.Audit log
Secure credentialsSource credentials are stored and handled as secrets and are never shown in the interface.Source connections
Data isolationEach workspace's data is kept separate from every other workspace.Workspace boundary
MonitoringIngestion health and delay are observed continuously and shown to operators.System status
API securityAPI access is authenticated, scoped to a workspace and rate limited.Developer settings
Enterprise access controlsPlannedSingle sign-on and policy controls for larger teams.Settings · Policies
See PulseControl with your own systems in mind.
Tell us which systems your team reconciles today. We will show you how the platform would handle them.