GetbeelDocs

Filings (F24, LIPE, VAT return)

Prepare the F24 for stamp duty, withholdings or VAT, the LIPE file or the annual VAT return data, with the values to copy, the link to the Agenzia delle Entrate page and email drafts, then record the receipt.

A filing is a payment Getbeel prepares for a tax deadline: the amount, the F24 lines, a reminder PDF and the next steps. You pay it yourself, in F24 web or from your bank; then you upload the receipt (quietanza) and the filing is paid.

Scope: taxes:read to read, taxes:write to prepare and upload the receipt.

Live keys only

Tax deadlines are real data: there is no sandbox. Test keys can read; preparing and uploading need a live key (403 livemode_required). Preparing is free; a filing is charged once, when it is paid or filed (402 insufficient_balance when the balance does not cover it).

What Getbeel prepares (v1)

typePeriodAmount
bolloQuarter (2026-Q3)Computed by Getbeel: €2 per issued invoice with bollo virtuale, or without it but with bollo due (below)
withholdingsMonth (2026-10)The sum of the withholdings on fees paid that month (codice tributo 1040), or amount if you do not record them in Getbeel
vat_paymentMonth or quarter, as the company settles VATThe VAT settlement computed from the VAT registers and saved (codici tributo 6001–6012, 6031–6033)
lipeQuarter (2026-Q3)No payment: the XML file of the Comunicazione liquidazioni periodiche IVA, from the quarter's saved settlements, checked against the official XSD
vat_returnYear (2026), once it is overThe data sheet of the annual VAT return (Dichiarazione IVA): amount is the balance to pay (VX1, codice tributo 6099). Not the file to send
redditi_pfYear (2026), once it is overIndividuals only: the data sheet of the Redditi PF return from the year's tax estimate: amount is the saldo of the year. Not the file to send

For stamp duty Getbeel follows the Agenzia delle Entrate's rules for the quarter's lists:

  • List A: invoices sent with bollo virtuale.
  • List B: invoices without bollo virtuale whose exempt or non-taxable lines (Natura N2.1, N2.2, N3.5, N3.6, N4) add up to more than €77.47: stamp duty is due on the part not subject to VAT. The Agenzia charges them anyway: Getbeel counts them and flags them (invoices_without_bollo_flag, needs_review). If one does not need it, remove it from the list in the "Fatture e corrispettivi" portal.
  • The quarter is the one of the SDI delivery. Invoices still waiting for SDI are in pending_invoices and not counted.
  • Small amounts: Q1 stamp duty below €5,000 may be paid by 30 September, and Q1 + Q2 below €5,000 by 30 November (deferral). Getbeel keeps the normal deadline and only tells you.

Invoices issued outside Getbeel, paper invoices and self-invoices are not counted.

Prepare an F24

curl -X POST https://www.getbeel.com/api/v1/filings \
  -H "Authorization: Bearer $GETBEEL_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{ "type": "bollo", "period": "2026-Q3" }'
curl -X POST https://www.getbeel.com/api/v1/filings \
  -H "Authorization: Bearer $GETBEEL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "type": "withholdings", "period": "2026-10" }'

For withholdings Getbeel adds up the fees recorded in /withholdings with paid_on in the month (the ritenuta is made when the fee is paid, art. 25 DPR 600/1973) and lists them in details.withholdings; once you upload the receipt those fees are remitted and can no longer change. If you do not record them in Getbeel, send amount with the total withheld. With no fees and no amount the answer is 422 nothing_due.

201 with the filing in status ready (webhook filing.ready). Calling again for the same period recomputes it until it is paid; then it answers 409 filing_completed. Stamp duty is prepared only once the quarter is over (period_not_closed) and when something is due (nothing_due).

vat_payment and lipe are prepared once the period is over too. vat_payment saves the settlement even when there is nothing to pay (a credit, up to €100 carried, Q4 of quarterly payers) and then answers 422 nothing_due; lipe answers 400 settlements_missing until every settlement of the quarter is saved, and companies send declarant_fiscal_code and declarant_role. The VAT inputs and the rules are in VAT registers and settlements.

