Skip to main content

Platform Overview

SpendOne is an AI-based platform for indirect corporate spend. It covers the full path from a request to spend money, through approval and ordering, to invoice processing, accounting export, and payment reconciliation.

This page is a mental map of the platform: the major modules, what they own, and how they connect. Use it as orientation before diving into specific guides or the API reference.

Module Groups​

The platform is organized into four groups. Each group contains modules that own a clear domain and expose their own set of API endpoints.

Procurement​

The intake and ordering side of spend.

  • Purchase Requests: A user expresses a need to spend money. Captures requester, items or description, cost center, intended supplier, and budget context. Source of truth for the early lifecycle.
  • Purchase Orders: Once approved, a request becomes (or is consolidated into) one or more purchase orders sent to suppliers. Tracks order state, expected delivery, and link-back to the originating request.
  • Approvals: Generic approval engine used by purchase requests, purchase orders, and invoices. Resolves who must approve based on configurable rules and tracks each step.
  • Suppliers: Master data for vendors: addresses, payment terms, tax IDs, default GL accounts, and approval status.
  • Products: Catalog and product master data, including subscription products and recurring items.

Finance​

The downstream financial processing of incoming documents.

  • Invoices: Ingestion, validation, matching, and approval of supplier invoices. Holds line items, tax breakdown, payment terms, and the link to the originating purchase order or subscription.
  • Accounting: Mapping of invoices to journal entries (cost centers, GL accounts, tax codes) and export to the customer's accounting system. See the Accounting System Integration guide.
  • Subscriptions: Recurring spend (SaaS, services). Tracks contract terms, billing cadence, renewal dates, and the link between an invoice and the contract it belongs to.
  • Reconciliation: Matches an incoming invoice against its purchase order and card transactions to detect duplicates, mismatches and missing documents. Not a module of its own: it is a substep of invoice review, under /invoices/{code}/reconciliation.

Payments​

How money actually leaves the company.

  • Payment Methods: Configured ways to pay an invoice: bank transfer (SEPA), corporate credit card, direct debit, etc.
  • Credit Cards: Card issuance and lifecycle, with the link from a card transaction to the invoice that justifies it. Transactions are read through /transaction-events/*; there is no card list or card-transaction list endpoint.

Cross-cutting​

Shared services that every module relies on.

  • Rules: Configurable business rules (approval thresholds, routing, automation triggers). Consumed by approvals, invoice processing, and purchase request validation.
  • Audit Log: Append-only record of state changes across the platform. Used for compliance and customer-side reporting.
  • Notifications: Email and in-app notifications driven by domain events (approval needed, invoice ready, card transaction unmatched).
  • Document Extraction: AI-based extraction of structured data from PDFs (invoices, delivery notes, order confirmations, quotes). Backs both human upload and inbox ingestion.

How Data Flows​

The following diagram shows the typical flow of a single piece of spend through the system.

Solid arrows are state transitions on real entities. Dotted arrows are cross-cutting services that observe or influence the flow without owning the data.

Where to Look Next​

  • Core Concepts: the object model these modules write into, and the roles that reach them.
  • The Spend Lifecycle: a stage-by-stage walkthrough of the same flow, with the endpoints each stage fires.
  • AI Capabilities: what the platform automates versus suggests, and where humans stay in the loop.
  • Accounting System Integration: how invoices become journal entries in the customer's accounting system.