Integrations and shared services
Toolora uses server-side adapters and shared services for accounting, archived mail, application messages and model calls. Each connection has its own identities, permissions and result evidence. Domain services preserve Toolora’s product rules at these boundaries. Existing adoption proposals do not establish that a provider migration is complete.
Integration ownership
Section titled “Integration ownership”Toolora owns product behaviour and its provider-neutral business contracts. Shared services own the capabilities assigned by their contracts, such as credentials or source preservation. Adoption must preserve identity, value and freshness requirements in the actual workflow. The landscape identifies dependencies without claiming that every provider operation is enabled.
Integration ownership describes company mappings, shared-service contracts and the current adoption boundary.
Accounting and Fortnox
Section titled “Accounting and Fortnox”The shared connector owns credential, rate-budget and read-feed contracts. Toolora still has an in-process invoice adapter behind its accounting interface. A complete invoice-write cutover is not established. Financial reconciliation needs explicit receipts and freshness evidence regardless of which adapter supplies an operation. Fortnox write tests have a separate approved company target.
Accounting and Fortnox compares invoice adapters, connector commands, payment projections and their outcome evidence.
Estate mail archive
Section titled “Estate mail archive”Estate supplies preserved mail metadata, originals and attachment evidence. Toolora projects selected content and applies its own active mailbox and reader policies. The mail workspace does not send or reply to messages. Original coverage remains authoritative in the archive, including gaps that Toolora must expose rather than fill by assumption.
Estate mail archive documents attested setup, administrator readers, bounded indexing and internal links.
Retries and external outcomes
Section titled “Retries and external outcomes”A network error can occur before or after an external service changes its state. Recovery must use the operation’s stable identity and available receipt or reconciliation read. API conflicts have different semantics from an unknown provider outcome. The detailed recovery reference compares current command, source and routing mechanisms and their limits.
Retries and external outcomes provides a diagnostic path for refusals, stale inputs, partial reads and unknown submissions.