LIPE: the schema check

When a lipe is prepared, Getbeel validates the XML against the official IVP18 schema of the Agenzia delle Entrate ("Specifiche IVP2018_SchemaIV18.zip", schema version 1.0, from the technical specifications page; the provvedimento of 14 March 2024 left it unchanged). The result is in checks.xsd. A file that fails is never saved: the answer is 500 file_invalid (a Getbeel bug, tell us).

checks.ade_control_software is always not_run. The Agenzia's control software ("Software di controllo Liquidazioni periodiche Iva" for the LIPE, the "procedura di controllo" for the VAT return) is a Java desktop program, started with Java Web Start, that updates itself at every launch. It has no documented command line or batch mode, and the Agenzia publishes no web service that checks a file without the taxpayer's login, nor terms that allow running it as a service for others. So Getbeel cannot honestly run it for you: it checks what it can (the schema for the LIPE; the arithmetic rules of the specifications for the VAT return, below), and the steps tell you to run the control software before sending.

VAT return (Dichiarazione IVA)

curl -X POST https://www.getbeel.com/api/v1/filings \
  -H "Authorization: Bearer $GETBEEL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "type": "vat_return", "period": "2026", "previous_year_credit": "1200.00" }'

Getbeel adds up the VAT registers of every settlement period of the year (12 months or 4 quarters), the settlements you saved and the VAT F24s marked paid, and returns the rows of the return in details.vat_return, in whole euros as filed, with the field code of the technical specifications (VE023001 = quadro VE, row 23, field 1). previous_year_credit is the credit of last year's return still available (VX5 minus what you already offset): it goes in VL25. Download the sheet with GET /filings/{id}/file?format=csv|xlsx|json (CSV by default).

It is not the file to send. The telematic return is a fixed-length record file (records A, B, D, Z of 1,900 characters) with many parts Getbeel does not know (front page, VA, VC, VO, VT, signatures). Fill it with the Agenzia's free "Software di compilazione Iva" or your accountant's software, check it with the control procedure and send it from your Agenzia area or through an intermediary, between 1 February and 30 April (art. 8 DPR 322/1998). Pay the balance by 16 March with codice tributo 6099.

