Dryrun recognized that a limitation resulting from the imported data in your accounting software is that when items come in tagged as ‘Recurring’, they are not actually created in your accounting software until the next relevant date. Therefore, Recurring items don't appear in Dryrun until the relevant date - making it difficult to plan and forecast regularly repeating items automatically.

Dryrun’s solution? We've released the Placeholder Item feature, which gives users the option of flexibly indicating whether an Item is one that should recur into the future.

How to Use Placeholders

By clicking Add Item anywhere inside Dryrun, you will see that you are able to toggle on the Placeholder Item button.

By toggling Placeholder Item, you're telling Dryrun to create a placeholder that recurs at the interval you specify. When doing so, you will indicate the frequency of repeat, date due, and the estimated dollar figure.

Please note that if you have multiple payments, you can also toggle on Placeholder for each one of the payments.

On the Placeholder Item trigger date, Dryrun removes your Placeholder Item to avoid duplicate entries, while retaining future placeholder items for forecasting purposes.

What is a Use Case for Placeholders?

Here’s an example:

Rent is a recurring item every 30 days in QuickBooks Online and is created there as such. Dryrun only imports the current and past instances of Rent. However, users understand that there is a very strong likelihood for Rent to continue indefinitely.

  • User clicks on the 'Rent' item in Dryrun, toggles 'Placeholder Item' and selects frequency and due date (ie the trigger date), and clicks Save.

  • Future Rent placeholder items are created as per user parameters.

  • On the trigger date, the ideal flow is that the Placeholder Item disappears (triggered on due date) and the QuickBooks Online Item is imported into Dryrun, resulting in no duplicate entries.

A few important things to note:

  • Placeholders are date-based and do not reconcile with QuickBooks Online items; behind the scenes, the two processes are independent of one another

  • Placeholder items are not a good fit for Dryrun items that do not regularly recur.

More questions? Send us an email at hello@dryrun.com or chat with us!

Did this answer your question?