We rarely deal with retainers, so this is a new problem for me. I will say that non-retainer invoicing and syncing with QBO has been working nicely for us once we got it set up.

One thing I have noticed is that if I create a billing item for "retainer" and there are no other billing items, the invoice simply will not create a balance due and will not sync to QBO. I'm curious if anyone has a work around. My plan is to manually create a retainer invoice in QBO so I can collect the retainer. Then I will manually create a retainer entry in AppColl. I don't know what manual process is going to be needed once I actually invoice but I'll figure it out when we do that.

What might be helpful is just to hear how other people have done this. Not asking for the platform to be changed, but just to hear from other end users that successfully handle retainers and also use AppColl for billing.

Hi,
Is anyone using the Signatures Module to obtain signatures on an assignment document for new filings? There might be 1, 2, 3, X inventors. I see the example documents have a case for 1 inventor and a case for 3 inventors. Any suggestions how to make a Word document that can expand to include signatures from multiple inventors, where the number of inventors differs on a matter by matter basis?

The other option we are trying is to create multiple copies of the same Assignment - but a 1-inventor version, 2-inventors version, 3-inventors version, and so on. The issue we have here is that our signature rule doesn't seem to distinguish which document to use depending on the quantity of inventors.

I'd love to hear if anyone is successfully using the signatures module for assignments. If so, how did you set it up?

Would like to enable AI forecasting and document generation for particular users. Last time we checked, enablement of those features is either "all-users" or "no-users." In our environment, because we do not want to enable those features for certain users, that means we cannot do testing of the AI tools.

I'm curious how other law firms handle IDSs in AppColl. We see that when the paralegal generates an IDS, AppColl automatically populates the "cited by" information in the list of references. So when an attorney reviews the list of references, it appears as though all documents have been cited (regardless of whether the IDS has been signed or filed). This is potentially disastrous.

We are trying to develop a workflow where the attorney does a review before the IDS is generated. That way the attorney can mark the cumulative references "do not cite" and do a review of unmarked refs. Then after that step, the paralegal generates the IDS and sends to the attorney to sign. After the paralegal files the IDS, they put the citation date. But the problem we are running into is that the paralegal staff might generate the IDS early and new refs come in. So, then we don't know whether we need attorney review (again) or new IDS task.

Happy to hear the workflow that other law firms have adopted. I spoke to another AppColl customer and was told they manage IDSs using a third-party. We might go that route but I'd love to use AppColl if we can figure out how they intended IDS workflow using AppColl in a multi-attorney/staff law firm.

Realize this is an old thread. But I'm a little surprised nothing has happened on this. The file storage feature in AppColl doesn't seem very useful for maintaining active files. It seems mostly relevant for linking files to tasks and that's about it.

I'd love to see some integration capability -- windows file explorer. Or maybe something that links to cloud storage at OneDrive, Google Drive, AWS, etc.