FAQ

It is a structured XML document. Italian invoices use SdI; a PDF alone is not the electronic invoice.

It validates the file, delivers it where possible and returns notifications. Keep receipts with the document.

No. XML is the structured document; the courtesy PDF makes it easier to read and share.

Business name, tax identifiers, address, regime and delivery details. Complete the company profile before issuing.

It identifies the delivery channel, not your profession. Use the code shown in settings.

In the Italian agency’s electronic-address registration service. Fiscal links it beside the recipient code.

Yes. Italian PEC delivery uses 0000000 plus PECDestinatario. Register the Fiscal channel to receive invoices in the portal.

Usually 0000000. Include the required tax details and provide a readable copy.

Do not assume international delivery. Italian reporting and the copy supplied to the customer are separate.

No. An Italian public-office code has six characters; private channels usually seven. Select the right buyer type.

Yes. A draft is not a transmission. Check number, date, buyer and amounts before sending.

Open the invoice row or details. Submission, delivery, non-delivery and rejection are different states.

No. Read the reason, fix the cause and follow the applicable resubmission procedure.

No. A non-delivered invoice may have passed SdI processing; rejection indicates a failed check.

Not to erase its fiscal effects. Use the appropriate correction procedure and retain the original.

Use the original document’s correction action, provide the reason and details, then verify before sending.

TD01 - invoice. Fiscal displays codes alongside their descriptions.

TD04 - credit note. It is a separate document linked to an invoice correction.

Fiscal separates counters by company, series, year and environment. A new year starts at the series initial value.

Yes, with the required settings permission. Controls prevent reusing already allocated numbers.

Yes. Fiscal derives the series from the authorized API caller while retaining the company and separate counters.

Environments are separate. Sandbox uses test series and must not transmit to the live channel.

No. Configure the correct regime; VAT, exemption codes and wording depend on the transaction and fiscal profile.

No. Where required, include the appropriate tax-nature code and explanatory wording.

Not solely from the total. Check transaction nature, qualifying amounts above €77.47 and possible exemptions.

The usual charge for a qualifying invoice is €2. Customer charging and tax payment are separate matters.

Document calculation is not payment to the tax agency. Check the agency lists and required payment.

Do not enable it merely because of registration. Fiscal separates surcharge choice from the pension profile.

The GROSS flow uses the paid total and splits applicable components. Check the summary before payment.

No. Buyer type, transaction, seller and regime also matter. Unconfigured cases are blocked.

No. Languages and profiles do not prove an operational national channel. Issuance requires active rules and connection.

No. Viewing files in the portal does not prove that compliant preservation has completed.

Yes, enrolment in the Italian tax agency service is required. Fiscal links the official settings path.

Verify that the agreement and process cover both issued and received invoices. A UI checkbox is not evidence.

Use PDF and XML actions in the invoice row and details, subject to permissions and file availability.

Configure the channel and register delivery with the agency. Keep received-document history in your workspace.

No. Historical imports must not automatically retransmit previously issued documents to SdI.

No. Without original XML it remains history or an attachment, not a reconstructed electronic invoice.

Yes. Authorized software sends sale data; Fiscal reuses the company profile without copying it into the cart.

Yes. Company context comes from the authorized identity, not an arbitrary browser-supplied identifier.

The same operation uses an idempotency key. Reuse it on retry to avoid duplicate documents and usage.

They update backend results from channel notifications. Clicking Send alone does not prove delivery.

No. Commercial quota covers the plan’s fiscal documents, not quotes or delivery notes.

No. Downloads, email, APIs, callbacks and retries do not add usage for the same document.

Create or sign into your account, complete the company and open Membership. Checkout uses configured annual pricing.

Only after successful payment verified by webhook. Returning from checkout is not sufficient.

No. Stripe handles card data. Saving a payment method for reuse requires explicit choice.

Payment may require strong authentication. Complete the bank verification without sharing codes with support.

Cancelled payment does not credit extras. History and account status remain separate from checkout.

Yes. Invoices for buying Fiscal and documents issued for your business have separate contexts.

Yes. Responsive views adapt tables and controls while retaining permissions and operation checks.

No. Reject in the banner or change footer preferences. Access and purchases do not depend on analytics consent.

No. A schema change is insufficient: applicable rules, dates and channels are required. Fiscal separates roadmap from live flows.

Contact info@avsof.com or Elena on +39 049 674 7089. Explain the issue and redact unnecessary data in attachments.