Circula API Integration Research

Date: 2026-05-13 Product: Circula (circula.com) -- Expense Management + Corporate Credit Cards, Berlin Purpose: Evaluate Circula's API capabilities for Orcha integration -- specifically for a German customer evaluating Circula as a Pleo alternative for employee credit cards while continuing to use Orcha for AP invoices and DATEV for accounting.

Important Context: What Circula Actually Is

Circula is NOT an ERP or accounting system. Like Pleo, Moss, and Payhawk, it is a German T&E-focused spend management platform that handles:

• Corporate credit cards (physical + virtual VISA, issued through Pliant)
• Travel expense management (per diems, mileage, trip-bundled receipts)
• Employee out-of-pocket reimbursements
• Pre-accounting (AI-powered receipt OCR + GoBD-compliant validation)
• Employee benefits (vouchers, lunch, mobility, internet, "Erholungsbeihilfe")
• Accounts Payable (announced module, "Coming Soon" at time of research)

Circula sits upstream of the ERP -- it captures, codes, and approves expenses, then exports pre-accounted data to the customer's actual accounting/ERP system. DATEV is the headline target -- Circula markets itself as a DATEV Marketplace Premium Partner and exports via DATEVconnect online / Rechnungsdatenservice 1.0 directly into Belege Online.

Critical difference vs Pleo and Payhawk: Circula does not appear to publish a customer-facing public REST API at all. There is no developer portal, no developers.circula.com, no API key issuance UI for customer-developed integrations, and no published OpenAPI spec. What Circula calls "API integrations" on its marketing site are partner-specific, vendor-built connectors -- DATEV, Personio, Pliant, Onesto, Lanes & Planes, Exact Online, Business Central. Each is implemented as a point-to-point integration where Circula is either the API consumer (Personio, Pliant, Lanes & Planes -> Circula) or the API producer for a single partner (Circula -> DATEV DUO). Customer developers cannot self-serve API keys to read Circula data programmatically.

Implication for Orcha: This is the single most important finding. For the customer scenario in scope (Orcha = AP, DATEV = accounting, Circula = card programme + T&E), the read-side path that worked cleanly for Payhawk (real-time webhooks + GET /expenses) is not available from Circula's public surface. The realistic integration paths are: (1) CSV/DATEV-XML file pickup from a shared location, (2) DATEV-as-intermediary (Circula -> DATEV DUO -> Orcha-reads-DATEV), (3) ask Circula sales to open a partner-program path -- existence not confirmed in any public source. See sections 6-8.

1. Summary -- Capability Matrix

Overall assessment: Circula's integration posture is dramatically narrower than Pleo's or Payhawk's. There is no documented public REST API, no developer portal, no webhook subscriptions, no API keys customers can issue, and no third-party iPaaS connectors (Zapier, Make, Workato, Celigo, n8n). Every "API integration" on Circula's marketing page is a vendor-built point-to-point connector where Circula has done the engineering itself with a specific partner. The realistic integration channels for Orcha are file-based (DATEV-XML, CSV, ZIP of PDFs) or via DATEV-as-intermediary. For real-time card-tx streams to Orcha, the cleanest path is bypassing Circula entirely and consuming Pliant's own API directly -- but that requires a separate Pliant contractual relationship and is essentially a different integration project.

2. API Landscape

Public API Surface

What Circula Means by "API"

Circula's marketing pages and Help Center repeatedly use the words "API" and "REST API" -- but in every concrete case, this refers to one of these partner-specific flows:

There is no path documented where a customer-side developer (or Orcha) calls a Circula-hosted REST endpoint with their own credential to read or write data. The closest thing Circula offers to developer self-service is the Standard CSV file export configurable in the UI -- that is the canonical "open" data export channel.

Authentication

Not applicable in any customer-developer sense. Where authentication is mentioned in the partner integrations, it is in the direction of Circula authenticating against the partner's API (e.g. Circula holding Personio OAuth tokens, or Circula holding DATEV Cloud Services tokens via the customer's MyDatev consent flow).

