The four capabilities
| Capability | Does | State |
|---|---|---|
| Match | Reconciles bank → payment → obligation → ledger. | In build |
| Collect | Takes money in on the best rail. | Planned |
| Pay | Sends money out on the best rail. | Planned |
| Optimise | Decides which rail and which day, from data. | Planned |
Optimise is the product. The other three exist so that it has something to reason over — a decision engine with no history of what payments actually cost and when they actually cleared is a set of assumptions, not intelligence.
Why this order
- Match is first because it moves no money, so it needs no processor relationship and carries no money-transmission exposure — while still exercising the entire canonical model and the connector contract.
- Collect and Pay follow because they are where the regulatory and operational weight is, and doing them second means doing them on a model that has already been proved.
- Optimise is last because it needs data. Building a rail-selection engine before there is any record of what rails cost in practice produces a model of somebody's assumptions.
This page describes an order, not a schedule. Nothing here should be planned around. If a capability matters to your decision, ask where it actually is rather than reading a roadmap.
What will not change
- Pey never writes journal entries. Not in Collect, not in Pay, not ever.
- Pey keeps its own database, separate from any ledger.
- The canonical model stays unlike any one system's schema.
- Portability is the product. A capability that only works against one ledger is not finished.
What this does not do
An order, not a schedule.
Collect, Pay and Optimise are planned.
Commercial terms are not set.
Questions
Can we be an early customer?
Ask. Match is the capability that exists.
Will Pey replace our payment processor?
It decides between rails. What that means commercially is not settled.
Does erp.io need Pey?
No. They are independent products.
Related
The first Pey capability: reconciling bank transaction to payment to obligation to general ledger, without moving any money.
PeyPey decides the economically best way to move money and does it on top of whichever ERP a customer already runs. A separate product from the erp.io suite, deliberately.