Accounting you can check.Accounting you can check.

The phone signs in to the same accounts as kvimo.lt. The web keeps its session in a cookie; the app gets a token and keeps it in the Keychain, never in settings, a log, a file or a screenshot. Signing out clears it and every cached read.

“Pamiršai slaptažodį?” (forgot your password?) opens kvimo.lt in Safari, so a reset happens in one place.

The lockout counts any email typed, with or without an account, and answers the same way, so it tells nobody which addresses exist. A correct password under the limit clears the count; during a lock even the right one is refused.

On the web, a change made with the session cookie must come from Kvimo's own address. A request from anywhere else is refused, even when the browser attaches the cookie.

An expired session clears the stored token and returns to the welcome screen with one sentence. Being offline at launch is not treated as signed out: the session is kept, and each screen says it couldn't load.

Bank data arrives through licensed aggregators. The simple view and the iPhone app use one aggregator; the accountant's full view can use a PSD2 provider registered by the company itself. SumUp and Stripe connect through their own APIs.

Consent length is never a constant in the code. The adapter clamps it to the bank's published maximum, and the screen prints the consent's own end date: “Banko leidimas galioja iki …”, the bank permission is valid until a given day.

Credentials live in a secret store, and no event in the system has a field a token could go into. A test enforces that. Payment files for the bank are download only: nothing in Kvimo sends money.

The rule is written into the architecture: corrections are reversals, never edits, so the log is a complete audit trail rather than a snapshot of the current state. “Taisyti” posts a reversal and a corrected entry in one call, and all three entries stay in the log.

The “Why?” button is the product. That line is from the design doc: any figure drills down to its journal lines, then to the source document and the AI's reasoning. Documents are matched to the bank payment that settled them, and each one shows a timeline: uploaded, read, linked to a payment.

Every company runs on Anthropic's Claude. The policy in the code is short. A proposal posts by itself at confidence 85 or above, or 90 if it touches income. Some things are always queued for the accountant, whatever the confidence: payroll, depreciation, cash income, recurring entries, issued invoices and fixed assets.

Whether a payer is familiar, a duplicate or confirmed by the owner is recomputed from the books, never taken from the model's word. Each company has a monthly AI budget; past it, Kvimo runs on rules and questions only.

Under every AI answer, “Paklausti buhalterio” (ask the accountant) copies the question and the answer into the accountant chat. Nothing is sent until the person presses send.

What the AI may not do: write to the journal directly, claim the owner confirmed something, charge anyone, or issue credentials.

Kvimo has three roles and keeps it that way: an owner administers, an accountant writes, a viewer reads. On top of roles sit nine areas, from the ledger and bank to payroll, declarations and AI chat, so access can be narrowed without inventing new roles.

Under GDPR, erasure is decided per field as one of three acts: delete, anonymise (the record stays and the name is folded out when read), or keep, with its legal term and end date. Invoices must be kept for ten years, so they are kept, and the reason is written down.

“Slėpti sumas” is a per-device preference. After sign-out, no amount stays on the home screen or the wrist.

When the focus moved to accounting sold as a service to ordinary small businesses, the front door changed. The simple view now covers six jobs: issue an invoice, ask Kvimo's AI, ask a real accountant, connect a bank, see bank operations, and match documents to them.

Owners on the managed service now see only the simple view. The full version stays for accountants.

The brand rules are strict on purpose: yellow #FFE58F is the only highlight, titles and big figures are set in Bricolage Grotesque, text in Figtree, and AA contrast is checked by tests.

Web and iPhone share values, not a single code base. The marketing site's values are the source; on iOS a JSON file feeds a script that generates the asset catalogue and a Swift tokens file, so a colour change is one edit and a regenerate.

The app sells the service with Stripe, outside in-app purchase, under the App Store rule for that kind of service. Tests cover it on both sides: 3,240 web tests pass in one run, and the iOS app has 634 test functions.