Uniconta MCP

20 questions to try

This question guide describes version 2.5.1. Check the running version and its release notes for later changes.

Questions, tools and underlying data for version 2.5.1. Updated 6 October 2026.

Prioritised for bookkeeping, financial management and operations. This guide presents questions, relevant tools and underlying data, and explains what missing information means and what the user can do about it.

How to use the list

For example, start with:

Use company [company-id]. State the company, dates and currency in your answers. Distinguish between documented findings, assumptions and missing information. If something cannot be checked, explain exactly what is missing, what that means for the conclusion and what the next step is. Do not make any changes.

Replace [company-id], [period], [date], [account-number], [customer-number], [budget-name] and [order-number] with specific values. For example, September 2026 means 2026-09-01 to 2026-09-30. Use the same date boundaries when comparing data.

The tools below represent the typical route to an answer; the agent may choose relevant follow-up calls. Companies are found and confirmed using list_companies, switch_company and get_current_company. get_accounting_context is used for financial years and periods; get_financial_reporting_context is used for existing budgets and templates.

When raw details are needed, use list_entities, describe_entity and query_entity. Older details may require your read approval, potentially through confirm_read. The agent must retrieve all necessary pages if the answer requires the complete dataset. If a read is interrupted or reaches a limit, the answer must explain which conclusions cannot yet be drawn.

When information is missing or needs investigation

When you try the questions, the agent may find discrepancies or lack the information needed to answer them fully. You should be able to understand what has been found, what it means and what you can do. It should also be clear which parts of the answer you can still use.

  • Missing information: You may, for example, be asked to obtain bank statements or supporting documents. The available figures may still be useful, but they are not necessarily reconciled. Check whether the answer identifies the affected accounts and periods and explains what is missing.
  • A discrepancy or validation error: Investigate the cause in Uniconta before correcting anything. A discrepancy does not, by itself, tell you which posting is wrong. During testing, you can compare the finding with what you see in Uniconta for the same company, period and scope.
  • An empty result: This does not always mean there is nothing to find. For example, orders without a delivery date do not appear in a query for next week's deliveries. Ask about the scope if you expected to see data.
  • Data could not be retrieved: You may be asked to sign in again or narrow the query. A failed query does not mean the balance is zero or that there is an accounting error.

If the answer simply says “the bank reconciliation evidence is incomplete” or shows the status incomplete, you can ask:

Which accounts and periods lack supporting evidence, what can we still conclude, and what exactly should I do?

When providing feedback on the test: Save your question and the agent's answer, and state the company, period and what you expected to see. Note whether the information is actually missing in Uniconta, whether the agent could not retrieve it, or whether the explanation was simply unclear. You do not need to correct accounting data to complete the test.

1. What should we investigate before closing the month?

Review [period]. What should we investigate before the month-end close? Prioritise specific findings and identify any checks that lack supporting evidence.

Tools: get_accounting_context, review_period; where needed, get_journal and get_account_activity.

Data: Financial years and period status, general-ledger balances calculated by Uniconta, retained journal lines, Uniconta's journal validation, customer/supplier reconciliation as of a specified date, and bank reconciliation evidence.

Scope and follow-up: The review does not close or post anything and does not cover every area, such as VAT, payroll, inventory and accruals/deferrals. If something is missing, the answer must identify the specific account or check and suggest the next investigation. Retained journal lines are not, by themselves, evidence of unposted work; the bookkeeper must establish whether they are reusable lines or entries that still need processing.

2. Can you prepare a short management summary of the finances?

Summarise the company's finances for [period] for a board meeting. Describe the financial result, balance sheet, liquidity and key uncertainties.

Tools: get_financial_statement, get_cash_forecast, get_receivables_aging, get_payables_aging; optionally, review_period to assess accounting quality.

Data: Financial reports calculated by Uniconta and the company's chart of accounts; posted bank/cash balances; current customer and supplier open items; and bank reconciliation results.

Scope and follow-up: The agent writes the summary from the tool results. Financial figures for specified dates and today's open items must be kept separate. If, for example, bank reconciliation evidence is missing, the posted figures can still be described, but must not be presented as confirmed available bank funds. State the specific uncertainty and the follow-up required. This is not an audit.

3. What does our liquidity look like over the next 60 days?

Show our projected cash position over the next 60 days. When is the balance lowest, and which payments and uncertainties should we focus on?

Tools: get_cash_forecast; list_open_customer_items and list_open_supplier_items for significant individual items.

Data: Bank/cash accounts in the chart of accounts and Uniconta-calculated general-ledger balances to establish the posted starting balance; current open items, outstanding amounts and due dates. Overdue and undated items, payment holds and bank reconciliation evidence are shown separately.

Scope and follow-up: Due dates are assumptions about payment. Items that are already overdue and items without a due date are shown separately and are not included as scheduled payments in the projection. Establish their expected payment dates, along with any missing payroll, tax and other payments, before using the forecast to make financial commitments. Your explicit additional inputs are shown as a separate scenario; existing items must not be counted again.

4. Can we rely on the liquidity figure we use for decisions?

Explain the basis for our liquidity figure. Which accounts are included, which balances are negative, and where is reconciliation or documentation missing?

Tools: get_cash_forecast; get_bank_reconciliation for further detail.

Data: Included bank/cash accounts, positive and negative posted balances, imported bank statements, bank reconciliation differences, unmatched items and supporting journal data.

Scope and follow-up: Posted net liquidity is not evidence of available funds. If bank reconciliation is missing, the bookkeeper must obtain and reconcile statements for the affected accounts. Before committing funds, the responsible person must also check current available balances, credit facilities and any restrictions with the bank. The agent must not set unknown amounts to zero. Selecting a subset of cash accounts requires your explicit confirmation; excluded balances remain visible.

