> ## 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. # Correct an approved payroll run's payday before payment > Interactive admin or approver only. Rebuilds the approved run and its unapproved Incomes Register draft at the true payday, preserving the figures and append-only ledger evidence. Fails closed after payment, reporting, or other downstream authorisation, and when the new payday changes the payment month. ## OpenAPI ````yaml /openapi.yaml post /payroll/payment-date openapi: 3.1.0 info: title: LAC Customer API version: 2026-10-06.2 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 Customer API requests carry `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. The Shopify App endpoints are provider-facing exceptions with explicit per-operation security: App Home assets are public, App Bridge actions use a Shopify session JWT, and privacy webhooks use Shopify's raw-body HMAC. 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: >- Review and named-human release for source-bound purchase, payroll, and reimbursement payments. Direct Open Payments delivery is the only rail: there is no manual payment composer and no bank or Wise 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 connects with the company's own PayPal app, whose Client ID and Secret this API accepts, or with PayPal partner consent, which depends on PayPal approving LAC as a partner and returns a URL that a company admin must open. Other browser-interactive consent flows remain portal-only. - name: Shopify App description: >- Public Shopify App Home, App Bridge token exchange, installation handoff, and mandatory privacy webhooks. Offline access tokens never enter a browser. - 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: /payroll/payment-date: post: tags: - Payroll summary: Correct an approved payroll run's payday before payment description: >- Interactive admin or approver only. Rebuilds the approved run and its unapproved Incomes Register draft at the true payday, preserving the figures and append-only ledger evidence. Fails closed after payment, reporting, or other downstream authorisation, and when the new payday changes the payment month. operationId: correctApprovedPayrollPaymentDate requestBody: required: true content: application/json: schema: type: object additionalProperties: false required: - period - run_id - payment_date - idempotency_key properties: customer_id: type: string period: type: string pattern: ^\\d{4}-\\d{2}$ run_id: type: string payment_date: type: string format: date idempotency_key: type: string maxLength: 256 responses: '200': description: Updated payroll workspace with the corrected approved run. content: application/json: schema: $ref: '#/components/schemas/PayrollWorkspaceData' '400': description: The requested date or idempotency key is invalid. '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '409': description: The run is no longer safe to correct in place. security: - firebaseToken: [] components: schemas: PayrollWorkspaceData: type: object description: >- The payroll workspace for a period: employees, employer settings, and runs. Amounts are integer cents; rates are basis points. Interior shapes beyond the documented payment evidence fields vary and are returned as-is. additionalProperties: true properties: known_people: type: array description: >- The employee parties this company already reimburses, offered to the employee form so a new or existing payroll employee can be bound to the person they already are. Each entry carries the exact `business.party` reference — revision included — to send back as `expected_party`; a picker that showed one person cannot commit a link to whoever that id names by the time it is saved. Only the last four digits of a saved reimbursement account travel with this read, and only under the admin/approver payroll role this whole workspace already requires. items: type: object required: - party_id - resource - name properties: party_id: type: string resource: $ref: '#/components/schemas/CanonicalResourceRef' name: type: string email: type: string saved_account_last4: type: string description: >- Empty when this person has no saved reimbursement account; reuse is refused for them. linked_employee_id: type: string description: >- The payroll employee that already holds this person, empty when they are free to link. run: type: - object - 'null' additionalProperties: true properties: payment_blocked_reason: type: string enum: - superseded_run description: >- An ordinary predecessor remains readable but cannot receive another payment. bank_paid_date: type: string format: date description: >- Identifiable statement debits prove every positive salary left on this date. This does not create settlement confirmations. payment_date_reported: type: boolean description: >- The Incomes Register holds an active report fact for this run, so its payday cannot be corrected from the portal. Absent means no such fact. payment_instructions: type: - object - 'null' additionalProperties: true properties: salary_total_cents: type: integer minimum: 0 description: >- Sum of remaining transferable salary lines; confirmed and bank-observed salaries remain in reconciliation. salary_lines: type: array description: >- Remaining transferable salaries only. Frozen batches and superseded runs have no manual instructions. items: type: object additionalProperties: true required: - employee_id - payee_name - amount_cents - status properties: employee_id: type: string payee_name: type: string amount_cents: type: integer minimum: 1 iban: type: string status: type: string enum: - ready - missing_iban payment_reconciliation: type: - object - 'null' additionalProperties: true properties: lines: type: array items: type: object additionalProperties: true properties: review_revision: type: string pattern: ^sha256:[a-f0-9]{64}$ description: >- Exact current customer bank-review capability; absent means no customer confirmation is available. Revalidated under locks on submission. bank_transaction_id: type: string bank_booking_date: type: string format: date bank_description: type: string bank_counterparty_name: type: string bank_reference: type: string state: type: string enum: - confirmed - proposed - ambiguous - unmatched - awaiting_instruction - bank_review description: >- Bank review blocks another transfer without asserting settlement or an actionable confirmation proposal. CanonicalResourceRef: type: object additionalProperties: false required: - uri - revision properties: uri: type: string format: uri revision: type: string 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. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.