Skip to main content
Glama

Export statement to journal entries

export_journal
Read-onlyIdempotent

Reshape camt.053 bank statement entries into ready-to-POST journal payloads for Xero or QuickBooks. Placeholders indicate fields needing operator input.

Instructions

Export a camt.053 statement as accounting-platform journal-entry payloads.

Use this to reshape a statement's booked entries into ready-to-POST Xero or
QuickBooks payloads (the tool builds the payloads only; it does not call any
external API or write files). To discover the valid ``target`` values first,
call ``list_export_journal_targets``.

Parses the supplied statement and re-shapes every booked entry
into a target-specific journal-entry payload ready for direct
POST to the accounting platform's REST API.

Supported targets (see ``camt053_mcp.export_journal.SUPPORTED_TARGETS``):

* ``"xero"`` - returns a list of Xero ``BankTransactions``
  payloads. Each entry maps to ``{Type, Reference, Date,
  BankAccount, Contact, LineAmountTypes, CurrencyCode,
  LineItems}``; CRDT entries become ``Type=RECEIVE`` and DBIT
  entries ``Type=SPEND``.
* ``"qbo"`` - returns a list of QuickBooks Online
  ``JournalEntry`` payloads. Each entry produces a balanced
  two-line journal (one to the bank account, one to a clearing
  account; sign flipped on debit entries).

Operator-specific values (account codes, contact identifiers,
realm IDs) appear as ``"OPERATOR_FILL"`` placeholders so the
operator knows exactly what still needs wiring. The response's
``placeholder_count`` field reports the total.

NetSuite + SAP S/4HANA targets are tracked as a follow-up in #17.

Args:
    xml: The raw camt.053 statement XML as a string.
    target: One of ``"xero"`` or ``"qbo"`` (default ``"xero"``).

Returns:
    ``{"target", "entries", "placeholder_count", "placeholder_field"}``
    on success, or ``{"error": ...}`` on failure (unsupported
    target / malformed XML / parse refusal).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xmlYesThe raw camt.053 statement XML document as a string; its booked entries are reshaped into journal-entry payloads.
targetNoThe accounting platform to shape journal-entry payloads for. Must be exactly one of: 'qbo', 'xero' (see list_export_journal_targets).xero
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds significant behavioral detail beyond annotations: it clarifies the tool does not call external APIs nor write files, describes the per-target output structure (Xero BankTransactions, QBO JournalEntry), explains placeholder fields, and notes unsupported targets. This fully compensates for the lack of detailed annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with a clear purpose first, followed by usage note, target details, and return format. It is slightly lengthy but every sentence contributes value. No unnecessary repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's two parameters and lack of output schema, the description fully specifies the input, output structure (including fields like placeholder_count), constraints (unsupported targets), and prerequisites. It leaves no ambiguity for an agent invoking the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the behavior per target, the placeholder concept, and that valid target values can be discovered via a sibling tool, going beyond the enum list in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it exports a camt.053 statement as journal-entry payloads. It distinguishes itself by noting it does not call external APIs or write files, and it references the sibling tool 'list_export_journal_targets' for discovering valid targets, differentiating from that tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates when to use the tool (to reshape statements into payloads for Xero or QBO) and advises calling 'list_export_journal_targets' first. It implicitly excludes actual posting, but doesn't explicitly state when not to use it or list alternatives beyond the sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebastienrousseau/camt053-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server