How it works

When an invoice enters PayShore (whether uploaded from email, generated from a payment request, or created directly), it carries a reference that travels with it through every step. The approval that authorizes payment links back to the invoice. The payment instruction that goes to the bank links back to the approval. The bank's settlement confirmation, when it arrives, links back to the payment. By the time the activity hits your general ledger, every entry is already tied to the invoice it paid against and the approval that authorized it.

The result is that reconciliation isn't a step finance has to assemble at month-end. It's already done, as a byproduct of how each payment moves through the system.

What this looks like at the close

The most visible change is what doesn't happen anymore. Finance teams using PayShore don't export bank transactions and match them against invoices in a spreadsheet, because the match already exists. They don't ask "which invoice did this $10,500 payment cover?" because the payment record knows. They don't reconstruct who approved what, because the approval is attached to the payment that resulted from it.

The exception report still exists (payments that didn't match a known invoice, invoices that didn't get paid on schedule), but it's a short, real exception report, not a manufactured one.

What's stored with each payment

Every payment in PayShore carries:

  • The originating invoice, or a clear note that no invoice applies (for example, a transfer between your own accounts)
  • The approval chain: every person who reviewed and approved, with timestamps
  • The bank instruction that was sent, with confirmation when received
  • The settlement record from the bank
  • Any notes or attachments added during the approval process

All of which exports cleanly to a CSV or PDF when an auditor or controller asks.

Why this matters

Reconciliation is one of those finance functions that gets treated as inevitable: a thing that has to happen at month-end because that's when the data comes together. It doesn't have to be that way. When the data is connected at the moment of the transaction, reconciliation is just the steady state of a properly designed system.

PayShore is built for that. Invoices, approvals, and payments are linked by design, not by reconstruction. Which means month-end is the same workload as mid-month. And the close is a checklist, not a project.