What’s new in Nordsynk

Your AI assistant can check the recorded outcome of an approved change. New DataLinks for unpaid invoices include cost centres and projects, with an option to include dimensions from invoice lines.

• A progress check reads the approval's recorded status without starting the change again.
• New open-invoice exports keep one row per invoice and show whether dimensions came from the invoice header or its lines. Existing links keep their column layout. Line details are optional and limited to 100 invoice reads per refresh.
• When a direct invoice detail limit is reached, the message explains how many reads were used and confirms that the next request was stopped before Fortnox.

When you approve several changes together, they run in the order they were submitted. If one fails or its result is unclear, the later changes wait, and you can try it again or skip it.

• Changes stopped by a temporary Fortnox error, such as too many requests, are retried automatically. If that still does not work, you can retry them yourself.
• Skipping a change asks you to confirm, and a change that is already running cannot be skipped.
• Retries and skips check the company's permissions and licence again, just like the original approval.

The ChatGPT guide follows ChatGPT's current menus, the first question works without a warning, and Nordsynk's cards follow light and dark mode in ChatGPT and Claude.

• The setup guides for ChatGPT and Claude follow their current menus and have new screenshots.
• ChatGPT no longer shows a security warning on the first question to Nordsynk.
• You can ask for your latest customer invoices without giving a period.
• Nordsynk's result and approval cards use the colours of ChatGPT and Claude in both light and dark mode.

Supplier invoice information is easier to review, yearly totals include credit notes, and limit messages explain what completed and how to continue.

• Credit notes are identified consistently when you read supplier invoices.
• You can filter supplier invoices for a period by supplier and include VAT and net amounts when available.
• Totals by supplier and financial year show invoice and credit-note counts and amounts.
• When a request from your AI assistant reaches its limit, the message shows the cap, what completed, and how to continue.

When you approve several changes together, Nordsynk carries them out in the order they were submitted. Later changes wait while an earlier item still needs a decision or its result is uncertain.

• A declined or expired change is skipped only if it was never attempted.
• If a change fails or the accounting system's result cannot be confirmed, later changes wait for review.
• When a voucher is created with files, the created voucher remains visible if an attachment fails or its result is uncertain. Check the attachments before continuing.

A connected admin can make a Fortnox company read-only in Nordsynk. The bank-statement review compares supplied statement rows with the company's ledger without changing Fortnox.

• The read-only setting keeps available reads open and blocks changes, including changes staged before the setting was enabled. Fortnox permissions still apply.
• The bank-statement review covers one confirmed period and ledger account, with up to 500 supplied statement rows. It reports matches and items to check; it does not update Fortnox's bank queue.

AI clients no longer need a special confirmation field: browser approval remains the default, while companies with auto-approve enabled can execute requested writes immediately.

• With browser approval enabled, Nordsynk still pauses the write and shows the exact company, operation, and request before anything reaches the accounting provider.
• With auto-approve enabled for a company, a requested write can execute without a separate approval page; provider permissions and Nordsynk access policies still apply.
• Older clients that still send the legacy confirmation field continue to work, but its value no longer changes the configured company policy.
• Dashboard and agent guidance now describe the same write-policy behavior across Fortnox and Spiris workflows.
• The Fortnox contract is synchronized with the current API, including EAN fields on contract, invoice, offer, and order rows.

AI clients can complete period reviews and invoice investigations through the right bounded workflow, while expired approvals record how work ended and how to continue.

• Period reviews resolve the selected Fortnox financial year and return ledger balances, transactions, receivables, and payables as one evidence bundle.
• Customer invoice investigations now combine invoice details, payment status, voucher evidence, and attachment availability while keeping optional failures visible.
• When an AI client reads a supplier invoice PDF, it sends only extracted fields to Nordsynk for a bounded exact, near, or no-match result; document bytes stay with the client.
• Expired approvals are classified as superseded, unopened, opened without a decision, or approved but unexecuted, with a safe recovery path recorded for each outcome.

Nordsynk can now carry a selected company and period through invoice investigation and correction preparation, while interrupted approvals explain how to continue safely.

