Know where the data—and the authority—stop.

Independent access and financial data

The real-file workspace checks Remit's own Clerk session on the server before rendering. The configured Frontend API must match the independent Remit instance; old shared ScopeMentor keys do not make the app ready. Account and workspace pages are private and excluded from discovery. Imported financial records live in page memory, not automatic browser saves. Changing account/session/organisation unmounts the workspace. The public example contains only synthetic records and has no file-import controls.

Cash-allocation controls

• Explicit supported currencies; separate totals and no inferred FX.
• Positive safe-integer minor units, strict dates, mapped fields and duplicate detection.
• Allocation lines cannot exceed available receipt cash or invoice balance.
• Remittance amounts and conflicting customer evidence are checked.
• Approval and export share validation; changed source invalidates prior decisions.
• Unapplied residuals stay visible in exported instructions.

Account lifecycle and paid AI

The real-file workspace also requires an active record in Remit's independent account database. Deleting product access tombstones that identity, clears its optional profile and revokes grants; it does not erase usage or recreate allowance. Export and deletion do not require a purchased grant. Unavailable database actions remain closed. Authentication alone does not grant paid AI. Optional AI requires explicit selected-data consent, a purchased server grant and durable atomic job/cost reservation. Unknown provider outcomes retain their reservation, and replays cannot dispatch twice. AI output cannot create monetary allocation lines or post a ledger entry; human approval is revalidated deterministically against the current full batch. Provider, purchased-grant and quota configuration remain activation requirements.

Limits and residual risks

A source checksum is not a digital signature. Review identity is recorded locally, not a tamper-proof audit service. Customer evidence can be wrong and browser/device compromise remains possible. Separate origins do not remove every parent-domain cookie or supply-chain risk. No tool here posts journals or certifies your books.

Working safely

Use one legal entity per batch, verify imported source balances, inspect every approval, retain exports securely and record the result in your accounting system. Do not use this release for net processor settlements, payment reversals, credit memos, cross-entity transfers or healthcare ERA files.