Rate Limits

Not published. Not applicable in the absence of a customer-facing API.

Versioning

Not applicable.

3. Write Capability Verification

Confidence: HIGH that no public write API exists.

File-Based Writes (Inbound to Circula)

The only inbound data path Circula offers to outside systems for reference data is its manual CSV import in the admin UI for:

• Employees
• Suppliers (the "Creditor numbers" import for DATEV mapping)
• Categories (chart of accounts mapping)

None of these are programmatic. They are admin-actioned file uploads.

Key Limitations Specifically Relevant to Orcha

1. No invoice push to Circula via API. Identical to Pleo, Payhawk, Moss. Not unusual for the category but worth restating.
2. No reference-data write to keep coding consistent. This is the biggest gap vs Pleo for the customer scenario in scope. With Pleo, Orcha could push the supplier list, CoA, tax codes, and cost centers programmatically to keep card-coding and AP-coding aligned. With Circula, the only way to do this is: (a) keep both systems pointed at DATEV as the master and rely on DATEV's manual setup wizards on each side, or (b) the customer's admin manually keeps Circula's mappings in sync by re-importing CSVs.
3. No webhook surface. No expense.created event Orcha can subscribe to.
4. No read-back endpoint. Orcha cannot query "give me all expenses since timestamp X" against Circula's own API. It can only consume what Circula has pushed to DATEV / Belege Online / a shared file location.

4. iPaaS & Middleware Findings

No iPaaS supports Circula. This is the clearest signal that Circula has not yet opened a customer-facing API surface: iPaaS vendors build connectors when a public API exists and a market wants no-code orchestration around it. The absence of a Circula connector across every major iPaaS is consistent with the absence of a developer portal.

Implication: There is no no-code / low-code intermediary option for Orcha to use as a stopgap. The realistic options collapse to file-based exchange or DATEV-as-intermediary.

5. Alternative Channels

DATEV Integration (Native, Strongest Channel)

This is Circula's only meaningful structured-data channel out of the system and is well-developed for the German market. Circula is a DATEV Marketplace Premium Partner.

Implication for Orcha-in-customer-stack: This is actually a viable read-side path if Orcha can read from DATEV (DUO Belege Online + booking entries) rather than from Circula. The customer is already on DATEV. Anything Circula exports to DUO ends up in the same DATEV environment where Orcha's invoice bookings will land. So the unified spend view can be built from the DATEV side, not the Circula side. See section 7 for the recommended architecture.

Native ERP/Accounting Integrations (Beyond DATEV)

Confirmed list:

HRIS / Payroll Integrations

• Personio (Premium Partner, API) -- Circula pulls employees from Personio via Personio's own API. Nightly sync. Personio integration article
• DATEV LODAS and DATEV Lohn und Gehalt (for reimbursement and benefit payroll bookings)
• Workday is mentioned in Capterra's listing but no Help Center article was located

Travel Integrations

• Lanes & Planes (Premium Partner; vendor-built API in the direction L&P -> Circula)
• Onesto (API; same direction)
• Perk / TravelPerk (API; same direction)

These are all inbound to Circula -- they expand the data Circula has, not data Orcha can pull out.

Credit Card Layer

Circula's cards are issued through Pliant Oy (Helsinki, Finland; VISA Europe Limited licensee; regulated by Finland's Financial Supervisory Authority as an e-money payment institution; Varengold Bank AG is the participating institution for payment processing). Card transactions flow Pliant -> Circula in real-time as draft expenses (merchant, date, amount, currency are captured; receipts and categorization must be added by the employee).

This matters for Orcha's options: Pliant has its own developer API (pliant.io). If the customer is willing to treat Pliant as the source of truth for raw card transactions (which it technically is), Orcha can integrate with Pliant directly -- bypassing Circula entirely on the read side. This is a separate research thread but worth flagging as the only realistic real-time card-tx path if Orcha needs transaction.created-style events.