• Period reviews return bounded findings with evidence references, affected documents, financial effects, and concrete next steps.
• Customer and supplier invoice investigations use the same selected company and period and report any unavailable or incomplete checks explicitly.
• Prepared corrections preserve their review and finding references in the approval preview so reviewers can trace each proposed change to its evidence.
• Expired approvals can be refreshed, failed batch members can be continued with corrected input, and unknown execution outcomes stop for verification instead of retrying blindly.

A browser-local tool now turns a Swedish SIE4 export into a focused monthly overview and five questions for the next finance review.

• No account or email address is required, and the accounting file never leaves the browser.
• The review highlights revenue movement, the accounts and vouchers with the largest changes, and bookkeeping-quality signals worth following up.
• Results can be switched between booked months, printed, or downloaded as a concise text brief.
• Månadskoll supports judgment rather than replacing reconciliation, month close, or year-end work. The tool is currently available in Swedish.

Nordsynk now prevents repeated invalid Fortnox work earlier, keeps corrective errors intact, and gathers supplier-invoice review evidence in one bounded workflow.

• Repeated or concurrent duplicate requests are stopped before they create extra Fortnox calls or duplicate write approvals.
• Known invoice, order, voucher, and print-template mistakes are validated before approval, and an unchanged request rejected by Fortnox must be corrected before it can be staged again.
• A supplier-invoice review can combine invoice details, attachments, attest state, and incoming OCR/inbox health while continuing past optional permission gaps.
• Passwordless sign-in delivery now has safer operational diagnostics without revealing whether an email address has an account.

AI clients can now see DataLink and every reviewed Nordsynk workflow when they connect, while Byrå teams can maintain one shared skill across client companies.

• A new MCP workflow-catalog resource exposes the same current route contract as codemode.describe, so clients no longer need to guess a DataLink search term.
• Customer-authored skills can be scoped once to an active Nordsynk Byrå account and discovered across its connected client companies without maintaining duplicate copies.
• Shared playbooks never act as a fallback company: the user and AI client still choose the exact Fortnox company before company-specific work.
• Approved DataLink and other deferred writes now preserve the exact Fortnox app profile and company context during server-side execution.

Nordsynk now distinguishes actionable request mistakes from connection failures and prevents avoidable high-volume or invalid voucher operations earlier.

• Validation and sandbox errors keep their exact corrective message instead of appearing as a generic Fortnox connection outage in compatible AI clients.
• Accidental one-record-at-a-time invoice, supplier-invoice, and voucher loops are stopped early and redirected to bounded bulk, ledger, SIE, or DataLink workflows.
• Voucher writes now verify that the selected Fortnox voucher series is manual before a single or batch approval is created or replayed.

Document attachments, audit-history reviews, and financial-year recovery now keep the intended company, record, and period explicit.

• Attaching an archive file to a voucher now requires an explicitly selected Fortnox financial year and verifies the exact voucher before approval, preventing identical series and numbers in another year from receiving the file.
• Claude can inspect the read-only Fortnox audit history available to the connected user, including supported topics and filtered activity, while existing Fortnox permissions still apply.
• Claude can now find one document attachment or several through the same predictable flow, and ledger-related actions have clearer Swedish names and descriptions.
• Financial-year and unsupported-filter errors now give targeted corrective guidance and stop unchanged retries instead of suggesting an unnecessary reconnect.

Send large, company- and fiscal-year-scoped Fortnox datasets directly to a spreadsheet without passing the rows through the AI client.

• Ask your AI client to create a DataLink for an explicitly selected company and Fortnox financial year, then approve it in Nordsynk as a write-sensitive access change.
• Copy the one-time IMPORTDATA formula from the Nordsynk dashboard into Google Sheets; Nordsynk serves the current cached ledger snapshot directly to the spreadsheet.
• Paste it into cell A1 of an empty sheet and click Allow access if Google shows its one-time external-data warning. Date columns remain readable as YYYY-MM-DD.
• No Google OAuth connection to Nordsynk, Google API key, or third-party destination integration is required.
• The bearer URL never enters the AI client's context. It is claimed once in the authenticated Nordsynk dashboard within 30 minutes and can be rotated or revoked there without disconnecting Fortnox.

