Skip to content
Business system

admin.digitaliseramera.nu

The firm's own system, built by the firm itself.

Industry
Accountancy
Type
Internal business system

The challenge

An accountancy firm has hundreds of clients, each with their own circumstances, integrations and routines. Off-the-shelf systems cover part of that; the rest becomes Excel, email and memory. That holds up until somebody is off sick.

What we built

  • A client record that adapts

    The menu shows modules based on the company type and on the integrations that particular client actually has.

  • Reconciliations

    Per account and period, with evidence status, comments, attachments, instructions and a full activity log.

  • Reconciliation against bank statements

    The file is uploaded, parsed and matched automatically, and the system remembers earlier matches so it improves every time.

  • Fortnox integration

    Per client with OAuth, a clear status and one-click reconnection.

  • AI reading of source documents

    Invoices and receipts are read, templates are learned per supplier layout, and draft journal entries are put forward for a human to approve.

  • Project costs

    The supplier invoice is fetched as a PDF, lines are built with labels and mark-up, and everything is reconciled against the posted entry before anything reaches the client.

  • Time reporting

    A timer and favourites, plus reports for time, profitability and invoicing.

  • Client documentation on two tracks

    What people write, and a log where the AI records what it actually did per client, searchable in Swedish.

  • VAT analysis

    VAT codes, mappings and exception reports.

  • A Slack channel per client

    With notifications whenever the client is mentioned.

Worth mentioning technically

A single thread-safe handler for Fortnox tokens with an atomic lock, so two simultaneous calls can never knock out a client's connection. A scheduled job refreshes only when needed and raises a Slack alert when something goes wrong. Every sign-in link is built against an allowlist of addresses, so a forged address cannot be used to hijack a login.

The result

A client's status, history and documents sit in one place instead of three. Fortnox connections no longer drop silently. Several errors that would have cost money in rebilling were caught inside the system rather than by the client.

Images

Illustration: a customer card where modules dock in one at a time with a timeline along the edge
Illustration: the customer card with modules switched on per client and history along the edge.
Illustration: documents flowing into a system, matched in pairs and passing an approval gate
Illustration: source documents matched automatically and passing an approval step.

Have you got something like this?

Tell us what is grinding.

Get in touch