Supported Use Cases
This page collects the main scenarios in which you can integrate the Sibill APIs into your management system, ERP, e-commerce or SaaS product.
โ What you can do with the Sibill APIsโ
Below you will find the main use cases organised by functional area.
๐งพ INVOICE MANAGEMENT
1. Automatically send electronic invoicesโ
๐ Use caseโ
Do you generate many invoices every month and want to avoid manual operations from the WebApp?
You can create and send electronic invoices directly from your system, using JSON or XML compatible with electronic invoicing.
๐ก Possible automationsโ
- Automatic invoice generation from your database
- Direct submission to the SDI (Sistema di Interscambio)
- Creation of drafts for internal review before submission
- Integration with e-commerce flows or recurring subscriptions
2. Track the status of invoices sent to the SDIโ
๐ Use caseโ
Do you want to know if an invoice is:
- Delivered
- Rejected
- Pending
- Discarded
๐ก Via API you canโ
- Receive webhook notifications on every status change
- Display the status in real time in your UI
- Sync ERP or CRM with the official SDI status
- Trigger automated workflows (e.g. reissue in case of error)
3. Retrieve and display invoices and related documentsโ
๐ Use caseโ
Are you building a management system or a customer portal with a document list, filters and advanced search?
๐ก Via API you canโ
- List all documents (issued and received)
- Filter by:
creation_datedelivery_datestatus
- Retrieve full details:
created_atcreation_datedelivery_datedelivery_statusdirectionflowsformatgross_amountvat_amountnumberstatusupdated_at
In addition to invoices, you can also access:
- Credit notes
- Debit notes
- Self-invoices
- Delivery notes (DDT)
- Quotes
Every document available in the WebApp is accessible via API.
4. Link invoices and payments for automatic reconciliationโ
๐ Use caseโ
Do you receive automatic payments (e.g. bank transfers, Stripe, PayPal) and want to avoid manual checks?
๐ก Via API you canโ
- Insert a
reconciliation_identifierat the time of issuance - Automatically associate the payment when it arrives
- Mark the invoice as paid in your system
- Build real-time reconciliation dashboards
๐ฆ ACCOUNTS & TRANSACTIONS
5. View company bank accounts and balancesโ
๐ Use caseโ
Do you want to know which account received a payment or show users an up-to-date balance?
๐ก Via API you canโ
- Retrieve all bank accounts linked to a company
- View details and updated balances
- Feed financial dashboards
- Build automated reports for CFOs or accounting teams
6. Retrieve transactions from a specific accountโ
๐ Use caseโ
Do you need to verify whether an invoice has been paid and update your system?
๐ก Via API you canโ
- Get all bank transactions for an account
- Access details such as:
dateamountdescription
- Automatically link transactions to invoices
- Implement custom matching logic
๐๏ธ FLOWS
7. Retrieve due dates for unpaid invoicesโ
๐ Use caseโ
Do you want to know which invoices are open and when they are due in order to:
- Send automated reminders
- Update the CRM
- Generate internal tasks
๐ก Via API you canโ
- Retrieve the due dates of open invoices
- Access data such as:
amountcreated_atexpected_payment_datepayment_statuspayment_methodpayment_date
This allows you to build fully automated follow-up systems.
๐ RECONCILIATIONS
8. Export reconciliations of documents and transactionsโ
๐ Use caseโ
Do you perform reconciliation both in Sibill and in your accounting software and want to avoid duplications?
๐ก Via API you canโ
- Retrieve the list of reconciliations per company
- Associate documents and flows with their related transactions
- Export data to your accounting software
- Reduce errors and manual work
๐ Typical integration
A complete integration can include:
- Automatic invoice creation
- Submission to the SDI
- Receiving webhooks for status updates
- Retrieving bank transactions
- Automatic reconciliation
- Dashboard and CRM updates
In practice: you automate the entire active cycle, from issuance to reconciliation.
If you are designing a complex integration (ERP, multi-tenant SaaS, marketplace platforms), the recommendation is to structure from the start:
- Idempotent webhook handling
- Automatic retries
- Audit logs
- Incremental synchronisation via update dates