the workflow
The workflow, end to end.
Four of the workflows a distribution business runs. Each follows the same shape: the agent reads, drafts and checks its own work, then stops at approval. Step through one, or let it run.
Purchase invoice matched to its PO and receipt, exceptions raised, posted on approval.
An invoice lands in the AP mailbox
No one opens it, renames it, or keys it in.
Illustrative documents and figures, shown to demonstrate the sequence. Scoping is done against your own volumes, chart of accounts and dimensions.
why this one
Private, local, and bought once.
private
Your documents stay yours
Invoices, statements and contracts are read on your own machine. They are never uploaded to an AI service, so there is no retention policy to trust and no training on your data to negotiate.
local
It runs in your building
One machine on your network, with the model on its own disk. It keeps working when your line goes down, and there is no outside service that can rate-limit you or change its terms.
learns
It learns from your documents
The coding, the dimensions and the vendor quirks come from how your team already posted the last few thousand documents — not from rules someone has to write and maintain.
cost
No monthly bill
A machine and an implementation, paid once. No per seat, no per token, no per document, no renewal increase. After that it costs electricity.
what it plugs into
It reads the systems you already run.
Connected with your own credentials, against your own tenants, with the scopes your administrator grants and can revoke.
Microsoft 365
Outlook · Excel · SharePoint · Teams
Microsoft Graph
Business Central
Dynamics 365 · your ledger
REST / OData · OAuth2
PLM
Teamcenter · Windchill · Arena
REST / SOA services
Product data
Akeneo PIM · your own catalogue
REST API
CRM and sales
D365 Sales · Salesforce · HubSpot
REST API
Banks and cards
through Business Central · Yodlee feed
REST / OData · OAuth2
It reads all of these. It writes to one.
Every connection above is read-only. The single exception is Business Central, and even there nothing is written until a person approves it.
Every connection above is a documented API, authenticated with your own credentials. Documents that arrive as files — an emailed invoice, a scan — are read through the mailbox or document library they already land in, which is the same Microsoft Graph connection.
the control model
What it may do, and what it may never do.
Enforced by the permissions on your own Business Central app registration, not by an assurance in a proposal. A request outside this list is refused by the API, and the registration can be revoked by your administrator in one action.
May read
- GL accounts, balances and dimensions
- Purchase orders, receipts and vendors
- Items, unit costs and stock movements
- Your posting history, as the pattern to follow
May propose
- Purchase invoices matched to a PO and receipt
- Journal batches with coding and dimensions
- Reconciliation matches against open entries
- Variance commentary for your review
May never
- Post anything without a named human approval
- Create or amend vendors, items or bank details
- Release a payment or touch payroll
- Send a document to any outside service
commercial model
A capital purchase, not a subscription.
This is the part most AI proposals are vague about, so here it is plainly. You are buying a machine and an implementation, once. You are not renting access to someone else's service, and there is no meter running.
The same four questions, asked of both
A per-seat AI subscription
What you are usually offered
- You pay every month, for as long as you use it
- Adding people to the team costs more
- The price can rise at renewal, and the terms can change
- Stop paying and access ends — you are left with nothing
This
What is being proposed here
- You pay once, up front, and that is the end of it
- Adding people to the team costs nothing
- There is no renewal, so there is nothing to raise
- Stop paying anyone and it keeps running — you own it
Paid once
- The machine
- A GPU workstation sized to your document volume. Yours, on your books, depreciable.
- Implementation
- Install, model selection, Business Central app registration, connector and approval console.
- Workflow build
- The workflows above, configured against your chart of accounts and your dimensions.
- Parallel run and handover
- Shadowing your current process until outputs agree, then training your team.
Ongoing
- Electricity
- The machine draws power. That is the running cost.
- Support, if you want it
- Optional and separable, quoted on its own. The system does not stop working without it.
Never
- Per user, per month
- Per token or per document
- Per company or per entity
- An increase at renewal