Why the ERP, not the AI, should calculate invoices, payroll and stock
The short answerLanguage models are good at understanding a request and poor at being exact. Invoice totals, tax, payroll and stock counts must come out the same every time, so an AI native ERP lets the model direct the work while deterministic engines do the arithmetic, in whole currency units, inside locked periods.
Key takeaways
- Use the model to understand the request, find the records and draft the work. Use the ERP engine to calculate.
- Money held in integer currency units cannot drift through rounding.
- A locked period means a payroll or accounting result does not change quietly after the fact.
- Stock should change through one controlled path, so every movement is validated and recorded.
Where a model helps, and where it must not guess
A language model is excellent at reading a messy request and working out what the person means. It is not designed to be exact. Ask it to add a column of figures twice and it may give two different answers, each delivered with the same confidence.
That is acceptable for drafting an email and unacceptable for an invoice. A sensible split gives each part of the work to the tool that is good at it:
| The model helps with | The ERP engine must calculate |
|---|---|
| Finding the right customer and catalog item | Invoice totals, tax and numbering |
| Drafting an invoice or a summary | Payroll gross pay, deductions and net pay |
| Asking for what is missing | Stock levels and movements |
| Explaining a variance in plain words | Journal entries that balance |
What a deterministic engine does
Take the invoice request "Invoice Acme for the implementation package and send it". In Agaro the assistant resolves the real record first: the customer, the catalog item, the stored price, the workspace currency, the tax and the payment terms. Then the finance engine takes over. It validates the request, calculates the totals and tax, allocates the invoice number, creates the invoice and commits the journal entry.
Two design choices matter here. First, amounts are held in integer currency units, which means whole cents rather than fractions of a cent, so repeated calculations cannot drift through rounding. Second, periods can be locked. Once a payroll or accounting period is locked, its results do not change silently afterwards. The same inputs give the same result, every time.
Payroll is the clearest case
Payroll shows why this split matters, because a small error is a real person paid the wrong amount. In Agaro the payroll engine takes employment contracts, stored compensation, attendance and work entries, approved overtime, bonuses and adjustments, benefits, deductions and taxes as inputs. It produces the register deterministically:
The outputs stay together: the payroll register, the payslip snapshot, the payment file, the payroll journal entry and an audit record. For US payroll the module covers W4 elections, Forms 941 and 940 and W2. The assistant can direct the workflow, for example by starting a run or explaining a result, but the engine calculates and enforces correctness. See payroll, attendance and time off in one system for the whole chain.
Stock: one chokepoint for every movement
The same idea applies to inventory. Orders, shipments, purchasing and warehouse work all change stock, and if each can write to the stock figures in its own way, the numbers stop agreeing. Agaro routes stock changes through a single stock write path, so every movement is validated and recorded.
The practical result is that you can trust a stock figure enough to act on it, and an assistant that reads it is reading the same figure everyone else sees.
How to test a vendor's claim
- Ask who calculates an invoice total: the model or an engine. Ask them to show you the engine.
- Run the same request twice and compare the results. They should be identical.
- Ask what happens when the assistant misreads a quantity. A good system validates the request before it creates the record, and shows you the draft first.
- Ask whether periods can be locked, and what happens to a locked result if an input changes.
- Ask where the activity is recorded, so you can see afterwards what was calculated and why.
Questions people ask
Can the AI still prepare the invoice?
Yes. It resolves the customer, the item and the terms, and it directs the workflow. The finance engine calculates the totals and tax, and by default you review the draft before it is sent.
Why do integer currency units matter?
Holding money as whole units, such as cents, avoids the tiny rounding errors that fractional arithmetic can introduce. Repeated calculations then produce the same total every time.
What if the assistant picks the wrong customer?
That is why the default approval mode is Ask first. You see the proposed record before it is applied, and the outcome is recorded in the activity history so it can be reviewed afterwards.
Does a locked period stop me from correcting a mistake?
A locked period protects a result from silent change. If something does have to change afterwards, it should be a deliberate, recorded action, so ask any vendor how corrections to a locked period are made and where they are logged.
Cite or share this guide
Agaro Technologies. "Why the ERP, not the AI, should calculate invoices, payroll and stock." Agaro blog, November 5, 2026. https://agaro.ai/blog/erp-calculations-not-ai-guesses