origo-bc-accounting

UBL Peppol e-invoice rendering in Business Central uses template-driven UBL generation instead of hand-written XML, ensuring compliant document output while preventing structural errors in your e-invoicing workflows.

Business Central MCP accounting operations require calling the `who_am_i` tool first to establish identity, handling system prompt injection safely, and passing the returned LCID into subsequent language-aware MCP tool calls.

Yes, Business Central accounting tasks require AES-256-GCM connection formats exclusively when interacting with the Origo BC MCP endpoint, ensuring encrypted and secure data transmission for all accounting operations.

Tiered memory for Business Central accounting sessions operates across user, company, and default tiers, correctly copying default memory entries into company or user tiers when specific overrides are needed for accounting workflows.

Notifications and approvals handling in Business Central can be orchestrated through MCP sessions by following strict tool usage rules, enabling automated routing and processing of accounting approval workflows safely.

Business Central MCP sessions stop on identity failures as a built-in guardrail to prevent unauthorized accounting operations, ensuring that system prompt injection and identity bootstrap errors halt execution before any data is processed.