Every transaction is evaluated against your rules as it replicates from NetSuite. When a row matches, an issue opens with severity, owner, and a link to the source record, and a task lands in the owner’s queue with a deadline — the same hour the transaction posted, not at next month’s review.
An issue opens the moment a row matches. The task routes, escalates, and resolves on a fixed cadence — and every transition is written to the audit log against the rule version that fired it.
Rule fires when the shipment posts. An issue opens at severity 2 with a link to the underlying record.
A task lands in Maria's queue with a 2-day deadline and the linked shipment.
Task crosses 48h unresolved. The issue escalates to Devin Park, Logistics Manager. Maria stays assigned.
Past 96h. The issue is added to the Friday operations review and the month-end stale-issue report.
Maria files a claim with the carrier and resolves with reason 'carrier delay'. The audit log records the rule version that fired.
Every rule has a test mode. Run it against any historical date range to see every transaction that would have matched, every issue that would have opened, and the exact query the engine evaluated. Adjust the threshold and re-run before activating.
Rules can be authored, edited, and activated by operators directly. Changes take effect the moment they save. The next matching transaction is evaluated under the new logic.
Issues open the same hour the transaction posts and route directly to the owner who can address them.