QuadroRows Getbeel fillsFrom
VEVE20–VE23 by rate (4, 5, 10, 22%), VE24–VE26, VE30–VE35 by Natura, VE37 (VAT due later), VE38 (split payment), VE39, VE50 (volume d'affari)Sales register
VFVF2, VF3, VF11, VF13 by rate, VF18, VF25–VF27, VF71 (VAT deducted)Purchase register and self-invoices
VJVJ1 (TD28), VJ3 (TD17, TD19), VJ9 (TD18), VJ19Self-invoices (reverse charge)
VLVL1–VL4, VL23, VL25, VL30 (fields 1–3), VL32, VL33, VL36, VL38, VL39The above, saved settlements, paid F24s
VXVX1 (to pay, not below €10.33), VX2 (credit)VL38, VL39

The column 2 of VE20–VE23 and VF2–VF13 is the rate times column 1, as the specifications require; the difference with the VAT in the registers goes in VE25 and VF26. details.vat_return.checks lists the specifications' controls Getbeel runs on the sheet (they hold by construction; a failure is a Getbeel bug).

Once the return's receipt is uploaded it is filed, and that year's vat_payment and lipe answer 409 filing_completed: a change after filing is a corrective return, for your accountant. Sales whose VAT you adjusted in the registers count with the adjusted VAT, as in the settlements (the difference shows in VE25). Domestic reverse charge (TD16) VAT is in the VJ19 total and the balance; you put it in its row.

details.vat_return.issues lists what to check before copying: documents missing from the registers, sales or purchases without a single row (Natura N2.2, N5, N7, purchases without VAT), domestic reverse charge (TD16) whose VJ row depends on the case, foreign suppliers without a self-invoice, non-deductible VAT (it goes in VF21/VF22, Getbeel keeps it in VF1–VF13), settlements not saved, the VAT advance paid outside Getbeel.

Which model. As of November 2026 the model for tax year 2026 ("IVA 2027") is not published, not even as a draft. The rows follow the latest one, "IVA 2026, periodo d'imposta 2025", approved by provvedimento prot. 51732 of 15 January 2026 (model and instructions), with the technical specifications of provvedimento prot. 50925 of 11 February 2026. details.vat_return.model says which one; the sheet will move to the 2027 model when it is published.

Not from an official source (Getbeel's reading, to check with your accountant): which row each Natura code goes to (N2.1 → VE34, N3.1–N3.4 → VE30 fields 2–5, N3.5 → VE31, N3.6 → VE32, N4 → VE33, N6.1–N6.8 → VE35 fields 2–9, N6.9 → VE35 field 1), which VJ row each self-invoice type goes to, and split-payment sales only in VE38 (read from the VE50 formula, which would otherwise count them twice). The instructions never name the FatturaPA codes.

Redditi PF (individuals)

For a persona fisica whose tax estimate of the year is forfettario, irpef or minimi:

curl -X POST https://getbeel.com/api/v1/filings \
  -H "Authorization: Bearer $GETBEEL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "type": "redditi_pf", "period": "2025" }'

details.redditi_pf.lines places the estimate on the Modello Redditi PF 2026 lines (tax year 2025), as printed in the AdE instructions (Fascicoli 1–3):

RegimeLines
forfettarioLM22 col. 3 revenue, LM34 col. 3 income, LM35 col. 2 contributions, LM38 taxable, LM39 substitute tax
minimiLM2, LM5 col. 5, LM6, LM7 col. 2, LM49, LM9 col. 3, LM10, LM11 (5%)
irpefRE21 col. 5 income (a business uses quadro RG: no rigo), RN1 col. 5, RN3, RN4, RN5, RN7 col. 4, RN26, RN33 col. 4, RN34, RV2 col. 2, RV10 col. 2
INPSRR5 col. 15 (gestione separata); artigiani and commercianti split it over RR2/RR3, so rigo is null
  • rigo: null means the line was not given as one rigo: the amount is shown with its meaning.
  • payments lists the saldo and acconti with their F24 codes; amount is the saldo of the year.
  • It is an estimate: other income, family and deductible expenses are not in Getbeel. GET /filings/{id}/file?format=csv|json downloads the sheet.
  • A company gets 400 redditi_pf_not_applicable.
  • It is completed as filed with the AdE receipt or the protocol number (charged once, see Pricing).

Which specification each file follows

Every prepared filing keeps the official specification its file follows, in file_spec (also in the Getbeel-File-Spec header of GET /v1/filings/{id}/file, and in MCP get_filing_file):

file_spec.idFileOfficial documentOfficial format
lipe:IVP18LIPE XMLSpecifiche tecniche and XSD IVP18 (Versione 1.0), provv. AdE prot. 125654 of 14 March 2024yes
vat_return:IVA2026VAT return data sheetModel IVA 2026 (tax year 2025), provv. AdE prot. 51732 of 15 January 2026no: the rows to copy
redditi_pf:PF2026Redditi PF data sheetModel Redditi PF 2026 (tax year 2025), provv. AdE prot. 72078 of 27 February 2026no: the lines to copy
f24:F24-2013F24 reminder (bollo, withholdings, VAT)Model "MOD. F24 – 2013 EURO", provv. AdE of 19 June 2013no: a reminder

file_spec also has the name, version, the act that approved it, its official page (source_url) other_tax_year (a return on the model of another tax year: check the rows against that year's model) and provisional (that model is the earlier one because the new one is not published yet: check it when it is). The id is stored when the filing is prepared; a file is only generated on that specification, never on another version: when Getbeel moves to a new one it keeps generating the old one for the filings that use it, and a specification it no longer generates answers 409 file_spec_outdated. A filing skipped before it was prepared has no file: file_spec is null and the file answers 409 filing_file_missing.

Next steps

GET /filings/{id} returns f24_lines (Erario section: codice tributo, reference month and year, amount) and next_steps:

FieldWhat
file_urlThe F24 reminder PDF (GET /filings/{id}/file): the values to enter, not the ministerial form; for a lipe, the XML file; for a vat_return, the data sheet
deep_linkThe Agenzia page to open: "Fatture e corrispettivi" for stamp duty, the reserved area (F24 web) for withholdings. You sign in with SPID, CIE or CNS
copy_valuesThe values to copy one by one: codice fiscale, codice tributo, year, amount, total
draftsEmail drafts (in Italian) to the bank or the commercialista. Getbeel never sends them: you review and send
stepsThe steps, in order

Record the receipt

After paying, upload the receipt (PDF, PNG or JPEG, up to 10 MB):

curl -X POST https://www.getbeel.com/api/v1/filings/$FILING_ID/receipt \
  -H "Authorization: Bearer $GETBEEL_API_KEY" \
  -F "file=@quietanza-f24.pdf"

The filing becomes paid; a LIPE or a VAT return, with the Agenzia's receipt, becomes filed (webhook filing.filed). The receipt is stored, not read: make sure you upload the right one.

No CBI F24 file yet

Companies with corporate banking can import F24 payments as a CBI file. Getbeel does not produce it: the CBI standard "Pagamenti F24" (CBI-F24-001) is distributed only to users registered on cbi-org.eu, under the CBI IPR policy, and the only public copy found is an outdated third-party mirror (version 6.15 of 2015). The file also needs your company's own SIA code and an F24 service agreed with your bank. Until Getbeel builds it from the version CBI distributes, use the values to copy, the reminder PDF or the email draft to your bank.

Review with the commercialista

Invite your commercialista (POST /v1/advisors or Taxes → Your commercialista): from then on every prepared filing starts in needs_review. The commercialista opens it in the app and approves it (approved, with who and when), sends it back (changes_requested, with a comment) or marks it not to be done (skipped, with the reason). Without a commercialista a prepared filing is ready.

StatusMeaning
readyPrepared, no review asked
needs_reviewWaiting for the commercialista
changes_requestedSent back: see the history
approvedVisto bueno: approved_at, approved_by
skippedNot to be done: skip_reason; never prepared automatically, never charged
filedA LIPE or VAT return sent: a receipt or filed_reference (protocol number)
paidAn F24 paid: the receipt
  • POST /v1/filings/{id}/status with status approved, skipped, needs_review (back to review, or reopen a skip) or filed (with reference). An API key acts as the team: changes_requested is the commercialista's, in the app.
  • POST /v1/filings/skip with type, period and reason for a deadline never prepared.
  • GET /v1/filings/{id}/events is the history (comments and status changes, who and why); POST adds a comment.
  • With require the commercialista's approval on (tax settings require_accountant_approval, set by an owner), only the commercialista approves, and a receipt or protocol number waits for the approval (409 approval_required).

Every step also shows up in the app's notifications, and by email:

  • a filing waiting for review (when it is prepared, or when you switch on the commercialista's approval) → the commercialista;
  • changes requested, with the whole comment → the owners and whoever prepared the filing;
  • approved by the commercialista → the owners;
  • with the commercialista's approval required, a filing due within 5 working days and still not approved (to review, or sent back for changes) → the commercialista and the owners, once per filing and due date (again only if a proroga moves the date).

Each email is in the recipient's language, links to the filing, and never goes to the person who made the change. An approval by a team member and a skip are in the app only.

Webhooks: filing.needs_review, filing.changes_requested, filing.approved, filing.skipped, filing.approval_due, filing.filed. MCP: get_filing, set_filing_status, skip_filing, comment_filing, list_filing_events.

With an AI assistant (MCP)

get_tax_calendar, prepare_filing, get_filing_next_steps, record_filing_receipt, get_vat_position, get_vat_registers, get_vat_settlement and ask_accountant_question (the company's own figures for a tax question, the official sources, and whether a commercialista is needed: Getbeel does not write the answer, the assistant does, from that data). The assistant asks before preparing an F24 or recording a receipt, and never pays or sends anything. See MCP server.

On this page