Tools we've built to solve problems users actually have.
Born out of real Acumatica implementation and support work, built by consultants who use them every day.
The problem line is already on your screen. Lumi makes sure you see it.
No-code highlight rules for Acumatica. Lumi colors the rows and cells that need attention — thin margins, missing costs, lines you cannot ship — across 15 entry and processing screens, using rules your own team writes in minutes.
Caught at entry.
Not discovered in a variance report three weeks after it posted.
No code, no developer.
Every rule writes its own plain-English summary as you build it.
40+ rules included.
Activate the ones that fit, move the thresholds, switch off the rest.
Watch Lumi in action
Who changed what, and when.
Acumatica's field-level audit history, turned into a plain-English timeline you can read in one pass — and paste into a ticket.
Unofficial — not affiliated with, endorsed by, or sponsored by Acumatica, Inc.
The problem
With field-level audit switched on, the Audit History screen is complete and unreadable. Adding one line to a sales order writes around 200 columns, of which maybe eight mean anything to a person — the rest are derived totals, base-currency mirrors, validity flags and counters. Working out what actually happened means eyeballing red and green cell pairs across a dozen collapsed batches, newest first.
What it gives you instead
4 recorded actions on Sales Order SO004417 by dmorgan@northwind.example and tlawson@northwind.example between 8/5/2026 4:45 PM and 8:15 PM.
- 4:45 PM · dmorgan — created sales order SO004417 — customer C01187 (HOLLAND, MARIE), customer PO 40928-02; added line 1 — 2 EA of HBX 480J10 (POLY-V BELT 10 RIBS, 48") @ $19.63 = $39.26; system recalculated tax — order total $39.26 → $41.75 (tax $2.49)
- 4:45 PM · dmorgan — printed the sales order
- 4:49 PM · dmorgan — flagged line 1 for drop-ship purchasing (warehouse 14)
- 8:15 PM · tlawson · Purchase Receipts (PO302000) — confirmed a shipment — 2 of line 1 shipped, completing the order
Sample data. Every sentence above is generated locally by rules inside the extension — no AI service is called.
What it does
Reads forwards.
One click gives a one-line overview, a bullet per business action, then the full chronological timeline. Acumatica lists changes newest-first, which tells the story backwards.
Plain English, not field names.
"Flagged line 1 for drop-ship purchasing" instead of eight columns of flags and counters. Every entry expands to the underlying field-level diff.
Signal over plumbing.
Counters, currency mirrors and validity flags sit behind a toggle — hidden, never discarded. Type in the filter box to answer "did anyone touch the unit cost?" without scrolling.
Complete, not just what's on screen.
The audit list is virtualized, so scraping the page silently truncates history. This reads Acumatica's own data instead — and says so plainly if anything could not be loaded, rather than summarizing a partial history.
Copy for a ticket, or for AI.
Take the timeline as markdown for an email, or a compact digest prefixed with your own prompt. Built-in presets run from "explain what happened" to an internal-controls review.
Free, private, open source.
No accounts, no analytics, and no network requests of any kind — not even to us. Audit data never leaves your browser. MIT-licensed — read the code yourself.
Works on the modern Audit History screen (SM205540) and on the classic-UI audit window found on older instances — including correcting that window's timestamps.
Why we built it
We get handed "this order is wrong, find out why" across a dozen customer instances a week. The answer is nearly always sitting in the audit history, buried under two hundred columns of counters and currency mirrors. So we built the thing that reads it for us, and it's free for the whole Acumatica community.
One click from error to answer.
Copy Acumatica trace exceptions to your clipboard — clean, complete, and ready to paste into Claude, ChatGPT, or any AI assistant.
The problem
An error hits. You open the trace and there are four exceptions, each with a stack trace hidden behind "Show more." You click, drag-select, miss half of it, and paste mangled HTML into your AI assistant — which then asks you which screen and action caused it. Information the trace grid knew all along.
What it does
One click, whole trace.
Grabs every exception on the page, auto-expanding every truncated "Show more" stack trace first — no drag-selecting, nothing missed.
Context included.
Captures the screen ID, command, request type, time, and duration of the request that caused the error — the first things anyone, human or AI, asks for.
Built for AI debugging.
"Copy for AI" prepends your own configurable prompt template, so the paste is a ready-made debugging request, not a wall of text.
Free, private, open source.
No accounts, no analytics, no network requests. MIT-licensed — read the code yourself.
Why we built it
We triage Acumatica errors every day. We got tired of drag-selecting stack traces and re-explaining which screen broke, so we built the tool we wished existed. Now it's free for the whole Acumatica community.
See it in action
How to install
Unofficial tools — not affiliated with, endorsed by, or sponsored by Acumatica, Inc.