Hi Peter,
most of these you can cover with the native Subscription Billing module in BC, but not all of them one-to-one. Recurring invoices, billing schedules, deferrals, per-statement pricing and contract-to-billing linkage are there standard, so points 1, 5, 7, 8, 9 and 12 map well. Recurring billing linked to purchase agreements (11) works through vendor contracts too.
Third-party subscriptions with markups (6) can work with usage-based billing, BC can import supplier usage and price it for customer billing, but the markup logic itself needs design, not just a setting.
The audit-specific items (2, 3, 4) are not native, BC has no concept of an "audit" in your sense, so custom fields and a status table feeding the billing trigger, some AL work.
Rule-based revenue recognition (9 in your sense) and Collection-to-Revenue (10) are the weakest, native deferrals exist but recognition tied to audit status or actual cash collection is a specific rule, extension territory.
So maybe 60-70% standard, rest is configuration plus a small extension.
Hope this help, Best regards.
✅ Tick the checkbox below to mark the answer as verified, if it helped resolve your question.
Regards
Gregory Mavrogeorgis
