Recurring bills

Problem

Pelcro supports recurring invoices on the Accounts Receivable side through subscriptions, but there is no equivalent capability on the Accounts Payable side. Vendors that need to be paid on a recurring basis—either as a fixed amount or based on shipment activity—cannot be modeled natively and require manual workarounds. Net invoice is NOT required - if someone needs both receivable and payable, they will be 2 different subscriptions, one receivable and one payable.

Solution

Extend the existing subscription and AI Billing Engine so it can generate recurring vendor bills using the same lifecycle as recurring invoices. The system should be able to create either an invoice or a bill from a subscription, based solely on configuration, without introducing new billing logic or math. A new attribute called billing_type will be added to the subscription object with two possible values of: [receivable, payable].

DOD:

1. I can create a vendor subscription using the same configuration flow as AR subscriptions.

2. I can select a vendor when creating the subscription.

3. I can configure a recurring bill plan for the subscription.

4. The system generates recurring bills automatically.

5. I can view the generated bills in Accounts Payable.

6. Bills can be calculated as a fixed recurring amount (e.g. $100 per month).

7. Bills can be calculated dynamically based on shipment quantities using simple rate logic.