Common questions about Lumra.
Lumra is built to help businesses verify supplier bank details before payment. Here are the questions most people ask when deciding whether it fits their workflow.
What does Lumra do?
+
Lumra helps businesses verify supplier payment details before payment. It loads unpaid bills from Xero, checks supplier identity and bank details against trusted supplier fingerprints, and gives a clear result before the pay run is processed.
How does Lumra fit into the payment workflow?
+
Lumra sits between bill entry and payment. Your team keeps bills up to date in Xero, loads the unpaid pay run into Lumra, clears safe bills, and reviews anything unusual before paying in Xero.
Does Lumra replace our accounting system?
+
No. Lumra does not replace Xero or your accounting workflow. It adds a focused verification layer before payment so teams can make a safer decision using the supplier and payment details already connected to the bill.
Does Lumra work with Xero?
+
Yes. Lumra is currently focused on a Xero-connected workflow. It loads unpaid bills from Xero and can prefill supplier name, ABN, domain, BSB, account number and account name where available.
What happens if the bank details do not match?
+
Lumra moves the bill into Needs review and tells the user to stop and verify the change with a trusted supplier contact before payment is approved. New details should only be saved after callback verification.
What is a supplier fingerprint?
+
A supplier fingerprint is the set of trusted supplier identity and payment details your business has already verified. Lumra uses that fingerprint as the comparison point when checking future Xero bills.
Can Lumra detect every kind of fraud?
+
No. Lumra is not trying to solve every fraud problem in a business. It is focused on one important control point: helping teams catch risky supplier payment changes before payment is approved.
Who is Lumra for?
+
Lumra is designed for business owners, bookkeepers, and finance teams who want a practical, repeatable check before supplier payments are approved.
Do we still need to callback verify changes?
+
Yes. Callback verification is a core part of the workflow. Lumra helps identify when a change needs attention, but trusted verification is still required before new details are saved as safe.
Is there a starter plan?
+
Not yet. Right now Lumra is focused on the Xero-connected workflow that gives the clearest value before payment. A lighter entry plan may come later.
See the product and decide whether the workflow fits your team.
Lumra is focused on one clear step: helping businesses catch risky payment changes before money leaves the account.