Webhooks

• NONE on Circula's side. No public webhook subscription product. No subscription.created, no expense.created, no transaction.created.
• The Pliant -> Circula transaction-arrival flow is implemented as a real-time push between Pliant and Circula but is not re-emitted to third parties. From the customer's perspective inside Circula, the transaction "appears" -- there is no event you can subscribe to.

CSV / File Exports

The CSV export with the receipt-URL column is the most useful artifact for Orcha. The receipts are accessible via that URL, but URL longevity / TTL is not documented publicly. Empirical testing required before relying on it. See section 7.

6. Licensing & Access Requirements

API Access

Circula does not sell API access as a product to customer developers. It cannot be enabled by the customer's admin or purchased as an add-on. Every "API" the customer encounters is one of the pre-built partner integrations listed above.

If Orcha needs a custom integration channel, the only documented paths are:

1. Use the existing partner-program slots (DATEV, Personio, Pliant, etc.) where Circula has already built a connector
2. Use the Standard CSV export + DATEV-XML export + ZIP receipts export as a file-based intake
3. Contact Circula sales / partnership team to explore whether a custom partnership is possible (not documented as a self-service program; existence not confirmed in public sources at time of research)

Plan Pricing (Module-Based)

Circula is priced per module + per license + (for the credit-card module) per platform.

Add-ons: Document Management System (GoBD), Customer Care Plus, Daily Trips, CO₂ Reporting, Multi-Entity Setup, Tailored Customizations.

API access is not listed as a feature in any tier or add-on. "Most integrations are included in standard packages; complex integrations incur additional fees" -- this implies that custom partner integrations (e.g. with an ERP not on the standard list) may be available as a service from Circula's professional services team for an additional fee, but this is not productized as an API SKU.

Customer Setup Checklist (Worst Case)

If the customer wants Circula data flowing into Orcha:

1. Customer needs the Credit Cards module (€99/platform/mo) and an Employee & Travel Expenses license (€15+/license/mo × user count, min 10 licenses)
2. Customer needs DATEV Unternehmen Online with Rechnungsdatenservice 1.0 "Erweitert" option active (added by the tax advisor) -- if relying on the DATEV-as-intermediary architecture
3. Customer's accountant (in Circula) configures the export to DATEV
4. Orcha reads from DATEV (booking entries + receipts in Belege Online), not from Circula
5. (Optional) Customer configures a scheduled CSV export from Circula to a shared location (SFTP / Google Drive / similar) for Orcha to pick up

There is no Orcha-Circula direct API integration the customer can enable. This is the single most consequential conclusion of this research.

Pricing-vs-Pleo / Payhawk Comparison

For the customer's headline cost concern: Circula's total cost for 30 card users is broadly comparable to Pleo and Payhawk. The cost difference is not what separates them. The integration capability gap is.

7. Orcha-Specific Deep Dive

Critical Question Comparison: Circula vs Pleo on the Customer's Pain Points

What Role Does Circula Play Relative to Orcha?

Circula and Orcha have overlapping AP functionality only in Circula's announced (not-yet-live) Accounts Payable module. For the customer scenario in scope, the customer keeps Orcha for AP and uses Circula only for cards + T&E. The split is clean:

So Circula's responsibility is cards + reimbursements + travel + their export to DATEV. Orcha's responsibility is AP invoices + their export to DATEV. The two streams converge in DATEV, not in either spend tool. This is the same shape as the recommended Payhawk architecture -- with the critical difference that for Payhawk, Orcha could supplement the DATEV convergence with a real-time webhook-driven read-side; for Circula, that supplement is not available.

Integration Scenarios for the Customer

Scenario A: Orcha reads card-tx + expense data from Circula via real-time API (the Payhawk-style path)

• Feasibility: NOT POSSIBLE. No public API. No webhooks. No customer-issuable credentials.

