Documentation

Overview

PulseControl brings financial events from many systems into one normalized record, compares expected and actual events, raises exceptions and provides a workspace to resolve them. It is organized in three layers: PulseConnect, PulseControl and PulseResolve.

Concepts

Core concepts
Concept	Definition
Source	A connected system that supplies events: a gateway, a bank feed, an ERP ledger, billing or an internal service.
Event	A normalized record of something that happened, such as a payment, settlement, credit or posting.
Expected record	What should have happened, derived from your systems or a provider report.
Match	An expected record and an actual event that agree within tolerance and timing rules.
Exception	A difference that remains after tolerance and timing are applied.
Case	The workspace for one exception: timeline, evidence, owner, actions and audit trail.

Quickstart

Create a workspace and a scoped API key.
Connect a source, or submit events through the API.
Define expected records, or import a provider settlement report.
Review matches and exceptions in the Command Center.
Register a webhook so exceptions reach your own tools.

Quickstartillustrative

"# 1. Create a scoped key in Settings, then submit an event"
curl -X POST https://api.concicohq.example/v1/transactions \
  -H "Authorization: Bearer $PULSE_API_KEY" \
  -d '{"source":"gateway_b","amount":"542580.00","currency":"INR","reference":"TXN-48291"'}

"# 2. Register a webhook for exceptions"
curl -X POST https://api.concicohq.example/v1/webhooks \
  -d '{"url":"https://your-service.example/pulse","events":["exception.created"]'}

Reconciliation rules

Rules decide what is a match, what is timing and what is an exception. They are explicit, can be paused, and each change is recorded in the audit trail.

Ruleillustrative syntax

"# Illustrative rule syntax"
"rule" "provider_hold_escalation"
  "when"  provider.status == "PARTIAL" "and" provider.reason == "HOLD"
  "then"  exception.severity = "HIGH"
          notify("finance-ops")

Exception lifecycle

Exception states
State	Meaning	Next
Open	Raised and unowned.	Investigating, Escalated, Resolved
Investigating	An owner is working the case.	Escalated, Resolved
Escalated	Routed to a lead or approver.	Resolved
Resolved	Closed with a reason and evidence.	—

Webhooks

State changes are delivered as signed events: exception.created, exception.escalated, exception.resolved, source.delayed and reconciliation.completed. Full payloads are shown on the developer platform page.

Glossary

T+1: One business day after the transaction date.
Variance: The difference between an expected and an actual amount.
Tolerance: A permitted difference below which records are treated as matched.
Idempotency key: A client-supplied value that makes a retried write safe.