fino data services logo
Contact
fino data services logo

Updated: 8 June 2026 · 60+ connected target systems

Document delivery as a feature for SaaS, ERP & finance software

Deliver documents to 60+ systems, with a single API integration.

pushdocs delivers your customers' documents — invoices, receipts and bank statements — automatically where they are needed: into their accounting, cloud storage or DMS. You only integrate a single API. pushdocs handles authentication, metadata transfer, delivery, duplicate detection and retry, under your brand.

Get in touch View API docs
</> pushdocs API Sandbox 
# Deliver document to a target system
POST /v1/transactions
{
  "identity": "cust_8a3f...",
  "connection": "conn_datev_77...",
  "document_type": "invoice",
  "file": "<base64 or URL>"
}

# 202 Accepted · Status via webhook
{
  "status": "queued",
  "transaction_id": "txn_4f2c..."
}

In brief

pushdocs delivers documents and their metadata from your software to 60+ target systems: invoices, receipts and bank statements into accounting systems like DATEV, sevdesk and Lexware Office, into cloud storage like Dropbox and OneDrive, into DMS and more. For cloud storage and DMS, any document type is possible. You integrate one API. pushdocs handles authentication, metadata transfer, duplicate detection, retry and delivery status, under your brand and for any number of end customers.
  • A complete feature, one API: 60+ target systems instead of dozens of in-house connectors
  • Reliable: duplicate detection, retry logic and delivery status included
  • For any number of end customers through one integration; your customer relationship stays with you
  • 60+ target systems accounting, cloud storage, DMS and more
  • >700,000 docs/month delivered via pushdocs
  • Dedup + retry duplicate detection and retry included
  • B2B2B white-label, no end-customer business

Who it's for

Built for software teams that deliver documents to many target systems.

If your customers need their documents in their own accounting, cloud storage or DMS, and your team doesn't want to build and maintain dozens of connectors, you're in the right place.

  • DMS & document management

    File documents into DocuWare, ecoDMS, SharePoint and more.

  • ERP & accounting software

    Deliver documents into DATEV, sevdesk, Lexware Office and the like.

  • Invoicing & billing software

    Bring generated documents straight into your customers' target systems.

  • AP/AR automation & spend

    Reliably deliver processed documents into the target system.

  • Vertical & industry SaaS

    Add document output as a ready-made feature to your product.

  • Tax advisor & practice software

    Deliver client documents into their target systems.

How it works

From your document to the target system.

Four steps, one integration. After that, delivery to 60+ systems runs for any number of end customers through your product.

Connect the target system

Your customer connects their target system once via the secure Connect interface (own subdomain). After that, pushdocs can deliver there.

Hand over the document

Your software hands over the document with its metadata via API — as a PDF, image or structured record.

Deliver

pushdocs authenticates, passes on the document with its metadata and delivers reliably, with duplicate detection and retry.

Receive status

You receive the delivery status per document via webhook or the API.

Target systems

Delivery to the systems your customers already use.

60+ systems across accounting, cloud storage and document management. Chances are your customers' system is among them.

Accounting & tax (25)

Cloud storage (17)

Document management (5)

ERP, project & other (11)

Your desired target system isn't listed? We're continuously adding more. Get in touch and we'll check whether it's already on the roadmap and factor your need into the planning.

Connect for end customers

Your customers connect their target systems via a secure interface.

To let pushdocs deliver, your customer connects their target system via a dedicated, secure pushdocs Connect interface, with its own subdomain per customer. You link there from your product; your customer selects their system and signs in. The interface can be styled to match your brand (white-label), and pushdocs manages the credentials securely and separately.

  • Dedicated, secure interface: a separate URL with its own subdomain per customer, kept apart from your frontend for security.
  • White-label: the Connect interface can be styled to match your design.
  • Secure credentials: encrypted separately, never visible in your frontend or API.
  • Status events: connection and delivery status via webhook.

For developers

One API, clear environments, complete docs.

Test in the sandbox against the same API as in production. Go live when your integration is ready.

</> Core endpoints 
POST /v1/identities // Create end-customer identity
POST /v1/transactions // Deliver document
GET  /v1/transactions/:id // Query delivery status
GET  /v1/integrations // available target systems
POST /v1/tokens // Token for Connect UI

