Payvol Connect
The last mile of a payment is somebody's existing system.
Connect carries 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.
See what ships today See all modules
one recordthin adaptersnot written yet Planned
The design is settled. The code is not written, so this page carries no measurements.
Today and not yet
This module is planned. Here is exactly what that means.
The canonical export exists and is documented: a reconciliation record in a stable shape, emitted locally, which a team can integrate against by hand today. What does not exist yet are the named adapters that would remove that hand work.
The design is settled. The code is not written, so this page carries no measurements.
What is real, drawn honestly
Solid and dashed
The left column is in the repository. The right column is a plan. We would rather you integrate against a small real thing than wait for a large described one.
The record does not change shape to travel
One record underneath
An adapter renders it as a journal line, an API call, or a bank message. The canonical record underneath stays identical, so two systems fed by two adapters still agree about what happened.
We adapt to them, 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. That is not a flaw to be fixed by the newcomer. The adapter absorbs the mismatch.
ISO 20022 alignment is a checklist, not a claim
Not yet compliant
Our data model lines up with the request-to-pay message family, and that is a useful thing to say. Compliant is a different word, and it needs a validated sample and somebody else software accepting it before we use it.
How it will work
Take, shape, deliver.
01
Take
- Subscribe to reconciliation records as they are appended
- Filter to the ones a given target cares about
- Respect the supersession chain, never the first version alone
02
Shape
- Map fields into the target own vocabulary
- Write down what the mapping loses, in the adapter 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
Three ways to reach a finance system
The last one is the only one that survives an upgrade.
01
Ask them to change
a new format for everyone
Publish a shape and expect the ERP, the treasury system and the bank to adopt it. Technically clean, and it has never once happened on schedule.
A migration nobody agreed to fund
02
One-off scripts
glue per customer
Write a bespoke exporter for each integration. Fast at first, and every one of them becomes a small private product with its own bugs and its own owner who left.
Maintenance that grows with every deal
03
Adapters over one record
Payvol Connect
One canonical record, and a thin adapter per target that is versioned, documented and replaceable. When a target changes, one adapter changes and nothing upstream notices.
The blast radius stays one file
Boundaries
What Connect deliberately does not do.
This module touches other people systems of record, which is precisely why its limits are written before its features.
For teams integrating today
You do not have to wait for the adapters.
The canonical export is stable and documented. Read it, map it once into your own system, and when a named adapter arrives it will produce the same fields you already handled.
There is no code sample on this page. The adapters are not written, and an API that does not exist cannot have a signature. The record they will carry is the one Reconcile already produces, and that one you can read today.
Where it is used
2 of the six situations reach Connect.
Tell us which system you need to reach.
The order the adapters get written in should be decided by the teams who need them, not by us guessing.