Alegor Tech
Case Study / Fintech & Workflows

When transaction, receipt, and accounting become one process From purchase to bookkeeping – in one unified workflow.

Kvitt unifies card transactions, receipts, users, and accounting data in a single continuous digital workflow. The result is a platform where financial events are tracked from initial purchase to finalized bookkeeping records – eliminating isolated data silos and manual intermediary steps.

Product Kvitt
Industry Fintech & Finance
Type SaaS / Financial Workflow
Our Role Product & Architecture
1. Paradigm Shift

The problem is not the receipt

A receipt is merely one piece of a financial puzzle. Many products stop at the basic question: "How do we store a photo of a receipt?". But for a company, an isolated photo or a scanned PDF is virtually useless to accounting and ERP software on its own.

The real question is: How do we transform an unstructured financial event into complete, validated, and actionable accounting records?

The organization must know with certainty which transaction matches the receipt, who authorized it, which card and corporate account were debited, which entity holds the liability, whether mandatory fields are complete, and exactly when it is verified for ledger posting.

What a Financial Event Truly Requires

For an expense to become verified accounting data, multiple independent variables must be established:

  • Card transaction and bank feed with amount and merchant
  • Physical receipt or digital PDF with tax breakdowns
  • Identified employee, approval chain, and cost center
  • Legal company entity and chart of accounts mapping
  • Contextual purpose, entertainment notes, or project codes
  • Status validation: missing docs vs. fully verified record
2. Data Streams

A single purchase generates multiple distinct data points

Financial data does not originate from a single source. Kvitt synthesizes disparate streams into one cohesive financial record.

Source A: Financial BANK / CARD

Card Transaction

Generated instantly at the point of sale via card network.

Amount:1 450,00 SEK
Merchant:SJ AB Stockholm
Date:2026-08-16 14:22
Card ID:•••• 8492
Source B: Document RECEIPT / PDF

Receipt Document

Physical paper slip or digital PDF from the supplier.

Supplier:SJ AB (Org 556196-1599)
VAT (6%):82,08 SEK
Items:1x Tågbiljett 2 Kl
Total:1 450,00 SEK
Source C: Business CONTEXT

Business Context

Organizational data from employee and enterprise structure.

Employee:Elin Berglund
Company:Nordic Tech Solutions AB
Category:5810 Resekostnader
Project:Kundworkshop Göteborg
K

Kvitt Unifies the Complete Record

Three isolated data sources consolidated into one verified financial record ready for the ledger.

✓ COMPLETE FINANCIAL RECORD
Deterministic Record Binding MATCH CONFIRMED
Bank / Card Feed
1 450,00 SEK
2026-08-16 14:22:10
SJ AB Stockholm
Card ID: •••• 8492
Receipt Document
1 450,00 SEK
2026-08-16 (Moms 6%)
SJ AB (Org 556196-1599)
User: Elin Berglund
Single Source of Truth ID: TX-20260816-8492

Card transaction and receipt data are permanently bound to a single transaction record without data duplication.

3. Data Matching

Two data sources. One financial event.

A cornerstone of Kvitt is the automated linking of incoming financial feeds. Card transactions stream in from bank and fintech feeds, while receipt documents are uploaded by users in the field or office.

By evaluating attributes such as amount, currency, timestamp windows, merchant name, user identity, and card identifiers, data points align without manual reconciliation by finance staff.

4. Transformation

From unstructured information to business workflow

Value is unlocked when a static file is transformed into structured, actionable attributes that business logic and accounting can process.

01

Document

Photo or PDF containing raw, unstructured pixel data.

IMAGE / PDF INPUT
02

Structured Data

Amount, tax rate, currency, supplier, VAT ID, and line items.

DATA NORMALIZATION
03

Business Workflow

Categorization, cost allocation, approvals, notes, and completeness rules.

PROCESS VALIDATION
04

Accounting

Final journal entry, export files, and direct ledger integration.

LEDGER INTEGRATION

"Digitization is not about turning paper into images. It is about making information structured and actionable."

5. Role-Based Domain Logic

Different roles interact with the same financial event differently

Rather than spawning duplicated spreadsheets and email threads, a single financial record transitions seamlessly across organizational roles.

01

The Employee

