> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lastaccountingcompany.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get the monthly, custom-range, or all-time general-ledger view

> Per-account opening, debit, credit, and closing over posted entries only. Monthly periods on/after an active fiscal opening snapshot rebase onto it (snapshot base + later movements), exactly like the statements reads. All time uses the snapshot as its opening and sums every movement from that boundary, or starts from zero when there is no snapshot, so its closing matches the latest monthly view. Monthly periods clamp to [first..latest posted]. Kpis are served when the chart is known (FI): cash_cents is the closing cash balance, while revenue_cents and net_income_cents cover the selected movement range (one month or the all-time boundary through the latest period). books_state explains legitimately partial balances (mirror tenants, running history imports).



## OpenAPI

````yaml /openapi.yaml get /accounting/gl
openapi: 3.1.0
info:
  title: LAC Customer API
  version: '2026-07-15'
  description: >
    Last Accounting Company (LAC) is an AI-native accounting firm for Finnish
    SMBs:

    continuous reconciliation, daily close, real-time dashboards, and full Vero
    reporting.

    This API is the same surface the LAC customer portal UI uses. It gives you
    programmatic

    access to your books (read-only general-ledger views), financial statements,
    documents,

    invoicing, payroll, source-system connections, and the message channel to
    Björn, the

    accounting agent.


    ## Authentication


    Every request carries `Authorization: Bearer <token>`. Two token kinds are
    accepted:


    - **Portal API key** (`lac_sk_...`) — minted in portal Settings → API
    access. Keys have a
      scope of `read` or `write`. Read-scoped keys are refused on all mutating methods
      (POST/PATCH/DELETE). Write-scoped keys act as the `operator` role: they can never
      use payroll endpoints (reads included), change company settings, grant access,
      approve or return an invoice, or manage API keys. Payroll and company settings
      require an interactive admin or existing broad approver. Invoice decisions require the matching invoice
      review permission. Write-scoped keys can prepare draft partner
      seller profiles. An interactive company admin must review the evidence and activate
      a profile or change an active profile.
    - **Firebase ID token** — the interactive session token used by the portal
    UI itself.


    API keys are pinned to a single company, so the `customer_id` parameter
    (query string on

    GETs, body field on writes) can always be omitted when authenticating with
    an API key.

    Interactive tokens with access to multiple companies use `customer_id` to
    select one.


    ## Conventions


    - All field names are `snake_case` on the wire.

    - Monetary amounts are **integer cents** (fields suffixed `_cents`).

    - Rates and percentages are **basis points** (fields suffixed
    `_basis_points`;
      10000 = 100%, e.g. Finnish standard VAT 25.5% = 2550).
    - Quantities on invoice lines are decimal strings (e.g. `"1"`, `"2.5"`).

    - Dates are `YYYY-MM-DD`; periods are `YYYY-MM`; ranges accept `YYYY-MM`,
    `YYYY-Qn`,
      `YYYY`, `all`, `this_month`, or `last_6_months`.

    ## Limits


    - Document uploads: at most 20 files and 25 MB per request.

    - Sheet pagination: `limit` is capped at 200 rows per page (0 =
    unpaginated).


    ## Errors


    Errors return a JSON envelope `{"error": "...", "detail": "..."}` with a
    conventional

    HTTP status code (401 missing/invalid token, 403 insufficient scope or role,
    404 not

    found, 422 validation failure).


    More at
    [docs.lastaccountingcompany.com](https://docs.lastaccountingcompany.com).
  contact:
    name: Last Accounting Company
    url: https://docs.lastaccountingcompany.com
servers:
  - url: https://api.app.lastaccountingcompany.com/portal
    description: Production (note the /portal base path).
security:
  - apiKey: []
tags:
  - name: Company
    description: Company profile, identity, overview, and agent status.
  - name: Onboarding
    description: Saved customer onboarding facts, source inventory, and opening statements.
  - name: Books
    description: >-
      Read-only windows into the canonical general ledger: the spreadsheet-style
      Books/VAT sheet, financial statements, and analytics. There is no
      cell-edit or batch-edit API — the books are maintained by LAC. The one
      write here is a row declaration: your answer about a row (no receipt
      exists, private, a split, or a different booking), recorded as evidence
      for Björn.
  - name: Dimensions
    description: >-
      Project, cost-centre, department, and customer-defined reporting lenses
      over posted general-ledger lines. Provider catalogs are read-only; local
      axes and values are available for bank/file-only books.
  - name: Documents
    description: Receipt/invoice/contract uploads and per-file ingest metadata.
  - name: Messages
    description: The chat channel to Björn, the accounting agent.
  - name: Work log
    description: >-
      Append-only work-hours log (date, minutes, note). Hours are records for
      invoicing and payroll evidence; they do not post to the books. Kilometres
      are not logged here — vehicle travel is submitted as an expense claim in
      the portal, where statutory reimbursement rates apply.
  - name: Filings
    description: Filing authorization, review requests, and produced output packages.
  - name: Invoicing
    description: >-
      Sales invoicing — drafts, partner seller profiles, e-invoice sending, PDF
      finalizing, credit notes, reminders, recurring templates, and the
      invoice-customer register. LAC sends buyer invoices on the e-invoice
      network only. A partner-profile invoice also sends its legal seller a
      bookkeeping PDF copy.
  - name: Payroll
    description: >-
      Payroll workspace — employees, tax cards, employer settings, draft runs,
      and payslips. Every payroll operation (reads included) requires an
      interactive admin or existing broad-approver session and is NOT available
      to API keys.
  - name: Payments
    description: >-
      Contextual review and named-human release for source-bound purchase,
      payroll, and reimbursement payments. There is no manual payment composer
      and no bank file: a batch that cannot be delivered directly to the bank
      fails closed rather than becoming the customer's manual task.
  - name: Connections
    description: >-
      Source-system connections (bank, settlement providers, commerce,
      accounting systems, inbox/Gmail, Google Sheets) and service-connection
      requests/confirmations. PayPal consent can start through this API and
      returns a URL that a company admin must open. Other browser-interactive
      consent flows remain portal-only.
  - name: Imports
    description: Historical import runs (e.g. migrated books) and their artifacts.
  - name: API keys
    description: >-
      Manage portal API keys. These endpoints require an interactive admin
      session (Firebase token) and are NOT available to API-key bearers, which
      receive 403.
  - name: Lens
    description: >-
      Typed, display-ready read models over the books: the transactions window
      (full row universe, three-state status, keyset pagination), the per-row
      booking view, data coverage, and the connections catalog.
  - name: Accounting
    description: >-
      The accountant's read models: general ledger, journal entries, context
      cards, the filings strip with previews, and the SQL explorer. Every
      endpoint here requires LAC staff access or the company admin role; other
      bearers receive 403.
paths:
  /accounting/gl:
    get:
      tags:
        - Accounting
      summary: Get the monthly, custom-range, or all-time general-ledger view
      description: >-
        Per-account opening, debit, credit, and closing over posted entries
        only. Monthly periods on/after an active fiscal opening snapshot rebase
        onto it (snapshot base + later movements), exactly like the statements
        reads. All time uses the snapshot as its opening and sums every movement
        from that boundary, or starts from zero when there is no snapshot, so
        its closing matches the latest monthly view. Monthly periods clamp to
        [first..latest posted]. Kpis are served when the chart is known (FI):
        cash_cents is the closing cash balance, while revenue_cents and
        net_income_cents cover the selected movement range (one month or the
        all-time boundary through the latest period). books_state explains
        legitimately partial balances (mirror tenants, running history imports).
      operationId: getAccountingGL
      parameters:
        - name: customer_id
          in: query
          schema:
            type: string
        - name: scope
          in: query
          description: >-
            Defaults to monthly. range requires period and from_period; all_time
            accepts neither.
          schema:
            type: string
            enum:
              - monthly
              - range
              - all_time
            default: monthly
        - name: period
          in: query
          description: Month for monthly scope or inclusive through-month for range scope.
          schema:
            type: string
            pattern: ^[0-9]{4}-(0[1-9]|1[0-2])$
        - name: from_period
          in: query
          description: Inclusive first month for range scope.
          schema:
            type: string
            pattern: ^[0-9]{4}-(0[1-9]|1[0-2])$
      responses:
        '200':
          description: >-
            The GL view. scope echoes the served range. In all_time,
            [movement_period_from, period] is the inclusive accounting-period
            range behind debit and credit: movement_period_from is the active
            opening-snapshot boundary, or period_bounds.first when there is no
            snapshot. Range responses echo their effective start. Monthly
            responses omit movement_period_from.
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '400':
          description: Unknown scope, malformed period, or period combined with all_time.
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
components:
  responses:
    Unauthorized:
      description: Missing or invalid bearer token.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Forbidden:
      description: >-
        Insufficient scope or role — e.g. a read-scoped key on a mutating
        method, or an API key on an interactive-session-only endpoint.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    Error:
      type: object
      description: Standard error envelope.
      properties:
        error:
          type: string
          description: Machine-readable error message.
        detail:
          type: string
          description: Human-readable detail.
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      bearerFormat: lac_sk_...
      description: >-
        Portal API key minted in portal Settings → API access. Scope `read` or
        `write`; pinned to one company. Send as `Authorization: Bearer
        lac_sk_...`.

````