Ekwo OS — open source accounting: ledger, invoices and VAT on your own Supabase or Postgres
NPM · @EKWO-AI/MCP · 2 COMPONENTS
Double-entry books an agent keeps as the user: invoices, VAT returns, 174 country packs.
Available components
Last scanned (15 hours ago)
Scores higher than 96% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 122 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Ekwo-ai/ekwo-os). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 18089 tokens (~238/item across 76 items; 76 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 77 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Nov 26 0
- Stability: 0.97 → pass security
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 −1
- Stability: pass → 0.90 functional
- 9 Nov 26 +5
- Source repository: unverified → pass ▲ security
- 8 Nov 26 −5
- Provenance: pass → unverified ▼ security
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 +15
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.22.0 → 0.24.0 functional
- Package version: 0.22.0 → 0.23.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@ekwo-ai/mcp@0.24.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Ekwo-ai/ekwo-os |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Ekwo-ai/ekwo-os/.github/workflows/release.yml@refs/tags/v0.24.0 |
| Rekor log index | 3542562844 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fe9fef5aee041c87699f738865d2d2de71865f938a360ac3690c11d8b1f1b4ae4befd4b17b042ca02f8cae96844798dbca60d3da08cc82c3bc58da3c6 |
Background: How many MCP packages publish verified provenance →
Dependencies 122 packages
| Packages resolved | 122 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
aged_balance Aged balance ~103
What customers still owe (or what is still owed to suppliers), bucketed by how overdue it is. It reads unmatched ledger lines, not invoices, so it ties back to the balance sheet: an invoice counts as settled only once its payment has been matched.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | The day to age at. Defaults to today. |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| group | string | – | – |
No output schema declared.
No examples provided.
analytic_report Result by analytic value ~255
The result of each value of one analytic axis over a period, read from the posted ledger: the income, the expense and their difference per value, in the company's currency, from the whole income statement — salaries, rent and depreciation included, wherever they were split — and fixed_assets, the net movement of the fixed-asset accounts, beside the result and never in it. A value with others below it holds their subtotal; its own amount alone is in the direct_ columns, and level is its depth. unassigned is the part no share of the axis reaches and total the whole period: the direct_ amounts and unassigned add up to total, so say how large unassigned is rather than presenting the values as the whole, and never add a parent to its children. The margin of each product is a different question, read from the invoices. It prepares figures; it files nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| axis | string | yes | The analytic axis, by its code or its id: list_analytic_axes names them. |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| from | string | yes | First day of the period. |
| to | string | yes | Last day of the period. |
No output schema declared.
No examples provided.
cancel_document Undo a posted invoice ~452
Undoes a posted sale or purchase invoice in one call, the one way its country and its facts allow, and says which in undone_by. 'draft': the country's posted_edit_policy lets a posted document go back to draft and nothing about this one has left — never sent nor on Peppol, not paid, not declared, its period open and, where numbering is gapless, its number the last one drawn; its entry is taken away, its number given back, and it is a draft to correct and post again. 'credit_note' otherwise, with the reason in why: its credit note — the same lines, taxes, accounts, contact, currency and rate — is issued naming it, posted and matched against it, and the invoice is cancelled, payment state reversed; the invoice keeps its number and its entry. Tell the user which it was. A date, or credit_note: true, asks for the credit note outright. Dated on the invoice's booking day unless you give a date; refused by name when that period is locked or closed (reversal_date_needed), and then you ask the user for a date rather than choosing one. Refused for a draft, a credit note, an invoice already cancelled or credited, and one that is paid in part or in full — the payment is unmatched first with unreconcile, and only when the user says so. Where you post in review, the credit note is a posting nobody approved, so that way is refused (approval_required) and the user cancels it themselves. Ask the user before calling it. This session follows each company's agent_posting.
| Name | Type | Req | Description |
|---|---|---|---|
| credit_note | boolean | – | True: undo it with a credit note even where it could go back to draft — the user wants the correction on the record. |
| date | string | – | The day a credit note is issued and booked on. Given, it asks for the credit note. Left out: the invoice's own booking day, and refused by name (reversal_date_needed) when that period is no longer op… |
| document_id | string | yes | The posted sale or purchase invoice to undo. |
No output schema declared.
No examples provided.
close_fiscal_year Close a fiscal year ~171
Closes a year: the result of the year leaves the income statement the way the country model says — straight to retained earnings, into a current-year result account, or through the appropriation accounts — every income and expense account goes back to zero, and the year stops accepting entries. The close can be undone with reopen_fiscal_year; final_close in the answer says whether the country also requires a final close, which cannot, and by when. Refused while the year holds a draft entry, while an earlier year with entries is open, or when a later year is already closed. It never writes what a general meeting decides to do with the result. Always ask the user before calling it.
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_year_id | string | yes | The year to close. Every entry in it must be posted. |
No output schema declared.
No examples provided.
close_fiscal_year_finally Close a fiscal year for good ~143
The final close: a year already closed is frozen, and from then on nobody can reopen it or change it — not the owner, not an accountant, not the operator. Refused on an open year (fiscal_year_not_closed) and while a closed year before it is not finally closed. Whether the country requires it, and by when, is final_close in the answer of close_fiscal_year. Irreversible: call it only when the user has asked for this specific year to be closed for good.
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_year_id | string | yes | The closed year to close for good. Every closed year before it must already be finally closed. |
No output schema declared.
No examples provided.
create_api_key Issue a key to a machine ~375
Issues a key so a script — a nightly import, a till, a bank feed — can work in one company without a person signing in. It carries an explicit list of capabilities and nothing else, it can never reach another company, and it cannot hold a capability you do not hold yourself — at issuance and at every use: if you lose a capability or leave the company, the key loses it too. Its posting_mode is fixed now and never raised afterwards: review by default, autopilot only when the user asks for it in so many words. The secret comes back once and is stored only as a hash: show it to the user and say it cannot be read back. Prefer this to sharing anybody’s password, and never suggest a service key.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | yes | Exactly what the machine may do, e.g. ["bank.write"]. You cannot put a capability on a key that you do not hold yourself. |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| expires_at | string|null | – | When it stops working, as a timestamp. Left out, it does not expire on its own. |
| name | string | yes | What this key is for, in the words an operator will read a year from now. |
| posting_mode | string | – | How the key posts a document, fixed for good: review (the default) — as the company’s agent_posting says, so a person approves each draft unless the company chose autopilot; autopilot — directly, on… |
No output schema declared.
No examples provided.
create_bank_account Add a bank account ~447
Registers a bank account of the company from its identifier — an IBAN, an ABA routing number and an account number, a sort code and an account number, whatever the banks of the company's country use; the pack of the country says which, and it is checked — and wires it to the bank journal and to the ledger account behind it — both of which the country template has already chosen, so neither has to be given. Running it twice with the same identifier returns the one that exists rather than creating a second. Do this once per account: until a company has one, an invoice carries no account to pay into and record_payment can only book on the journal's default account.
| Name | Type | Req | Description |
|---|---|---|---|
| account_code | string | – | The ledger account behind it. Left out, the journal's default account, which the country template chose. |
| account_id | string | – | – |
| account_identifier | string | – | What identifies the account at its bank, in the scheme of the company's country: an IBAN, an ABA routing number and an account number, a sort code and an account number, a BSB and an account number,… |
| bank_name | string | – | – |
| bic | string | – | The bank identifier code, where the bank has one. |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| currency_code | string | – | Defaults to the company's own currency. |
| iban | string | – | Deprecated: an alias of account_identifier, accepted only where the country identifies accounts by IBAN. |
| journal_code | string | – | The financial journal it books through. Left out, the bank journal of the company. |
| journal_id | string | – | – |
| label | string | – | What it is called in the books. Defaults to the bank name, then to the identifier. |
No output schema declared.
No examples provided.
create_bank_transaction Add a bank transaction ~189
Records one statement line by hand, for an installation without a bank feed. `amount` is signed: positive is money in. It books nothing — the line waits as pending until a payment is recorded.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string|number | yes | Signed: positive is money in, negative is money out. |
| bank_account_id | string | yes | – |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| contact_id | string | – | – |
| counterpart_iban | string | – | – |
| counterpart_name | string | – | – |
| description | string | – | – |
| reference | string | – | – |
| statement_id | string | – | – |
| structured_reference | string | – | A structured communication, e.g. +++000/0000/00000+++ or RF… |
| transaction_date | string | yes | – |
| value_date | string | – | – |
No output schema declared.
No examples provided.
create_company Create a company ~260
Creates a company on a country pack: its chart of accounts, its journals and its taxes are copied in, its first financial year is opened on the month that country opens one on, and you become its first member. Creating a company is an instance-level act — it needs an instance administrator, and being one is not the same as being on anybody’s books. Ask the user for the country rather than guessing: the wrong answer is a whole chart of accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| chart_code | string | – | Which chart, where the country offers several. |
| country | string | yes | Which country pack: its chart of accounts, its taxes and its declaration form. list_companies shows what the installation already uses. |
| currency_code | string | – | Left out, the country pack's. |
| fiscal_year | integer | – | Calendar year the first financial year opens in. Default this year. |
| fiscal_year_start | string | – | First day of it. Left out, the month the country pack opens a year on — and a pack that names none is a refusal, not a January. |
| language | string | – | Language the books are kept in — it decides the labels of the chart. Left out, the country pack's. |
| name | string | yes | – |
No output schema declared.
No examples provided.
create_contact Create a contact ~328
Adds a customer, supplier or other third party to a company. Search first: a duplicate contact splits a customer account in two and the aged balance stops making sense. payment_terms_days drives the due date a posted invoice gets when none is given. Next: create_document with the id it returns.
| Name | Type | Req | Description |
|---|---|---|---|
| address_line1 | string | – | – |
| auxiliary_code | string | – | Sub-ledger code; the French FEC reports it. |
| city | string | – | – |
| client_ref | string | – | Your own reference for this creation. Calling again with the same one returns what was created the first time (`replayed: true`) instead of creating a second — use it whenever a call might be repeate… |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| contact_type | string | yes | – |
| country | string | – | ISO country code, e.g. BE. |
| string | – | – | |
| identifiers | object | – | Every identifier with no column of its own, by the code of its scheme — {"<scheme>": "<identifier>"}. The schemes a country's e-invoice reads are on its set-up page and in describe_pack. |
| name | string | yes | – |
| payment_terms_days | integer | – | – |
| phone | string | – | As the party writes it, international form where the e-invoice of its country asks for one. |
| postal_code | string | – | – |
| registration_number | string | – | The number of the commercial register of its country. |
| vat_number | string | – | – |
No output schema declared.
No examples provided.
create_document Create a draft invoice ~343
Creates a draft invoice, credit note or quote with its lines, and returns it with the totals the database computed — never with totals you supplied. A line may name a product_code, which fills in its text, price, unit, account and tax; anything the line carries wins over that. With no product and no account_code, the account falls back to the company default and then to its country model. A tax is different: a line with none is booked as a base with no VAT box, which is not the same as 0 %. Nothing is in the ledger yet. Next: show the draft to the user; update_document_lines changes it, and post_document books it once they agree.
| Name | Type | Req | Description |
|---|---|---|---|
| accounting_date | string | – | The date the entry is booked on, when it differs from the document date. |
| client_ref | string | – | Your own reference for this creation. Calling again with the same one returns what was created the first time (`replayed: true`) instead of creating a second — use it whenever a call might be repeate… |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| contact_id | string | yes | – |
| currency_code | string | – | – |
| doc_type | string | yes | – |
| document_date | string | yes | – |
| due_date | string | – | – |
| journal_id | string | – | – |
| lines | array | yes | – |
| number | string | – | Your own number. Left out, posting takes the entry number. |
| payment_reference | string | – | – |
| supplier_reference | string | – | The supplier's own invoice number, on a purchase. |
No output schema declared.
No examples provided.
create_product Add a product ~452
Adds an item to the catalogue: a code unique in the company, a name, a unit, a price, and optionally the account and the tax a sale or a purchase of it carries. It changes nothing already booked — a product is what a new line is filled in from, never a rule applied to the past. Search first: a second code for the same thing is how a price list stops being one.
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | object | – | What the electronic invoice format of the country asks of a line selling this item that no other field says, by the name its brick reads — describe_pack lists them (line_attributes). A line filled in… |
| code | string | yes | Your own reference for the item. Unique in the company, and what EN 16931 calls the seller's item identifier (BT-155). |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| currency_code | string | – | – |
| description | string | – | The longer text under the name (BT-154). |
| kind | string | – | Defaults to service. Goods and services are not taxed alike and do not feed the same declaration boxes. |
| name | string | yes | What appears on the invoice line (BT-153). |
| purchase_account_code | string | – | Expense account a purchase of this books to. |
| purchase_account_id | string | – | – |
| purchase_price | string|number | – | – |
| purchase_tax_code | string | – | – |
| purchase_tax_id | string | – | – |
| sale_account_code | string | – | Income account a sale of this books to. |
| sale_account_id | string | – | – |
| sale_price | string|number | – | Net unit price on a sale. A line may still carry another. |
| sale_tax_code | string | – | Tax applied when it is sold, by code. |
| sale_tax_id | string | – | – |
| unit_code | string | – | UN/ECE recommendation 20: C62 a piece, HUR an hour, DAY a day, MON a month, KGM, LTR, MTR, KWH. Defaults to C62. |
No output schema declared.
No examples provided.
describe_pack Where a country pack comes from ~194
The country packs this installation holds, with their version, how much anyone has read them, and the register of texts each was built from — the title, the official publisher, an absolute link and the day somebody opened it, per text. Use it whenever you are asked where a rate, a chart of accounts or a box of the declaration comes from, and before repeating a figure a pack gave you: a community pack has not been read by an accountant, and the status says so. The article behind a single rule is on that rule itself — legal_reference on a tax or on a box — and the register is where that article can be read. It carries no copy of the law: a link that has gone quiet means the register is stale, never that the rule is wrong.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2, upper case. Left out, every pack this installation holds. |
No output schema declared.
No examples provided.
ec_sales_list Recapitulative statement of European Union supplies ~267
Who, in another Member State, was supplied without VAT over a period, and for how much: one line per customer VAT number and per nature — goods, services — read from the treatment of the tax on each sale line, with credit notes deducted. The totals tie back to the European Union boxes of vat_return for the same period. A line that carries an issue cannot be filed as it stands, most often because the customer has no VAT number recorded: say so rather than leaving it out of the answer. Name a report_code to have the period checked against the cadence this company files that statement on — it has one of its own, and it is rarely the cadence of the return. No country rule lives in this tool. It prepares a statement; it files nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| from | string | yes | – |
| report_code | string | – | Which recapitulative statement form, when the installation carries one and you are filing it. Name it and the period is checked against the cadence this company files that statement on, which is not… |
| to | string | yes | – |
No output schema declared.
No examples provided.
financial_analysis Financial analysis ~295
The figures an analysis of a company is computed from — revenue, other operating income, purchases, staff costs, depreciation, the financial result, income tax, the net result, equity, total and current assets, cash, trade receivables, current liabilities, trade payables, long-term debt — each with the accounts that make it. The movements are read over the period and the balances at its end; equity includes the result of the years not closed yet. Which accounts make each figure is written in the company's country pack and in no tool. Each row carries source: pack when the country pack defines the analysis; framework when it defines none and the figures are read by account type through the generic framework, which leaves out staff costs, the financial result and income tax because no account type tells them apart — say those are not read rather than zero. The figures are never to be guessed from account codes. Ratios — a margin, a current ratio, days of sales outstanding — are worked out from these, not stored. It prepares figures; it files nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| from | string | yes | First day of the period the movements are read on: revenue, purchases, the result. |
| to | string | yes | Last day of the period, and the day the balances are read at: equity, assets, debts, cash. |
No output schema declared.
No examples provided.
financial_statement Financial statement ~181
A balance sheet or an income statement for a period, on the scheme the country pack declares — the Belgian abbreviated model, the French liasse — or on the generic framework by account type. Each line is summed from the accounts its rules catch and the totals are derived from the lines; no country rule lives in this tool. It also returns the accounts no line catches: if that list is not empty, say so instead of presenting a statement that does not tie out. It prepares figures; it files nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| from | string | yes | – |
| statement_code | string | yes | Which scheme, from list_statements (BE-BNB-ABBR-BS, FR-2050, IFRS-SME-BS). |
| to | string | yes | – |
No output schema declared.
No examples provided.
general_ledger General ledger ~137
Every posted line of an account over a period, with the balance carried forward from before it and a running balance. Give account_code for one account; leave it out for all of them, which on a real company is a lot of lines.
| Name | Type | Req | Description |
|---|---|---|---|
| account_code | string | – | The account to detail, by its code, e.g. "400000". |
| account_ids | array | – | The accounts to detail, by id. Leave both out for every account. |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| from | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
generate_fec Generate the French FEC ~118
The Fichier des Écritures Comptables for a period: the eighteen columns of the arrêté du 29 juillet 2013, as text, with the checks a tax inspector applies first (mandatory fields, one side per line, entries balancing) and the filename the format wants. The file comes back in the answer; writing it to disk is the caller's business.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| from | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
get_company Company settings ~115
Everything needed before booking in a company: its financial years and whether they are closed, its lock dates, its journals, and the accounts that play the receivable, payable, suspense and retained-earnings roles. Read this before creating a document if you do not already know the journals and the lock dates. Next: list_accounts and the ekwo://companies/{companyId}/taxes resource give the codes a document line names.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
No output schema declared.
No examples provided.
get_document Read a document ~91
One document with its lines, the account and tax of each line, the legal mentions its country requires on it, that country's payment and e-invoicing rules, and — when it has been posted — the ledger entry it produced with every ledger line. Use it to check what a document will book, what it did book, and what has to be printed on it.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | – |
No output schema declared.
No examples provided.
get_preferences What this user prefers ~120
The signed-in user’s own preferences — which company an interface opens on, the language they read labels in, their timezone and how they like a date and a number written — and the language chain to read labels with: theirs, then the company’s, then the country pack’s. Every one of them may be null, and null means "take the next answer in the chain" rather than a default this installation picked.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | – | Resolve the language chain against this company. Left out, only what the user themselves chose is returned. |
No output schema declared.
No examples provided.
import_bank_statement Import a bank statement ~481
Reads a bank statement file and writes its statements and lines. `format` says what the file is — `camt.053` (the ISO 20022 XML statement), `coda` or `cfonb120`, which are the ones this server reads today — and `content` is the file as text. It is never guessed from the content. It books nothing: every line waits as pending, to be settled afterwards. Safe to repeat: the same file imported twice creates nothing the second time, and a statement overlapping an earlier one imports only the new lines. Refused by name, with nothing written: an account the company does not have (create it first with create_bank_account — an import never creates one), a statement whose opening balance plus lines is not its closing balance, a line in another currency. Signalled in `warnings`, not refused: an opening balance that is not the previous closing one, which means a statement is missing.
| Name | Type | Req | Description |
|---|---|---|---|
| bank_account_id | string | – | Only for a file of one statement whose account the company identifies otherwise than the file does. Left out, the account is found by the identifier the statement carries, and an unknown one is refus… |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| content | string | yes | The file itself, as text (UTF-8). |
| file_name | string | – | The name the file had, kept on the statement. |
| format | string | yes | What the file is. Required, and never guessed from the content: `camt.053` is the ISO 20022 XML statement, `coda` the coded statement of account of 128-character records, `cfonb120` the statement of… |
| iban_country | string | – | Only for `cfonb120`, which identifies an account by a bank code, a branch code and a number, and names no country. With the two letters of the country the account is held in, the statement is matched… |
| storage_path | string | – | Where the caller stored the file, if it did. With it the file is recorded in attachments, on the statement; this server stores no bytes. |
No output schema declared.
No examples provided.
import_books Import books from another system ~1,531
Takes over the books a user kept elsewhere — a FEC, an XML audit file, an export of journal items, a journal report, a transaction journal, a trial balance, or the export of odoo or xero or quickbooks-online or pennylane or sage-50 or exact-online by name — whole or not at all. Each file is read by the reader of its source; every account of the old chart is matched to one of this company's chart and every old journal to a journal of the company. The codes give a candidate (the same code, the same digits without the padding zeros, or the longest beginning of three digits or more), and what the files say of the old account — its type, its name, the side of its balance — is held against what the chart says the candidate is, never a country: only the same code, not contradicted, is `exact`; anything else is `suggested` with its reason, or `none`. Each old journal is proposed from what its entries touch, never its name — the opening (entries on the first day of a year, balance accounts only), sales, purchases, bank, else the general journal — with its reason under journal_reasons. Call it with dry_run first: it returns the correspondence proposed, the suggestions under mapping.suggested, what is unanswered, and — when everything is answered — what the database would write, rehearsed and rolled back. Show the user every suggested line and its reason first; nothing is posted while one is unconfirmed. Settle each by writing its code under mapping.accounts, or, once the user has read and approved them all, pass accept_suggestions. Every entry is posted through post_entry(); a trial balance becomes the opening entry, on the first day of a year or the day inside it the books were taken over, and the open items beside it (open_items) posted documents that statement matching finds. Imported lines carry no tax and feed no VAT box. The same files twice are refused. The files travel as text, up to 256 KiB in all: a larger export is imported from the terminal with `ekwo import`, wh…
| Name | Type | Req | Description |
|---|---|---|---|
| accept_suggestions | boolean | – | Take every account the proposal only suggested as the answer. Only after the user has read each suggested line and its reason, and said yes to all of them; left out, a suggestion stops the import. |
| allow_result_accounts | boolean | – | Let an opening balance carry income and expense accounts: books taken over in the middle of a year. |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| date_order | string | – | For `journal-report` and `transaction-journal`: the order of a date written only in digits, which the file does not say. |
| dry_run | boolean | – | Show what would be written — the correspondence proposed, the entries, the numbers — and write nothing. Always first, and the user reads it before the real call. |
| files | array | yes | The files of one source, in the order given. `journal-items` and `journal-report` take the chart of accounts and the parties beside the lines, and `transaction-journal` the list of accounts, each rec… |
| keep_numbers | boolean | – | Post each entry under the number it had. Where the country forbids a hole in the sequence it takes the entries.import capability; left out, the journal draws the numbers and the old one is kept as th… |
| mapping | object | – | The correspondence, as a previous call with dry_run returned it and the user completed it. What it answers wins over the proposal. |
| open_items | object | – | With an opening: the invoices and credit notes still open on its day, as CSV — type (sale_invoice, sale_credit_note, purchase_invoice, purchase_credit_note), number, contact (the code the balance nam… |
| open_years | boolean | – | Open the fiscal years the entries fall in where the company has none, on the length and first day of its own. Off, such an entry is refused by name. |
| opening_date | string | – | For a trial balance: the day it opens on — the first day of a fiscal year, or the day inside it the books were taken over. The file does not say it; an audit file does, and needs none. |
| source | string | yes | What the files are, never guessed from their content: `trial-balance` — a trial balance as CSV — account, debit, credit, or a signed balance — which becomes the opening entry of a year; `fec` — a fic… |
No output schema declared.
No examples provided.
instalment_plan VAT instalments of a period ~153
The payments on account of a declaration that the VAT scheme a company recorded asks for during its period — a simplified scheme pays part of the year's tax before filing the annual return — with what was due, what was paid and what is outstanding. The schedule, the percentages and the box of the previous year they are read on are country pack data; no country rule lives in this tool. It reads; it pays nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| from | string | yes | First day of the period of the declaration the instalments are paid on account of — usually 1 January. |
| to | string | yes | Last day of that period. |
No output schema declared.
No examples provided.
invite_member Invite somebody into a company ~241
Invites an address into a company with a preset — viewer reads, client reads and hands pieces over, accountant keeps the books, owner also administers — and any capability granted on top of it. It returns a token once and stores only its hash, so hand the token to the person you invited: they accept it themselves, signed in with that address. It does not send an e-mail, and it does not create an account. Inviting the same address again withdraws the invitation that was pending.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | – | Capability codes granted on top of the preset, e.g. members.manage. get_company lists what this installation knows. |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| string | yes | The address the invitation is for. Matched when it is accepted. | |
| role | string | – | The preset. Default viewer, which reads and changes nothing. client is the person whose company it is, invited by whoever keeps their books: it reads the same, and may also hand a file over (document… |
| valid_for_days | integer | – | Default 14. |
No output schema declared.
No examples provided.
journal_book Journal book ~196
The book of a journal: every line of every posted entry over a period, in the order a book is read — day, journal, entry number, line — each with its entry, the document behind it, its account and its contact, and the totals of each journal at the head. Give journal_code for one journal (the sales journal, the bank); leave it out for the book of every journal, which on a real company is a lot of lines. For one account with its running balance, use general_ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| from | string | yes | – |
| journal_code | string | – | The journal to read, by its code, e.g. "SAL". Leave both out for the book of every journal. |
| journal_ids | array | – | The journals to read, by id. |
| to | string | yes | – |
No output schema declared.
No examples provided.
leave_line_unnamed Leave a ledger line without a contact ~153
Records that an open line on a receivable or payable account names nobody on purpose — a cash difference, a one-off refund — with the user's reason: suggest_line_contacts no longer proposes it. The line does not move and stays an open item. Refused by name: unknown_line, not_allowed, reason_required, reason_too_long, line_not_posted, line_has_contact, line_not_third_party, line_left_unnamed. Ask the user before calling it.
| Name | Type | Req | Description |
|---|---|---|---|
| line_id | string | yes | The open line on a receivable or payable account that names nobody, as suggest_line_contacts returns it. |
| reason | string | yes | Why the line names nobody, in the user's words. |
No output schema declared.
No examples provided.
list_accounts Chart of accounts ~352
The accounts a company actually works with, filtered by code prefix, by account type, or by a search on the name. Use it to find the income or expense account a document line should carry. By default it returns the working chart — the accounts that carry entries, that the company's settings or an enabled module point at, or that somebody pinned — because a country pack transcribes the whole regulation and a company uses a few dozen of its several hundred accounts; `in_use_from` and `in_use_to` narrow the movements to a period, `include_all` returns the whole chart, and `include_deprecated` returns it with the retired accounts too. This is a reading and not a restriction: any account of the chart that is not deprecated may still be booked on.
| Name | Type | Req | Description |
|---|---|---|---|
| account_type | string | – | One of the eighteen account types, e.g. asset_receivable. |
| code_prefix | string | – | Only accounts whose code starts with this, e.g. "70". |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| in_use_from | string | – | Narrows the movements to entries on or after this date. References and pinned accounts are not dated and stay in. |
| in_use_to | string | – | The other end of that period. |
| include_all | boolean | – | Return the whole chart instead of the accounts in use. Use it when a search over the working chart found nothing. |
| include_deprecated | boolean | – | Include deprecated accounts. A deprecated account is never in use, so this returns the whole chart. |
| limit | integer | – | – |
| search | string | – | Case-insensitive match on the account name. |
No output schema declared.
No examples provided.
list_analytic_axes Analytic axes ~142
The analytic axes of a company — a cost centre, a project, a site, a business unit — each with its values, which may nest under a parent_id, and required_on: none, or expense, income or result — the lines that must carry the axis whole, or posting refuses them (analytic_axis_required). A value says what a cost, a revenue or a fixed asset is for; a product says what was sold or bought. A retired value takes no new share. Read it before analytic_report, which takes an axis by its code.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
No output schema declared.
No examples provided.
list_api_keys Machine keys of a company ~121
The keys a company has issued to machines, what each one may do, how it posts a document (posting_mode, review or autopilot, fixed when it was issued), when it was last used and whether it is still live. Only somebody who manages members sees them, and no secret is in here: a key is shown once, when it is issued.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| include_withdrawn | boolean | – | Also the ones withdrawn or expired. Default false. |
No output schema declared.
No examples provided.
list_bank_accounts Bank accounts ~93
The bank accounts of a company, with their identifier and the scheme it is written in, the journal they book through and the ledger account behind each. Read it before recording a payment on a particular account, and to find out whether the company has one at all.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| include_inactive | boolean | – | Default false. |
No output schema declared.
No examples provided.
list_bank_transactions Bank transactions ~124
Statement lines of a company, pending by default — the ones still waiting to be dealt with. `amount` is signed: positive is money in. A statement line is not a ledger entry; recording a payment is what books it.
| Name | Type | Req | Description |
|---|---|---|---|
| bank_account_id | string | – | – |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| from | string | – | – |
| limit | integer | – | – |
| state | string | – | Defaults to pending: what still has to be dealt with. |
| to | string | – | – |
No output schema declared.
No examples provided.
list_companies List companies ~79
The companies of this installation that you are a member of, with your role on each. Start here: every other tool needs a company_id. Returns id, name, country, currency and your role. It does not list companies you were never invited to — those are invisible, not hidden. Next: get_company on the one the user means.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_documents List documents ~180
Invoices, credit notes and quotes of a company, filtered by type, state, settlement state, contact or date range. `state` is the document (draft, posted, cancelled) and `payment_state` is the settlement (not_paid, partially_paid, paid) — two different questions. Returns headers and totals, not lines; use get_document for those.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| contact_id | string | – | – |
| doc_type | string | – | – |
| from | string | – | Earliest document date. |
| limit | integer | – | – |
| payment_state | string | – | – |
| state | string | – | – |
| to | string | – | Latest document date. |
| unpaid | boolean | – | True: posted and still owed — not paid, or partially. |
No output schema declared.
No examples provided.
list_invitations Invitations into a company ~114
The people invited into a company and not yet on its books, with the preset and the capabilities each was invited with, and whether the invitation is still pending, expired, accepted or withdrawn. Only somebody who manages members sees them. The token is never in here: it is shown once, when the invitation is issued.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| include_settled | boolean | – | Also the ones already accepted or withdrawn. Default false. |
No output schema declared.
No examples provided.
list_shares Public links onto documents ~132
The links a company has published onto its own sales documents, with how many times each was opened and when it was last opened. No token is in here: a link is shown once, when it is made. Use it to answer "did the customer open the invoice?" and to find the link to withdraw.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| document_id | string | – | Only the links onto this document. Left out, the whole company. |
| include_withdrawn | boolean | – | Also the ones withdrawn or expired. Default false. |
No output schema declared.
No examples provided.
list_statements List financial statements ~92
The schemes this company can be presented on: those of its country and of its chart of accounts, plus the generic framework by account type that fits any chart. Ask this before financial_statement rather than guessing a code.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | The day to read the schemes in force at. Defaults to today. |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
No output schema declared.
No examples provided.
lock_period Lock a period ~135
Moves the accounting lock date, the VAT lock date, or both. After this, nothing can be booked, changed or deleted on or before that date — including corrections you may want later. Only an owner of the company may do it. Always ask the user first, and never lock a period you have just posted into without being told to.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| lock_date | – | – | Nothing may be booked on or before this date. null lifts the lock. |
| tax_lock_date | – | – | Additionally freezes anything carrying a VAT box. null lifts it. |
No output schema declared.
No examples provided.
matching_difference_options The reasons and the tolerance for booking a difference ~106
What reconcile_with_difference accepts for this company: the largest difference it books (in units of the currency and as an amount) and the reasons — rounding, exchange_difference — each with the account the pack gives, the side it answers (charge, income, either) and whether it is available. No pack carries a role for bank charges or payment discounts, so they are not reasons.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
No output schema declared.
No examples provided.
merge_contacts Merge two contacts of one company ~275
One party created twice — two spellings of one customer, two imports of one supplier: everything that names the absorbed contact names the kept one afterwards, in one transaction — posted ledger lines and issued documents included, statement lines, payments, branches, files and learned motifs — and the kept contact's empty fields (VAT number, IBAN, address, email…) are filled from the absorbed one without overwriting any. The absorbed contact is retired, never deleted, and no row may name it again. No amount, account, date or tax box moves, and there is no unmerge. Refused by name: unknown_contact (also a contact of another company), same_contact, already_merged, different_identifiers (two different VAT or registration numbers are two parties), matching_across_parties, not_allowed. suggest_duplicate_contacts proposes the pairs. Show the user the two contacts side by side with search_contacts and ask which one to keep before calling it; never decide that two contacts are one yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| absorb_contact_id | string | yes | The duplicate the user chose to retire: everything naming it will name the kept contact. A contact of the same company. |
| keep_contact_id | string | yes | The contact that stays and takes the history of the other — the one the user chose to keep, as search_contacts returns it. |
No output schema declared.
No examples provided.
opening_balance Import an opening balance ~400
Turns the trial balance of whatever kept the books before into the opening entry of a fiscal year, on the opening journal, dated on its first day — or on opening_date, the day inside the year the books were taken over. Lines are {account_code, debit, credit}; total debit must equal total credit. Balance-sheet accounts only, unless allow_result_accounts is set, which is for taking books over in the middle of a year. items are the invoices and credit notes still open that day, each posted as a document with its number, payment reference and due date, so a bank statement finds it; the items of an account replace its line and must add up to it. A year holds one opening: a second call is refused rather than added to.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_result_accounts | boolean | – | Default false: an opening balance is made of the balance sheet. Pass true only when taking books over in the middle of a year that has already run. |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| fiscal_year_id | string | yes | The year the balance opens. The entry is dated on its first day unless opening_date says otherwise. |
| items | array | – | The invoices and credit notes still open on the opening day. Each becomes a posted document on the opening journal, with its number, reference and dates, against the suspense account — nothing is boo… |
| lines | array | yes | The trial balance of the previous system, one entry per row. Total debit must equal total credit. |
| opening_date | string | – | The day the books were taken over, inside that year. Left out, its first day. The balance is what the previous system held at the end of the day before. |
No output schema declared.
No examples provided.
pin_accounts Pin accounts to the working chart ~133
Adds accounts to the working chart of a company, so list_accounts offers them whether or not anything has been booked on them. Pass pinned: false to take one back out. Pinning is display and nothing else: an unpinned account may still be booked on, and a pinned one is still hidden once it is deprecated.
| Name | Type | Req | Description |
|---|---|---|---|
| account_codes | array | yes | Codes in this company's chart. list_accounts with include_all says what exists. |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| pinned | boolean | – | True pins, false unpins. Defaults to true. |
No output schema declared.
No examples provided.
portfolio_filings_touched_since Declared periods that moved, across your companies ~157
Which declarations, across your portfolio — every company you may read the declarations of, which for an accounting firm is its clients — had entries posted into their period after they were filed — with the company named, how many entries, and how many of the filed figures now disagree. A period stays open after its return has gone, on purpose; this is what keeps a late entry from going unnoticed. Companies with nothing to report are named too, with how many filed declarations were examined. It reads; whether a corrective is owed is for whoever keeps the books.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Only declarations whose period ends on or after this day. |
| to | string | – | Only declarations whose period starts on or before this day. |
No output schema declared.
No examples provided.
portfolio_upcoming_filings Returns falling due, across your companies ~201
What falls due between two dates in every company you may read the declarations of — the question a firm asks of all the books it keeps, and the one a person asks of the single company they run. "Portfolio" is meant as an accounting firm means it — its client portfolio — and is nothing but that: the companies you hold filings.read on, worked out at each call, never a list anybody maintains. Every one of them is in the answer, including a company whose country pack names no deadline, which is listed without a date and says so; a company left out would be indistinguishable from one that was never looked at. No country rule lives in this tool. It reads a calendar; it prepares and files nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | First day a return may fall due on. Go back a few days to catch what is already late. |
| to | string | yes | Last day a return may fall due on. |
No output schema declared.
No examples provided.
post_document Post a document to the ledger ~314
Books a draft document: base lines, VAT lines from the tax configuration, and the customer or supplier counterpart, numbered and posted. A posted entry is never edited; a mistake is undone by cancel_document, which puts the document back to draft only where its country allows it and nothing has left, and issues a credit note otherwise. The database decides whether you may, from the company's agent_posting (get_company) and this session's choice: in review, the default, only once a person has approved this draft as it stands (ekwo doc approve, or the web application) — refused with approval_required otherwise, and again if the draft changed after the approval; in autopilot, directly, within your rights; autopilot_forbidden where the session asked for autopilot and the company allows review only. Either way the posting is recorded on the audit trail as an agent's, with the mode and the session. dry_run: true is always allowed and is what to show the user before they approve. This session follows each company's agent_posting. It refuses a locked period, a tax that is not in force, and a header total that disagrees with the lines. Next: get_document shows the entry it wrote, and record_payment books the money when it moves.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | – |
| dry_run | boolean | – | True: the database posts for real and takes it back, and the entry it would have written is returned. Nothing is written; a refusal is the one posting would give. |
No output schema declared.
No examples provided.
read_audit_log Audit trail ~406
Who changed what, and when. Every change to the configuration and reference data of a company — the chart of accounts, the journals, the taxes and the accounts they post to, the bank accounts, the contacts, the products, the financial years, the members and their roles, the country pack version — and every act that changes a state: a document posted or cancelled, an entry posted or reversed, a payment booked, matched or unmatched, a financial year closed or reopened. Filter by table, by natural key, by user, by act, or by date range. The ledger itself is not in here: a posted entry is immutable and is corrected by a reversal, so what is recorded is the act of posting and never the lines. Read-only, and there is no tool that writes it: the trail is append-only and even the operator cannot edit a row.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | One act: document_posted, document_cancelled, entry_posted, entry_reversed, payment_posted, payment_reconciled, payment_unreconciled, fiscal_year_closed, fiscal_year_reopened, fiscal_year_finally_clo… |
| actor_id | string | – | Only what this user changed. Their auth.users id. |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| from | string | – | Earliest date, inclusive. |
| limit | integer | – | – |
| operation | string | – | – |
| record_key | string | – | The natural key of one row — an account code, a tax code, an invoice number. |
| table | string | – | One table of the schema: accounts, journals, taxes, tax_postings, contacts, products, bank_accounts, companies, fiscal_years, company_members, company_packs, api_keys, documents, payments, entries, r… |
| to | string | – | Latest date, inclusive — the whole of that day. |
No output schema declared.
No examples provided.
reconcile Match two ledger lines ~130
Matches a debit line against a credit line on the same reconcilable account, for an amount, defaulting to the smaller of the two open amounts. Use it to settle an invoice against a payment by hand. Matching changes no account and stays possible after a period is locked.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string|number | – | Left out: the smaller of the two open amounts. |
| line_a | string | yes | A ledger line to match. Either side; the schema works out which is the debit. |
| line_b | string | yes | The line it settles. Both must be on the same reconcilable account. |
No output schema declared.
No examples provided.
reconcile_many Match several ledger lines together ~158
Matches several lines together in one call — one payment against several invoices, one invoice against several instalments — when their open debits and credits are equal to the cent: posted lines of one company, one reconcilable account, one counterparty (a line naming nobody is attributed by the matching), in the company's currency. Paired oldest first through reconcile, under one letter. Refused by name, and never settled in part: reconcile_unbalanced gives the difference. Show the user the lines and ask before calling it.
| Name | Type | Req | Description |
|---|---|---|---|
| line_ids | array | yes | The ledger lines to match together, as suggest_item_combinations returns them: the line and the lines it settles. One counterparty, one account, at least one debit and one credit. |
No output schema declared.
No examples provided.
reconcile_with_difference Match ledger lines and book a small difference ~211
Matches the same set of lines as reconcile_many when their totals differ by no more than the company's tolerance: posts an entry that books the difference on the same account and counterparty against the account the pack gives for the reason (matching_difference_options: rounding, exchange_difference), then matches everything under one letter. Refused by name: difference_above_tolerance, no_difference, unknown_difference_reason, no_account_for_reason, and every refusal of reconcile_many. The entry is posted; unreconcile of the matching of the difference line takes it back. Show the user the difference and the account, and let them choose the reason, before calling it.
| Name | Type | Req | Description |
|---|---|---|---|
| line_ids | array | yes | The ledger lines to match together, as suggest_item_combinations returns them: the line and the lines it settles. One counterparty, one account, at least one debit and one credit. |
| reason | string | yes | Why the lines differ, as matching_difference_options lists it: rounding or exchange_difference. The user chooses it. |
No output schema declared.
No examples provided.
record_payment Record a payment ~477
Records money in or out, books it (bank against the customer or supplier account) and, unless you say otherwise, matches it against that contact's oldest open invoices up to the amount paid. Matching is what makes an invoice count as paid. The entry it produces cannot be unposted, though the matching can be undone with unreconcile.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string|number | yes | A positive decimal string; the direction carries the sign. |
| bank_account_id | string | – | Which bank account the money moved on. list_bank_accounts says what exists. Given alone, it also names the journal; left out, the default account of the journal is used. |
| client_ref | string | – | Your own reference for this creation. Calling again with the same one returns what was created the first time (`replayed: true`) instead of creating a second — use it whenever a call might be repeate… |
| company_id | string | yes | The company to work in. Ask list_companies if unsure. |
| contact_id | string | – | Who paid or was paid. Needed for the payment to be matched against their invoices. |
| currency_code | string | – | Left out: the currency the company keeps its books in. |
| direction | string | – | inbound: a customer paid you. outbound: you paid a supplier. May be left out when document_id is given. |
| document_id | string | – | The posted document this money pays. It names the contact and the direction, read off what is still open on it, and the matching is offered to that document alone rather than to the oldest open items. |
| exchange_rate | string|number | – | Units of the payment currency for one unit of the company currency, as a rate table states it. Only needed when the payment is in another currency; the realised difference against the invoice is book… |
| journal_code | string | – | The bank or cash journal, by code, e.g. BNK. Not needed when bank_account_id is given: the account knows its journal. |
| journal_id | string | – | – |
| match_open_items | boolean | – | Default true: match the payment against the oldest open invoices of that contact, up to the amount paid. |
| memo | string | – | – |
| payment_date | string | yes | – |
| reference | string | – | – |
No output schema declared.
No examples provided.
How do I install the Ekwo OS — open source accounting: ledger, invoices and VAT… MCP server?
Ekwo OS — open source accounting: ledger, invoices and VAT… runs locally as an npm package, launched with npx -y @ekwo-ai/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ekwo-ai/mcp
claude mcp add ai-ekwo-mcp -- npx -y @ekwo-ai/mcp
What is the Ekwo OS — open source accounting: ledger, invoices and VAT… MCP server?
Ekwo OS — open source accounting: ledger, invoices and VAT… is an MCP server listed in the public MCP registry as ai.ekwo/mcp. Double-entry books an agent keeps as the user: invoices, VAT returns, 174 country packs. This page covers its npm package (@ekwo-ai/mcp).
Is the Ekwo OS — open source accounting: ledger, invoices and VAT… MCP server safe to use?
Ekwo OS — open source accounting: ledger, invoices and VAT… scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Ekwo OS — open source accounting: ledger, invoices and VAT… MCP server expose?
Ekwo OS — open source accounting: ledger, invoices and VAT… exposes 76 tools: list_companies, get_company, list_accounts, search_contacts, suggest_duplicate_contacts, and 71 more. Their descriptions and schemas cost roughly 17,408 tokens of context every time the server is loaded.
Is the Ekwo OS — open source accounting: ledger, invoices and VAT… MCP server still maintained?
Ekwo OS — open source accounting: ledger, invoices and VAT… is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Ekwo OS — open source accounting: ledger, invoices and VAT… MCP server under?
Ekwo OS — open source accounting: ledger, invoices and VAT… declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Ekwo OS — open source accounting: ledger, invoices and VAT… MCP server?
VerifyMCP ran 16 checks on Ekwo OS — open source accounting: ledger, invoices and VAT…, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.