Runtime as featured inForbesRead the article

Payment operations

Trace the reconciliation break. Prepare the next step.

Investigate settlement differences and suspense-account exceptions across payment records, bank files, and your ledger. Review the evidence before adjustments post.

Book a demo
Start for free
Illustrative workflow · Sample data
Runtime session · payment-ops-agent
ER
Elena Rossi

The morning bank file and ledger differ by $43,050. Can you trace the variance and prepare the next steps?

payment-ops-agentRuntimeworking

I’ll compare the settlement references, bank activity, and ledger entries. Any adjustment will stay in draft.

Read the bank activity file
Matched settlement references
Checked the pending batch
Compared settlement fees
Prepared a fee adjustment draft
5 tool calls · variance explained

The $43,050 difference consists of a $41,800 batch still awaiting bank settlement and a $1,250 fee missing from the ledger. I prepared a settlement follow-up and a fee-entry draft with source references. No entries have been posted.

Review reconciliationView fee draft
Message payment-ops-agent

Trusted by teams running mission-critical operations.

RainNixtlaMonoLineLeap

Give every exception a clear investigation.

Specialized agents compare the records, research mismatches, and prepare supported next steps for your payments team.

Explain the difference

Trace unmatched amounts through settlement batches, timing differences, fees, and ledger entries.

Work the exception queue

Investigate suspense items and missing references, with unresolved cases routed to the right owner.

Prepare reviewed adjustments

Draft the correction or follow-up with source files attached and approval required before posting.

Follow the amount across the payment lifecycle.

Compare the source records

Match processor reports and bank activity with the ledger, preserving the references behind each difference.

Modern TreasuryStripeInternal ledger
Evidence · payment-ops-agentready for review
Read the bank activity file$43,050 variance against the ledger
Matched settlement referencesOne batch pending bank settlement
Checked the pending batch$41,800 timing difference
Compared settlement fees$1,250 fee not yet recorded
Prepared a fee adjustment draft$1,250 · sources attached

Resolve with the evidence attached

Separate timing differences from corrections. Let your team review journal drafts, payment instructions, and unresolved exceptions.

NetSuiteMicrosoft Teams
Awaiting your team

Reconciliation review ready

$43,050 variance · timing difference and unposted fee

Review reconciliationRequest changes
$41,800 settlement timing identifiedfollow-up
$1,250 fee entry draftedreview required
No ledger entries postedread-only

Connect payment records to the books.

Bring the processor, bank, and accounting records needed to investigate the exceptions in your reconciliation process. Systems shown are examples; connector availability, API access, and permissions are confirmed during setup.

Payment and settlement records

Follow the flow of funds

Read approved settlement batches, transfer references, and bank activity to trace an unmatched amount.

Modern Treasury
Stripe
Column
Marqeta
Accounting and internal data

Match against your ledger

Compare the accounting records and exception history, then prepare supported adjustments or follow-ups.

NetSuite
QuickBooks
Internal ledger
Snowflake

How Runtime works

Define one reconciliation process and the evidence your team needs before resolving an exception.

01

Create a payments agent

Add matching rules, timing tolerances, and exception-handling procedures.

02

Connect the records

Scope access to processor reports, bank files, accounting systems, and the ledger.

03

Investigate the breaks

Run on a schedule or new file. Trace mismatches and prepare evidence-backed next steps.

04

Approve the resolution

Review corrections, route unresolved items, and approve any accounting or payment action.

Book a demo

Investigate freely within read-only boundaries.

Read about our security
AuditedSOC 2Compliant

Separate reads from writes

Start with read-only access to files and ledgers. Enable adjustment tools only with explicit permissions.

Approval before posting

Keep journal entries, payment instructions, and exception closure behind your review process.

A traceable reconciliation

Retain the source references, comparison steps, drafts, and decisions under your data policies.

Payment operations: common questions

01What kinds of reconciliation breaks can agents investigate?
Examples include settlement timing differences, missing references, unposted fees, and suspense-account items. Configure the matching criteria and source records for the process you want to evaluate.
02Can we keep our existing reconciliation engine?
Yes. Its exception output can be the starting point. The agent can research the breaks using the approved sources and prepare next steps for the operations team.
03Does an agent post journal entries automatically?
Start with draft-only adjustments and read-only ledger access. Any posting capability should be explicitly enabled and subject to your authorized approval process.
04How does it handle settlement timing differences?
Your procedure defines the expected settlement windows and tolerances. The agent compares dates and references, identifies apparent timing differences, and flags items that still need confirmation.
05Can this run when new bank or processor files arrive?
Yes, using an approved event trigger or schedule. Define file access, the records to compare, and where the investigation output should go.
06What is a useful demo dataset?
Bring anonymized processor and bank files, corresponding ledger records, and a few known exceptions. The demo can show how each difference is traced and prepared for review.

See a reconciliation break explained.

Watch an agent trace the difference across payment records and prepare the next step for your team.

Book a demo
Start for free