Skip to content
Payvol

Payvol Connect

The last mile of a payment is somebody's existing system.

Connect will carry a reconciliation record out to the software a finance team already runs, in the shape that software expects. Nobody changes their ERP to accept a better payment format.

Start with the record See all modules

one recordthin adapters

Not built yet. There is nothing to install.

What it will do

One record underneath, and an adapter per system.

The reconciliation record exists today: Reconcile returns it, with its fields typed in the package. Connect adds the adapters that would carry that record into named finance systems.

What exists, and what does not yet

Solid and dashed

The left column is the record Reconcile returns. The right column is the set of adapters Connect will add. A team can map the left column into its own system now.

The record does not change shape to travel

One record underneath

An adapter will render it as a journal line, an API call, or a bank message. The record underneath stays identical, so two systems fed by two adapters still agree about what happened.

Adapters fit their system, not the other way round

Their schema wins

Their schema is a decade old, their release train is quarterly, and an auditor already signed off on it. An adapter will absorb the mismatch rather than ask the target to change.

ISO 20022 alignment is a checklist, not a claim

Aligned, not compliant

The data model lines up with the request-to-pay message family. Compliance is a different word: it needs a validated sample accepted by software Payvol did not write.

How it will work

Take, shape, deliver.

01

Take

  • Read reconciliation records as they are appended
  • Keep the ones a given target cares about
  • Follow the supersession chain, never the first version alone

02

Shape

  • Map fields into the target's own vocabulary
  • Write down what the mapping loses, in the adapter's own docs
  • Refuse to invent a field the record does not contain

03

Deliver

  • Push, or wait to be pulled, whichever the target prefers
  • Retry without producing a second posting
  • Leave a local trail of what was delivered and when

Scope

What Connect will leave to your systems.

It does not post to your ledger An adapter delivers a record. Whether that becomes a journal entry is your accounting system's decision, under your controls and your approvals.
It does not interpret accounting No revenue recognition, no tax treatment, no classification beyond what the reconciliation record already states.
It does not become a hosted integration service Adapters run where your records are. There is no Payvol middleware sitting between your ledger and your ERP.
It does not claim a standard it has not passed Alignment is stated. Compliance needs a validated sample and a successful import into software Payvol did not write.

Who it is for

Finance teams whose ERP, treasury system or bank expects payment data in its own format.

Connect is part of these situations.

Get started

Start with the record it will carry.

The record it will carry is the one Reconcile returns, so a team can map those fields into its own system today and keep that mapping when an adapter arrives.

The record it will carry See a record produced