The agent layer between your finance tools
Cortena reads from the tools you already run and writes booking-ready work back into them. Native access, not brittle scraping.
Connect the stack you already run
Each connection is a working data path in production today. The bookkeeping tools receive booking-ready batches. The rest feed Cortena the context it needs.
RechnungswesenPost booking-ready batches to DATEV Rechnungswesen.
Accounting & ERP
View integrationPost booking-ready batches to DATEV Unternehmen Online.
Accounting & ERP
View integration
LivePost coded invoices into Exact Online.
Accounting & ERP
View integration
LiveProvisional and final bookings in Twinfield.
Accounting & ERP
View integration
LiveEmployee expenses, coded like invoices.
Spend Tools
View integration
LiveSend approved invoices to Embat treasury.
Treasury & Banking
View integration
Live2,000+ banks connect for reconciliation and cash positions.
Treasury & Banking
View integration
LiveAutomated AR workflows in weclapp.
Accounting & ERP
LiveCustomer context on every invoice.
CRM
Google DriveExport batches and reports to Drive.
File sharing
Google MailCapture invoices from Gmail.
Microsoft OutlookCapture invoices from Outlook.
MCPAsk Cortena from ChatGPT or Claude.
MCP
Every connection is built for native access, full traceability, and audit-ready by default.
Data is hosted in Germany, encrypted at rest, and never used to train models. GoBD-aligned, with the archive staying in DATEV.
More tools on the roadmap
These connections are next, across accounting, ERP and spend. They follow the same rule as the rest: read the source, code it once, keep the trail.
Post coded invoices into NetSuite.
Accounting & ERP
Booking-ready entries into Dynamics 365.
Accounting & ERP
Post entries into SAP S/4HANA.
Accounting & ERP
Sync coded invoices with Odoo.
Accounting & ERP
Booking-ready entries into QuickBooks.
Accounting & ERP
Post coded invoices into Xero.
Accounting & ERP
Pleo card spend, coded and approved.
Spend Tools
Spendesk spend, coded and approved.
Spend Tools
Moss card and invoice spend, booked.
Spend Tools
Airwallex card and spend, coded.
Spend Tools
Order and customer data from Shopware.
Revenue Ops
Match Stripe payments to invoices.
Treasury & Banking
Booking-ready entries into AFAS.
Accounting & ERP
Booking-ready entries into Visma.
Accounting & ERP
Payroll postings from DATEV LODAS.
Accounting & ERP
Customer context from Salesforce.
CRM
Order and customer data from Shopify.
Revenue Ops
Subscription billing from Chargebee.
Revenue Ops
Cash flow data from Agicap.
Treasury & Banking
Approvals and alerts in Slack.
Collaboration
Roadmap items are framed as vision, not shipped features. Timelines shift as we build.
Integration questions, answered
Cortena uses the official DATEV Rechnungsdatenservice 1.0 to export booking-ready batches into DATEV Unternehmen online. Nothing is scraped and no credentials are shared. The archive stays in DATEV.
DATEV, Exact Online and Twinfield are live today. Each receives coded, approved invoices as booking-ready entries, so your team stops rekeying. Exact and Twinfield also keep the document linked to the entry.
Yes. Import MT940, CAMT.053 and CSV statements, or connect your bank directly through our Yapily partnership across 2,000+ European banks. Both reconcile against booked invoices.
The MCP server lets ChatGPT and Claude query Cortena in plain language. Read access is open, and any write action is gated behind approval so the audit trail stays intact.
- Still have a question?
Put the agent layer over your finance stack
See how Cortena reads from your tools and writes booking-ready work back into them.
Book a demo