Accountants and attestor pay

Status: Built, runs on simulator

Registration is required by the software, but professional eligibility and compensation for an attestor are not decided.

Q-043 separates these questions. The chain registry records authority to perform supported actions. The available records do not say which professional qualifications are acceptable, how reviewers are appointed in practice or how they are paid.

The backend restricts case access to an active, indexed registration and the addressed case. Proposing an attestor does not itself grant access. A real operating process needs to verify that the expected person controls the registered signing and encryption keys.

Evidence boundaries

For the supported accountant flow, the issuer sends documents and the income opening encrypted for the chosen reviewer. The ordinary server stores ciphertext and does not hold that decryption key. Public chain records contain commitments, payments and statuses rather than those documents. See the data map.

The final engagement must cover scope, fees, conflicts, responsibility, confidentiality and retention. None of those commercial or professional terms is inferred from successful registration. The actual evidence-signing instructions remain held while the backend interface is changing.

What can go wrong

A registered key is not a published professional standard or an agreed fee arrangement. An appointed reviewer still needs a defined engagement and an approved evidence workflow.