> ## 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. # Resolve one ambiguous direct submission from bank evidence > Persists an explicitly authorized recovery intent before provider recovery I/O. ## OpenAPI ````yaml /openapi.yaml post /payment-batches/{batch_id}/resolve 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 `. 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: /payment-batches/{batch_id}/resolve: post: tags: - Payments summary: Resolve one ambiguous direct submission from bank evidence description: >- Persists an explicitly authorized recovery intent before provider recovery I/O. operationId: resolvePaymentBatch parameters: - name: batch_id in: path required: true schema: type: string requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/PaymentResolutionInput' responses: '200': description: Current canonical batch lifecycle. content: application/json: schema: type: object required: - batch properties: batch: $ref: '#/components/schemas/PaymentBatch' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '409': description: The durable attempt evidence does not permit that resolution. '503': description: Global direct delivery readiness is unavailable. security: - firebaseToken: [] components: schemas: PaymentResolutionInput: type: object additionalProperties: false required: - customer_id - idempotency_key - resolution properties: customer_id: type: string idempotency_key: type: string minLength: 1 maxLength: 256 resolution: type: string enum: - submitted - rejected PaymentBatch: type: object additionalProperties: false required: - id - payload_hash - sources - purpose - requested_execution_date - debtor_name - debtor_iban - currency - total_cents - instructions - state - status_message - can_release - can_poll - can_resolve - can_resolve_submitted - can_resolve_rejected - requires_bank_authorization - created_at properties: id: type: string payload_hash: type: string pattern: ^[0-9a-f]{64}$ sources: type: array items: type: object additionalProperties: false required: - kind - id - revision properties: kind: type: string enum: - purchase_invoice - payroll_run - reimbursement id: type: string revision: type: string pattern: ^sha256:[0-9a-f]{64}$ purpose: type: string requested_execution_date: type: string format: date debtor_name: type: string debtor_iban: type: string currency: type: string const: EUR total_cents: type: integer format: int64 minimum: 1 instructions: type: array minItems: 1 items: $ref: '#/components/schemas/PaymentInstruction' state: type: string enum: - ready_to_release - delivery_pending - bank_authorization_required - bank_processing - awaiting_bank_confirmation - needs_review - rejected - paid status_message: type: string can_release: type: boolean can_poll: type: boolean can_resolve: type: boolean can_resolve_submitted: type: boolean can_resolve_rejected: type: boolean requires_bank_authorization: type: boolean created_at: type: string format: date-time PaymentInstruction: type: object additionalProperties: false required: - id - creditor_name - creditor_iban - amount_cents - currency - requested_execution_date properties: id: type: string creditor_name: type: string creditor_iban: type: string amount_cents: type: integer format: int64 minimum: 1 currency: type: string const: EUR remittance: type: string creditor_reference: type: string category_purpose: type: string requested_execution_date: type: string format: date Error: type: object description: Standard error envelope. properties: error: type: string description: Machine-readable error message. detail: type: string description: Human-readable detail. 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' 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_...`. firebaseToken: type: http scheme: bearer bearerFormat: JWT description: >- Firebase ID token from an interactive portal session. Required for interactive operations (payroll, company settings, API-key management) and invoice decisions allowed by the member's review permissions. ````