Focus on frictionless capture at point of expense.

  • Makes purchase with corporate card
  • Uploads receipt document instantly
  • Adds business context and purpose
02

Company Admin

High-level oversight of spend, cards, and staff.

  • Monitors spending across teams
  • Manages corporate cards and limits
  • Tracks missing receipt statuses
03

The Accountant

Focus on compliance, tax codes, and ledger rules.

  • Audits complete financial packets
  • Verifies tax codes & account charts
  • Exports journal entries to ERP
04

System Admin

Platform-wide security and ecosystem integration.

  • Configures multi-tenant companies
  • Governs role permissions & access
  • Monitors API health & bank feeds
6. Card Infrastructure

The card is an identified data source in the workflow

In generic expense tools, a credit card is just an external payment instrument. In Kvitt, the card is an intrinsic entity in the data architecture.

Each card is bound to an employee, a legal corporate tenant, and explicit approval policies. The moment a transaction triggers, the platform inherently knows ownership, cost center, and downstream ledger paths.

Relational Entity Mapping
1. CARD ENTITY •••• •••• •••• 8492 (Mastercard / Visa)
↓ bound to
2. USER / EMPLOYEE Elin Berglund (Consulting Lead)
↓ triggers
3. TRANSACTION RECORD 1 450,00 SEK @ SJ AB Stockholm
↓ paired with
4. RECEIPT ATTACHMENT Verified Doc (6% Tax Code Verified)
↓ synchronized to
5. ACCOUNTING LEDGER Journal Entry Posted (Account 5810)
7. Deterministic Control

Great automation removes manual labour – not control

Financial systems must never act as opaque black boxes. Accounting rigor demands full transparency, complete audit trails, and deterministic human oversight.

01

Clear Status & Exceptions

The platform flags what has been paired automatically and explicitly highlights missing documents or items requiring manual review.

02

Correction & Approvals

Financial controllers and approvers retain full authority to adjust account codes, tax rates, and allocations prior to final export.

03

Immutable Audit Trails

Every modification, match event, and approval is immutably timestamped with user context for rigorous audit compliance.

8. Integration Strategy

A specialized platform connecting directly with the enterprise ecosystem

Kvitt is not built to be an isolated silo or to reinvent the general ledger. The core value emerges when validated financial records flow seamlessly into external ERPs and accounting suites.

A great specialized product does not replace the entire financial ecosystem. It solves a specific, complex operational domain with perfection, then integrates with everything else.

The architecture supports API-based sync routines, standardized export formats, and continuous transaction feeds into corporate ledgers.

End-to-End System Pipeline
1. BANK & KORT API / Feed Ingestion
2. KVITT CORE Matchning & Validering
3. ATTEST & STATUS Verifikationskontroll
4. EKONOMISYSTEM Bokföring / ERP Synk
9. Financial Integrity

Financial data requires a higher degree of architectural discipline

Engineering financial workflows is fundamentally different from standard CRUD applications. The architecture must guarantee absolute tenant separation and data integrity.

Tenant Separation

Strict Tenant Isolation

Corporate data, cards, and receipts are isolated at the database layer to ensure zero cross-tenant data contamination.

Auditability

Comprehensive Audit Trails

Every status update, matching adjustment, and approval records an immutable record of user, timestamp, and changes.

Deterministic Validation

Deterministic Validation

Strict arithmetic and tax balance validation before any record is approved for export.

Role Permissions

Fine-Grained Permissions

Role-based access control (RBAC) strictly enforcing who can view, edit, approve, and export records.

Secure Storage

Secure Document Storage

Encrypted, structured object storage for original receipts and audit documents with signed URL access.

Idempotency & Sync

Idempotent Sync Routines

Integration pipelines built with strict idempotency keys to completely eliminate duplicate ledger entries.

10. SaaS Architecture

Engineered as a multi-company, multi-user SaaS platform

Kvitt is architected from the ground up to host numerous companies, thousands of active employees, and high-volume transaction feeds on a unified platform.

Each company operates its own policies, card rosters, chart of accounts, approval hierarchies, and integrations within a shared modern multi-tenant platform.