# Webhook example (delivery status)
{
  "event": "transaction.delivered",
  "transaction_id": "txn_4f2c...",
  "connection": "conn_datev_77..."
}

Document types

You hand over the document as a finished file, supplemented with structured metadata depending on the target system. pushdocs passes the document on unchanged. Which target systems are supported is shown in the section above.

  • Invoice
  • Credit note
  • Delivery note
  • Receipt
  • Bank statement
  • Payment receipt
  • Dunning notice
  • Order confirmation
  • Separate environments: Sandbox and production via the same API.
  • Webhooks & status: Delivery and error status in real time.
  • Docs & quick start: docs.pushdocs.io

Build vs. Buy

Build it yourself, or embed pushdocs.

One job: reliably bringing your documents into your customers' target systems. The commercial customer relationship stays with you.

Criterion
Embed with pushdocs
Build & operate yourself
Effort
one API
dozens of connectors
Target systems
60+ connected
connect each system yourself
Authentication and credentials
we handle it
secure it yourself
Deduplication, retry, delivery status
included
build yourself
Secure Connect interface for end customers
included
build yourself
Keeping connectors current
we handle it
ongoing in-house upkeep

Criterion

  • Effort
  • Target systems
  • Authentication and credentials
  • Deduplication, retry, delivery status
  • Secure Connect interface for end customers
  • Keeping connectors current

Embed with pushdocs Recommended

  • one API
  • 60+ connected
  • we handle it
  • included
  • included
  • we handle it

Build & operate yourself

  • dozens of connectors
  • connect each system yourself
  • secure it yourself
  • build yourself
  • build yourself
  • ongoing in-house upkeep

Is pushdocs a fit for your product?

Get in touch so we can discuss your requirements.

Get in touch

Security & operations

Infrastructure you can build your product on.

Infrastructure you can build your product on.

Certified & monitored

Duplicate detection prevents double delivery, retry logic catches failures, and the delivery status is available per document. Failed deliveries are reported so your product can react.

Secure credentials

Your customers' credentials are stored encrypted and separately, and are visible neither in your frontend nor via the API.

Operations & support

Operated by fino data services GmbH as an established provider. We support you from the first integration through go-live.

FAQ

Do we have to build the connectors ourselves?

No. pushdocs delivers to 60+ target systems through a single REST API. pushdocs handles authentication, metadata transfer and delivery. You integrate once and offer delivery under your brand.

Which target systems are supported?

60+ systems across accounting (DATEV, sevdesk, Lexware Office, Xero, QuickBooks), cloud storage (Dropbox, OneDrive, Google Drive, SharePoint) and document management (DocuWare, ecoDMS), plus SFTP and more.

Does it work with many end customers (multi-tenant)?

Yes. Via identities and connections you manage many end customers and their target systems through a single integration. It is designed for multi-tenant SaaS and ERP vendors with many customers.

What happens if a delivery fails?

pushdocs detects duplicates, automatically retries failed deliveries and reports the status per document via webhook or API. That keeps it traceable what was delivered.

Can our customers connect their target systems themselves?

Yes. Your customers connect their target system themselves via a secure pushdocs Connect interface, with its own subdomain per customer and styleable to match your brand. You link there from your product. pushdocs manages the credentials securely and separately.

Do I need a partnership with the target system?

It depends on the target system. Most integrations are available out of the box and need no partnership or certification, for example Google Drive. For a few target systems a direct partnership is required; pushdocs then acts as your technical integrator and supports you in initiating and establishing the partnership.

Does the customer relationship stay with us?

Yes. pushdocs does not sell a competing product to your customers and does not appear towards them. The commercial customer relationship stays entirely with you.

How are our customers' credentials protected?

Credentials are stored encrypted and separately and are visible neither in your frontend nor via the API. pushdocs handles authentication towards the target systems.

Is there a sandbox and developer documentation?

Yes. There are separate development and production environments as well as API documentation at docs.pushdocs.io with quick start, data models and an integration overview.

Bring document delivery into your product?

Get in touch.
We'll show the delivery flow and clarify target systems, multi-tenant setup and go-live.

Get in touch