Make Eonebill the invoice backend for your finance workflows

Add controlled invoice creation, customer context, and lifecycle signals to your platform without turning human-authorized sends into autonomous actions.

Review the APIStart an integration

Create invoice drafts

Create organization-scoped invoice drafts that stay inside Eonebill until a person reviews and sends them.

Sync customer records

Create and read customer records so finance workflows can keep billing context connected.

React to lifecycle signals

Receive signed events when invoices are sent, viewed, paid, or first become overdue.

A clear invoice lifecycle, end to end

Your platform can prepare the work, observe what happens next, and keep the customer-facing send under human control.

  1. Draft
  2. Human review
  3. Sent
  4. Viewed
  5. Paid

Four ways to connect

Start with the surface that fits your product, then keep permissions as narrow as the workflow allows.

REST API

Use an OpenAPI 3.1 contract and scoped organization keys for supported invoice and customer operations.

Review the API

Signed webhooks

Subscribe to six organization-scoped events, verify HMAC-SHA256 signatures, and handle stable delivery IDs.

See webhook events

Zapier

Prototype with five polling triggers and three controlled actions while public directory review remains separate.

View Zapier preview

Read-only MCP

Give compatible AI clients eight read-only finance tools without registering create, update, send, or delete tools.

Open server card

AP-readable invoice self-check

Field readiness against public portal documentation

This comparison checks whether Eonebill exposes nine common invoice fields documented by Coupa and SAP. It does not claim a direct portal integration or guarantee acceptance: buyer, country, tax, and PO rules can require additional data.

4

Ready fields

5

Conditional fields

9

Fields reviewed

CoupaInvoice import fieldsSAP Ariba Buying and InvoicingInvoice data fieldsSAP Business NetworkInvoice rules and fields
Ready

Invoice number

Included in the visible PDF and structured JSON.

Coupa
Invoice Number is required for invoice imports.
SAP Ariba Buying and Invoicing
InvoiceNumber is part of the invoice header data.
SAP Business Network
Invoice Number is always required.
Ready

Invoice date

Included as a date in the visible PDF and structured JSON.

Coupa
Invoice date is supported; imports should provide a date only.
SAP Ariba Buying and Invoicing
InvoiceDate is part of the invoice header data.
SAP Business Network
Invoice date participates in invoice identity and validation.
Conditional

Due date / payment terms

Due date is included; a separate structured net-terms field is not.

Coupa
Payment-term requirements depend on the invoice channel and buyer.
SAP Ariba Buying and Invoicing
PaymentTerms is available in invoice header data.
SAP Business Network
Net terms can be made required by buyer rules.
Conditional

PO reference

Header PO number is optional; PO line references are not structured.

Coupa
PO invoices can require a PO line or supplier part reference.
SAP Ariba Buying and Invoicing
ERP order ID and order-line number are represented at line level.
SAP Business Network
PO line reference is required for PO invoices.
Ready

Supplier / payee

Legal name, optional tax ID, and remit-to text are structured.

Coupa
Supplier name or supplier number identifies the invoice supplier.
SAP Ariba Buying and Invoicing
Supplier and supplier location are present in header data.
SAP Business Network
Supplier identity is represented by the From party.
Conditional

Buyer / payer

Buyer legal name is structured; buyer address and portal ID are not.

Coupa
Buyer context normally comes from the customer or backing PO.
SAP Ariba Buying and Invoicing
PurchasingUnit identifies the buying unit in exported invoice data.
SAP Business Network
To is required; Bill To and Sold To can be buyer-required.
Conditional

Line items

Description, quantity, unit price, and amount are structured; line ID and UOM are not.

Coupa
Line description and price are required import fields.
SAP Ariba Buying and Invoicing
Description, amount, unit price, currency, and order references are line data.
SAP Business Network
Description and quantity are required; PO invoices need line references.
Conditional

Tax

Tax rate and amount are structured; category, code, and local-currency tax are not.

Coupa
Tax fields vary by customer configuration and country rules.
SAP Ariba Buying and Invoicing
Tax code, type, and tax charge can be represented at line level.
SAP Business Network
Tax amount and category are required; extra details can be rule-driven.
Ready

Total and currency

Subtotal, tax amount, total, and ISO currency code are structured.

Coupa
Invoice totals and currency are represented in invoice data.
SAP Ariba Buying and Invoicing
GrossAmount and GrossAmountCurrency are header fields.
SAP Business Network
Subtotal and Amount Due are always required.

Conditional means the core field exists, but portal-specific identifiers, addresses, line references, units of measure, or tax classifications may still be required. Validate against the buyer's active rules before submission.

Signed signals for the moments that matter

Each delivery includes a stable event ID and delivery ID. Consumers verify a timestamped HMAC-SHA256 signature and can process retries idempotently.

invoice.sentinvoice.viewedinvoice.paidinvoice.overduew9.submitted1099.threshold_reached

The platform prepares. A person sends.

Eonebill supports useful automation without silently crossing the customer-communication boundary.

  • Sending invoices and reminders remains a signed-in human action
  • Organization API keys are scoped and revocable
  • Webhook payloads are signed and retried with stable delivery IDs
  • MCP exposes read-only tools and records authenticated tool calls

Your integration checklist

A reviewable path from first technical check to user enablement.

  1. 01

    Review the contract

    Map the OpenAPI operations and event payloads you need.

  2. 02

    Choose least privilege

    Create a scoped key for only the approved workflow.

  3. 03

    Build in a test workspace

    Exercise draft creation, reads, signatures, and retries.

  4. 04

    Complete joint review

    Verify human-control boundaries before enabling users.

Ready to review an Eonebill connection?

Start with the public contract, then contact Eonebill to align the scopes, events, and human-control boundary for your platform.

Review the APIStart an integration