Invoicing options -- enterprise Customers for RECAP Search Alerts

[s-taube]

• What are different services we can use to invoice customers?
• Is there a way to automate invoicing? Or do we need to generate and send them by hand?

User stories:

• As an FLP admin, I want invoices automatically generated and sent to customers, so that FLP can scale to hundreds of customers without manually managing invoices. (may be a v2)
• As a customer, I want a view of all my previous invoices and payments in one place. (may be a v2)

Definition of Done:

• A list of different invoicing options/services
• Pros and cons of each
• Include pricing (if external service)
• Choose what to implement as v1, and what for v2 (if applicable)

Notes:

• Stripe: usage-based pricing models

To Do

• look into other api usage and billing options
• Additional analysis if anything else looks good

[s-taube]

Xero can do invoicing, but there is no dashboard for customers:

[s-taube]

Xero: Manage invoices is available, you can automate reminders, and can manage customers.

[mlissner]

Thinking about how to move this forward, here's our definition of done:

A list of different invoicing options/services

We've looked at Stripe and Xero so far. I imagine there are other API invoicing/billing/tracking tools. Can you look into this too, please?

Pros and cons of each

Between Xero and Stripe, there's no point in further analysis — stripe wins. But if we find other options, perhaps we should write down the features we get from each so we can compare.

That can solve this too:

Include pricing (if external service)

And then we just have:

Choose what to implement as v1, and what for v2 (if applicable)

Which should be fairly easy at that point. I hope?

[mlissner]

Oops, sorry, one more thought. Once we've got this issue wrapped, I think a good next step is to have a developer use curl to prototype the system we wind up choosing. That'd help us identify the objects, how to create them, how to update them, and how to build the system we need.