Thred
All posts

The invoice that arrives after you close: late documents, lock dates and agents

A February invoice lands on 12 March, after February is reported. How controllers decide between booking it now and reopening, and what software should do with it.

Manoj Tutika6 min read

Working on this yourself? Talk to Mark, our co-founder. We’re here to solve it with you.

Book a demo
On this page

When an invoice dated in a month you have already closed arrives, the sensible default is to book it in the current open period with its original date and reference, and to reopen the closed month only when a named person decides the amount changes something you reported. A lock date in your ledger makes that default stick.

Every controller knows the scenario. February is closed, the management report has gone to the board, the BTW return is being prepared, and on 12 March a supplier invoice turns up dated 27 February. For years it simply waited in a pile until someone decided what to do with it. That is changing. Once an agent or integration books supplier invoices as they arrive, the late invoice no longer waits for anyone. It gets booked within minutes, and the only question is where.

This post is for controllers, finance leads and accounting firms who close monthly and are starting to let software post to the ledger. It covers why late documents keep coming, how to decide between booking now and reopening, what happens to the VAT, and how write access should be set up so a closed month stays the month you reported.

Why do documents for closed months keep arriving?

Late documents are not a sign of a sloppy close. They are built into how other companies bill.

  • Suppliers invoice on their own cycle. A contractor who works the last week of February may only invoice when their own month-end is done.
  • Utility, telecom and lease companies send annual or quarterly settlements that relate to months long gone.
  • Credit notes follow disputes, and disputes take weeks.
  • Payment providers and marketplaces sometimes correct fees or chargebacks after the statement period has ended.
  • An integration whose connection lapsed resumes and imports a backlog, some of it dated before the lock.

You can reduce the volume with accruals and better supplier deadlines, but you cannot bring it to zero. So the useful question is not how to stop late documents, but what your process does with them.

Book it in March, or reopen February?

Take an illustrative example. February is closed and reported. On 12 March an invoice arrives from an installation company, dated 27 February, for €1,000.00 plus 21% BTW of €210.00, so €1,210.00 in total. The work was done in February.

There are two defensible answers.

Book it in March. The entry goes into the open period, with the supplier's invoice date and number preserved and a note that it relates to February. February's figures stay exactly as reported, and the March management report mentions the item if anyone needs to know. For most late invoices of this size, this is the right call.

Reopen February. Sometimes the amount matters. It moves a covenant ratio you reported to the bank, it changes a result the board is about to discuss, or it belongs to a year-end that the auditor will examine. Then a named person unlocks February, the invoice is booked there, February is locked again, the reason is logged and the report is reissued.

What decides between the two is materiality, and materiality is a judgement about your users: the board, the bank, the auditor, the tax authority. A few questions help:

  1. Would anyone who received February's figures act differently if they knew?
  2. Is February part of a year-end or a period you have certified to a third party?
  3. Is this a one-off, or the fourth late invoice from the same supplier this quarter, which together would matter?

That third question is one people often skip. Ten small late invoices can add up to something you would have reopened for.

What happens to the VAT?

The VAT treatment does not have to follow the bookkeeping choice, and it is worth keeping the two apart.

In the Netherlands, input VAT is generally deducted in the return for the period in which you receive the invoice, so in the example the €210.00 belongs in the March or first-quarter return regardless of where the cost lands. Corrections to a return you have already filed are a different matter. Both the Belastingdienst and HMRC let smaller errors be corrected in a later return and require a separate correction above certain thresholds, and the thresholds differ. Check with your accountant before you correct a filed period, and never fix a VAT error by editing the original entry, because the ledger will then disagree with the return you submitted.

What should software do the moment it finds one?

This is where write access comes in. An agent that books supplier invoices will meet the 27 February invoice long before a controller does, so its behaviour needs to be decided in advance.

The behaviour we think is right is simple. The agent notices that the document date falls in a locked period. It does not post into February, and it does not touch the lock date. It prepares the entry in March with the original date and reference, and puts it in front of the controller with the reason: "Invoice dated in February, which is locked. Proposed in March." The controller approves it in March, or decides to reopen.

For that to hold, a few permissions need to be set before any software writes to your books.

Start read-only

Every connection begins with read access. Writing is granted per system and per task. An agent that answers questions about your margins has no reason to post journals.

Limit what each agent may create

