GetbeelDocs

VAT registers and settlements

The sales and purchase VAT registers, the monthly or quarterly VAT settlement (liquidazione) with its F24, and the LIPE file, prepared from the documents in Getbeel.

Getbeel builds the VAT registers (sales and purchases) of a month or quarter from the issued invoices, supplier invoices and autofatture it already has, computes the period's VAT settlement (liquidazione IVA) in the rows of the LIPE (VP2–VP14) and, from it, prepares the F24 and the LIPE file. These are the same pages as Taxes → VAT registers and Taxes → VAT settlements in the app.

Scope: taxes:read to read, taxes:write to save a settlement or prepare the LIPE (through Filings). Italian companies with VAT only: forfettari and minimi get 400 vat_not_applicable.

To check (da verificare)

Registers and settlements only count the documents in Getbeel. reliable is always false: Getbeel does not know deductibility (art. 19-bis.1), the pro-rata, documents kept elsewhere, VP10 payments or VP11 tax credits. Check with your accountant before paying or filing. Getbeel never signs, pays or sends anything.

First choose in the app (Taxes → Settings) whether the company settles VAT monthly or quarterly: until then the settlement answers 400 settings_missing, and a period in the wrong format (a month for a quarterly payer) answers 400 parameter_invalid.

VAT registers

curl "https://www.getbeel.com/api/v1/companies/me/vat-registers?period=2026-Q3" \
  -H "Authorization: Bearer $GETBEEL_API_KEY"

period is a month (2026-10) or a quarter (2026-Q3).

Sales register (art. 23 DPR 633/1972):

  • Invoices issued in Getbeel and accepted by SDI (delivered or not delivered), by document date. Taxable amount and VAT per rate and natura are the XML's DatiRiepilogo. A document whose submission SDI rejected with 00404 because it already accepted a copy also counts as issued: its row is flagged needs_review until support links the accepted submission (SDI lifecycle).
  • Credit notes (TD04, TD08) are negative.
  • Split payment (art. 17-ter): recorded but not due (vat_counted 0, flag split_payment).
  • Deferred VAT (EsigibilitaIVA D): due when the invoice is collected (art. 6, c. 5 DPR 633/1972) and, under IVA per cassa, one year after the operation at the latest (art. 32-bis DL 83/2012); the row counts in that period (deferred_vat_collected). A row that reaches the one-year limit unpaid is flagged needs_review: the limit does not apply to art. 6, c. 5 sales, and the e-invoice does not say which case it is.
  • Reverse-charge autofatture TD16–TD19 and TD28 (art. 17 DPR 633/1972; arts. 46–47 DL 331/1993): the VAT is due here and, as a rule, deducted on the purchase side, so they appear in both registers (flag reverse_charge).

Purchase register (art. 25 DPR 633/1972):

  • Supplier invoices as soon as the AI has read them, including those received through SDI. Those you have not reviewed yet count too, with the unreviewed flag on their row; totals.to_review counts the rows to check. Rejected documents never count.
  • Period: the period of receipt. An invoice received by the 15th of the month after the operation counts in the operation's period, never across years (art. 1, c. 1, DPR 100/1998). The receipt date is known for invoices received through SDI; for the others the document date is used (late_receipt marks invoices received later).
  • VAT charged by foreign suppliers is not Italian VAT: it counts 0 (foreign_vat); the autofattura carries it. A supplier whose country cannot be told (no country, a tax ID that is neither Italian nor prefixed by a known country) is not taken for Italian: its VAT counts 0, flag country_unknown.
  • Reverse-charge autofatture, as above.

Each row has breakdown (per rate and natura), taxable, vat, vat_counted (the VAT entering the settlement), counted, flags and adjustment. Each register's totals are in totals (also per rate, by_rate).

