What Pey is
Pey works out the economically best way to move money — which payment rail, on which day, at what cost — and then moves it, on top of whichever accounting system a business already runs. The value is a payment graph fed by many ledgers, and a graph built from one small ERP's users is a thin graph.
That is why it is documented here as a separate product rather than as a thirteenth module. It has its own repository, its own database, and a design constraint that only makes sense if it is genuinely portable.
The rule that keeps it honest
It emits events; the connected accounting system books them. That keeps the ledger authoritative, keeps Pey genuinely portable, and means a QuickBooks customer gets exactly the same product an erp.io customer does. Break it once and Pey is an erp.io feature with extra steps — which would be a smaller product with a smaller market, and would quietly make the ledger answerable to something outside itself.
| Pey does | Pey does not |
|---|---|
| Decide which rail to pay on. | Post the payment to your ledger. |
| Reconcile bank → payment → obligation → GL. | Own the general ledger. |
| Emit an event when something happens. | Book that event itself. |
| Hold a canonical model of payments. | Mirror any one ERP's schema. |
Where it is today
Pey is in build. The service exists, the canonical model exists, and there is no customer-facing application yet — which is why this section is marked In progress and why Pey does not appear in the erp.io module list as something you can switch on.
The first capability: reconciling bank, payment, obligation and ledger.
ConnectorsIn progressHow Pey reads a ledger, and which ledgers are planned.
RoadmapPlannedMatch, then Collect, Pay and Optimise — and why in that order.
Both were learned expensively elsewhere and cost nothing to get right here. Money is an amount plus a currency, never a bare number — retrofitting currency onto columns that assumed one took four separate changes. And tenancy is a required column with no default — a default lets a write land silently in the wrong tenant.
In this section
The first Pey capability: reconciling bank transaction to payment to obligation to general ledger, without moving any money.
ConnectorsIn progressHow Pey reads a ledger, the first connector, and why the connector contract matters more than the first system it connects to.
RoadmapPlannedMatch, then Collect, Pay and Optimise — the order Pey is being built in, and the reasoning behind it.
What this does not do
Pey is a separate product with its own account. It is not in the erp.io module list.
The service exists; there is no customer-facing interface.
By design, permanently.
Match moves no money. That is deliberate — see Match.
Questions
Will Pey work with QuickBooks and Xero?
That is the point of the design. They are planned connectors against the same canonical model.
Is Pey included in an erp.io plan?
No. Separate product, separate commercial relationship.
Why document it here at all?
Because people ask what it is and how it relates to the suite, and the answer is more useful than silence.