5. How has our financial result developed compared with last year?

Show the income statement for [period] and the corresponding period last year. Highlight the largest changes in revenue and expenses.

Tools: get_accounting_context, get_financial_statement; optionally, get_account_activity for specific explanations.

Data: Period movements in the general ledger calculated by Uniconta, excluding opening entries, account types, the chart of accounts and any selected report template. Two explicit date periods.

Scope and follow-up: Changes in amounts do not establish their causes. The agent can identify the largest changes and retrieve postings for follow-up. If supporting documents or a business explanation are missing, the bookkeeper or responsible person must supplement the information. Compare periods of equivalent length and with a comparable accounting basis.

6. What does the balance sheet look like on a specific date?

Show the balance sheet as of [date], preferably compared with [comparison-date]. Explain the largest changes in assets, liabilities and equity.

Tools: get_accounting_context, get_financial_statement with balance_sheet.

Data: The chart of accounts and balances calculated by Uniconta from the start of the relevant financial year to each balance-sheet date, including opening entries.

Scope and follow-up: Report data is not an audited financial statement or a completed statutory filing. Each comparison date requires the correct financial-year start. The fact that a report can be calculated does not prove that, for example, bank balances, inventory and receivables are supported by evidence; material balance changes must be followed up with the relevant reconciliations and supporting documents.

7. Where do we deviate most from the budget?

Compare the posted financial result for [period] with [budget-name]. Show the largest variances in amounts and percentages, and explain the calculation basis.

Tools: get_financial_reporting_context, get_budget_vs_actual.

Data: An existing Uniconta budget and actual movements calculated by Uniconta for the same period and report rows. Uniconta handles the budget's recurrence, adjustments and any sub-budgets.

Scope and follow-up: Variance is actual minus budget; the sign alone does not determine whether the variance is favourable. If the budget is zero, the amount variance is shown, but the percentage cannot be calculated. If the company lacks a budget for the period, the user must select an existing budget or have the relevant budget created in Uniconta. The agent must neither invent budget figures nor switch company without making it clear. No breakdown by dimension.

8. Can I get a trial balance broken down by month?

Show a trial balance with one column for each month in [period]. Show monthly movements and a separate closing balance including opening entries.

Tools: get_accounting_context, get_trial_balance.

Data: The chart of accounts and debit, credit and net amounts calculated by Uniconta for the selected date columns. Inclusion of opening entries is explicitly selected for each column.

Scope and follow-up: Opening entries here means the financial year's opening entries. Monthly movements and accumulated balances must not be added together, and subtotal accounts must not be counted again on top of the underlying accounts. If the complete report cannot be retrieved, the agent must explain the limitation and suggest, for example, fewer periods per call rather than presenting a partial report as complete.

9. Which postings explain the movement on this account?

Show the opening balance, movement and closing balance for account [account-number] in [period]. Which postings contribute most to the movement?

Tools: get_account_activity.

Data: Complete balances calculated by Uniconta and detailed general-ledger transactions for the specific account and period, including dates, voucher references and amounts.

Scope and follow-up: Postings may be paginated and may require read approval for older history. The agent must retrieve all relevant pages before identifying the largest contributors. If it cannot do so, the complete report totals can still be shown, but the explanation of the movement must be marked as incomplete. Specific causes often require supporting documents.

10. Do customer and supplier balances reconcile with the general ledger?

Check as of [date] whether customer and supplier balances reconcile with the general-ledger control accounts. Show any differences and their calculation basis.

Tools: get_accounting_context, review_period; get_account_activity to follow up on the control accounts.

Data: Customer/supplier balances as of the specified date from Uniconta, posted general-ledger balances and the currently configured control accounts. The difference is the general ledger minus the relevant subledger.

Scope and follow-up: This uses balances as of a specified date, rather than comparing the historical general ledger with today's open items. If there is a difference, the bookkeeper should investigate postings to control accounts, opening entries and any changes in account assignments. The difference does not, by itself, identify what should be posted. A net match does not rule out offsetting errors either.

11. Which bank accounts have differences or missing reconciliation evidence?

Review the bank reconciliation for [period]. Show differences, unmatched items and missing bank statement evidence for each bank account.

Tools: get_bank_reconciliation; optionally, get_account_activity and query_entity for details.

Data: Bank configuration, imported bank statements, posted bank balances, current matching status, unmatched item counts/amounts/oldest dates, and bank-related journal lines.

Scope and follow-up: Amounts in different bank currencies are kept separate. Where statements are missing, the bookkeeper must obtain evidence for the entire period, import it if necessary and repeat the reconciliation. Where there is a difference, investigate the statements, opening balance and specific unmatched items. A relationship between amounts is a lead, not proof of a particular account assignment. Matching status is observed now; zero unmatched items or the latest statement date does not prove complete coverage.

12. Are there any journals that fail validation?

Review the journals using [date] as the validation date. Show retained lines and validation errors from Uniconta that the bookkeeper should investigate. Do not post anything.

Tools: list_journals, get_journal with validate=true.

Data: Journal headers, retained journal lines and the result of Uniconta's journal validation, including the first returned error and any fields, voucher references or lines.

Scope and follow-up: Validation applies to the entire journal, and the validation date does not filter its lines. If Uniconta does not identify a voucher or line, the agent must say so and direct the user to check the entire journal in Uniconta. The first error is not necessarily the only one. Passing validation proves neither posting nor accounting correctness; the status of the lines and their supporting documents still need to be established.

