01 / The idea
Clarity at each financial step.
Configured service terms describe the billing basis. Projects, invoices, payment confirmation, and reconciliation each have their own role, keeping operational progress separate from financial authority.
Pactveris / Billing & paymentsFrom invoice
The financial context
From invoice
to a connected record.
Keep service terms, invoices, eligible payments, and receipts connected to the account and its work.
Follow the connection02 / The flow
Keep the next step
in sight.
01
Set the basis
Use the configured service terms to express the applicable upfront, staged, or recurring billing context.
02
Issue the invoice
Maintain the obligation and related schedule with the account. Saving a project alone does not create an invoice.
03
Confirm the payment
Eligible checkout uses a configured Stripe connection. Confirmation is verified against the expected payment and invoice context.
04
Keep and reconcile
Retain the payment and receipt records. Reconciliation separately checks the record against financial evidence.
03 / The detail
A confirmation
with context.
A successful return page alone is not proof of payment. The supported workflow verifies processor confirmation before updating eligible records. Clients cannot mark their own invoices paid.
04 / Worth knowing
The context matters.
Connections make checkout possible
Live payments require the supported merchant connection, provider permissions, and configuration. Available methods depend on that connection; bank confirmation can take time.
The account keeps the trail
Invoices, confirmed payments, receipts, and financial documents remain associated with the relationship. Payment confirmation, reconciliation, and bank settlement are distinct.
The relationship. The work. Connected.
Let’s look at
your next step.
Demo scheduling is not connected yet.