Scenario B: Orcha reads expense data from Circula via scheduled CSV/DATEV-XML/ZIP file pickup

• Feasibility: MEDIUM, requires customer-side automation glue.
• Customer's accountant schedules a recurring export from Circula's UI (CSV + ZIP + DATEV-XML) and drops files to a shared location (SFTP, Google Drive, S3, email-to-Orcha-inbox)
• Orcha picks up the file batch on a cron and parses it
• Latency is whatever cadence the accountant configures -- typically daily or weekly. No real-time.
• Receipts available either via the URL column (TTL unverified) or via the parallel ZIP archive (more durable, recommended)
• This is the realistic Circula-as-source path.

Scenario C: Orcha reads via DATEV-as-intermediary (recommended)

• Feasibility: HIGH, leveraging assets the customer already has.
• Customer already uses DATEV. Circula already exports to DATEV in structured form (RDS 1.0 -> DUO + Belege Online).
• Orcha reads from DATEV (whatever path Orcha already uses for the customer's accounting integration) to pick up the Circula-originated bookings + receipts.
• Latency: matches Circula's export cadence (typically when the accountant kicks off the export, or whenever Circula auto-schedules).
• No new customer setup beyond what they already do for AP-into-DATEV.
• This is the recommended path because it puts the integration burden on infrastructure that's already proven and reuses Circula's strongest export channel.

Scenario D: Orcha reads card transactions directly from Pliant (bypass Circula entirely)

• Feasibility: MEDIUM-HIGH, requires separate Pliant relationship.
• Pliant has its own developer API (pliant.io / developer.pliant.com).
• If the customer is willing to provision Pliant API credentials directly for Orcha, Orcha can subscribe to Pliant's transaction events in real-time without depending on Circula.
• Caveat: customer would need to be the Pliant card programme account holder; in some Circula configurations Circula is the contracting party, not the customer.
• This is a separate integration project -- documented separately if pursued.

Scenario E: Orcha writes reference data into Circula to keep coding aligned

• Feasibility: NOT POSSIBLE via API.
• The realistic substitute is: customer's admin sets up DATEV's reference data once (CoA, KOST, tax codes, employee Kreditor numbers) and then manually maps in Circula. If Orcha is the supplier-master authority, the customer must manually keep Circula's supplier list aligned via CSV import in the UI. Not scriptable.
• This is materially worse than Pleo's full CRUD for reference data.

Scenario F: Orcha pushes invoices into Circula

• NOT relevant for this customer (they use Orcha for AP, not Circula).
• Also NOT POSSIBLE via API even if it were relevant -- email-to-app / UI upload are the only invoice intake channels.

Receipt URL Longevity -- Same Unknown as Payhawk

The CSV export's receipt-URL column is the most attractive structured-data artifact, but TTL is undocumented. Recommendation: rely on the parallel ZIP archive export, which contains the original receipt files in their durable form. This sidesteps the TTL question entirely -- the customer's automation exports ZIP + CSV together; Orcha downloads the ZIP at pickup time and stores receipts in its own object storage.

Field Completeness on Card Transactions

What Circula natively captures (per the Pliant integration docs):

So even via the CSV/DATEV-XML export path, the data Orcha receives is only the post-completion expense -- the raw pre-review card-tx is not exposed in any export. For a unified spend view, this means Orcha sees card transactions only after the employee has completed them inside Circula (with whatever latency that introduces). If the customer needs pre-review card-tx visibility, the only path is directly from Pliant.

Orcha Integration Capability Summary

8. Recommended Path Forward

Assessment: Circula is a Materially Weaker Integration Partner for Orcha Than Pleo or Payhawk

The customer evaluating Circula as a Pleo replacement gets:

• A comparable corporate card programme (real VISA via Pliant; physical + virtual; €750k per-card limit; reimbursement-free spending) -- so the headline product is genuinely competitive
• The deepest DATEV integration in the category among the products we've researched -- if the customer's only requirement is "Circula -> DATEV", they win
• A markedly worse posture for any read-side integration from Orcha back into Circula -- no public API, no webhooks, no iPaaS connector, no developer self-service

Recommended Architecture

[Card transactions]                                    [Vendor invoices]
       |                                                      |
       v                                                      v
   Pliant -- real-time push --> Circula                    Orcha
                                  |                           |
                                  | (RDS 1.0 + Belege Online) | (DATEV direct)
                                  v                           v
                                DATEV  <-- shared books -->  DATEV
                                  ^
                                  |
                                  +--- Orcha reads here for the unified spend view

The recommended Orcha read-side pattern is to read from DATEV, not from Circula. Both Circula and Orcha land in DATEV; the unified spend view is built at the DATEV layer.

If DATEV-side reads are not available or insufficient for the analytics use case, fall back to:

1. Scheduled CSV + ZIP export from Circula to a customer-managed shared location (SFTP / Drive / S3 / email-to-Orcha-inbox)
2. Orcha picks up the bundle on a cron, parses CSV, extracts ZIP receipts into Orcha's storage
3. Latency is daily/weekly depending on customer scheduling

If real-time pre-review card-tx visibility is non-negotiable, the only path is a direct Pliant integration, treated as a separate project. This bypasses Circula and is technically clean (Pliant has a real API with documented webhooks for transaction events), but requires the customer's Pliant card programme to be set up with API access enabled.

Write Side (Orcha -> Circula)

Skip. There is no API to write to. The realistic options are:

1. Rely on DATEV as the master for CoA, KOST, tax codes, employee Kreditor numbers -- customer admin configures DATEV, then manually maps inside Circula's UI. No Orcha involvement on the Circula side.
2. For suppliers: if Orcha is the supplier-master authority, the customer's admin manually keeps Circula's supplier list aligned via CSV import. Not scriptable.

When to Recommend Circula to a Customer

1. Customer's primary need is the deepest DATEV integration available and they don't need any custom programmatic access. Circula wins on DATEV depth and German-market fit.
2. Customer is happy with file-based or DATEV-mediated reporting and does not need real-time spend analytics in Orcha.
3. Customer values the Berlin-headquartered, GoBD-certified, German-server-hosted posture for compliance reasons.

When NOT to Recommend Circula

1. Customer needs real-time card-tx events in Orcha for live spend analytics -- Pleo and Payhawk both offer this; Circula does not.
2. Customer expects Orcha to keep reference data in sync via API -- Pleo offers full CRUD; Circula does not.
3. Customer has invested in iPaaS tooling (Zapier, Make, Workato) and expects to use it to orchestrate around the spend tool -- no Circula connector exists on any iPaaS.

Architecture Decision

Pre-Implementation Verification Needed

Before any engineering commitment to integrate with Circula:

1. Confirm with Circula sales whether a partner-program or private API channel exists for customer-developed integrations -- not documented publicly, may exist on request. If yes, get the developer docs + sample credentials and re-do this research.
2. Probe the receipt-URL TTL on the CSV export -- not strictly necessary if Orcha uses the ZIP fallback, but useful to know.
3. Confirm whether Circula's auto-export to DATEV can be scheduled to fire on every approved expense, or only on accountant-triggered batches. The DATEV-as-intermediary path's latency depends on this.
4. Confirm Pliant's API availability under Circula's card programme -- in some configurations Circula is the Pliant account holder and the customer cannot self-serve Pliant API credentials.
5. Confirm field-level completeness of the DATEV-XML / CSV export -- specifically: card last-4, FX details, approver names, cost center (KOST1/KOST2 if mapped), tax code (BU keys). The Help Center is not specific enough about which fields are guaranteed to be populated.

Recommendation Summary

For the customer scenario (DATEV + Orcha + Pleo replacement with Circula for cards): integrate via DATEV-as-intermediary (Scenario C). Add a scheduled CSV + ZIP export fallback (Scenario B) if the DATEV path doesn't carry the field detail Orcha needs. Do not plan for a direct Circula API integration -- one does not exist as a customer-facing product, and the absence of any iPaaS connector confirms this is not an oversight in our research.

Circula compared to Pleo on the three critical gaps that prompted this evaluation:

1. Realtime: WORSE. Pleo's Export Jobs API + Svix webhooks at least let Orcha trigger a fresh export. Circula has no equivalent and no public webhook product.
2. Receipt URL longevity: TBD but mitigable. Pleo's 24h URL expiry is matched by Circula's undocumented URL TTL on CSV exports -- but Circula's parallel ZIP archive export gives Orcha durable receipt files, sidestepping the problem.
3. API pricing tier: Not productized at all. Pleo gates API to its Advanced plan ($109/mo+); Circula doesn't sell API access in any plan.

Where Circula beats Pleo: DATEV depth (Premium Partner, RDS 1.0, Belege Online, LODAS, Lohn und Gehalt, EO comfort all native), German-market polish, GoBD certification, German server hosting.

Bottom line: Circula is a strong DATEV-paired T&E and card tool for German SMEs. It is a weak standalone-API integration partner. The customer should choose Circula if their integration appetite is "Circula exports everything to DATEV and we work from there"; they should choose Payhawk if they want real-time webhooks and a customer-facing developer API; they should keep Pleo if they specifically need full-CRUD reference data writes (Pleo's only real edge over Payhawk).

9. Sources

Official Circula Pages

• Circula main site
• Expense Management product
• Travel Expense Management
• Corporate Credit Cards
• Circula for CFOs
• Pricing & Plans
• Plug-and-play Integrations Overview
• Integrations Product Page
• Circula launches fully digital corporate credit card (blog)
• Corporate Credit Card wiki
• Terms & Conditions (Pliant Oy / Varengold Bank AG references)

DATEV Integration

• Circula on DATEV Marketplace
• Circula DATEV integration (English)
• Circula DATEV product page
• Circula DATEV Payroll integration
• DATEV Magazin partner profile of Circula
• Help Center: Transfer to DATEV Unternehmen Online (Cloud Services)
• Help Center: Export zu DATEV Unternehmen Online (Cloud Services, DE)
• Help Center: Export DATEV XML File
• Help Center: Exports for DATEV LODAS and Lohn und Gehalt
• Help Center: DATEV EO Comfort. Part 1: Import
• Help Center: DATEV EO Comfort. Part 3: Export
• YouTube: Integration zu DATEV Rechnungsdatenservice 1.0

Partner Integrations (the "API" surface)

• Help Center: Personio integration
• Help Center: Personio Multi-Integration Setup
• Personio integration product page
• Help Center: pliant Credit Card Integration
• Help Center: pliant -- Enable integration
• Help Center: Issuing new credit cards
• Help Center: Credit Card collection
• Lanes & Planes x Circula integration
• Help Center: Onesto
• Onesto x Circula product page
• Help Center: Perk
• TravelPerk partnership page
• Help Center: Exact Online Integration

Export & File-Based Channels

• Help Center: Exporting expenses (CSV, DATEV-XML, SEPA-XML, PDF, ZIP)
• Help Center: Submitting digital invoices

API Catalog & Developer Surface

• Circula on apitracker.io (profile mostly empty)
• Circula technologies on apitracker.io (no developer URLs)

Pricing & Plans

• Circula Pricing (EN)
• Circula Pricing (DE)
• Circula 2026 on Capterra
• Circula 2026 on G2
• Circula on SaaSworthy
• Circula on GetApp
• Circula on OMR Reviews

Reviews & Comparisons

• Circula on G2 (company)
• Circula on Capterra (Canada)
• Compare Pleo vs Circula on Capterra
• Circula competitors on G2

Card Issuer Background

• Pliant Oy as issuer; Varengold Bank AG payment processing (referenced in Circula T&Cs)

Negative Findings (No Connector / No Public API Surface)

• Zapier search for zapier.com/apps/circula: no result
• Make.com search for make.com/en/integrations/circula: no result
• Workato search for workato.com/integrations/circula: no result
• Celigo, n8n, Tray.io: no Circula connector listed in marketplaces
• developers.circula.com, api.circula.com, circula.com/developers: no public developer portal found
• "circula" GraphQL OR OpenAPI OR Swagger OR Postman: no Circula-specific hits
• Circula GitHub organization: no public API artifacts surfaced

Addendum 2026-05-14 — Defense, Cannibalization, Funding Model

Scope: Supplementary research for a customer-facing assessment. Customer is a German defense-sector company on Pleo (employee cards) + DATEV (accounting) + Orcha (AP), wanting to replace Pleo. Updated customer priorities: (1) excellent employee credit cards as the core need, (2) strong mobile receipt-capture app, (3) a very good API Orcha can use to READ and WRITE, (4) a non-prepaid card funding model (charge card / credit line preferred). This addendum confirms/updates the four areas below; the main doc above remains valid.

1. Defense-Sector Posture — Verdict: GREEN (with one caveat)

Verdict: GREEN. Circula itself carries no defense exclusion, hosts data in Germany, and holds ISO 27001 + GoBD. This is the cleanest defense posture of the vendors assessed so far (vs Qonto RED, Pleo AMBER). The single caveat: the Pliant/Varengold card-issuer layer's prohibited-business stance is not public — get it in writing. No BSI C5 (matches Qonto/Pleo) — flag if the customer's security function mandates it.

2. Cannibalization Risk vs Orcha — Rating: MEDIUM (rising)

This is a change from the main doc, which (written 2026-05-13) treated Circula's AP module as "announced / Coming Soon" and the Circula↔Orcha split as clean. Re-checking on 2026-05-14:

• Circula's Accounts Payable module is still "Coming Soon" on the live pricing page (€149/platform/mo, 100 invoices) — not yet GA. So today the overlap is still latent.
• But Circula's current marketing has hardened the consolidation pitch: it now positions itself as "the flexible spend management solution… combining all company spend in one modular platform: from employee and travel expenses, corporate cards, and employee benefits to accounts payable" — with AI invoice OCR (extracts invoicing party, invoice number/date, line items, amounts), UStG §14 checks, and DATEV + SEPA push. That is functionally the same job Orcha does (deep invoice extraction, tax-compliance, GoBD coding, DATEV push).
• The AP module is built natively around German tax law and DATEV — i.e. aimed squarely at Orcha's home turf, not a generic bolt-on.

So the trajectory mirrors Qonto's: shallow/not-yet-live today, but a deliberate, funded move into Orcha's category, and German-market-specific. It is less acute than Qonto (no Regate-style acquisition; AP still pre-GA) but more pointed than Pleo (whose invoice OCR is static and not marketed as an AP platform). Rating: MEDIUM, trend rising. For this customer the split stays clean only as long as they keep Orcha for AP and never enable Circula's AP module — that boundary is now a sales-side risk to manage, not a given.

3. API Read/Write Refresh — Still NO public API. This is disqualifying against the customer's stated priority.

Re-verified 2026-05-14. Nothing has changed: Circula has not launched a public customer-facing API.

• developer.circula.com → connection refused. circula.com/en/developers → HTTP 404. No api.circula.com, no developer portal, no published OpenAPI spec, no Postman collection, no API-key issuance UI for customer developers.
• The apitracker.io Circula profile appears to show "OpenAPI", "webhooks", "SDKs", "sandbox", "OAuth playground" — but these are apitracker's generic catalog feature-checklist template, not links to real Circula artifacts (every field resolves to the marketing site or is blank). This is the same false-positive flagged in §2 of the main doc; do not be misled by it.
• The Circula integrations page still uses "REST API" only to describe vendor-built point-to-point partner connectors (DATEV, Personio, Pliant, Lanes & Planes, etc.) — Circula is the one calling those APIs, or producing data for one named partner. No customer-developer self-serve path.
• Still no iPaaS connector anywhere (Zapier / Make / Workato / Celigo / n8n).

What Orcha can READ: nothing directly from Circula. Only indirectly — via DATEV-as-intermediary (Circula → DUO/Belege Online → Orcha reads DATEV) or scheduled CSV/DATEV-XML/ZIP file pickup. Batch cadence, customer-admin setup, no real-time. What Orcha can WRITE: nothing. No API to write reference data (CoA, cost centers, tax codes, suppliers, employees) — those are configured in DATEV and manually mapped in Circula's UI, or CSV-imported by an admin.

Blunt assessment: the customer's priority is "a very good API so Orcha can both READ and WRITE." Circula offers neither. There is no API at all — not a weak one, not a gated one, none. Against this specific, explicitly-stated customer priority, Circula is disqualified. Payhawk (real-time webhooks + REST API free on all plans) and Qonto (webhooks + free API + payment-write endpoints) both clear this bar; Circula does not come close.

4. Card Funding Model + Cards/App UX

Funding model — matches the customer's preference. Circula's card is issued via Pliant, and Pliant's model is explicitly: "neither a prepaid nor a debit card… bank-account independent… does not need to be charged in advance." It is a real credit card with a credit line and custom billing cycles — spend now, settle on a billing cycle, backed by a Varengold-provided credit line. Circula's own card FAQ confirms "all our cards are real credit cards." This is exactly the non-prepaid / charge-card-style model the customer asked for — a clear win, and a point of differentiation vs prepaid-wallet competitors. (Per-card transaction limit €750k; 2% FX markup; 1% cashback; Apple/Google Pay; 200+ countries.)

Cards product — solid but thin on controls depth. Unlimited physical + virtual VISA cards for €99/platform/mo. In-app: issue/freeze/terminate cards, set limits, manage PINs, real-time transaction view, cost-center tracking. AI auto-matches card transactions to receipts. Competent and real, but the main doc notes auto-captured fields at transaction arrival are limited (merchant, date, amount, currency); categorization/receipts are employee-completed.

Mobile app + receipt capture — this is Circula's genuine strength. Reviews are strongly positive: G2 4.6/5 (120+ reviews), OMR 4.5/5 (276 reviews), "Top Rated — Spend Management Q2/26." Reviewers specifically praise the auto-fill receipt-capture tool and user-friendly mobile app as standout features — employees photograph a receipt, AI extracts the data, validates against local VAT rules, detects duplicates, and pre-assigns cost centers. Receipt capture / mobile UX is the most-praised part of the product across all review sites. Verdict: the app and receipt capture meet the customer's priority well.

Net for this customer: Circula nails three of the four updated priorities — strong cards, excellent receipt-capture app, and the right (non-prepaid) funding model. It fails the fourth — the API — completely, and that failure is on an explicitly-stated, load-bearing priority. Defense posture is GREEN (cleanest of the assessed vendors), cannibalization is a manageable MEDIUM. The API gap is the decisive negative.

Addendum Sources

• Circula Terms & Conditions
• Circula Compliance
• Circula Privacy Policy
• Circula Help Center — Data protection
• Circula Pricing
• Circula Integrations
• Circula Corporate Credit Cards
• Pliant — business credit card / payment platform
• Pliant — credit cards for corporations
• CPI — Pliant, Transact and Varengold partner to launch Visa business credit card
• Varengold Bank — Wikipedia
• Circula reviews — OMR
• Circula reviews — G2
• Circula reviews — Capterra
• Circula on apitracker.io (catalog template, not real API artifacts)
• Negative findings: developer.circula.com connection refused; circula.com/en/developers HTTP 404; no api.circula.com; no Zapier/Make/Workato/Celigo/n8n connector