Every ERP can produce a document. The question is how many arrived without a person
Automation is the easiest promise in an ERP sale and the hardest thing to verify after the signature. So NG One measures it: the share of documents handled automatically per process, the number of actions with no human touch, and the executions that failed — on the same screen where the work happens, not in an annual review.
- Event → condition → action
- Every rule has a version and an effective date
- Executions are logged, successes and failures
- Automation KPI
A rule nobody can see is a rule nobody trusts
In most systems automation is configured once, at go-live, and after that nobody knows whether it still runs.
Both Pantheon and Business Central have automation rules. Neither shows how much those rules actually did. The consequence is familiar: a rule is configured at go-live, three months later someone changes a code list, the rule quietly stops firing — and nobody notices until work appears that 'always used to happen by itself'. Automation without measurement is an assumption, not a feature.
That is why the Automation Center is a hero screen rather than a setting buried in administration: active rules, execution history with outcomes, a list of what the system handled without a person, and — just as important — a list of executions that failed, with the reason. A system that shows only its successes is asking for trust it has not earned.
A rule is always three-stage: event, condition, action. The workflow kernel at the core of the system carries it rather than a model — which is why it runs deterministically and why there is always an answer to which rule produced what. Every rule has a version and an effective date, so even for a document from a year ago it is known which rule applied then. What the system cannot match, it leaves to a person with an explanation of why — quiet guessing costs more than an unmatched line.
The Automation Center
Rules and the measure in one place. The cyan share is what the system handled on its own, the neutral share is what stayed with a person — and an action a person confirms is not hidden, it is drawn as exactly that.
47
documents posted with no manual entry
The last 30 days in the demo tenant: purchase invoices, statement lines and recurring invoices under contract.
93%
of purchase invoices matched automatically
The share that passed 3-way match with no discrepancy. The remaining 7% went to a person, with the reason it could not.
83%
of bank statement lines matched
Matched on reference, amount and counterparty. Partial payments are never guessed — they stay open.
Invoice from a delivery note
System executesEventDelivery note confirmed
Shipment to the customer closed
ConditionThe order allows invoicing
Customer not blocked and with no open dispute
ActionThe invoice is raised from the lines
No re-entry and no retyping
18 invoices this month
Purchase invoice matching
System executesEventPurchase invoice received
Through SEF or as a scan
ConditionOrder, receipt and invoice agree
3-way match within tolerance
ActionA posting proposal
A discrepancy goes to a person, with the reason
93% of invoices passed with no person
Bank statement matching
System executesEventStatement imported
The bank's daily file
ConditionReference, amount and party hit an open item
A partial payment is never guessed
ActionThe item is closed
Any remainder stays open
83% of statement lines matched
Replenishment proposal from stock minimum
Person confirmsEventStock fell below its minimum
After an issue or a reservation
ConditionNo open purchase order for the item
Material in transit counts
ActionA purchase order as a draft
Procurement picks the supplier and confirms
14 proposals awaiting confirmation
Dunning on due date
Person confirmsEventInvoice 30+ days late
By value date
ConditionNo dispute and no agreed deferral
Checked before the message exists
ActionA dunning letter as a draft
Collections reviews and sends
9 letters prepared
The figures shown are an illustration from a demo tenant with twelve months of data. They show the SHAPE of the measure and the path to each number, not a measured outcome in your company — your share depends on your data and your rules.
What the Automation Center covers
Six named capabilities on one workflow kernel: the Automation Center itself, event → condition → action rules, the 'what the ERP did on its own' KPI, SLAs with escalation and delegation, time saved and correction-free auto-posting, and durable orchestration with retries and compensations when a step fails.
Automation Center: what the ERP did by itself
Automation is visible, measured and reversible. A rule nobody can see is a rule nobody trusts.
6 capabilities
Automation Center
A hero screen: active rules, execution history with outcomes, time saved, and the list of what the system completed without a person.
Event → condition → action rules
Automation rules on the workflow kernel: expected receipts from purchase orders, replenishment proposals, dunning on due date, recurring invoices, statement matching.
Automation KPI: “what the ERP did on its own”
Share of documents processed automatically per process and the count of actions with no human touch — a measure that either rises or does not, but is never assumed.
SLAs, escalations and delegation
A deadline on the task, escalation when the deadline breaks, a stand-in when the owner is away — without a reminder living in somebody's inbox.
Time saved and correction-free auto-posting
Time saved per process and the share of documents posted automatically with no correction at all — tracked month over month at the same client.
Durable orchestration of multi-step processes
Retries and compensations when a step fails; the process does not stop halfway and leave a partial state somebody discovers a month later.
Ask us what would run itself in your company
Name the work that repeats every day — statement matching, dunning, replenishment — and we will show you the rule that carries it, including the part that stays with a person.