13. How much are we owed, and how old are the receivables?

Show our total receivables, split into items not yet due and aging buckets. Highlight the largest overdue customer balances.

Tools: get_receivables_aging.

Data: Today's customer open items, with customer, outstanding amount, due date and currency. Totals are calculated over all open items within the tool's complete read.

Scope and follow-up: This represents the position today and does not reconstruct open items as of a historical balance-sheet date. Items without a due date must be shown separately; the bookkeeper should check payment terms and dates before using them in a payment forecast. The customer list may be shorter than the dataset used for the total; ask for specific customer details when following up.

14. Which customers should we follow up with first?

Prioritise the customers we should contact about overdue payments. Show amounts, delays and the specific open items behind the prioritisation.

Tools: list_worst_payers, list_open_customer_items; optionally, get_customer_statement.

Data: Current customer open items, due dates, days overdue, outstanding amounts and available dunning information.

Scope and follow-up: The ranking describes open items now, not documented historical payment behaviour or customer churn risk. Before contacting a customer, the responsible person should check for disputes, credit notes, payment arrangements and recent receipts, for example. Missing dunning information does not prove that no reminder has ever been sent. No reminders are sent.

15. What is the status of this customer's account?

Give me an overview of customer [customer-number]: balance, payment terms, open items and recorded dunning information.

Tools: get_customer_statement.

Data: The customer master record (DebtorClient), the customer's current balance, payment terms, blocked status and customer open items with available dunning fields.

Scope and follow-up: This is a current receivables overview, not a complete historical statement including all paid invoices and settlements. Missing dunning information must be described as not provided, rather than as proof of no previous contact. If the balance is disputed, the bookkeeper must investigate invoices, payments and settlements in Uniconta.

16. How much do we owe our suppliers?

Show total supplier debt, split into amounts not yet due and overdue amounts. Which suppliers have the largest overdue balances?

Tools: get_payables_aging.

Data: Today's supplier open items, with supplier, outstanding amount, due date and currency. This tool shows debt as positive amounts owed.

Scope and follow-up: This is the current open debt, not a historical supplier reconciliation. A limited supplier list does not limit the totals. Large or old balances provide a basis for follow-up; check supporting documents, credit notes and any disputes before making a payment decision.

17. Which supplier payments fall due in the next 14 days?

Prepare information to support decisions on supplier payments over the next 14 days. Show overdue items separately and flag payment holds. Do not create any payments.

Tools: list_open_supplier_items with dueWithinDays=14; use item due dates to separate already overdue items from upcoming payments. onlyOverdue=true can check the overdue portion. Optionally, get_cash_forecast.

Data: Supplier open items with amounts, due dates, payment IDs/methods, voucher references and payment holds. For a liquidity assessment, supplement these with the cash forecast.

Scope and follow-up: dueWithinDays=14 also includes items that are already overdue. The agent must separate them from upcoming due dates and count each item once. Items on payment hold require clarification from the person responsible for payments; they must not simply be proposed for payment. Undated items must also be clarified if the payment plan is to be complete. The tool does not make bank payments or create payment files, and does not document payment approval.

18. Which sales orders are scheduled for delivery next week?

Find sales orders with planned delivery in [period]. Show the customer, delivery date, approval status and order details we should follow up on. Also state how many retained orders lack a delivery date and therefore cannot be assigned to the period.

Tools: list_sales_orders; get_sales_order for relevant orders.

Data: Retained sales order headers (DebtorOrderClient) with delivery date, customer and approval status; current order lines for further detail.

Scope and follow-up: An empty date-filtered query may be due to missing delivery dates. The agent should show how many retained orders lack a date, based on a complete query without a date filter. The person responsible for orders can then establish and record the planned dates, after which the question can be repeated. Planned dates do not establish stock availability or the ability to deliver; approval is not delivery or invoicing status.

19. What has been delivered and invoiced on this order?

Review order [order-number]. Show item numbers, quantities, prices, discounts, and delivered and invoiced quantities per line. Flag unknown information.

Tools: get_sales_order.

Data: The current sales order header and retained order lines (DebtorOrderClient and DebtorOrderLineClient), including QtyDelivered and QtyInvoiced.

Scope and follow-up: All relevant pages of lines must be read. Deleted lines and historical invoices are not reconstructed. If an order or a piece of information is missing, the person responsible for orders should check the delivery and invoice archives in Uniconta. A missing result does not prove that the order never existed or was never invoiced.

20. How would invoicing this order be posted?

Show a preview of invoicing order [order-number], including the simulated postings. Do not post or send the invoice.

Tools: get_sales_order, invoice_order in its initial preview call.

Data: The existing order and its lines, customer data and Uniconta's own invoice simulation, including general-ledger/customer postings and VAT amounts.

Scope and follow-up: The preview does not post anything. The simulation may cover fewer units than the entire order, so compare the underlying quantities and simulated amounts. The user can review the result without confirming anything. Actual invoicing requires separate human approval and a client with the necessary support. If the response to an actual write is lost, use get_operation_status and check in Uniconta; invoicing must not be blindly repeated.

General qualifications

Access depends on your Uniconta login, permitted companies and the company's configuration. Missing information must be explained specifically; it must not be replaced with zero or a definitive conclusion. Financial reports cover one company and do not support dimension filters in the tools described here. Multiple tool calls do not constitute a single consistent snapshot of the accounts. Answers should always state the company, relevant dates, currency and data limitations.

Source references in the project

