Build the run→ Route→ Pay→ Reconcile

Approved invoices,
waiting to be paid.

Eight approved invoices across four countries. Pick what goes in the run and the policy it runs under; PayRail chooses a rail for each one and tells you why it chose it.

	Vendor	Destination	Due	Amount

Run policy

What the router optimises for, and the controls finance asked for.

Cheapest rail that meets the due date Fastest rail available

Second approval over $50,000 Validate bank details before sending

Selected

8 invoices

$0

Add an invoice

Yours goes through the same checks as the eight above. US accounts are validated against the ABA checksum, European and UK ones against IBAN mod-97, so a number that is wrong will be caught here rather than by the bank.

Build the run→ Route→ Pay→ Reconcile

Every payment on a rail,
with the reason.

Vendor	Rail	Lands	Amount	Fee	Status

Rails, fees and cut-off times here are illustrative and set in this file. In a deployment they come from your bank agreements, and the router reads them rather than assuming them.

Build the run→ Route→ Pay→ Reconcile

Released, returned,
and matched to the books.

The bank statement came back. Matching runs against your ledger, and what did not match is an exception with an owner rather than a line in a spreadsheet.

Payments

Vendor	Rail	Sent	Received	Reconciliation

Click a row for the audit trail.

Exceptions

Each one is routed to whoever can resolve it.

Approved invoices,waiting to be paid.