Client Portal - Errands View

Errands: Resolving Operational Issues

The Errands view in the Client Portal lists all operational issues or data errors that require your action to ensure continued processing of your invoices, factoring, or collection cases. Resolving these issues quickly ensures timely payments and prevents service disruptions.

The Errands screen is divided into two main sections: Unresolved issues (requiring immediate action) and Resolved issues (for historical reference).

1. Unresolved Errands: Issues Requiring Action

This section lists issues organized by category, with a count of how many problems fall under each type. The categories in the menu on the left are Failed Bookkeeping, Proceed to Next Step, Provide identification number, Provide correct invoice address, Provide correct e-mail, Resolve Invoice Issue and Failed Distribution. Each row has Solve, and on most categories also Force Close, see Force Close.

Issue 1: Failed Bookkeeping

Description	Why It Happens	How to Resolve
Failed bookkeeping	A voucher from Quiddly could not be booked in your own ERP. Quiddly sends vouchers for payments, fees and other transactions on your account to your ERP, and the ERP refused this one. Only the export of this voucher to your ERP failed: the voucher and the fees charged are unchanged in Quiddly.	Search payments: the list shows Date, Description and Amount of each transaction whose voucher failed. The Booked column says “Error when bookkeeping”, and the red error icon shows the ERP’s own message after “Message from ERP:”. Fix the cause in your ERP, then press the retry icon (Retry bookkeep, with a counter of the attempts so far) on the row. The voucher is queued for a new attempt. The row menu also downloads the voucher and the other documents of the transaction.

The ERP’s message states the cause. Typical causes are an accounting period that is locked in the ERP (unlock it), an account that requires a cost centre (make the cost centre optional in the ERP for that account), and a payment that cannot be booked on an invoice that is already marked as fully paid in the ERP. The list shows the current month by default. Change From and To to find older rows, and use Currency to narrow the list.

Issue 2: Proceed to Next Step

Description	Why It Happens	How to Resolve
Select Next Step for the Debt Collection Case	A debt collection case has reached a decision step in its collection profile and waits for you to choose what happens next.	Review and decide: the table lists the Created date, the Invoice Number, the Collection no., the Debtor and a Description. Click Solve, choose a Select Next Step option (Send to Enforcement, Change Status to Watch, Close Debt Collection Case or Other Suggestion; the collection profile can limit the choices), add a Comment if you like and click Submit. The dialog notes that the request needs approval by an operating agent and creates a change request.

The older invoice-level form of this errand, “Should we proceed to the next step with invoice …?”, is legacy and no longer occurs, so you will only see the debt collection form.

Issue 3: Provide Identification/Address/Email

Description	Why It Happens	How to Resolve
Provide identification number	The debtor is missing a required national or legal identification number (e.g., corporate ID).	Click Solve on the row, enter the debtor’s identification number in the dialog and click Submit. Ignore closes the errand without a correction.
Provide correct invoice address	The debtor’s address is missing or invalid, preventing physical distribution of the invoice.	Click Solve on the row, enter the correct invoice address in the dialog and click Submit.
Provide correct e-mail	The debtor’s email address is missing or invalid, preventing electronic distribution.	Click Solve on the row, enter the correct e-mail address in the dialog (it shows the invalid address and the error message) and click Submit. Ignore closes the errand without a correction.

Issue 4: Resolve Invoice Issue

Description	Why It Happens	How to Resolve
Resolve invoice issue	A general validation error occurred during the initial submission or processing of the invoice.	Edit and Submit: The table lists the Invoice number and a Description of the validation error. Click Solve to open the Invoice Editor. Correct the missing/invalid fields (e.g., Invoice Date, VAT Number, Customer Number, or Article lines) and click SUBMIT to retry processing.

Issue 5: Failed Distribution

Description	Why It Happens	How to Resolve
Failed distribution	An invoice or reminder could not be delivered to the debtor (e.g., undeliverable email, no recipient found for E-invoice). The dialog shows the reason at the top.	Click Solve to open the Failed Distribution dialog. The options depend on the channel that failed, see below.

E-mail failed. Choose Update Email and enter the correct address, or Choose new distribution method and pick Letter, E-mail or Kivra.

E-invoice failed. The options are Distribute Again with Same Reference, Choose new distribution method, and Update Fields (GLN, Order Number, Your Reference). When the dialog lists validation issues for the e-invoice, it says whether the invoice will fall back to another distribution method on its own or has to be distributed with another one.

E-invoice sender or receiver not found. The options are Select sender from Crediflow’s Registry or Select receiver from Crediflow’s Registry, with the matches found, or Close Without Any Action. Tick Skip Creation of Future Errands to stop new errands of this kind for the same party.

“Receiver party has compliance …, but ‘prefer’ is required”. The receiving party has not accepted e-invoices from you as sender. With every attempt, Quiddly sends an invitation to the e-mail address on the debtor through the e-invoice distribution partner, and the message says that an invite has been sent. The invoice can only be delivered as an e-invoice once the receiver accepts the invitation, and neither you nor your operator can speed that up. Until then, choose Choose new distribution method to send the invoice another way. If the message says the automatic invite failed due to missing information, add an e-mail address on the debtor.

Force Close

Force Close sits next to Solve on an open errand. It is a last resort: it closes the errand without solving the problem, for example for an errand tied to an archived invoice. A dialog asks you to confirm and takes an optional comment. It needs a right on your user, see Rights, roles and users and the rights catalogue.

Force Close is offered on Proceed to Next Step, Provide identification number, Provide correct invoice address, Provide correct e-mail and Failed Distribution errands. It is not offered on Resolve Invoice Issue and Failed Bookkeeping, which are handled differently.
Force Close is silent. The invoice keeps its status, no webhook is sent and no validation call is made to an integration. Only the errand moves from open to closed.

The errand e-mail

Each morning your e-mail recipients receive an e-mail with the number of open errands, split into the new ones from yesterday and the total, for decisions, identification numbers, addresses, e-mail addresses and failed distribution. It does not include Failed Bookkeeping or Resolve Invoice Issue. It is sent in your language when that is Swedish, Norwegian, Finnish or English, and in Swedish otherwise. It is one of the system e-mails, see When each email is sent. The e-mail can be switched off per client with the CLIENT_ERRAND_REPORT client setting.

2. Resolved Errands

The Resolved section allows you to review historical issues that have been addressed.

Click See all to view the list of all resolved errands, filtered by category.
This section serves as an audit trail for data correction and manual intervention decisions.