{
  "object": "vat_registers",
  "period": "2026-Q3",
  "start": "2026-07-01",
  "end": "2026-09-30",
  "currency": "EUR",
  "sales": {
    "rows": [
      {
        "key": "sales:issued_invoice:fe_3f2a…",
        "source": "issued_invoice",
        "document_id": "fe_3f2a…",
        "number": "42",
        "date": "2026-07-15",
        "received_date": null,
        "counterparty_name": "Rossi S.r.l.",
        "counterparty_vat": "IT01234567897",
        "tipo_documento": "TD01",
        "breakdown": [
          {
            "rate": "22.00",
            "natura": null,
            "taxable": "1000.00",
            "vat": "220.00"
          }
        ],
        "taxable": "1000.00",
        "vat": "220.00",
        "vat_counted": "220.00",
        "counted": true,
        "flags": [],
        "adjustment": null
      }
    ],
    "totals": {
      "documents": 1,
      "taxable": "1000.00",
      "vat": "220.00",
      "vat_counted": "220.00",
      "excluded": 0,
      "adjusted": 0,
      "by_rate": []
    }
  },
  "purchases": {
    "rows": [],
    "totals": {
      "documents": 0,
      "taxable": "0.00",
      "vat": "0.00",
      "vat_counted": "0.00",
      "excluded": 0,
      "adjusted": 0,
      "by_rate": []
    }
  },
  "missing": [
    {
      "source": "received_invoice",
      "id": "inv_…",
      "number": "A/17",
      "date": "2026-09-28",
      "name": "Fornitore S.p.A.",
      "reason": "processing"
    }
  ],
  "reliable": false,
  "note": "To check (da verificare): …"
}

missing lists the period's documents not in the registers yet: processing (the AI is still reading it; it joins on its own), no_vat_data (foreign-currency amounts without a euro value), pending_sdi (issued invoice still waiting for SDI), autofattura_pending, autofattura_unreadable, autofattura_missing (a foreign purchase whose TD17/TD18/TD19 was not sent to SDI yet: due by the 15th of the next month; only purchases received since the automatic proposals exist, and not when any TD17/TD18/TD19 sent for the same supplier has the same invoice number or a close amount in the same or an adjacent month).

Excluding or correcting a row

Getbeel cannot know whether a purchase is only partly deductible (company cars, phones, pro-rata) or whether you deduct it later. In the app (Taxes → VAT registers → Edit) you can exclude a row from the settlement or set the VAT that counts, always with a reason. The row shows adjustment and vat_counted changes accordingly. For a purchase with non-deductible VAT set the VAT to 0 rather than excluding it: the LIPE instructions count non-deductible purchases among the operazioni passive (VP3). Exclude only documents that do not belong to the period or the company. A deferred-VAT row not due yet cannot be changed: change it in the period it is due.

The same correction through the API, on the row's key (register:source:document_id). It needs taxes:write and a live key:

curl -X PUT "https://www.getbeel.com/api/v1/companies/me/vat-adjustments/purchases:received_invoice:$INVOICE_ID" \
  -H "Authorization: Bearer $GETBEEL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "action": "adjust", "vat_amount": "8.80", "reason": "Auto aziendale, IVA detraibile al 40%" }'

action is exclude or adjust (with vat_amount, the VAT that counts); reason is required. DELETE /companies/me/vat-adjustments/{key} removes the correction. A row that is not this company's answers 404, a source in the wrong register 400. A liquidazione already saved keeps its numbers until you prepare it again. MCP tools: set_vat_adjustment, remove_vat_adjustment.

Export

In the app each register downloads as CSV, Excel (XLSX) or PDF, for you or your accountant.

VAT settlement (liquidazione)

curl "https://www.getbeel.com/api/v1/companies/me/vat-settlements?period=2026-10" \
  -H "Authorization: Bearer $GETBEEL_API_KEY"

period is a month for monthly payers, a quarter for quarterly payers. The settlement is computed now from the registers, in the LIPE rows (lipe):

