Introduce Carrier tips

Problem Statement

Newspaper publishers want subscribers to add recurring tips for delivery drivers as part of their subscription. Pelcro currently lacks a way to collect these tips, exclude them from revenue, and convert them into accounts payable for carriers or drivers.

User Story

As a subscriber, I want to add an optional recurring carrier tip so my driver is rewarded automatically.

As a publisher, I want tips to be billed clearly, excluded from revenue, and converted into AP bills payable to vendors.

Scope & Impact

Impacted Components: UI, API, Accounting & Reporting

Use Case: Print subscriptions only

Functional Requirements

Tip Entry

1. Subscribers can add or manage a recurring carrier tip during checkout or via subscription management.

2. Tip is optional, fixed-amount, and billed on the same cycle and payment method as the subscription.

3. Admins can enable/disable tips and configure allowed amounts.

Billing & Invoicing

1. Tips appear as a separate invoice line item (vendor_tip).

2. Clearly labeled, non-discountable, non-taxable by default.

3. Charged together with the subscription.

Accounting Treatment

1. Tips are not revenue and are excluded from MRR/ARR.

2. Recorded as liabilities until paid.

AP Conversion (Bills & Vendors)

1. Each subscription is linked to a Vendor (individual driver or carrier company).

2. On successful invoice payment:

3. Pelcro creates AP Bill for the Vendor.

4. Tip is added as a Bill Line Item referencing the source invoice.

Payouts

1. Pelcro does not execute payouts.

2. Publishers pay vendors via existing AP workflows and mark bills as paid in Pelcro.

Definition of Done

1. Subscribers can add/manage recurring carrier tips.

2. Tips bill correctly and appear separately on invoices.

3. Tips are excluded from revenue metrics.

4. AP Bills are automatically generated per Vendor.

5. Invoice → Bill traceability is available.

6. APIs, docs, and automated tests are updated.