Open accounting events

Every financial event in Quiddly, such as an invoice, a payment, a fee or a payout, becomes an accounting event that is then booked as a voucher. Booking normally takes minutes at most. Until it is done, the event is open, and a period cannot be closed while any open event was created on or before the closing date. Open accounting events lists those events, so you can see what stops a close and send stuck events for booking again.

Where to find it

Go to Accounting > Bookkeeping and open the Open accounting events tab.

When Close Period is refused because of open events, the Close accounting window shows how many are open and how many are stuck, with a Show events button. It closes the window and opens this tab with Created up to set to the date you tried to close. See Closing of Accounts, step 5.

What the tab shows

At the top, the open and stuck counts, for example “8 open, 3 stuck”, and a table with the Topic, Type, Open and Stuck count for each kind of event. Below it, one row per open event:

Column	Shows
Id	The event’s number. Give it to Quiddly support when you report an event that stays stuck
Status	Pending: waiting to be booked. Processing: being booked. Error: the last attempt failed, or the event was sent for retry and booking has not started again yet
Topic	INTERNAL for your own bookkeeping, the general ledger you close. CLIENT for a client’s bookkeeping
Type	What the event records, for example INTERNAL_PAYMENT_UNPLACED
Created	The day the event was created. This is the date the closing check compares with the closing date
Last activity	The last time booking was attempted, or the created date if it never was
	Stuck when the event has made no progress for 30 minutes

Booked events are not listed, and neither are events that turned out to have nothing to book.

The quick filters All, Pending, Processing and Error narrow the list by status. Created up to shows only events created on or before that date, the same rule Close Period uses. Leave it empty to see every open event.

Stuck events

An event is stuck when nothing has happened to it for 30 minutes. Quiddly retries stuck events by itself once an hour, so most of them clear without anyone doing anything. Retry stuck sends them for booking straight away instead.

1. Set Created up to to the date you want to close, or leave it empty to retry every stuck event.

2. Press Retry stuck. It is greyed out when nothing is stuck.

3. Read the message. Each press sends up to 500 stuck events, for example “500 accounting events were sent for retry. 312 still stuck, press Retry stuck again to send the next batch.” Press again until no stuck events are left.

4. Wait a few minutes and check the counts. An event that was sent shows as Error until booking starts again, and leaves the list once it is booked.

Events that are still being booked are not sent again, and an event that was just sent is not counted as stuck for the next 30 minutes, so pressing again picks up the next batch.

If some events could not be sent, the message turns into a warning that says how many, for example “2 could not be sent and are still stuck. Try again in a few minutes.” They stay stuck, so you can press Retry stuck again, and the hourly retry picks them up too.

An event that keeps coming back

Retrying fixes an event that was interrupted, for example by a restart. An event that fails for a reason in its data fails the same way every time, and comes back as stuck after each retry. Contact Quiddly support with its Id and Type. It will block closing until it has been fixed.

Rights

To	Needs
See the list and the counts	ReadVoucherSettingsLockedPeriod, the same right that shows the closing date
Use Retry stuck	RetryVoucherPostingCreate

The tab and the button show for every user who can open Accounting > Bookkeeping. Without the right, the tab shows an error and Retry stuck shows the refusal when pressed. See Rights, roles and users and the rights catalogue.