The source paths follow the current Core structure. The tool descriptions are still based on version 2.5.1; updating the paths does not constitute a new validation of functionality.

  • Uniconta.MCP.Core/Tools/Shared/McpServerInstructions.cs
  • Uniconta.MCP.Core/Tools/Accounting/LiquidityTools.cs
  • Uniconta.MCP.Core/Tools/Accounting/ReceivablesTools.cs
  • Uniconta.MCP.Core/Tools/Accounting/PayablesTools.cs
  • Uniconta.MCP.Core/Tools/Invoicing/SalesOrderTools.cs
  • Uniconta.MCP.Core/Tools/Invoicing/InvoiceTools.cs
  • Uniconta.MCP.Core/Tools/Accounting/FinancialReportingTools.cs
  • Uniconta.MCP.Core/Tools/Accounting/PeriodReviewTools.cs
  • Uniconta.MCP.Core/Tools/Accounting/NativeTools.cs
Tool list — raw descriptions and underlying data

All 33 tools, in alphabetical order by tool name. Description is the tool's English description for agents in version 2.5.1. Configuration-dependent page limits may vary between servers; always use the limits stated by the connected server. Data explains the underlying data. The existing English data explanations from the Danish source are retained here once, without the duplicate Danish paragraphs.

confirm_read

Description:

Record the user's explicit chat decision for an approvalRequest returned by query_entity or get_account_activity. First show its company, query scope, expiry and row limit to the user and ask whether to proceed. WAIT for their reply before calling this tool. Set approved=true only after they explicitly accept that preview; set false if they decline. Never infer approval from the original data request. The server trusts the agent to report the human's decision; this is not a client-verified dialog. This changes only temporary read-approval state, never ERP data, and fetches no rows. After acceptance, repeat the original read tool call with the returned readApproval. All existing access checks and read limits still apply. Cannot approve ERP writes.

Data: The server's temporary read-approval request: caller, company, query, date range, expiry and row limit, together with the user's explicit decision. Updates only the approval state and retrieves no ERP records.

create_customer

Description:

Create a new customer (DebtorClient) with its name, CVR number and address. This is a two-call write: the first call previews what will be created and writes nothing, returning a requestState. Call again with that same requestState and confirmed=true, and the server will ask the user to approve the write before it happens: the tool call returns input_required until they do. An account number that already exists is REFUSED and the existing customer is named, so use update_customer to change one instead. A CVR already used by another customer is allowed but reported in the preview, because branches and group companies share one. Requires a client that supports elicitation. Disabled while output anonymisation is enabled.

Data: The supplied customer details and existing customer master records (DebtorClient), used to check the account number and possible duplicate CVR registration numbers. The preview saves nothing in the ERP; the customer record is created only after explicit approval.

create_quick_invoice

Description:

Invoice a customer using two separate human approvals. Save each step's operationId; after a lost response use get_operation_status before attempting another write. First call: preview creation of an unposted sales order, without writing anything. Confirm its requestState to approve order creation; this returns a NEW requestState and Uniconta's simulated invoice, including ledger accounts and VAT. Confirm that new state to approve posting. An abandoned simulation leaves the named order unposted; resume with invoice_order, do not create it again. A nonzero unit price is always required. The invoice date is fixed at the posting preview. A posted invoice cannot be withdrawn; correction requires a credit note. Requires elicitation. Disabled while output anonymisation is enabled.

Data: The selected customer (DebtorClient), the supplied invoice lines and, after creation, the sales order and its lines (DebtorOrderClient, DebtorOrderLineClient). Uniconta's invoice simulation provides VAT and general-ledger/customer postings. The first approval creates an unposted order; a new, separate approval posts the invoice. The server also stores approval state and operation status.

describe_entity

Description:

Describe one entity's fields and their types, so you know exactly what to filter, sort and select on in query_entity. These are declared SDK properties for the selected company, including custom properties on its generated User types and user tables. Uniconta still applies the selected company licence, configuration and permissions to data calls. Describe the entity for the company you are about to query. See list_entities for valid entity names.

Data: SDK metadata for the selected table: declared field names and data types, including the company's generated custom fields and user tables. The description comes from the schema, not from a sample of accounting records.

get_account_activity

Description:

Explain one posting account with SDK opening, period movement and closing balances plus a page of supporting postings. Company-wide, one financial year per request; no dimension filters. Movement excludes primo. Closing includes primo from year start; opening is closing minus movement and includes first-day primo. That arithmetic identity is not an independent reconciliation. Totals are independent of the page. Sum/formula/percentage accounts use get_trial_balance. Older/future raw postings require the same human read approval as query_entity. For approval_required, show approvalRequest.preview, await the user's answer, call confirm_read, then repeat with readApproval. Never sum a partial posting page or interpret pending approval as an empty result. Page size defaults to 100 and allows up to 1000 rows. A response-size-limited page includes nextSkip; continue from that value. Shared read budgets still apply.

Data: The chart of accounts and financial years, plus Uniconta's report calculation of the account's period movement and closing balance including opening entries. Also reads general-ledger transactions (GLTransClient) for the selected account and period, including dates, vouchers, text and amounts. Report totals and detail pages are retrieved separately.

get_accounting_context

Description:

Resolve an explicit accounting period against SDK financial years. Returns available years, month/year posting states and company currency. period_unavailable means the dates are not covered by unambiguous consecutive years, not zero activity. State is configuration, not permission to post.

Data: Company identity and currency, plus financial-year configuration and monthly posting states (CompanyFinanceYear). Checks whether the requested dates are covered by the financial years. Does not retrieve a trial balance or raw general-ledger transactions.

get_bank_reconciliation

Description:

