User Roles AdminStaff user ✗External contributor ✗Pulse user 

This article explains why Silverfin sometimes opens an unexpected next period after you shorten a period in a client file and resync. It is relevant if you manage synced client files, particularly when you shorten a period for a liquidation, year-end change, or interim closure.


Table of contents 

What is the difference between the booking period and the booking date?

  • Silverfin uses the booking period, not the booking date, to decide which period a transaction sits in. The booking date only appears in the account's view ledger.
  • This matters when a period is shortened. Because the original period is no longer a full period, Silverfin pushes its data into the next period.
  • Both values sync for every transaction, but the booking period always wins.

How does the reporting frequency affect the length of a period?

A client file can report monthly, quarterly, or yearly. The reporting frequency determines how Silverfin groups transactions into ledgers, so it plays a central role whenever a period is adjusted.

What happens when I shorten a monthly period?

Imagine you report monthly and your client file runs from 01/01/2026 to 31/12/2026. Because 11 May is the liquidation date, you shorten the period so that it ends on 11/05/2026.

All your May bookings are posted on 10/05/2026 in your bookkeeping system, so you expect everything to land in May.

After you shorten the period in Silverfin and resync, the period June 2026 opens unexpectedly.

Why does this happen?

When you check the synced data, the bookings are dated before 11/05/2026, but their booking period ends on 31/05/2026.

Because you shortened the period to end on 11/05/2026, May is no longer a full month. Silverfin therefore pushes the bookings whose booking period ends on 31/05/2026 into the next available period, June 2026.

Quick check: in the synced data, compare the booking date against the booking period end. If the booking period ends after your new (shortened) period end, that booking will move to the next ledger.

How do I fix it?

There are two options.

Option 1: Adjust the booking period in your bookkeeping system

This is the cleanest fix. Update the booking period of the affected entries in your bookkeeping system so that it ends on or before your shortened period end. After the next sync, the data lands in the correct ledger in Silverfin.

If this is not possible, use Option 2.

Option 2: Work around it from the Silverfin side

For this option, contact Silverfin Support. The steps involve resetting the period and switching off the sync, and we will guide you through them. The process is as follows:

  1. Silverfin Support sets the period back to its original end date (31/12/2026) and resyncs the client file. May 2026 becomes a full period again, so the May data sits correctly in the May ledger.
  2. You check that everything is correct.
  3. Silverfin Support switches off the sync, then adjusts the period and the May ledger back to 11/05/2026.

What happens in quarterly client files?

The same logic applies when a client file reports quarterly. If shortening a period leaves a quarter that is no longer full, Silverfin pushes the bookings from that quarter into the next quarter.

How do I fix it in a quarterly client file?

Contact Silverfin Support. The process is as follows:

  1. Silverfin Support sets the period back to its original end date and resyncs. The affected quarter becomes a full quarter again, so its data sits in the correct ledger.
  2. You check that everything is correct.
  3. Silverfin Support switches off the sync, then adjusts the period and the affected ledger back to the shortened date.
  4. If you later want to sync the client file again, let Silverfin Support know. The affected ledger needs to be adjusted back to its original end date first.

What if the company is not being liquidated?

If the company is still active and you want to keep working in the client file after producing the quarterly report, follow the three steps above. Silverfin Support can then set the date back to the original year-end for you.