Utlegg Documentation

The Utlegg app supports several methods for importing documents automatically to avoid manual uploads. Documents received through these channels can be processed from the intake area or the user's inbox when creating a report. Supported intake methods include:

• Email sent to a designated receiving address
• EHF (Elektronisk Handelsformat)
• Other system integrations where invoice data is transmitted via API/integration.

The Utlegg app provides several integration paths depending on the organizational need:

• User Authentication & Onboarding: Use SSO and Provisioning for job account logins, or SCIM for automatic user provisioning.
• Financial Data Flow: Use 'Regnskap og eksport' (Accounting and Export) to send reports to accounting or payroll systems.
• Automated Document Intake: Use 'Fakturamottak' (Invoice Reception) for automatic invoice/document receipt, or 'Digitale kvitteringer og kortdata' for digital receipts and card data.
• Notifications & AI: Integrate with Slack for notifications, or use AI assistants (e.g., Claude) via MCP to query reports and expenses.

The Utlegg app is composed of three primary components that share a common set of core concepts (users, accounts, organizations, reports, attachments, assessments, and integrations):

1. Public API: The single source of truth for object status and business rules.
2. Client Applications: The mobile app and web dashboard, which implement the core concepts for end-users.
3. External Integrations: Handles SSO, provisioning, accounting, exports, and receipt streams. These may be event-driven or batch/setup-oriented.

Integrations with the Utlegg app typically follow these patterns:

• Redirect or step-by-step onboarding to link an organization to an external system.
• Webhooks for event-driven updates.
• Scheduled synchronization for structural data and status updates.
• Service accounts for secure machine-to-machine (M2M) calls.
• File import/export when direct API connections are unavailable.

Attachments serve as the evidentiary basis in the Utlegg app, assisting users with data entry and providing documentation for approvers and accounting. Attachments can enter the system via:

• Photos taken directly within the app
• Images or files selected from the device storage
• Sharing from other third-party applications
• Inbox or digital receipts received via integrations

Administrators have full access to Employee and Approver functions, as well as the following administrative menus:

• Oversikt (Overview): Track organization activity and KPIs.
• Brukere (Users): Add, deactivate, and change user roles.
• Avdelinger (Departments): Build the organizational structure.
• Prosjekter (Projects): Link expenses to projects or cost centers.
• Kontoer (Accounts): Manage the chart of accounts and posting.
• Eksport (Export): Export data to accounting or download as CSV.
• Arkiv (Archive): Find submitted reports via search and filtering.
• Innstillinger (Settings): Configure expense types, rates, workflows, integrations, and subscriptions.
• Kom i gang (Get Started): Access the new setup checklist.
• Enterprise: Manage multiple companies (available for organizations with group functions).

Utleggsappen distinguishes between a user's identity (account) and their organizational affiliation (role within a specific organization). A single user can hold different roles across different organizations. There are five primary role sets:

• Organization Role: Controls general access to the organization (Values: Bruker, Godkjenner, Admin).
• Department Role: Determines who approves for a specific department (Values: Medlem, Godkjenner).
• Project Role: Manages assignment and approval routing per project (Values: Eier, Admin, Godkjenner, Bruker).
• Account Role: Controls access to payment and payroll accounts (Values: Medlem, Godkjenner).
• Enterprise Role: Used for central management of multiple companies at a group level (Values: Bruker, Admin).

An Enterprise account provides a management layer above multiple organizations. It is the correct choice when you have multiple companies or departments that need collective governance but must continue to operate their own users, reports, and approvals independently. Key use cases include:

• Managing multiple organizations collectively.
• Standardizing categories or products across the group.
• Centralizing billing.
• Requiring group-level users with cross-organization visibility.

If you only have one organization, use the standard organization setup instead.