Read SDK/WPF bank reconciliation evidence for an explicit period. Returns per-bank closing statement and posted balances, differences in bank currency, unmatched counts/net/gross amounts and oldest dates, pending journals and void counts. Never net different currencies or count pending journals as posted cash. No raw transaction descriptions are returned. Missing statements or reads produce incomplete/unavailable, not zero differences. Matching is observed now; it does not establish historical match state or statement completeness. Last statement date is an activity date, not a coverage certificate. Explain which bank and period lack evidence, what cannot be concluded, and ask for a complete statement/import and reconciliation. Use query_entity/get_account_activity with normal history approval for detailed investigation. No import, matching, settlement or posting.

Data: Bank reconciliation configuration (BankStatement), imported bank statements and Uniconta's report data for the bank account's general-ledger transactions and journal lines. Uses the bank's starting balance, SDK opening entries, currency, reconciliation status and void flags. Returns totals and reconciliation evidence; it does not query the bank directly for an available balance.

get_budget_vs_actual

Description:

Compare posted actual movements with one explicitly selected SDK budget for the same period and report rows. Discover budgetName with get_financial_reporting_context. SDK calculates recurrence, regulation and base/sub-budgets; missing budgets never become zero. One financial year, company-wide, company currency, no opening entries. layout is profit_and_loss or template with templateName. Returns actual, budget, actual-minus-budget and relative percentage using signed budget, as WPF; zero budget gives null percentage. Do not infer favourable/unfavourable from sign alone. Template selections include posting accounts only, as WPF; use chart layout for budgets on subtotal accounts. No closing balance-sheet budgets, dimension filters, saved report columns or forecast substitution. Does not create or change a budget.

Data: The chart of accounts, financial years, the named budget (GLBudget) and, optionally, a report template and its lines (GLReportTemplate, GLReportLine). ReportAPI.GenerateTotal and GenerateBudgetTotals supply actual and budget amounts for the same period; MCP calculates differences and percentages for the resulting report rows. The budget is not changed.

get_cash_forecast

Description:

Project posted bank/cash balances using current customer and supplier open items in company currency. Use horizonDays=60 for a 60-day liquidity assessment. Shows non-overlapping periods and the lowest daily net balance, including shortages inside a period. Due dates are assumptions, not confirmed payment dates. Overdue, undated and beyond-horizon items are reported separately and EXCLUDED from scheduled cash flows; on-hold scheduled amounts are identified as subsets. Payroll, tax, future sales and other flows are absent unless represented in the data. Optional additionalCashFlows produces a SEPARATE scenario alongside the unchanged base forecast; use only explicit user-supplied dates and company-currency amounts not already in open items. Never invent or double count expected payments. cashBasis separates positive and negative posted balances and includes bank reconciliation evidence. SDK Bank classification may include loans, credit cards or restricted funds; the default net balance is NOT verified available cash. Optional includedCashAccounts selects an explicit user-confirmed subset; excluded balances remain visible. Never exclude a debt just to improve the forecast. Credit facilities and availableToSpend remain unknown. No ERP writes. State the assumptions and missing cash flows in the answer.

Data: The chart of accounts (GLAccountClient) and financial years (CompanyFinanceYearClient), general-ledger totals (GLTransSumClient) for completed months and general-ledger transactions (GLTransClient) in the current month, used to establish the posted starting balance. Also uses complete customer/supplier open-item sets (DebtorTransOpenClient, CreditorTransOpenClient) and bank reconciliation evidence. Explicit user assumptions can be included in a separate scenario. Does not retrieve the bank's current available balance or credit limit.

get_current_company

Description:

Show the SDK session's currently selected company, including id, number and name. A companyId of 0 means no company has been selected: call switch_company or pass companyId explicitly. Separate OAuth logins keep independent selections; Basic authentication does not retain selection between requests.

Data: The authenticated SDK session's current company selection and the company's ID, number and name. Retrieves no accounting records; company ID 0 means that no company has been selected.

get_customer_statement

Description:

One customer's receivables position: balance, payment terms, every open item aged, and available dunning fields on those open items. Answers 'what is the story with this customer'. This is the current position, not a historical statement, settled-payment history or complete dunning log. Missing dunning fields do not prove that no reminders were sent.

Data: The customer master record (DebtorClient), including balance, payment terms, group and blocked status, together with current customer open items (DebtorTransOpenClient), outstanding amounts, due dates and available dunning fields. This is not a complete historical archive of payments and customer communications.

get_financial_reporting_context

Description:

Discover company currency, configured financial report templates, budget names/date coverage/active status and saved report names on v95. Use before choosing a template or budget. Saved reports are discovery only: select a template and explicit periods; saved columns and print settings are not executed. Empty configuration is reported honestly; no template or budget is invented. Does not change report settings.

Data: Company currency, report templates (GLReportTemplate), budgets (GLBudget) and saved report definitions (Balance). Returns information such as names, budget periods and active status. Saved report columns and print settings are not executed.

get_financial_statement

Description:

Generate a financial statement from native SDK actual totals and the configured chart of accounts or a named report template. layout=profit_and_loss uses movements without opening entries; balance_sheet requires financial-year-start periods with includeOpening=true; template applies configured account selections, sign inversions, hidden totals and bounded arithmetic/Sum formulas in WPF order. At most 12 explicit columns, each within one configured financial year. Use get_accounting_context for year boundaries. One company, company currency, full cent precision; no dimension filters, journal simulation, cross-company columns or PDF rendering. Hidden rows remain marked for traceability; do not add detail and subtotals together. Unsupported formulas fail explicitly. SDK template division by zero returns zero, as WPF; formula units depend on the template author and are not inferred. This reproduces reporting data, not an audited or statutory filing. Read-only aggregate limits apply; detailed historical postings use normal read approval.