FieldLIPE rowWhat
operations_active / operations_passiveVP2 / VP3Taxable sales and purchases (without art. 15 exclusions, N1)
vat_due / vat_deductedVP4 / VP5VAT due and VAT deducted (the registers' vat_counted)
vat_balance_debit / vat_balance_creditVP6Balance owed or in credit
previous_debtVP7Previous period's debt up to €100, not paid
previous_creditVP8Previous period's credit (not in the first period of the year)
annual_creditVP9Previous year's credit used in this settlement
car_payments / tax_creditsVP10/VP11Not known to Getbeel: always 0.00
interestVP121% interest for quarterly payers (Q1–Q3)
advance, advance_methodVP13VAT advance (acconto), December or Q4 only
amount_due / amount_creditVP14Amount to pay or in credit (null for Q4 of quarterly payers)

The rules Getbeel applies:

  • Minimum payment: up to €100 is not paid and moves to the next period (carried_debt, note below_minimum_carried), but it must be paid by 16 December (monthly) or 16 November (quarterly) anyway: November, December, Q3 and Q4 VAT is never carried (art. 1, c. 4, DPR 100/1998; art. 7 DPR 542/1999, as amended by D.Lgs. 1/2024).
  • Credit: a negative result moves to the next period (carried_credit, the next settlement's VP8) within the same year.
  • Previous period: VP7 and VP8 come from the previous period of the same year: its saved settlement or, if it is not saved, the one Getbeel computes from its registers, back through the year. previous says which (source: saved, computed or input). Only when Getbeel has no earlier data that year do you pass them (previous_debt, previous_credit); the note previous_missing says so. Amounts you pass replace the computed ones.
  • Quarterly interest: 1% on the amount due for Q1, Q2 and Q3 (art. 7 DPR 542/1999), note interest_added.
  • Q4 of quarterly payers: paid with the annual balance (code 6099, by 16 March, plus 1%): amount_to_pay is 0.00 and the note is paid_with_annual_balance.
  • Advance (art. 6 L. 405/1990): in December or Q4 give the advance paid (advance, at least €103.29) and its method (advance_method: 1 historical, 2 forecast, 3 analytical, 4 special sectors).

amount_to_pay is what the F24 pays now; tax_code and due_date are the tax code (6001–6012 for months, 6031–6033 for quarters) and the deadline. saved is the saved version, with outdated: true when the registers changed since.

{
  "object": "vat_settlement",
  "period": "2026-10",
  "periodicity": "monthly",
  "start": "2026-10-01",
  "end": "2026-10-31",
  "currency": "EUR",
  "lipe": {
    "operations_active": "12000.00",
    "operations_passive": "4000.00",
    "vat_due": "2640.00",
    "vat_deducted": "880.00",
    "vat_balance_debit": "1760.00",
    "vat_balance_credit": "0.00",
    "previous_debt": "0.00",
    "previous_credit": "300.00",
    "annual_credit": "0.00",
    "car_payments": "0.00",
    "tax_credits": "0.00",
    "interest": "0.00",
    "advance": "0.00",
    "advance_method": null,
    "amount_due": "1460.00",
    "amount_credit": "0.00"
  },
  "result": "1460.00",
  "amount_to_pay": "1460.00",
  "carried_debt": "0.00",
  "carried_credit": "0.00",
  "tax_code": "6010",
  "due_date": "2026-11-16",
  "notes": [],
  "inputs": {
    "previous_credit": null,
    "previous_debt": null,
    "annual_credit_used": null,
    "advance": null,
    "advance_method": null
  },
  "registers": {
    "sales": { "documents": 14, "…": "…" },
    "purchases": { "documents": 6, "…": "…" },
    "missing": 0
  },
  "saved": null,
  "reliable": false,
  "note": "To check (da verificare): …"
}

Saving the settlement and preparing the F24

Once the period is over, save the settlement with POST /v1/filings and type: vat_payment:

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": "vat_payment", "period": "2026-10" }'

Optional: previous_credit, previous_debt (to replace the computed carry-over, or when Getbeel has no earlier data that year), annual_credit_used, advance and advance_method (December or Q4). The response is the filing with its F24 line and details.settlement (the LIPE rows). When there is nothing to pay (a credit, up to €100 carried, Q4 of quarterly payers) the settlement is still saved, an F24 prepared earlier for the period and not paid is deleted, and the answer is 422 nothing_due. Until the F24 is paid you can recompute it; afterwards it answers 409 filing_completed, and so it does once the LIPE of the quarter is filed (a change then goes into a corrective LIPE). previous_debt (VP7) is at most 100.00.

The LIPE

The Comunicazione liquidazioni periodiche IVA (art. 21-bis DL 78/2010) is sent every quarter: by 31 May, 30 September, 30 November and the end of February of the next year. Getbeel prepares the XML file from the quarter's saved settlements (its three months, or the quarter):

curl -X POST https://www.getbeel.com/api/v1/filings \
  -H "Authorization: Bearer $GETBEEL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "type": "lipe", "period": "2026-Q3", "declarant_fiscal_code": "RSSMRA80A01F205X", "declarant_role": 1 }'
  • Companies name who signs: declarant_fiscal_code (16-character codice fiscale) and declarant_role (codice carica, 1 = legal representative).
  • A settlement of the quarter not saved yet: 400 settlements_missing; an invalid company codice fiscale or partita IVA: fiscal_code_invalid, vat_number_invalid.
  • The file follows the Agenzia's technical specifications (supply IVP18): one module per month or one for the quarter; Q4 of quarterly payers is quarter 5, without interest or VP14. File name: IT{codice fiscale}_LI_{5 characters}.xml, unique for each file. The specifications want the codice fiscale of whoever transmits it: Getbeel uses the company's, since you upload it from the company's own area; an accountant who sends it renames it with their own.

GET /filings/{id}/file returns the XML (application/xml). You then check it with the Agenzia's control software, sign it and upload it in "Fatture e corrispettivi" (or hand it to your accountant). When you upload the receipt with POST /filings/{id}/receipt the LIPE becomes filed (webhook filing.filed).

SDKs, CLI and MCP

const registers = await getbeel.taxes.vatRegisters('2026-Q3');
const settlement = await getbeel.taxes.vatSettlement('2026-10');
registers = client.taxes.vat_registers("2026-Q3")
settlement = client.taxes.vat_settlement("2026-10")
getbeel taxes registers --period 2026-Q3
getbeel taxes settlement --period 2026-10
getbeel filings prepare --type vat_payment --period 2026-10

With an AI assistant: get_vat_registers, get_vat_settlement and prepare_filing (types vat_payment and lipe). The assistant shows the settlement and asks before saving it. See MCP server.

Sources

The rules above follow the official texts, read on 2 November 2026. Check them with your accountant: Getbeel prepares, you file.

  • LIPE: technical specifications SpecificheIVP18_2024.pdf, XSD Specifiche IVP2018_SchemaIV18.zip (version 1.0) and the instructions IVA period_2024.pdf, approved by provvedimento of the Agenzia delle Entrate prot. 125654 of 14 March 2024, on agenziaentrate.gov.it. The XSD and the AdE control software still call VP10 VersamentiAutoUE; Getbeel never fills it.
  • Monthly settlement and the €100 threshold: art. 1 DPR 100/1998 (as amended by D.Lgs. 1/2024).
  • Quarterly settlement and the 1% interest: art. 7 DPR 542/1999. The 1% is "calcolati sugli importi da versare … relativamente alla liquidazione del trimestre" (LIPE instructions, VP12): Getbeel applies it to the quarter's own amount (VP6 − VP8 − VP9). A debt carried in VP7 is left out because it already includes its interest: the €100 threshold is checked "comprensivo degli interessi dovuti dai contribuenti trimestrali" (Istruzioni IVA 2026, quadro VH).
  • Advance: art. 6 L. 405/1990 (due by 27 December); the €103.29 minimum is in the LIPE instructions and specifications.
  • LIPE deadlines: art. 21-bis DL 78/2010.
  • Registers and deduction: artt. 19, 23 and 25 DPR 633/1972 (artt. 19 and 25 as amended by D.Lgs. 148/2026 from 12 August 2026: deduction at the latest with the return of the second following year); split payment art. 17-ter; deferred VAT art. 6, c. 5 and art. 32-bis DL 83/2012.
  • From 1 January 2027 most of these articles move to the Testo unico IVA (D.Lgs. 10/2026) and the Testo unico adempimenti (D.Lgs. 141/2026); DPR 100/1998 and DPR 542/1999 stay.

Not from an official text (to confirm with your accountant): leaving amounts excluded under art. 15 (natura N1) out of VP2, and counting a deferred-VAT sale in VP2 of the period it was issued only.

On this page