FAQ

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 bank details before payment. It compares the bank details shown on an invoice against the supplier fingerprint already trusted by your business, then gives a clear risk result before payment is approved.

How does Lumra fit into the payment workflow?

+

Lumra is designed to sit just before payment approval. A user starts with an unpaid bill in Xero, checks the bank details shown on the invoice, and sees whether those details still match what is already trusted.

Does Lumra replace our accounting system?

+

No. Lumra is not an accounting platform. It adds a practical verification step before payment so teams can make a safer decision using the invoice and supplier details already in front of them.

Does Lumra work with Xero?

+

Yes. Lumra is currently focused on a Xero-connected workflow. It can load unpaid bills from Xero and prefill supplier identity details so users can review the invoice in the right context.

What happens if the bank details do not match?

+

Lumra 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 payment details your business has already verified. Lumra uses that fingerprint as the comparison point when checking future invoices.

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.

Still deciding?

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.