Data: A fresh chart of accounts, financial years and Uniconta's calculated general-ledger totals through ReportAPI.GenerateTotal and SDK formatting. A named template also uses GLReportTemplate and GLReportLine, including account selections, signs, hidden totals and supported formulas. The result consists of report rows, not a raw transaction export.

get_journal

Description:

Inspect a retained journal with paged lines and optional read-only SDK CheckDailyJournal. skip=0 or validate=true reads the COMPLETE journal fresh. Continuation pages with validate=false may reuse this login's complete read for up to five minutes from creation; keep company, journal and postingDate unchanged. Other clients' changes may remain invisible until refresh/expiry. After changes restart at skip=0 and validate again. postingDate is a check date, not a line-date filter. Validation checks all lines, including those outside a review period; SDK returns the first error. Normally validate the first page only, then use validate=false and nextSkip for following pages. Shared complete-read limits apply. Without an SDK line/voucher reference, do not attribute the error to a specific line or prescribe a correction. A pass does not prove posting or accounting correctness. Does not save, post, simulate, allocate voucher numbers or infer imbalance from line amounts. Retained recurring lines may have been posted previously. For fixed-date journals supply the intended postingDate; Today uses SDK date behaviour, Free uses line dates. Page size defaults to 100 and allows up to 1000 rows. A response-size-limited page includes nextSkip; continue from that value. Shared read budgets still apply.

Data: A journal header (GLDailyJournal) and all its retained journal lines (GLDailyJournalLine). When validation is requested, PostingAPI.CheckDailyJournal checks the entire journal. Returns a page of lines and, optionally, the validation result; does not save or post the journal.

get_operation_status

Description:

Read a durable write checkpoint using the operationId returned by its preview. Works after a server restart. Only the original login and company can read it. For an invoice, also checks Uniconta for matching invoices. A matching order alone does not prove this operation created the invoice; no match does not prove a timed-out posting failed. Never posts, retries, approves or releases an unresolved write. Disabled while output anonymisation is enabled.

Data: The MCP server's durable operation journal for the specified operationId, scoped to the original login and company. For invoice operations, also reads relevant invoices (DebtorInvoiceClient) in Uniconta to check details such as order, invoice number, customer and amount. The tool neither retries nor approves a write.

get_payables_aging

Description:

Total unpaid supplier balances split by how overdue they are: not due, 1-30, 31-60, 61-90 and over 90 days, plus items with no due date. Answers 'how much do we owe and what is already late'. Amounts are positive for money owed. Calculated as of today against the company currency, not a historical balance. Totals cover all open items even when the supplier list is capped.

Data: All current supplier open items (CreditorTransOpenClient) within the read limits: supplier, outstanding amount in company currency, due date, currency information and payment hold status. Calculates aging buckets and totals; limiting the displayed supplier list does not change the data used for the totals.

get_receivables_aging

Description:

Total open customer balances split by how overdue they are: not due, 1-30, 31-60, 61-90 and over 90 days, plus items with no due date. Answers 'how much are we owed and how old is it'. Calculated as of today in company currency, not a historical balance. Totals cover all open items even when the customer list is capped.

Data: All current customer open items (DebtorTransOpenClient) within the read limits: customer, outstanding amount in company currency, due date, currency information and available dunning fields. Calculates aging buckets and totals; limiting the displayed customer list does not change the data used for the totals.

get_sales_order

Description:

Read one retained sales order by orderNumber, including customer information on the order and a bounded page of its lines. Shows quantities, prices, discounts and per-line delivery/invoicing status. Missing quantities are unknown, not zero. No invoice simulation or writes. Order totals are not a payable invoice amount. When truncated, repeat orderNumber with skip=nextSkip to read more lines. Example: {"orderNumber":29}.

Data: One retained sales order header (DebtorOrderClient) and a page of its order lines (DebtorOrderLineClient). Uses customer information on the order, dates, currency, prices, discounts, ordered quantities, delivered quantities and invoiced quantities. Does not retrieve a historical invoice archive or simulate invoicing.

get_trial_balance

Description:

Complete trial balance / saldobalance from Uniconta's .NET report API, following WPF's date and primo parameters and SDK account formatting. Supply 1-24 columns for monthly movements, year-to-date or comparisons. For period movements use includeOpening=false; for a closing balance start at the financial year's first day and use includeOpening=true. Dates must be covered by financial years. Returns all accounts including SDK sum and expression accounts, in company currency, debit minus credit. No raw ledger export, unposted journals, dimension filters or custom report template. Dedicated complete reports retain their explicit period without the generic 90-day cutoff or generic historical-read approval. Read budgets and complete-result limits apply. Unavailable while output anonymization is enabled.

Data: Financial years, a fresh chart of accounts and Uniconta's report calculations through ReportAPI.GenerateTotal and Format, including SDK subtotal and formula accounts. Each column has explicit dates and an opening-entry setting. Uniconta calculates the amounts; MCP does not retrieve the entire general-ledger history to calculate the report itself.

invoice_order

Description:

Invoice a sales order that already exists, by its order number. Save operationId and use get_operation_status after a lost response before attempting another write. The same posting approval as create_quick_invoice: the first call shows Uniconta's own simulated posting and posts nothing, the second posts it after the user approves. It does not create or edit the order before simulation; approval DOES post an invoice. Use the simulated quantities, VAT and total as the posting preview, not stored order totals; partial invoicing can differ. If the order changes between the two calls the write is refused. Order, lines, customer and simulated postings are rechecked; the upstream API cannot make this check atomic with posting. An invoice number is drawn on confirmation and CANNOT be withdrawn. Requires a client that supports elicitation. Disabled while output anonymisation is enabled.