Matching a bank line is a different act from posting a manual journal to equity. A sensible starting point is to let agents book supplier invoices, match payments and post scheduled adjustments such as depreciation, and to keep journals to equity, intercompany and provisions with a person.

Set amounts that trigger a question

An invoice of €180 from a known supplier can be booked; one of €18,000 from a new supplier waits for approval. The limit is yours and can differ per agent.

Keep the period decision human

Moving a lock date and reopening a month are the two actions an agent should never take, whatever its other permissions are.

Keep the ledger's own lock on

Ledgers differ in how strictly a lock is enforced and in whether it applies to API connections as well as people, so test yours before connecting anything that writes. Even with well-behaved agents, the ledger's own lock is a free backstop against a misconfigured integration.

Which other late changes reach closed months?

Late invoices are the obvious case, but a few other changes reach back into reported months in the same quiet way, and the same rules handle them.

  • A bulk instruction such as "move every invoice from this supplier to the new cost centre" runs across the whole year rather than the open month.
  • A re-sync after a lapsed connection imports a week of sales that were already booked, half of them before the lock.
  • A booking error from January is fixed by editing the original entry instead of reversing it in the open period.

In each case the remedy is the same. Changes land in the open period, corrections are made by reversal and a new entry so both the mistake and the fix stay visible, and anything that would alter a closed month goes to a person.

How do you build late documents into your close?

A small routine keeps late documents from becoming a monthly argument.

  1. Agree a materiality threshold for reopening, per entity, and write it down.
  2. Keep one list of documents that arrived for closed periods, with the proposed treatment for each.
  3. Review the list weekly, not at the next close, so reopen decisions are made while they are still cheap.
  4. Log every reopen with the person, the reason and the reissued report.
  5. Look at the list each quarter for repeat suppliers, and fix their deadlines or add an accrual.

Agents make this routine easier to run. They check every proposed entry against the period status before writing, collect late documents into that one list with a suggested treatment, and prepare reversals and rebookings so the controller only reviews.

How does Thred handle it?

Thred's agents read by default, write only with your permission and ask above the limits you set. You choose per agent whether it asks first or works autonomously. Every entry is traceable to its source document and to whoever approved it, and nothing is deleted from the record; entries are reviewed and reversed instead. Our security page sets this out. When Thred runs on top of your existing ledger through Thred Layer, finished entries are written back only to the systems, and within the limits, you have approved.

If you want late invoices handled without your reported months moving, book a demo.

Frequently asked questions

Should a late supplier invoice be booked in the closed month?

Usually not. Book it in the open period with the original invoice date and reference, and mention it in the next report. Reopen the closed month only if the amount would change a decision by the board, the bank or the auditor.

What is a lock date in accounting software?

A lock date is the date up to which the ledger refuses new or changed entries. It protects periods that have been closed, reported or used for a VAT return. Some systems block postings outright, others only warn, so check how yours behaves.

Do lock dates apply to integrations and API connections?

Not always in the way you expect. An API connection often writes with the permissions of the user who authorised it, so an administrator's connection may reach further than a normal user. Test it or ask the vendor before you grant write access.

How do you correct a mistake in a closed month?

Book a reversal and a corrected entry in the current open period, with a reference to the original, rather than editing the closed month. Reopen the period only when the error is material, and record who decided and why.

Can a filed VAT return be corrected in the next return?

Both the Belastingdienst and HMRC allow smaller corrections in a later return and require a separate correction above certain thresholds. The thresholds and conditions differ per country, so check them with your accountant before correcting a filed period.

Should an AI agent be allowed to unlock a period?

No. Moving a lock date and reopening a period should stay human decisions. An agent can flag late documents for closed months and prepare correction entries, but a named person should decide whether the period changes.

Sources

  1. Set or remove a lock date (Xero Central)
  2. Aangifte btw corrigeren (Belastingdienst)
  3. How to correct VAT errors and make adjustments or claims, VAT Notice 700/45 (GOV.UK)
  4. Identity and access management, 10 Steps to Cyber Security (NCSC)

Read next

Where Thred comes in

Security

Hosted in the EU, GDPR compliant, encrypted at rest and in transit. Thred reads by default and writes only with your permission.

Keep reading

Finance, handled.

Book a demo, or request a callback and we will call you.

Book a demo