These are draft service principles for Azuren’s financial operations product direction. Binding terms require legal review and an executed customer agreement before production use.
Draft product terms — not legal advice, a binding offer, or a replacement for counsel-reviewed terms.
Azuren is being developed as a financial operations layer for source-data ingestion, reconciliation review, receivables visibility, collection proposals, controls, and auditability. It is not represented as an accounting system of record, an accountant, a bank, a lender, or a payment executor.
Customers are responsible for the authority to connect source systems, the accuracy and lawfulness of data they provide, review of financial decisions, and the approvals and communication rules applicable to their organization.
Integrations and import paths are enabled only when they are configured and operationally verified. A product label such as integration-ready does not mean a provider connection is active for a particular customer.
Automation must remain governed by identity, authorization, policy, validation, and the appropriate approval model. Analytical output and proposed actions are not authority to contact a customer, reconcile a record, or initiate a payment.
Pilot scope, pricing, implementation responsibilities, support, data processing, retention, and any service commitments must be set out in the customer’s executed agreement. This page does not establish a commercial offer or service-level commitment.
Azuren can make source evidence and proposed workflows clearer, but it should not be treated as financial, legal, tax, or accounting advice, nor as an autonomous decision-maker.