Data: The existing sales order and all relevant lines (DebtorOrderClient, DebtorOrderLineClient), the customer master record and Uniconta's invoice simulation with amounts, VAT and postings. Also uses the server's approval snapshot, operation journal and any email permission. The first call is a preview; posting occurs only after separate approval and revalidation.

list_companies

Description:

List companies returned by the authenticated SDK session, restricted by the server's company allowlist. Returns company id, number and name. Uniconta permissions still apply when opening a company.

Data: The company list returned by the user's authenticated SDK session, filtered by the MCP server's company allowlist. Returns company ID, number and name. Uniconta still controls access to each company's data.

list_entities

Description:

List the Uniconta entity (table) names that can be read with query_entity. Call this first to discover what is available instead of guessing entity names. A tenant can expose hundreds of entities, so pass nameContains to narrow the list when you already know roughly what you are looking for. Supply companyId or select a company to include its custom fields/types and user tables. Without a selected company, only standard SDK entities are listed. Discovery describes types; Uniconta permissions still apply when reading data.

Data: The SDK table catalogue and, when a company is specified or selected, that company's generated user types and user tables. Returns available table names; does not read the accounting data stored in those tables.

list_journals

Description:

List complete journal headers in one company. Headers are reusable templates, not evidence of outstanding work. Use get_journal for retained lines and SDK validation. Shared complete-read limits apply.

Data: The company's journal headers (GLDailyJournal), including details such as name, identity, date function and blocked status. Does not retrieve journal lines or validate journals; use get_journal for those operations.

list_open_customer_items

Description:

The individual unpaid customer items behind the ageing: due date, days overdue, open amount, invoice number and a link to the invoice document. Use after get_receivables_aging to see what makes up a figure, or pass an account to see one customer. These are items open today, not at a past reporting date. top caps the displayed items only; totals cover every match. If truncated, increase top within read limits or narrow the account; this tool has no skip parameter.

Data: Current customer open items (DebtorTransOpenClient), optionally restricted to one customer or overdue items. Uses due dates, outstanding amounts, invoice numbers, document links, payment hold status and available dunning fields. Totals cover all matching items even when only a limited list is displayed.

list_open_supplier_items

Description:

The individual unpaid supplier items behind the ageing: due date, days overdue, amount owed, invoice number, payment reference and payment method. Use after get_payables_aging to see what makes up a figure, to plan a payment run, or pass an account to see one supplier. These are items open today, not at a past reporting date. dueWithinDays includes already overdue items and excludes items without a due date; separate overdue debt from future payments. top caps the displayed items only; totals cover every match. If truncated, increase top within read limits or narrow the account; this tool has no skip parameter.

Data: Current supplier open items (CreditorTransOpenClient), optionally restricted to one supplier, overdue items or a due-date cutoff. Uses outstanding amounts, due dates, invoice/voucher references, payment IDs, payment methods and payment hold status. Does not create payments or payment files.

list_sales_orders

Description:

Read a compact page of sales order headers. Filter by exact customer account, creation or delivery dates, or approval status. Does not fetch lines or calculate totals across orders. For delivered/invoiced quantities use get_sales_order. These are retained orders, not an invoice archive. Dates are inclusive yyyy-MM-dd. When truncated, repeat the same filters with skip=nextSkip. Date filtering examines at most top candidate headers per call; even an empty page may have truncated=true and an advancing nextSkip; continue even when that page is empty. Orders without a delivery date do not match a delivery-date filter, so no matches does not prove no upcoming deliveries. Example: {"account":"33266928","top":25}.

Data: Retained sales order headers (DebtorOrderClient), including customer, creation and delivery dates, approval status, currency and stored order totals. Does not retrieve order lines, inventory availability or the invoice archive.

list_worst_payers

Description:

Customers ranked by how LATE their money is rather than by how much they owe: days overdue weighted by positive open amounts, worst single overdue item, dunning letters sent and whether they are on hold. Answers 'who do we chase first'. Use get_receivables_aging instead for 'where is the biggest exposure' - the largest debtor is often the punctual one. Ranks only customers with a positive net overdue amount today. Undated and not-yet-due positive items carry zero days; credits do not affect weighted days. creditAmount is negative, and totalOpen is the net balance; a zero or credit net balance does not itself exclude a customer. This is not a payment history, so a customer who habitually pays late but is square right now does not appear.

Calculation: Weighted days overdue = sum of (positive open amount × days overdue) divided by total positive open amounts, rounded to the nearest whole day (halves up). Undated and not-yet-due positive items contribute zero days. positiveOpenAmount is the weighting basis; creditAmount is the sum of negative open amounts, retaining the negative sign. Credits still contribute to the net figures totalOpen, overdueAmount and undatedAmount where applicable. Eligibility requires positive net overdue; a credit net balance alone does not exclude a customer. Example: 62,317.50 overdue for 166 days and an undated credit of −2,750.00 give 166 weighted days and a net balance of 59,567.50.

Data: Current customer open items (DebtorTransOpenClient) with amounts, due dates, customer, payment hold status and available dunning information. Calculates measures such as amount-weighted days overdue from the open items. Does not read the customer's complete historical payment behaviour.

lookup_cvr

Description:

