How does Scell.io quote numbering work?

Quotes follow the DEV-YYYY-NNNN sequence, isolated per (tenant_id, sub_tenant_id) pair. A PostgreSQL counter guarantees zero collision between clients on the same platform. The sequence is immutable and audited in the ISCA ledger.

Can the client sign a quote without a Scell.io account?

Yes. The sent quote generates a unique public link (90-day TTL, signed token). The client clicks, reads the quote, and signs via a canvas interface in their browser. No account, no app to install.

What is the difference between a signed quote and a deposit invoice?

A quote is a pre-contractual commercial document, not subject to VAT. The deposit invoice (type 386) is a fiscal document: it triggers immediate VAT liability (CGI art. 289) and enters the ISCA chain. The quote is converted to a deposit via convertToDeposit, never manually.

Can you issue multiple deposit invoices from the same quote?

Yes. convertToDeposit can be called N times on the same accepted quote, with different percentages or amounts. The final balance invoice will be automatically calculated as the quote total minus all deposits already issued.

Is the quote included in the ISCA ledger?

The quote has its own audit log (quote_audit_logs) with an isolated SHA-256 chain. It does not enter the main ISCA fiscal chain (reserved for invoices and credit notes). Both chains are queryable via dedicated endpoints.

Can the email sent with the quote be customized?

Yes, via the email_message parameter in the send call. The subject and body can be customized. The signing link is added automatically.

What happens if the client refuses the quote?

The client can refuse via the public link. The status changes to "refused", a webhook is triggered, and the quote is archived. No invoice is issued in case of refusal.

Can a quote be duplicated?

Yes, via the /quotes/{id}/duplicate endpoint. A new quote with a new DEV-YYYY-NNNN number is created in draft status. Useful for recurring quotes or variants.

How is the signed quote sealed, and is it enforceable?

After a Simple Electronic Signature (eIDAS SES), Scell.io seals the quote PDF using the same cryptographic circuit as invoices: PAdES signature (PKCS#7, Scell.io server certificate), timestamping, then anchoring of the SHA-256 fingerprint onto the Bitcoin blockchain via OpenTimestamps. The response exposes a sealing object (is_sealed, pades_signed_at, signed_pdf_sha256, ots_status, ots_submitted_at, ots_bitcoin_confirmed_at, bitcoin_block_height, ots_proof_base64). The .ots receipt is verifiable offline, without depending on Scell.io. This is a sealed and anchored SES — not a Qualified Electronic Signature (QES) nor a qualified TSA timestamp.

Quotes · Deposit type 386 · Balance type 380

From signed quote to balance invoice — without switching tools.

DEV-YYYY-NNNN numbering. Canvas signature. 90-day public link. Deposit (type 386) and balance (type 380 + BG-22) conversion in one API call.

Create my first quote →See code example

$api = ScellApiClient::withApiKey('sk_live_...');

$quote = $api->quotes()->builder()
    ->buyer('12345678901234', 'Acme SAS', new Address('1 rue Test', '75001', 'Paris'))
    ->line('Prestation conseil', 1, 2500.00, 20.0)
    ->line('Hébergement', 3, 150.00, 20.0)
    ->validUntil(new DateTime('+30 days'))
    ->signatureRequired()
    ->create();

echo 'Quote ' . $quote->quote_number . ' created';

The problem

✕Fragmented cycle across 4 tools — Email, hand-signed PDF, separate billing tool, tracking spreadsheet. No link between them.
✕Deposits calculated manually — No automatic link quote → deposit → balance. Each conversion is a source of accounting error.
✕None of these tools produce Factur-X — Invoices from the quote cycle are not EN16931-compliant or PPF/PDP-compatible.

Our solution

✓Complete cycle in 1 API — DEV-YYYY-NNNN, email send, 90-day public link, canvas signature, Factur-X deposit/balance conversion.
✓Automatic convertToDeposit / convertToBalance — VAT due (type 386) and BG-22 deduction (type 380) calculated without manual intervention.
✓Continuous ISCA chain — Every invoice issued from a quote enters the SHA-256 fiscal ledger. End-to-end DGFiP traceability.

6 features, 1 complete cycle

DEV-YYYY-NNNN numbering

Compliant fiscal sequence, isolated per (tenant, sub_tenant). Zero collision between clients on the same platform. PG trigger quote_sequences.

0 numbering collisions

Canvas signature + public link

Client signs from their browser, no account needed. Signed token, 90-day TTL. Signature cycle under 24h.

Signature cycle < 24h

Integrated email delivery

No external SMTP required for testing. send_email: true in the payload. Standard deliverability included.

No email config required

Deposit type 386 conversion

VAT immediately due (CGI art. 289). Percent or amount parameter. Cash collected without waiting for the balance invoice.

Immediate VAT due

Balance type 380 + BG-22 conversion

Automatic deduction of already-invoiced deposits via auto-calculated parent_invoice_ids. 0 accounting errors, 0 corrective credit notes.

Auto balance calculation

Append-only audit log

Traceability of every action (creation, send, signature, refusal) in quote_audit_logs. PG trigger SECURITY DEFINER. DGFiP-valid timestamped proof.

DGFiP traceability

The signed quote is cryptographically sealed

Once the quote is signed electronically (eIDAS Simple Electronic Signature, SES), Scell.io seals its PDF using the exact same cryptographic circuit as your invoices and fiscal closings: PAdES signature (PKCS#7, Scell.io server certificate), timestamping, then anchoring of the SHA-256 fingerprint onto the Bitcoin blockchain via OpenTimestamps. You get an independent proof of existence, verifiable offline, without depending on Scell.io.

PAdES signature + timestamping

The signed quote PDF is PAdES-sealed (PKCS#7) with the Scell.io server certificate and timestamped. The response's sealing object exposes is_sealed, pades_signed_at and signed_pdf_sha256 (the exact fingerprint anchored in Bitcoin).

Sealed PDF + SHA-256 fingerprint

Bitcoin OpenTimestamps anchoring

The fingerprint is submitted to OpenTimestamps then confirmed in a Bitcoin block. sealing.ots_status moves from pending to confirmed, with bitcoin_block_height and ots_proof_base64 (the offline-verifiable .ots receipt via ots verify). An enforceable proof of existence, independent of Scell.io.

Offline-verifiable proof

Note: this is an eIDAS Simple Electronic Signature (SES), PAdES-sealed and Bitcoin-anchored — not a Qualified Electronic Signature (QES) nor a qualified TSA timestamp.

Hébergé en FranceScaleway Paris

RGPDDonnées FR

Factur-X conformeDGFiP EN16931

eIDAS SESRègl. 910/2014

ISCA SHA-256Ledger immuable

TLS 1.3Chiffrement bout-à-bout

Frequently asked questions

Ready to automate your quote cycle?

Free sandbox. No credit card required. First quote in 15 minutes.

Start for free View SDKs