I was curious if we could share the data from billings between to users on separate computers? That way we can both enter in time slips and keep track of the projects? Does anyone here use billings for several users? Thanks,
Chris

I don't think you should do that unless you can ensure that only one of the copies is running at a time so you don't corrupt your data file with simultaneous use.

I also don't know what the licensing would be in that case, would you need a second license even though you're only running one copy at a time? (Is it per-installed-seat or per-running-instance?)

I have a related question to this: is there a solution that allows importing timesheets into Billings from another timer program or CSV or similar?

What would be ideal is a small satellite "Timer" program to run on other computers...

I have a client who does exactly this using Billings2. He uses 2 licensed copies of Billings2. His serves as the "Master" to collect all the slips and run invoices. His assistant uses a second copy with exactly the same clients and projects (the Billings AB group is kept exactly consistent using a single dotMac account to keep both computers in sync). At the end of each month each client's project slips are exported from the assistant's copy using Billings "File –> Export –> Slips" command, moved across the network to where the "Master" copy of Billings resides and are imported into that using the "File –> Import" command. The nice thing about this is that the slips are imported into the correct projects but the differences from the two users (billing rates, etc) are retained after import. Once imported, the slips are deleted from the assistants copy to begin a new month of slips.

It is not the most elegant solution, but if you don't have lots of ongoing projects it is very doable and does not take a lot of time. It may even be possible to create a script/Automator workflow to do some of this automatically. The key here is that the clients/projects on the two systems must be IDENTICAL or the import will create a new projects on the Master rather than merging them into an already created project.

Hope this helps.