CNC — Credit & Collection

Review configured limits and customer exposure with assigned approval authority.

Follow unpaid invoices and outstanding balances in the assigned scope.

Assign collection follow-ups and review target progress.

Submit payment details for Accounts verification and authorized posting.

Group outstanding invoices by due-date/aging context.

Send permitted reminders using configured communication providers.

Track customer disputes and route adjustments to the authorized approver.

Review assigned collector activity and recorded collection outcomes.

Bring credit reviews, follow-ups, disputes and payment submissions together.

Create a customer receipt, submit it, and require a different authorized reviewer to approve or reject. Rejection requires a reason.

Allocate only approved receipts to the same customer and currency, with remaining receipt/invoice balance checks and a CNC subledger entry.

Record invoice due dates and currency, then inspect a customer ledger and currency-grouped balances. This is not a completed general-ledger integration.

Submit adjustment requests and post the source adjustment only after independent authorized review.

Record company bank metadata, review deposits independently, import statement lines and manually match eligible approved deposits. This does not initiate a bank transfer.

Inspect stale pending deposits, unmatched statement lines and approved deposits awaiting a match.

The receipt collector can submit a bounded handover against their approved receipt. A different authorized reviewer verifies or rejects it.

Compare approved receipts with verified handovers by collector, date and currency; require an explanation for shortage/excess and independent review.

Plan collector routes, record visits and allow the assigned collector to complete or mark no-contact. Optional submitted coordinates are not independently verified device GPS.

Set period/currency targets and compare approved receipt amounts. These figures do not prove bank-settled recovery; visit performance is a separate count.

Configure basis-point plans, calculate eligible claim proposals and route claims to independent review. Approval is not payroll payment.

Record promises, fulfillment/break/cancel states, disputes, escalation and resolution. Forecast summary is descriptive, not predictive AI.

Schedule follow-ups, complete/cancel tasks, generate reminder records and review a supervisor queue.

Record templates, campaign approval, planned communication history and manually reported outcomes. A manual status is not provider-verified delivery.

Store purpose/channel preferences with change history and cancel queued notices when consent is withdrawn.

Use consent checks, idempotency keys, attempts, dead-letter records and independently reviewed recovery requests in the notification foundation.

The source manager dashboard supports review, follow-up, independent decisions, eligible closure and rejected-item rework for recovery-security alert reviews.

Filter by status, decision and manager, search text and browse 50 records per page in the source approval-review queue.

Assigned managers can add a follow-up to at most 25 eligible reviews together. This does not bulk-approve, reject or close them.

Inspect advisory same-department workloads, choose an eligible active manager and reassign only open unreviewed items with a reason and history.

Monitor overdue review work and issue scheduled, company-scoped internal reminders using configured policy.

View decision/rework history, verify the recorded audit chain and export bounded formula-neutralized reports within company permissions.

Organize the company ledger accounts and their authorized use.

Record and review source-linked accounting entries.

Track supplier obligations and customer balances.

Maintain authorized bank-account and reconciliation context.

Review payment/receipt records with controlled accounting posting.

Apply configured currencies, rates and accounting treatment.

Produce reports that reconcile to the underlying ledger.

Compare permitted budgets and costs within assigned responsibility.

Use configured jurisdiction-specific tax profiles and maintained rules.

Reconcile business handoffs before treating integration as complete.

Channel listing, members, creation, grant and revoke are recorded in the source batch; active company context is required.

Company/channel speaking-turn controls use a 15-second lease and a holder-only release.

Initial Flutter sign-in, secure token storage and read-only channel selection exist.

Microphone capture, an independently authorized media service and live audio delivery remain to be implemented.

Present summaries only within the viewer’s authorized scope.

Review operational source-linked summaries and exceptions.

Reconcile finance summaries to the underlying ledger.

Review configured trade movement and transaction summaries.

Follow available milestone and carrier-status information.

Review open balances, due dates and recorded follow-up.

Analyze permitted sales and reconciled cost information.

Apply permitted report fields, scope and saved filters.

Enable the format suitable for the particular authorized report.

Summarize defined metrics with traceable source records.

Thirty-day department notice and escalation summaries distinguish generated notices from confirmed external delivery.

Seven-day worker run/failure trends summarize global operational telemetry without exposing other tenants’ approval records.

Health incidents can be manually mapped to a company department. Department counts and the separate 30-day reviewer decision summary have explicit windows and overlap limits.

Limit document categories and access to the departments that need them.

Use authorized file handling for the linked business record.

Provide a print/PDF option where the specific document type supports it.

Enable the right templates for the relevant department and workflow.

Retain the document version associated with an approval or change.

Route the chosen version to assigned reviewers.

Track sensitive document access and lifecycle actions.

Find authorized files by their record and metadata.

Export permitted document-list metadata when the workflow requires it.

Attach supported documents contextually; no universal document menu or format grant.

Private Office Mail attachment storage, hold/review and recovery workflows are documented in their own modules. They do not implement versioning or governance for every Document Center record.

Adapt authorized workspaces to supported screen sizes.

Prioritize tasks and forms relevant to mobile users.

Provide employee-specific requests and published information.

Expose only assigned approval work with applicable limits.

Plan configured delivery channels and permission-aware routing.

Publish supported authorized integration interfaces as they are implemented.

Connect approved shipping, payment and messaging providers.

Deliver configured business messages through approved providers.

One installable app for Android, iPhone and desktop.

Connect assigned rider, sales, collection and supervisor tasks.

Recipients are company users, not public email addresses.

An active department member can send to up to 100 other active members. Department delivery is recorded as one database transaction.

Internal notices identify new messages and uploaded attachments.

Sender upload supports PDF, PNG, JPEG and plain text up to 5 MiB.

Retention previews, legal holds, configured company quotas and independent cleanup review connect to the dedicated governance workspace.

Office Mail stays inside the company database. It does not use SMTP/IMAP or create a company-domain mailbox.

Thread participation and company identity determine which messages an authenticated user can access.

Fetch up to 100 messages newer than the caller cursor from threads they belong to. Polling is distinct from WebSockets or background push.

A thread member can advance their own read position. This is not a delivery confirmation or a read receipt for every participant.

Realtime push, voice/video transport and mobile background delivery require separate infrastructure and validation.