One engagement context
Link the authorized client, legal entity, service terms, renewal dates, funding obligations and responsible staff to the same governed record.
Connect agreements, controlled funding, service delivery, client-money oversight and reconciled billing—with clear approvals and an auditable record.
For professional practices, enterprises and government teams. Production financial execution remains subject to certification.
Retainer management becomes difficult when the agreed scope, delivered work, funding status, accounting records and approvals disagree. Retainer360 is designed to connect those responsibilities within ERP360 while keeping regulated actions with their authoritative providers.
Link the authorized client, legal entity, service terms, renewal dates, funding obligations and responsible staff to the same governed record.
Distinguish a funding request from verified receipts, available liabilities, fees and reconciled balances. Financial source records belong to Accounting360.
Define who may prepare, review, approve, receive a notification or view client evidence using scoped roles, independent checks and retained audit history.
Follow the information and approval handoffs through eight connected stages. Each stage has a defined owner, upstream evidence and a fail-closed control—not just a completion checkbox.
Resolve client, tenant, company, engagement and jurisdiction before an operational record is created.
ERP360 Identity + permissionsNo cross-tenant or cross-client accessDescribe scope, rate, billing period, milestones, renewal rules and signatory responsibilities.
Retainer360 + Contract360Controlled revisions and delegationVerify commercial terms, policy, recipient permissions and signed-document provenance.
Maker / checkerSeparation of duties and evidenceRecord a funding request and await bank/Accounting360 receipt and reconciliation.
Accounting360 + bank authorityRequested funds are not available fundsCapture approved professional time, service milestones and consumption against an authorized engagement.
Professional / engagement teamScope, budget and fee-policy checksCompare contract, service, client-money and posted-journal evidence; resolve discrepancies first.
Finance / trust officerSigned reconciliation and exception reviewIssue statutory invoices and statements only through certified financial services; notify scoped recipients.
Accounting360 + Notification360Tax, FX, recipient and delivery controlsHandle renewals, balances, adjustments, evidence retention and privacy/legal holds under approval.
Operations + records governanceAudit trail and controlled closureWorkflow is the governed solution design. Actual native route execution, bank/provider connections, invoice issuance and client-money movements are not yet certified for production.
The product scope now extends well beyond recurring fees: it covers contractual evidence, client money, finance, approvals, privacy and role-aware operations.
Define client identity, legal entity, contracting scope, currency, fee terms, funding rules and service periods with clear ownership.
Prepare drafts and link authoritative agreement records, signed versions and supporting documents using governed Contract360 and DocuSphere360 connections.
Separate requested, received, reconciled and available balances. Never treat an unverified deposit or payment request as spendable funds.
Track time, milestones, service delivery, agreed limits and fee consumption against the right engagement and approval policy.
Route invoice, credit, fee posting, tax and bank-reconciliation evidence through certified Accounting360 authority—not a duplicate ledger.
Support maker/checker review, delegated authority, exceptions, reversals, privacy requests, audit history and legal holds.
Design scoped access to retainers, invoices, receipts, requests and secure documents without exposing other clients or companies.
Role-aware next actions, contextual Help & Guide, Support360 escalation and conditional API360/Notification360 workflows with governed release gates.
Regulated organizations need to see what is requested, what has been independently authorized, what has actually posted, and who is allowed to act next.
Retainer360's control architecture is intended to support privacy, accounting, audit, contractual and sector-specific obligations without claiming certification before evidence is complete.
The R19 source map defines 14 persona models and 38 workspace areas across five portal families. These are planned navigation and policy scopes—not a claim that every workspace is operational in production.
Package governance, catalogues, subscriptions and controlled release operations.
Commercial retainers, clients, funding, billing and reconciliation operations.
Client matters, time, fees, trust controls, approvals and statements.
Departmental contracts, public funding controls, approvals and accountable reporting.
Privacy-scoped visibility into retainers, invoices, requests and secure documents.
Defined role families · Access depends on assignment, tenant scope and entitlements. The API service principal is machine-only.
Retainer360 is designed as an ERP360 add-on, not an orphaned product. Source contracts and shared catalogues establish the integration architecture, while real provider execution is enabled only after separate UAT certification.
Shared tenant/legal-entity/client context, entitlements, scoped access and add-on lifecycle.
Executed agreements, authorised signatories, delegation and binding scope receipts.
Document versions, signed evidence, immutable verification and retention authority.
Trust and liability posting, reconciliation, statutory invoices and financial reporting.
Authoritative add-on/expansion pricing, billing terms, FX, taxes, proration and entitlements.
Scoped approval, funding, renewal, exception and privacy events across governed channels.
Conditional APIs, events, signed webhooks, idempotency and replay protection.
Role-aware help, next-best actions, workflow guidance and support escalation.
Operational telemetry, release records, access trails and independent evidence.
No source-only integration is presented as an independently certified live provider. The central API360 Book currently registers Retainer360 with unavailable native runtime operations.
ERP360 PricingHub is the pricing authority. The values below are the currently configured USD catalogue reference—not a checkout offer or a guaranteed tax-inclusive quote.
Or $490/year · Base catalogue price
Additional users, legal entities, storage, AI credits, active retainers and billing units have separately governed PricingHub SKUs. The configured 14-day trial does not mean self-service activation is currently available.
The current commercial record identifies Retainer360 Enterprise AI as an ERP360 add-on. Acquisition, eligible bundles and entitlements are governed by PricingHub and Administration360; no separate standalone checkout is offered.
No. Requested or unverified amounts must not become available funds. Certified Accounting360 ledger, bank reconciliation and trust controls are required before any permitted financial action.
Its solution design uses Contract360 for agreement authority, DocuSphere360 for document evidence and Accounting360 for posted financial outcomes. Each real provider connection must pass independent integration and security certification.
Only a properly entitled, authenticated role with current tenant, legal-entity, client and engagement scope should access the relevant information. The 14 source personas do not automatically create live user assignments.
You can request a tailored enterprise demo. This is not a promise that all Retainer360 workflows are available in production; the demonstration team can identify the present implementation stage and required integration path.
The pricebook contains a configured 14-day trial, but Retainer360 public checkout and automatic entitlement activation remain disabled pending native release, payment, FX/tax and provider certification.
Tell the Numerish team about your service model, jurisdictions, client-money controls and existing systems. Explore the fit before activating regulated workflows.