On Boarding Steps (Prime Billing)

Go-live essentials for Prime Billing. Start with Top customer deliverables, then four scopes.

Platform prerequisites: On Boarding Steps (Prime Platform)

Top customer deliverables

Ordered by priority — what the customer must provide for go-live:

Prio	Deliverable	Owner (customer)

Prio	Deliverable	Owner (customer)
1	Company & bank data — legal entity/entities, invoice header/footer, SEPA creditor ID / bank account (or gateway credentials)	Finance
2	Allowed payment methods — which methods customers may use (SEPA direct debit, bank transfer, none/cash-only segments, payment gateway if used)	Finance / commercial
3	Products / tariffs — the sellable products with prices, types, and billing cycles	Commercial
4	Tax & cost centers — tax rates, cost centers, and yearly-charge months	Finance
5	Invoice template & numbering — branding for invoice/letters and number ranges	Finance / Marketing
6	Named owners & access — who may run settlement and change billing config in production	IT / Finance

Scopes

#	Scope	Goal

#	Scope	Goal
1	Access & enable	Billing users can open the app
2	Main decisions	Companies, products, taxes, payment methods agreed
3	Initial data	Companies, accounts, products loaded
4	Acceptance	Test settlement signed off

1. Access & enable

NMS Prime brings	Customer brings

NMS Prime brings	Customer brings
Package & enable (see app main page)	Billing / finance user groups
Default billing menus	Staging + production access

Decide: who may execute settlement runs in production?

2. Main decisions

NMS Prime brings	Customer brings

NMS Prime brings	Customer brings
Company/account model, templates, SEPA & gateway options	Legal entities, bank / creditor data, gateway choice
Product/item model and billing cycles	Product & tariff catalogue with prices
Cost center scheduling	Tax rates, cost centers, yearly-charge months

Payment methods — decide at onboarding

Agree which payment methods are allowed for go-live and how they appear on contracts, invoices, and (if used) the Order Portal.

Method	Typical use	Customer decides

Method	Typical use	Customer decides
SEPA direct debit	Recurring collection via settlement	Creditor ID, mandate process, which product segments
Bank transfer / invoice	Customer pays manually; transfer reason rules	Invoice text, payment period
None / cash	Prepaid or external collection	Which customer segments
Payment gateway (if licensed)	Card / online payment	Provider credentials, which channels

Decide:

Default payment method for new contracts

SEPA vs bank transfer vs both (per segment / product)

Payment gateway in scope? (credentials + reconciliation owner)

Shop / Order Portal payment options aligned with billing (if digital sales in scope)

Also decide:

Companies / accounts and their templates

Product / tariff list and billing cycles

Tax rates and cost centers

Number ranges

Phone/CDR billing (OS VoIP) in scope?

Overdue + Customer Control in scope?

Related onboarding: Prime Overdue · Prime Document Management (letter templates)

3. Initial data

NMS Prime brings	Customer brings

NMS Prime brings	Customer brings
Setup guides (Billing Setup)	Company/account/product data; sample contracts
Template help (LaTeX)	Final invoice/letter branding

Decide:

Who loads companies, accounts, products

Who owns the invoice template

4. Acceptance

NMS Prime brings	Customer brings

NMS Prime brings	Customer brings
Unit Test Protocol (Prime Billing)	Billing + finance testers

Decide: which checklist rows block go-live? (Recommend company/account, product, item, settlement, SEPA, payment method matrix, and invoice template.)