Pennylane API integration services (FacturX · OpenFinance · Pro Account)

Feature modules we deliver

Data available for integration

The table below is derived from the Pennylane data-sharing schema, the public Company API, and analysis of the Android and iOS apps. It is the canonical inventory we use when scoping projects.

Typical integration scenarios

1. FacturX issuance from a custom billing engine. Your SaaS already issues invoices, but the 2026 French e-invoicing reform requires routing through an approved platform. We push your structured invoices into Pennylane via POST /v2/customer_invoices, attach the FacturX hybrid PDF, and let Pennylane (a registered PDP) deliver to the recipient and to the public portal.
2. Pro Account treasury dashboard. A finance team wants a single Looker view across Qonto, Pennylane, and a corporate Mastercard program. We schedule an authorized pull of Pro Account transactions, normalize them into a common fct_transactions table, and emit a webhook on each Pennylane mobile push for near real-time updates.
3. ERP-to-accounting reconciliation. An e-commerce SME issues invoices in NetSuite and pays suppliers from Pennylane. We sync supplier invoices into NetSuite as bills, replay Pennylane's reconciliation suggestions, and write back the ledger reference so the accountant view stays aligned.
4. Accounting-firm multi-tenant analytics. A 50-client cabinet wants overdue-invoice and VAT-recovery KPIs across all clients. We register an OAuth 2.0 marketplace integration against the Firm API, paginate through each company's data, and feed a multi-tenant warehouse with row-level isolation.
5. Mobile expense capture for field teams. Field staff snap receipts in WhatsApp; a serverless OCR pipeline forwards each receipt and the matching Pro Account card transaction into Pennylane via the supplier-invoice endpoint, completing categorization before month-end close.

Technical implementation

The Company API v2 uses Bearer tokens generated from account settings (multiple tokens per company, each with scopes and expiry). Marketplace integrations require OAuth 2.0 registration with integrations@pennylane.com. Rate limit: 5 requests per second per token across production and sandbox — wrap with exponential backoff and a leaky-bucket queue.

POST https://app.pennylane.com/api/external/v2/customer_invoices
Authorization: Bearer <COMPANY_API_TOKEN>
Content-Type: application/json

{
  "customer": { "source_id": "CUST-1042" },
  "date": "2026-04-01",
  "deadline": "2026-04-30",
  "currency": "EUR",
  "line_items": [
    { "label": "Annual SaaS subscription",
      "quantity": 1,
      "unit_amount": { "currency": "EUR", "value": "1200.00" },
      "vat_rate": "FR_200" }
  ],
  "format": "facturx"
}

Response 201:
{ "id": "inv_8f42...", "public_id": "F2026-000123",
  "status": "draft", "facturx_pdf_url": "https://..." }

GET /api/external/v2/transactions?
    bank_account_id=acct_pro_FR76...&
    from=2026-03-01&to=2026-03-31&
    page=1&per_page=100
Authorization: Bearer <COMPANY_API_TOKEN>

# Response includes: amount, currency, label,
# counterpart_iban, mcc, card_last4, status,
# matched_invoice_id, vat_code, attached_receipt_url
# 429 -> honor Retry-After, fall back to 1 req/s

// 1. Authorization code flow (PKCE)
GET /oauth/authorize?
    client_id=...&response_type=code&
    scope=firm.read+firm.write&
    redirect_uri=https://your.app/callback

// 2. Exchange code -> access_token + refresh_token
POST /oauth/token  (grant_type=authorization_code)

// 3. Subscribe to events
POST /v2/webhooks
{ "url": "https://your.app/hooks/pennylane",
  "events": ["invoice.paid", "transaction.created"],
  "signing_secret": "whsec_..." }

// 4. Verify HMAC-SHA256 signature on every delivery

Compliance & privacy

Pennylane operates under several overlapping French and EU regimes. Every integration we ship is reviewed against them before go-live:

• French e-invoicing reform (2026) — Pennylane is a registered Plateforme Agréée (PDP). Connectors must respect FacturX, UBL, or CII output and route through approved channels.
• PSD2 / Open Banking — Pro Account funds are custodied by an ACPR-approved institution; AISP/PISP-style flows must follow strong customer authentication and explicit consent.
• GDPR — data minimization, lawful basis, retention windows, and DPA wording are part of every delivery package; subject access and erasure flows are documented.
• French Code général des impôts — VAT codes, archive periods, and audit trails are preserved in our integration tests.

Data flow / architecture

A typical pipeline for a Pennylane-powered finance dataset:

• 1. Pennylane mobile / web client — invoice creation, Pro Account card swipe, supplier upload.
• 2. Authorized API ingestion — our connector pulls Company API or Firm API endpoints and listens to webhooks (HMAC verified).
• 3. Normalization & storage — payloads are mapped to a canonical schema (invoices, transactions, ledger entries) and persisted in Postgres or BigQuery with row-level tenancy.
• 4. Analytics & outbound APIs — downstream BI tools, ERP write-back, or your own customer-facing API consume the normalized layer.

Market positioning & user profile

Pennylane is a France-first B2B platform serving small and mid-sized businesses and the accounting firms that support them. Primary users include CFOs and finance leads at SMEs (10–250 employees), bookkeepers inside cabinets d'expertise comptable, and freelancers upgrading from spreadsheet workflows. Mobile coverage spans Android (com.pennylane) and iOS, with the desktop web app handling the heavy accounting close. Adoption is heavily concentrated in France, with growing reach across French-speaking Europe as the 2026 e-invoicing reform pushes companies onto certified platforms.

Screenshots

Click any thumbnail to view a larger preview. Screenshots are sourced from the official store listing and illustrate the screens we map to API endpoints.

Similar apps & integration landscape

Finance and accounting teams rarely operate Pennylane in isolation. The apps below frequently appear alongside it; we've shipped integrations between Pennylane and several of them. Each is described purely as part of the broader OpenFinance ecosystem.

• Qonto — European neobank for professionals; teams running both Qonto and Pennylane usually want unified transaction exports and consolidated SEPA reconciliation.
• Indy — French accounting platform aimed at freelancers and self-employed professionals; integration scenarios focus on migrating ledgers or running parallel VAT preparation.
• Tiime — TPE/SMB-focused accounting and invoicing app; common asks include synchronizing customer files and bridging FacturX issuance.
• Agicap — Lyon-based cash-flow management software; combined Pennylane + Agicap pipelines power 13-week cash forecasts.
• Sage — Reference accounting suite for structured SMEs; we map Pennylane ledger entries into Sage analytical accounts during migrations.
• Evoliz — Invoicing tool for very small businesses, auto-entrepreneurs, and craftsmen; teams switching to Pennylane often need a one-time export bridge.
• EBP — Long-standing French accounting suite; integration use cases include double-write of journal entries during a transition phase.
• Regate by Qonto — Finance automation platform; reconciliation and supplier-payment workflows often need to coexist with Pennylane data.
• IPaidThat — Receipt and supplier-invoice automation; pipelines forward extracted PDFs into Pennylane's supplier-invoice endpoint.
• Dougs — Online accounting service; data extraction is typically requested when a customer migrates to Pennylane Firm.
• QuickBooks Online — International alternative; cross-border SMEs frequently sync invoices between QuickBooks and Pennylane for French subsidiaries.

Contact

To request a quote, share your target Pennylane scope, or start a sandbox build, open our contact page:

Open contact page