KVITT MULTI-TENANT CORE
├── Company A (Nordic Tech AB)
├── Employees (24 users)
├── Corporate Cards (18 active)
├── Transactions & Receipts
└── ERP Sync Integration
├── Company B (Logistics Group AB)
├── Employees (110 users)
├── Corporate Cards (85 active)
├── Transactions & Receipts
└── Custom Accounting Export
└── Company C (Creative Agency AB)
├── Employees (12 users)
├── Corporate Cards (12 active)
└── Transactions & Receipts
11. Product Philosophy

The product is the workflow

Rather than a disconnected set of standalone features, Kvitt is engineered as an unbroken chain from expense to verified ledger entry.

STEG 1

Purchase

Employee executes purchase with card.

STEG 2

Transaction

Bank feed captures card transaction.

STEG 3

Receipt

Receipt uploaded and auto-paired.

STEG 4

Complete

Category, project, and taxes confirmed.

STEG 5

Review

Finance team reviews and verifies.

STEG 6

Accounting

Data posts to accounting system.

12 & 13. Architecture & Engineering

The right technical tools for distinct engineering challenges

We do not choose technologies to make architecture needlessly complex. We employ specialized runtimes when operational challenges genuinely differ.

Web & Mobile Application

Vue.js & Modern Frontend

Fast, responsive interface for receipt capture, card management, and real-time administrative workflows.

Business Core API

PHP / Laravel Core

Orchestrates tenants, role permissions, business rules, transactional models, and audit logs with rock-solid stability.

Integration Services

FastAPI & Python Microservices

High-throughput microservices engineered for financial integrations, data extraction, and asynchronous feed pipelines.

Asynchronous Processing

Queues & Background Workers

Background queues handling media optimization, bank synchronization, and push alerts without blocking the UI.

Structured Financial Storage

Relational Data & Object Store

Strict relational database schemas for ACID integrity paired with encrypted object storage for receipt files.

External Accounting Sync

REST & Webhook Connectors

Standardized interfaces for journal exports and bi-directional synchronisation with enterprise accounting suites.

14. Architectural Reuse

Don’t spend development cycles rebuilding user management for the fiftieth time

A fintech application requires a massive foundation of non-domain plumbing: multi-tenant organizations, user identities, roles, permissions, secure auth, file handling, notifications, and audit trails.

By leveraging a battle-tested modular core, engineering focus and budget are dedicated strictly to what makes the product unique: transaction matching, card entity binding, and financial workflow automation.

Platform Core Auth, multi-tenancy, RBAC, files, logging & API architecture
Unique Domain Logic Card management, transaction matching & accounting automation
15. Domain Modeling

A transaction is not just an amount

We don’t just write simple forms and CRUD tables – we engineer real-world business models and operational relationships.

When a financial transaction is modeled with its complete web of relationships, the entire downstream lifecycle can be automated with total precision.

TRANSACTION ENTITY MODEL
→ Card Entity Active Corporate Card binding
→ Employee / User Author & Cardholder profile
→ Tenant / Company Legal corporate entity scope
→ Receipt Document Attached immutable scan / PDF
→ Merchant Details Normalized vendor profile & VAT ID
→ VAT & Line Items Calculated tax breakdown (e.g. 6%, 12%, 25%)
→ Accounting Category General ledger account chart mapping
→ Status & Audit Log Complete / Verified for Export
16. Delivered Value

Delivered Results in Production

Concrete operational improvements in everyday finance workflows without fabricated metrics.

Unified Financial Flow

Card transactions, receipts, and contextual metadata are handled as a single financial entity through the complete lifecycle.

Zero Data Fragmentation

Users, corporate cards, transactions, and documents coexist in a unified system rather than scattered across inboxes and spreadsheets.

Automation with Oversight

Manual effort is drastically reduced while approval gates, exceptions, and audit trails remain fully transparent.

Engineered for Integration

Financial data is continuously transferred into external accounting ledgers rather than trapped in a consumer-style app.

Multi-Tenant SaaS

Architected around corporate workspaces, roles, and strict multi-tenant data boundaries on a single modern engine.

Do you have a financial workflow that still relies on manual intermediaries?

We engineer platforms that unite transactions, documents, people, and external financial systems into structured digital workflows.

Discuss your system with us

Cookie Usage

We use cookies to enhance your experience, analyze website traffic, and measure marketing performance. Read more in our cookie policy.

Cookie Usage

Strictly Necessary Cookies

Essential for core website operation and security. Cannot be disabled.