A practical verification step before money leaves your account.
Lumra helps businesses verify Xero pay runs before payment. It fits into the approval step that matters most: after bills are entered, but before money is released.
Owners, bookkeepers and finance teams who want a clearer answer before payment.
How Lumra works in practice
Lumra is designed to fit into a workflow your team can actually use. It starts with your unpaid bills in Xero and ends with a clearer decision before payment.
Update your unpaid bills in Xero
Keep using Xero as your source of truth. Once your unpaid bills are entered and ready for a pay run, open Lumra to verify the payment details before money leaves the business.
Load the pay run into Lumra
Lumra pulls the unpaid bills from Xero and pre-fills the supplier name, ABN, domain, BSB, account number and account name where available.
Verify the payment details
Lumra compares the Xero payment details against the supplier fingerprint already trusted by your business and highlights anything that needs attention.
Clear safe bills or review exceptions
Safe bills can be marked as cleared in Lumra. Bills with mismatches or risky changes are moved into Needs review so they are not lost in the pay run.
Verify changes before paying in Xero
If something does not match, Lumra tells your team to stop and verify the change with a trusted supplier contact before the payment is processed in Xero.
What Lumra checks before payment
Lumra focuses on the details that can change a payment outcome: the supplier identity, the bank details held against the Xero bill, and whether those details still match what your business already trusts.
Bank-detail matching
Checks whether the BSB, account number and account name from Xero match the supplier fingerprint already trusted by your business.
Supplier identity checks
Highlights ABN and domain mismatches so teams can spot identity issues, not just bank-detail changes.
Pay-run queue
Separates bills into To verify, Needs review and Cleared so finance teams can work through a pay run without losing track of exceptions.
Verification history
Keeps useful records of scans, decisions and security activity so your team can see what was checked, what changed, and when it was verified.
Lumra helps your team respond properly when something does not match.
If the invoice bank details do not match what is already trusted, Lumra does not ask your team to guess. It tells them to stop, verify the change with a trusted supplier contact, and only save new details after callback verification.
That keeps the workflow practical while still building a stronger payment control.
- ✓Clearer decisions before payment approval
- ✓Less guesswork when supplier details change
- ✓A stronger callback-verification habit
- ✓Useful records of what was checked and when
See how Lumra fits into your payment approval workflow.
A simple, practical verification step before money leaves the business.