01
Morning
Overnight invoices are already structured, matched and coded. The AP lead opens a worklist of 14 exceptions — not 600 invoices.
← Suites · Suite · Procure-to-Pay
From request to payment, in a single line of evidence.
Requisitions, purchase orders, vendor onboarding, invoice capture, three-way matching, approvals, payment runs — one continuous record, every step auditable.
Most P2P stacks are a relay race: a requisition tool hands off to a PO tool, which emails an invoice tool, which exports a payment file someone uploads to the bank. Lunari folds the whole chain into one ledger. The same record that started life as a requisition becomes the journal that hits the GL — without re-keying, re-coding, or re-attaching.
lunari.cloud / p2p / inv-44218
Invoice INV-44218 · Northwind Logistics
Three-way match$ 18,420.00 USD
Purchase order
PO-2118
- Pallet handling · 200u$ 14,000.00
- Freight surcharge$ 3,200.00
- Documentation$ 1,220.00
Goods receipt
GR-991
- Pallet handling · 200u$ 14,000.00
- Freight surcharge$ 3,200.00
- Documentation$ 1,220.00
Invoice
INV-44218
- Pallet handling · 200u$ 14,000.00
- Freight surcharge$ 3,200.00
- Fuel adjustment$ 1,220.00
Line 3 description differs from PO — within tolerance, routed to Megan for one-click approval.
Chapter I · The process, end-to-end
From first event to posted journal.
- Requisition
- Purchase order
- Receipt
- Invoice
- Match & approve
- Pay
Chapter II · A day in the suite
The rhythm, hour by hour.
03 moments
02
Midday
A new vendor request comes in. KYC, sanctions screen and bank verification run before the requester finishes typing the PO line.
03
Close of day
A single payment run releases ACH, SEPA and wire batches. The evidence — PO, receipt, invoice, approval, remittance — is locked together against the journal.
Chapter III · Why it's different
Three things that aren't in the spec sheet.
The features any vendor will list. These are the architectural choices that change how the suite behaves at month thirteen.
I
No relay race
The PO record and the invoice record are the same record at different stages of life. Nothing copies, nothing drifts.
II
Exceptions, not invoices
AP humans only see the items the rules cannot finish. The straight-through stream never reaches their queue.
III
Bank-agnostic
Generate the file your bank prefers; keep your banking relationships untouched. Switch banks without re-implementing AP.
Chapter IV · What's inside
Capabilities in Procure-to-Pay.
04 capabilities, all on the same ledger and identity layer.
Vendor & purchase orders
Onboard vendors with controls. Issue POs that match the policy.
Read moreInvoice capture & 3-way match
Capture every invoice. Match every line. Pay with confidence.
Read moreExpense management
Cards, receipts and reimbursements that close themselves.
Read moreEvidence & document vault
One vault. Hashed. Versioned. Linked to every transaction.
Read moreChapter V · Outcomes reported
What teams measure after the switch.
Metric · 01
↓ 62%
invoice cycle time
Metric · 02
100%
match evidence retained
Metric · 03
↓ 78%
exception backlog
Chapter VI · Adjacent suites
What sits next to it on the platform.
Ready when you are
See Procure-to-Pay on your numbers.
We'll walk through your current process and show you the same flow inside Lunari.