Byrå teams can now route questions and pending Fortnox writes to the right accountant without losing company context or approval control.

• Send an accounting question to a named accountant who already has access to the selected client company.
• Delegate a pending single or batch write approval to an active accountant with write access; nothing executes until that accountant signs in and approves it.
• A shared Byrå inbox keeps the question, replies, status, company, and safe write preview together.
• Customers can list their submitted Nordsynk feedback, check its current status, and enable or disable email updates later.

Nordsynk can now research accounting questions against a maintained corpus of official Swedish rules and Fortnox guidance instead of relying on model memory.

• Research combines applicable law, Bokföringsnämnden material, Skatteverket and Verksamt guidance, and Fortnox product documentation while keeping their authority levels separate.
• Entity type, accounting framework, effective dates, and the selected fiscal period are checked before evidence is treated as applicable.
• Combined exact-match and meaning-based search returns precise citations and says when the published sources do not support a confident answer instead of guessing.
• The K2 annual-close workflow gathers a focused set of Fortnox evidence for one explicitly selected company and fiscal year, while clearly reporting unavailable checks or permissions.

AI clients can discover the real Fortnox request contract before calling it, while customers can follow the feedback they send to Nordsynk.

• Endpoint descriptions now expose the same accepted query parameters that Nordsynk validates, including pagination and sorting where supported.
• Full descriptions add constraints and request guidance instead of repeating the compact parameter list.
• Invalid paths, parameters, and unchanged failed retries are stopped before they become repeated Fortnox requests.
• Feedback has a customer-visible status, with optional updates sent only to the verified account email after explicit consent.

Claude and other compatible clients can receive PDFs and images through the authenticated Nordsynk connection without exposing the original document publicly.

• Document access stays bound to the signed-in Nordsynk user and the selected Fortnox company.
• Every PDF page is rendered to a JPEG for model vision. Nordsynk performs no PDF text extraction, OCR, description, summarization, or interpretation; the original PDF remains unchanged, tenant-scoped, and available through authenticated or manual retrieval.
• HEIC and HEIF images are delivered as compatible JPEG copies while the original stored document remains unchanged.
• Nordsynk does not OCR or interpret scanned documents; unsupported or expired files fail closed and can be read again from Fortnox.

Month-close reviews and multi-record invoice or voucher analysis are now faster, safer, and easier to repeat.

• A new month-close skill keeps the company, exact interval, and fiscal-year boundary explicit from evidence gathering through final reporting.
• Bounded invoice, supplier-invoice, and voucher detail reads replace long one-record-at-a-time request chains.
• Invalid skill calls now return the exact expected signature and unchanged validation retries are stopped automatically.
• Write approvals expose a Requested → Viewed → Decided → Executed funnel, while reliability separates platform failures from expected user, permission, and Fortnox business-rule stops.

Nordsynk now makes the analyzed accounting period explicit instead of relying on a Fortnox login year or a hidden default.

• Claude and other AI clients ask the user to choose before reading period-spanning financial data; a current, latest, or sole overlapping year is never treated as consent.
• Broken financial years are handled explicitly: choose a calendar year or a specific Fortnox financial year.
• Cross-company comparisons always require a user-selected period and comparison basis, and disclose each company's fiscal boundaries.
• Results show the exact analyzed interval and financial-year boundary.

A new MCP foundation for safer Fortnox work, multi-company access, reusable skills, and clearer in-client recovery.

• One code tool covers the reviewed Fortnox OpenAPI surface while keeping discovery compact.
• Multi-company access is selected per request—there is no fallback company.
• MCP Apps present company context, results, approvals, reconnect actions, and permission guidance inside supported clients.
• Reviewed Nordsynk skills and company playbooks make repeatable accounting workflows easier to discover and reuse.

New customers can connect companies and AI clients through a short guided setup without unrelated Fortnox permissions stopping activation.

• Capability checks explain which Fortnox areas the connected human user can access.
• A missing optional permission is guidance, not a blocker for the rest of Nordsynk.
• Connection verification and next steps are shown in one onboarding flow.