MIO°Participants
Participant summary

Attested Accounts™

24 September 2026 · John Stroh, Director, My Digital Sovereignty Ltd

What it is

Attested Accounts, at accounts.amiomega.digital, makes a financial record, and what happens to it afterwards, checkable later by someone outside the business, without an MDSL account. Every write to an invoice, quote, recurring invoice, expense or time entry is signed under the tenant's key at the moment it happens, on the same SSST design that AVA™ and Conduct Record™ use. A third party can check a downloaded bundle offline with a published verification tool.

It sits alongside an accounting package, not in place of it, and is neither an audit opinion nor accounting advice. It is an evidence layer over the Business Village's existing invoicing, quoting, recurring billing, time and expense tracking. It is built into the Business Village rather than sold as a separate product. Sealing is switched on in the software for every Business-featured Village; the product is available on request.

Published pricing: NZ$263 per Village per month, and NZ$114 per pack of 100 Qualified Receipts. Access is arranged directly with John Stroh.

Built vs roadmap

Status as of 24 September 2026, established by AI agents from the code and plans; no person has checked every line (see the status page).

Capability Status What it means for a customer
Signing of every write on invoices, quotes, recurring invoices, expenses, time entries Available on request Alteration of a record after signing is detectable. It says nothing about whether the figures are right
Hash-linking of the sealed history (deleted or reordered entries detectable) Live since 24 September 2026, 11:30 NZST; entries written from then on only Earlier entries are not linked retrospectively
Concurrent-write safety on the history Live Two simultaneous writes cannot silently overwrite each other's entry
Action-history view on an invoice Available on request, invoices only Shows created and updated entries; names a person only for creation, otherwise a system note
Downloadable verification bundle, checked offline Available on request, invoices only A third party checks a record on their own machine, with no account and no call to MDSL. Until the signing key is separated, the check still relies on MDSL not having rewritten and re-signed the record.
Erasure requests report finance records held under a retention rule and scrub the erasable remainder Available on request Requests are not silently skipped. No retention period is stated on the pages
Qualified (RFC 3161, eIDAS) timestamp receipt on one invoice Available on request, opt-in; switched on per customer because each stamp is priced (NZ$114 per 100 receipts) Enabled per customer through an allow-list
Batch receipt (up to 1,000 records under one digest) and ten included receipts a month Not available Both are stated on the pricing page. A receipt covers one invoice at a time, and no monthly allowance is enforced
Truncation detection after a compaction (length anchor) Built, not switched on for finance records Anchoring is built and tested; nothing in production calls it yet
Quotes, expenses, time entries: history view, receipt, bundle Not built Sealing covers them; the history view, receipt and bundle are for invoices today
Practice-facing console: one view across many small clients Not built Follows a client-access rule and practice pricing
Agentic bookkeeping and any MIO-STD-01 claim for it Not built Nothing here is a conformance claim

For a practice, today's route is one client's Business Village at a time. A practice console follows a client-access rule and practice pricing. The distributor model deliberately grants no access to member content, so a scoped read of one client's finance records needs a new capability, not a setting.

The full participant one-pager, with the competitive landscape and the risks and open decisions, is shared in the private room, to named people, with a record of who opened it. Write to john.stroh@mysovereignty.digital to be invited.

← All products