Autonomous Multi‑Agent Architecture for Enterprise Closes.
GreyStele runs a team of specialised agents on your ledgers and ERP systems. Each one does a single job, writes down what it did, and hands the result to the next. The close finishes with proof, not a feeling.
How a close runs
One run of the month-end close for a single entity, as GreyStele records it.
Ingest
Journals, sub-ledgers and bank statements are pulled from the systems of record. Every file is hashed on arrival, so what the agents saw can never be in doubt.
Match
Bank statements are matched to the ledger line by line, across accounts and currencies. Unmatched items are listed, not estimated.
Reconcile
Intercompany balances are reconciled against every counterparty. The rules are explicit and the same every month.
Verify and seal
Debits equal credits, or the run stops. When the ledger balances, the record is sealed with a hash and the figure is written: Δ 0.00.
Review
Anything outside a threshold is handed to a person, with the evidence attached. Agents never decide an exception; they surface it.
The agents
Narrow by design. Each agent has one job, one set of rules and one place to write.
- Ingest agents
- Connect to ledgers, ERPs and banks. Pull, hash and stage the data. Nothing is transformed on the way in.
- Reconciliation agents
- Match, net and reconcile under explicit rules. The same inputs produce the same result, every run.
- Verification agents
- Check the arithmetic, the controls and the completeness of the record before anything is sealed.
- Review agents
- Route exceptions to the right person with the evidence, record the decision, and carry it into the next run.
The audit model
Inscribed, not inferred. Every agent action is a line in a permanent record.
A GreyStele record is written as the run happens. Each line carries the time, the agent, its inputs, its outputs and a hash of all of them. Lines are never edited or deleted. When the ledger balances, the run is sealed and the seal depends on every line before it.
Any run can be replayed. Give an auditor the record and the inputs and they can reproduce the close, step by step, and get the same figures. There is no model to interpret and no probability to argue over.
Month-end close · EU entity
Proof sealed
| Time | Step | Result | Hash | |
|---|---|---|---|---|
| 09:02:14 | Journal ingestingest | 48,210 rows · hash ok | 7c1e…b204 | |
| 09:02:38 | Bank statement matchrecon-01 | 12,604 / 12,604 | d93a…41f0 | |
| 09:02:51 | Intercompany reconciliationrecon-02 | 47,988 matched | 02e7…9ac3 | |
| 09:03:07 | Ledger balanceverify | Δ 0.00 · proof sealed | a41f…9c0e | |
| 09:03:09 | FX revaluationfx-reval | 222 items · need review | 5b70…e118 |
Sealed 09:03:07 · sha256 a41f07c2e93b5d109c0e…
Your systems, unchanged
GreyStele reads from and writes to the systems you already run. It does not replace them.
Agents connect to the general ledger, sub-ledgers and core banking systems through their own interfaces and post back through the same controls your people use. Nothing is copied into a second system of record; the record stays where it is, and GreyStele adds the proof.
Typical environments include SAP S/4HANA, Oracle Fusion and Workday Financials alongside core banking and treasury platforms. Ask in your briefing about the systems you run.
See a close run on your own ledger.
A briefing is forty minutes with an engineer, on your systems and your close calendar. No slides.