FAQs
Frequently Asked Questions
Have questions about Lowki.ai? We've got answers. Browse our most common inquiries below.
What is Lexi?
Lexi processes sales orders and invoices directly into Epicor Kinetic using generative AI. It reads customer emails, extracts key information, and prepares everything for your ERP — driving up to an 80% increase in order processing throughput.
Why choose Lexi over more traditional AI integration tools?
Lexi is built end-to-end around the order entry workflow, not just data extraction. It's natively integrated with Epicor Kinetic, has been hardened in live production for over 20 months, and links ERP entries back to the original email conversation and attachments — giving your team full visibility and quick access when working from shared inboxes.
How does Lexi integrate with Epicor Kinetic?
Lexi uses Epicor Kinetic's REST API so data passes through your existing business logic. It works within your current validations, rules, and processes rather than bypassing them.
How is our data handled and secured?
Lexi runs as a Docker container on infrastructure managed by lowki.ai, with enterprise-grade security practices and GDPR compliance. Your order data is processed to fulfil your orders and is never used to train external AI models. We're happy to walk your IT and information security teams through our architecture in detail.
What happens to the original email and attachments?
The original email and its attachments stay in your Exchange Online mailbox where they belong. Lexi adds a link from the Epicor order straight back to the email — so when a customer rings up about their order, you're one click away from their original message instead of hunting through someone else's filing system. The link keeps working as long as the email stays within the same mailbox, so your team is free to file it into whatever folders, sub-folders, or archives suit how you work.
Who can see the linked emails, and what about retention policies?
Access follows your existing Exchange Online permissions: only users with rights to the mailbox can open the linked email from Epicor, so Lexi doesn't change who can see what. The link itself will become inaccessible if your retention policies delete the email or if it's migrated out of the mailbox — so it's worth aligning email retention to how long you want to be able to trace orders back to their source.
What happens if Lexi can't read an order, or gets something wrong?
Lexi is designed with human-in-the-loop review at its core. Anything Lexi can't confidently process — unfamiliar customers, ambiguous part numbers, missing fields — is flagged for your team to review.
How is Lexi priced?
Lexi is offered on monthly billing across four tiers — PAYG, Production, Growth, and Scale — with pricing based on the number of order lines processed. All tiers include onboarding training and business-hours email support. Full pricing is available on our pricing page.
How long does implementation take?
Implementation is typically completed within a day. This includes setup, Epicor integration, testing, and onboarding your team. Most customers are processing live orders by the end of day one.
What kind of accuracy can I expect?
Lexi has demonstrated 98% customer matching accuracy, 97% ship-to address accuracy, and 95% PO number accuracy in production environments processing more than 40,000 orders. It is designed to work out of the box with minimal setup.
Do we need to train Lexi like other AI document extraction tools?
No. Lexi is designed to deliver value from day one without the need for template building or ongoing training.
Does Lexi only process sales orders?
Today, Lexi is focused on sales order automation. We have also implemented accounts payable invoice logging and matching, with plans to expand further into finance and other back-office processes.
What email systems does Lexi work with?
Lexi currently integrates with Microsoft Exchange Online. If you use another email platform, talk to us — we're actively expanding integrations.
Can I only get documents into Kinetic via email?
No. You can also drag and drop documents directly onto an order in Kinetic and mark them as 'AI Needs Processing'. Lexi will then read the document and populate the order. This is useful for documents that didn't arrive through your monitored sales inbox — orders forwarded internally, received via personal email, or sent as follow-ups to phone calls.
Will it work with my Epicor customisations?
Yes. Because Lexi works through Epicor's REST API, your existing Method Directives and Data Directives still apply. That helps ensure processing stays aligned with your current business rules and system behaviour.
Will it work on-prem or cloud?
We support both on-prem and cloud so no one is left out in the cold. For the more technical minded we just need access to your REST endpoints like any intergration system needs from Kinetic.
Are there plans for a dashboard?
Yes. We are exploring dashboards to give teams better visibility of processed orders and activity. In the meantime, your IT team can surface this data using Epicor BAQs and dashboards filtered by the integration user account.
Why was Lexi created?
Lexi was created to solve a real operational problem: too much time spent on manual order entry. It was built to free up teams for higher-value work while improving speed, consistency, and visibility.
What is AP invoice logging?
Lowki.ai reads inbound supplier invoices from your email, splits multi-invoice PDFs, and creates a logged AP invoice batch in Kinetic's Logged AP Invoice Entry, posted to the suspense account. Liability is recognised and tax recovered, with nothing committed to your real accounts until a person approves it. Both the logging and the approval happen in the Kinetic screens your team already uses.
What is AP invoice matching?
Once a logged invoice is approved, Lowki.ai pulls it into an invoice group and runs matching by driving Kinetic's own Get Receipts, validating the goods receipts against the invoice. Kinetic shows the result as the group balance: a balanced group is matched, a residual variance is a mismatch. Lowki.ai adds notes against any invoice where it sees a problem, so your team knows where to look before posting.
Does Lowki.ai post or pay invoices automatically?
No. Lowki.ai does the entry and the matching, but a person always approves the logged invoice and a person always posts the group. It never posts on its own, the same way it never takes a sales order off hold. The ERP stays the source of truth and every commit decision stays with your team.
Why automate accounts payable?
The case is financial control, not headcount. Automated logging and matching helps catch duplicate payments, flags price drift between the purchase order and the invoice, and helps you capture early-payment discounts. At lower invoice volumes the time saving is modest; the value is in the control.
