Connecting Fatture in Cloud to your software or online shop

What usually gets retyped

The online shop sells, and at the end of the day someone opens Fatture in Cloud and rebuilds the invoice from the order. A technician closes a job, and the office types the hours and parts again. The accountant asks which invoices have been paid, and someone has to compare two screens.

This data already exists somewhere. The connection saves typing it again.

What can be connected

Fatture in Cloud has an official REST API with OAuth access and webhooks. These are the connections needed most:

• from an order or job to the invoice, with customer, lines and VAT already filled in;
• customers, which stay the same in both programs, so there are no two different records;
• payments: when an invoice shows as paid, your software knows and stops sending reminders;
• products, with codes and prices;
• invoice PDFs, which open from your software without going into another program.

Webhooks tell your software when a document changes, with no need to keep asking. Webhook subscriptions expire, so they have to be renewed by an automatic job: it is one of those details that make connections stop after a few months.

Decisions to make first

Who is in charge of customers. If a customer changes address, where is it corrected? Decide it once and write it down.

How exceptions are handled. An order with a return, a hand-made discount, a credit note: for each, decide what the software does and what a person does. The connection handles normal cases, and odd ones go into a list to check.

Which VAT, which account. VAT codes and payment methods have different names in the two programs: you need a matching table, made together with whoever does the accounts.

How I work

1. We look at a real order or job, from when it starts to the invoice. The analysis is free.
2. I test the connection on a trial account, with fake invoices.
3. It starts with a draft to check, and every step stays logged.
4. If something stops, an email goes out, and on restart what was left behind is recovered.

I have worked with Fatture in Cloud before. If you use another program, or want to receive invoices directly from SDI, see e-invoices in your software. For integrations in general there is the Integrations and automation page.

Frequently asked questions

Do I need a different Fatture in Cloud plan?

It depends on what you want to do. API access and resource limits depend on your plan: I check first, so you don't find a limit once work has started.

Are invoices sent to SDI automatically?

They can be, if you want. It is often better to stop at the draft: the software prepares it, and a person checks and sends it, at least for the first months.

How many invoices can the connection handle?

The APIs allow 1,000 requests an hour and 40,000 a month per company and application, and 300 every five minutes overall. That is enough for a small company, and more can be requested.

Do I have to give you my password?

No. The connection goes through OAuth: you authorise the application from your account and can revoke it whenever you like.

Read more

• The service: Integrations and automation
• More pages like this: Connections, automation and AI