The calendar repeats for many Italian finance teams: during the first days of the month, supplier invoices related to the prior period must be posted, discrepancies resolved, and reliable data prepared for VAT, reporting, and consolidation. The volume is not always higher; the available processing window is simply much shorter.
Calling this “the accounting close by the 15th” mixes two separate concepts. The month-end close and Italy’s 15th-day VAT rule serve different purposes, even though both can affect the same AP team at the same time.
Month-end close, financial close, and fast close
Month-end close and financial close are the standard terms for the process. “Booking close” is not normally used to describe the full set of closing activities.
A close makes the period complete and consistent through postings, reconciliations, cut-off checks, accruals, deferrals, unbilled liabilities, controls, and reporting. A fast close shortens the cycle without lowering data quality by bringing work forward and standardizing workflows.
Listed and multi-entity companies often feel more pressure because reliable figures feed consolidation, governance, and periodic financial information. This does not mean that every listed company has a statutory monthly close deadline on the 15th: “day X” is often an internal milestone in the group close calendar.
What Italy’s 15th-day VAT rule actually says
The relevant rule is in Article 1(1) of Presidential Decree 100/1998. In summary, where the applicable requirements are met, input VAT on purchase documents received and recorded by the 15th day of the following month may be deducted in the VAT settlement for the month in which the transaction took place.
Example
A purchase takes place on 30 March. The invoice is received on 10 April and recorded by 15 April. If the other deduction requirements are satisfied, the input VAT may be included in the March settlement.
Two limitations matter. The rule concerns documents that are both received and recorded; it is not a general requirement to post every prior-month invoice by the 15th. It also excludes purchase documents relating to transactions performed in the previous year, so December-to-January needs separate treatment.
Nor does the provision itself create a requirement to “communicate all invoices by the 15th” to an external recipient. It determines the VAT settlement period in which qualifying input VAT may be deducted; separate reporting obligations follow their own rules and deadlines.
The Italian Revenue Agency’s e-invoicing guide distinguishes transaction, issue, receipt, and recording dates. The exact treatment depends on the transaction and the taxpayer’s circumstances, so specific cases should be reviewed with a qualified tax adviser.
Why an April invoice may relate to March
A supplier invoice issued or received in early April may document goods delivered or services performed in March. This can happen when the document is created after month-end within the permitted timing or summarizes documented prior-period transactions.
For financial reporting, invoice date and cost period are not necessarily the same. If the goods or services belong to March, Finance must assess whether the cost should be recognized in March even when the invoice arrives in April. When the document is not yet available, unbilled liability or invoice accrual entries may be required under the applicable accrual accounting principles and company policies.
Three calendars intersect: operational delivery, document issue and receipt, and the accounting and tax treatment. Treating them as one date creates avoidable errors.
Why AP workload peaks during close
- invoices arrive close to cut-off and must be captured in a batch;
- PO, delivery, or cost-center references are missing;
- price and quantity discrepancies require procurement or operations;
- approvals are distributed across inboxes and different owners;
- Finance must separate postable invoices from cases requiring estimates or investigation;
- each unresolved exception reduces visibility into period costs and liabilities.
The bottleneck is not just reading a PDF faster. It is reconstructing context and routing an exception to the person who can resolve it before cut-off. That is why enterprise AP vendors increasingly connect invoice automation to a faster month-end close.
From a monthly rush to continuous control
A credible promise is not to “automate the close” in the abstract. It is to reach day X with more work already complete and a visible, prioritized, owned exception queue. AP automation can capture invoices as they become available, extract header and line data, match invoices with POs and delivery notes, flag discrepancies immediately, and show which prior-period invoices still require action.
TypeLens captures supplier invoices and delivery notes, compares them with purchase orders already held in the ERP, and flags discrepancies. Its value for the close comes from continuity: matching and exception handling start when the document arrives, not on the morning of the deadline. Explore accounts payable automation.
An operational close checklist
- Define the perimeter: entities, ledgers, invoice types, and periods in scope.
- Separate cut-offs: internal close, VAT settlement, and consolidation deadlines are not interchangeable.
- Measure the queue: received, captured, unmatched, in exception, awaiting approval, and ready to post.
- Assign exceptions: every issue needs a cause, owner, and expected resolution date.
- Identify missing invoices: use purchase orders and receipts to find prior-period costs without documents.
- Control year-end: do not apply the 15th-day VAT mechanism automatically across December and January.
- Review after close: measure close days, team hours, day-X exceptions, and post-close corrections.
Frequently asked questions
Informational content updated on 7 September 2026. It is not tax or accounting advice.