Pey: know what every deposit was for

A deposit lands for an odd amount. Is that the fleet customer paying two invoices at once, short a bank fee? Is it the card takings from last week? A payment went out to a distributor for less than the bill. Was that the early-pay discount, or did someone short-pay by mistake? Answering those questions line by line is what eats a Friday afternoon.

Pey does that work. It reads your obligations, the invoices you have issued and the bills you owe, and your bank transactions from the connected ledger. Then it matches each transaction to what it paid, classifies any difference, such as a payment short by a wire fee or one transfer settling two invoices, and explains every suggestion it makes.

You confirm, reject or reopen a match. If Pey had nothing, you can match by hand or mark the line as having no invoice behind it. Where exactly one suggestion clears the confidence threshold, you can confirm a batch in one go.

Shops buy a lot of parts and accessories, and some suppliers offer terms like a small discount for paying within ten days instead of thirty. On one bill that is a few dollars. Across a year of weekly bills it can be real money, but only if the cash to pay early costs you less than the discount is worth.

Pey ranks those discounts against your own cost of capital and shows you which ones are worth taking and by when. It does not move any money and does not schedule a payment; it gives you the list, and you pay from wherever you pay today.

That restraint is on purpose. Pey is built to recommend and to match, not to hold or send funds. Collecting and paying through Pey appear in its sidebar as coming soon, and they are not built.

Pey never writes journal entries. It reads from the connected ledger and queues what it concludes as events for the ledger to act on. Today its connector is erp.io Accounting, read through an organization-scoped API key; QuickBooks and Xero are planned later against the same model. Because the Accounting API is read-only today, those events show as undelivered in Pey until Accounting accepts them.

The Service plan puts Pey in the payment chain: customers pay repair invoices through Stripe inside Service, the payments post to Accounting, and Pey matches them to the bank deposits. Service invoices are live, but payments against them are recorded by hand and nothing posts to Accounting yet, so today Pey matches what is already in Accounting.

Pey keeps its own database, separate from the ledger it reads, and it refuses to sync a partial set of invoices rather than match against half the picture. That matters more than it sounds: matching against a truncated list does not fail loudly, it reports real payments as unexplained and sends someone hunting for problems that do not exist.

Monday morning is when most owners look at the bank. With Pey, the list waiting for you is short: the matches it is confident about, ready to confirm in bulk, and the handful it could not explain, each with a reason. A bank charge nothing accounts for sits at the top instead of hiding in a spreadsheet.

The discounts list is the other half. Before you pay the week of supplier bills, check which ones carry an early-payment discount that is worth more than the cash costs you, and which deadlines are this week. If a connection to the ledger breaks, Pey emails you once for that outage, not once an hour.