Solju
Draft — not yet in force Not reviewed by a lawyer. The liability and jurisdiction sections in particular are placeholders describing intent, not enforceable language — see the notes inline. Nobody is bound by this until it is finished and a firm has actually agreed to it.

Terms of Service

Draft of 5.9.2026 — Solju

What Solju is

Solju reads a company's Revolut Business exports and produces two things: source documents renamed and matched to bank transactions, and a draft accounting journal with proposed account and VAT coding for import into Fennoa. Solju is sold to accounting firms, who use it on behalf of the companies they act for.

The rule everything else here is subordinate to: the tool proposes, the accountant decides. Every account and VAT code Solju produces carries a confidence level. Nothing is posted to Fennoa automatically, and nothing below Solju's own "high confidence" threshold is presented as settled — it is placed in front of a human for review instead. Solju is a drafting tool. It does not replace the accountant's professional judgement or their firm's own review process, and it is not a substitute for that judgement being exercised.

What a firm is responsible for

What Solju does not do

Availability

[This service is provided during a pilot phase without a formal uptime commitment. A specific availability target, if one is offered, belongs here once the product is priced and sold rather than piloted — see the accepted risks below in the meantime.]

Accepted risks, stated rather than hidden in fine print

Two facts about the current state of the service that a firm should know before relying on it for anything time-critical:

Fees

Pricing is per client company per month and is agreed directly with each firm — see the pricing section of the main site. [Payment terms, invoicing cadence and what happens on non-payment belong here once a firm is actually being charged.]

Ending the relationship

Either side may end the arrangement [notice period to be agreed — a pilot has different expectations than a paying customer, and this should probably differ between the two]. On ending, a firm's data is handled as described in the Data Processing Agreement.

Liability

[This section needs a lawyer, not a template. What is defensible here depends on Finnish contract law and on how this entity is actually structured — an unreviewed liability cap or exclusion is worse than none, because a court can find it unenforceable in a way that also undermines a clause that would otherwise have held. Left blank deliberately rather than filled with boilerplate language that has not been checked against the jurisdiction this contract will actually run under.]

Governing law

[To be confirmed with the entity's actual place of registration — likely Finland given where the product and its first customers are, but stated here as a placeholder, not a decision.]

Changes to these terms

A firm with an active account is told directly before a material change takes effect, not left to notice a date at the bottom of this page.