Look up a company by its CVR or other registration number and get back its registered name, address, postcode, city, country and company status. This reads a PUBLIC REGISTER and not Uniconta, and the result says so: it carries the source and the time of the lookup. It writes nothing and it changes no customer. To use what it finds, pass the values you want to create_customer or update_customer, where they go through the normal approval before anything is saved. Note the country it returns is a two-letter code, which is NOT what Uniconta's own country field accepts - that one takes a country name such as 'Denmark'.

Data: An external public company register through the configured lookup service. Uses registration number and country to retrieve the registered name, address and company status, with source and lookup timestamp. Does not read or change Uniconta customer master records.

query_entity

Description:

Read raw entity rows when no dedicated tool covers the question. Prefer get_cash_forecast for liquidity, get_receivables_aging/get_payables_aging for aging, list_open_customer_items/list_open_supplier_items for open items, get_customer_statement for statements and list_sales_orders/get_sales_order for orders. Never calculate a total from a partial page. Historical entities default to the configured recent date window; readScope states the applied dates. Check status first: approval_required means the query was NOT executed and there are no result or paging fields; completed means rows are actual query results. Broader history requires human approval. If approvalRequired is true, no rows were fetched: show approvalRequest.preview, wait for the user's explicit answer and call confirm_read. Then repeat the identical query with readApproval. Do not interpret a pending approval as an empty result. Call list_entities and describe_entity first to find valid entity and field names. Results are paged: when truncated is true, call again with skip set to nextSkip. Customer, supplier and account master pages may reuse the same sorted read for up to five minutes within this login. Keep filters, select and orderBy unchanged while paging; skip=0 always starts a fresh read. A cache miss or expiry reads again, so pages are not an atomic snapshot.

Data: The specific Uniconta entity selected by the agent, using the supplied filters, selected fields, sorting and pagination. May cover master data, open items, historical transactions and company-specific user types or user tables. The exact data source depends on the entity; permissions, historical-read approval and read limits apply.

review_period

Description:

Run a bounded, repeatable month-end review in one company and financial year: SDK trial balance, year/month states, retained journal candidates and SDK journal validation, plus dated debtor/creditor reconciliation on SDK/server v95. journalCoverage lists every discovered journal as checked, failed or not_checked, including empty and out-of-period journals. Whole-journal validation findings are not automatically attributed to the selected period or a voucher. reconciliations compare signed SDK balances at toDate in company currency with the union of current configured GL control accounts; each GL account is counted once. Missing/ambiguous setup, shared debtor/creditor control accounts or unsupported server versions return unavailable and no difference. Optional explicit balanceRules compare closing balances to inclusive minimum/maximum ranges in company currency. No negative balance is assumed wrong. Checks return passed/findings/not_applicable/unavailable/failed with evidence. incomplete must not be described as clean books. Explain each material finding or missing check, its consequence and the next concrete investigation. passed applies only to that check; not_applicable is not a passed test, and unavailable is not a zero difference. A net match does not exclude offsetting errors or historical account-mapping changes. Includes SDK bank reconciliation evidence with pending journals excluded from posted balances. Missing statement evidence makes the review incomplete; matching does not certify feed completeness. Period states are configuration, not instructions to close years; differences require investigation before proposing corrections. Company-wide; no dimension filters or VAT review. At most 50 journal templates and shared complete-read limits. Raw posting drill-down uses get_account_activity and its historical-read approval. This reads and checks only; it does not perform or certify a month-end close.

Data: Financial years and period states, SDK trial balance, journal headers and lines, and SDK journal validation. Customer/supplier master records and groups (Debtor, Creditor, DebtorGroup, CreditorGroup) determine the control accounts; dated balances are retrieved through DebtorAgeTotal and CreditorAgeTotal. Also uses bank reconciliation evidence and any explicit balance thresholds supplied by the user. Checks and combines results; does not close or post the period.

suggest_tool

Description:

Record a suggestion for something this MCP server should be able to do but cannot. Use it whenever you could not answer the user's question because no tool covered it - say what was missing and what the user was actually trying to do. This writes ONLY to this server's own suggestion log; it changes nothing in Uniconta, reads no accounting data and needs no approval. Do not use it for a tool that already exists but failed: that is a fault to report, not a gap to fill.

Data: The user's suggestion, task description, timestamp and available caller identity. Writes only to the MCP server's own suggestion log; reads no accounting data and does not automatically create a task in an external issue-tracking system.

switch_company

Description:

Switch the default company for this authenticated SDK session, like selecting a company in Uniconta. Accepts number, numeric id or name. Both the server allowlist and Uniconta permissions must allow access. Separate OAuth logins have independent company selections. Basic authentication creates a session per HTTP request; Basic clients must supply companyId on subsequent data calls. Pass companyId explicitly whenever scope must be unambiguous.

Data: The SDK session's available companies, their numbers, IDs and names, and the server's company access policy. Changes the session's default company after access checks; does not change accounting or master data.

update_customer

Description:

Change an existing customer's name, CVR number or address in place. ONLY the fields you name are changed and everything else is left exactly as it is, so omitting a field never blanks it. A field cannot be CLEARED through this API at all, only changed to a new value. This is a two-call write: the first call previews the current and the proposed value of every field it would change, and writes nothing, returning a requestState. Call again with that same requestState and confirmed=true, and the server will ask the user to approve before it writes. If someone else changes one of those fields between the two calls the write is REFUSED, because the approval described values that no longer hold. Requires a client that supports elicitation. Disabled while output anonymisation is enabled.

Data: The existing customer master record (DebtorClient), the requested changes and checks for possible duplicate CVR registration numbers. The preview compares current and proposed field values. After approval, the fields are checked again before explicitly supplied values are updated; all other fields are preserved.