Accounting and Fortnox
Toolora’s accounting boundary is provider-neutral at the business layer, with operation-specific implementations below it. The shared Fortnox connector owns credential, coordinated rate-budget and selected command/read-feed contracts. Toolora still has an in-process invoice adapter. A configured connector is not proof that every invoice write uses it.
Implemented paths
Section titled “Implemented paths”| Path | Toolora owner | External boundary and evidence |
|---|---|---|
| Customer invoice export and selected syncs | Accounting interface, invoice export/outbox and services/fortnox |
Existing local adapter; preserve its frozen document, stable operation identity and readback rules |
| Purchase-invoice bookkeeping | Approved AP snapshot and purchase_invoice_worker |
Connector command submission, later command state and verified provider readback |
| Approved-time handoff | Approved-time/payroll outbox and worker | Connector handoff receipt; it does not prove a payroll run or payment |
| Receivable/payable payments | accounting_payment_feed and local projection |
Connector event pages with opaque continuation and current company validation |
| Other accounting exporters | Their guarded configuration entry | An adapter name does not establish supported configuration or ROT/RUT representation |
The reviewed direct non-Fortnox exporter entry points refuse unavailable canonical configuration rather than pretending to start. They also refuse unsupported frozen deduction contracts. Do not advertise them as interchangeable enabled integrations. Settlement owns invoice approval, delivery, credits and the evidence needed to call a balance settled.
Command lifecycle
Section titled “Command lifecycle”The connector client submits a company-scoped command containing stable idempotency identity, operation, provider request and approval assertion. It returns command identity/state, external reference and outcome metadata. Its POST is not transparently retried after a transport exception: the connector may have accepted it. That exception is deliberately classified as an unknown submission result.
The AP worker claims leased export work, loads the approved snapshot and performs
its required supplier/invoice/bookkeeping steps. It records operation-specific
keys and local command state. submitted_unknown or needs_human leads to
reconciliation, not a second fresh-key bookkeeping action. A succeeded command
still needs the workflow’s expected references/readback before the local result
is treated as verified. Database claims prevent competing processing within their
lease contract; they do not make a provider operation part of the SQL transaction.
Payment projection
Section titled “Payment projection”The feed worker reads bounded pages using the connector’s opaque cursor. It checks the configured company before applying supported receivable/payable payment events. Known upsert, tombstone and resurrection kinds have explicit semantics; unknown additive kinds are not interpreted as current payment data. Envelope/type/value validation protects against skipping or misbinding a supported payment event.
A local payment row is a projection. Current register parity, deletion observations, freshness and reconciliation coverage determine whether an outstanding-balance conclusion is justified. Absence of a payment row alone does not prove non-payment. The MCP contract exposes those limits through section coverage and missing information rather than replacing them with a single convenient total.
Safe operation and recovery
Section titled “Safe operation and recovery”Vi Målar’s Fortnox company is real bookkeeping. Never exercise final attest, accounting send/export or payroll-queuing time approval there for a test. Only Fortnox test company 1026975 is approved for provider writes, and no Toolora tenant is currently bound to it. Do not change a binding to bypass that restriction.
For synthetic Export A, keep the existing command identity after a timeout and inspect its command/result before deciding on another attempt. For synthetic Feed B, a company mismatch or invalid supported event must not be bypassed by advancing the cursor. Focused client/worker/feed tests substitute provider responses; actual provider lifecycle evidence remains tied to the named release, company and scenario. This reference adds no direct Fortnox call and claims no completed invoice cutover.