Sign in Start free trial
Platform

Company-to-Company Network

Share commission data between two  AI companies, with consent from both sides.

Company-to-Company Network lets one company, such as a manufacturer or network operator, share commission statements with a dealer or franchise that runs its own  AI. Both sides consent, either can pause or revoke, and the dealer recalculates its own employees' pay on its own plans without those employees ever seeing the vendor's earnings. Today this covers commission data and related invoicing; it is not a general exchange for every record.

41 features available 4 planned 8 capability areas
Highlights

What stands out

Consent from both sides

Nothing flows until both companies agree, and either can stop it instantly.

Employees never see vendor earnings

A database-level guard keeps vendor figures with the owner and finance.

Recalculate on your own plans

The dealer pays its people from its own rules, using vendor credits as input.

Reconciled to the cent

Vendor totals and ingested totals are compared and exceptions raised.

Regions respected

Cross-region movement is blocked unless explicitly allowed and recorded.

Capabilities

Every feature, in one list

Search or filter. Planned items are labelled; everything else is available now.

Secure connection

No shared database and no shared identity: two companies stay two companies.

6 features
  • Scoped per-link credentialsEach link has its own credentials that only deliver to that link, and they are never reused.
  • Automatic credential rotationCredentials rotate on a schedule you set, with overlap and an audit entry.
  • Signed requests with replay protectionTimestamped, one-time requests; a replayed delivery lands once.
  • Endpoint safetyEndpoints resolve only to the platform's own routing, so free-form addresses cannot be used to attack other systems.
  • Volume and rate caps per linkSize and rate limits protect the dealer from floods.
  • Separate credentials per environmentTest and production use different keys.

What the vendor shares

The vendor decides what leaves; sensitive classes never do.

6 features
  • Statements, credits, transactions and adjustmentsShare statement totals, credits, transaction references and reversals or clawbacks.
  • Exposure levelsMinimal, standard and full levels control detail; customer identity, other payees, private codes and secrets never cross.
  • Delivery by event and nightly catch-upSend on publish with a nightly catch-up so a missed event heals itself.
  • Recipient-created tax invoiceThe vendor's self-billing invoice can arrive as a document and become the dealer's sales invoice.
  • Payment status back to the dealerRemittance and paid status return to the statement and the receivable.
  • Real-time per-credit pushPlannedAvailable only for vendors with the real-time engine and off by default.

Landing in the dealer's tenant

Vendor data arrives as facts; landing never pays anyone.

7 features
  • Landing area and mappingDeliveries land through data integration with a vendor-statement mapping and a dry run.
  • Dedupe by source id and revisionReplays do nothing; new revisions create new rows; conflicting content is held for the owner.
  • Staging gateThe first delivery and any large change wait for the owner or finance to accept.
  • Revisions, reversals and clawbacks flow throughA revised statement supersedes the old one and the dealer is told by how much.
  • QuarantineSuspicious deliveries are quarantined, not applied.
  • ReconciliationVendor total versus ingested total by component and currency, with explained differences and exceptions.
  • Replay and retention controlsRe-pull a delivery and apply the dealer's retention policy to source data.

Recalculating the dealer's own pay

The dealer's employees are paid on the dealer's plans.

3 features
  • Vendor credits as inputsDealer plans read vendor credits as measures through normal crediting rules.
  • Starter recalculation packFlat share per store, tiered by store attainment, or split by seller code, each an editable plan.
  • Adjustment proposals on late revisionsIf a statement changes after pay is locked,  AI proposes an adjustment or clawback for a person to confirm.

Privacy inside the dealer

Employees see only their own pay.

4 features
  • Restricted-class guardVendor-sourced rows are visible only to the owner, finance and roles the owner names.
  • Enforced on every read pathScreens, reports, search, exports, AI and API reads are all probed as a non-recipient in tests.
  • Derived totals protectedA figure that would reveal the vendor earning is restricted too.
  • Per-vendor rolesA dealer with several vendors can let finance see one vendor and not another.

Residency and disputes

Respect regions and keep conversations where they belong.

4 features
  • Cross-region blocked by defaultMoving data between hosting regions needs a reason, a recorded basis and the owner's confirmation.
  • Dispute link-backDisputes are raised in the vendor's portal by deep link; the dealer keeps a reference row.
  • Non- AI vendorsThe same import path takes a file or API from a vendor that does not run  AI.
  • Several vendors in one dealer tenantEach vendor source has its own namespace, mapping and restricted roles.
Assistant

What  AI prepares here

It prepares the work. A person confirms it.

  • Prepare a share offer for a person to approve
  • Explain a restricted source to an owner
  • Prepare changes to who has portal access
  • Explain a pay line and trace its deal
  • Draft a dispute for a person to submit
Inside every hub

Workflow, reporting, integration, migration

The same four building blocks, specific to Company-to-Company Network.

Workflow

Shares above the standard level need four-eyes approval, large revisions are held for acceptance, and late revisions produce adjustment proposals a person confirms.

  • Wider share level approved by a second person
  • First delivery held until the owner accepts
  • Adjustment after a late vendor revision confirmed by a person

Reporting and analytics

Reconciliation by delivery and period, with restricted rows excluded from reports unless the viewer holds the role.

Datasets

Vendor statementsReconciliation exceptions

Dashboards

Share health

Integration

Federation uses the public API surface, signed events and data integration landing.

Share and delivery endpoints on the /v1 surface

Events

Statement publishedDelivery acknowledgedDispute state changed

Connectors

Vendor statement mapping profiles for  AI, file and API sources

Migration

Not applicable.

Mobile

On the phone

Dealer portal screens are mobile-first responsive; the native app is planned.

Who uses it

Vendor compensation administratorDealer ownerDealer financeStore managerEmployee payee

Industries

  • Telecom dealers and franchises are the worked scenario; other channel businesses fit the same pattern
Questions

Frequently asked

Do the two companies share a database?

No. Each stays its own tenant; data crosses only through a consented, signed link.

Can the vendor see our employees' pay?

No. The dealer recalculates on its own plans and the vendor sees acknowledgements only.

Can employees see the vendor's earnings?

No. Vendor-sourced rows are restricted to the owner, finance and roles the owner names.

What if the vendor revises a statement?

A new revision lands, the old one is superseded, and any adjustment for employees is proposed for a person to confirm.

Can we revoke?

Yes, either side, at once. Data already received stays with the dealer under its retention policy.

Does the vendor need  AI?

For this share, yes. A dealer whose vendor does not use  AI can import a file or API in the same way.

Can we share records other than commission?

Not yet. Today the exchange covers commission data and its invoicing.

See Company-to-Company Network on  AI

Talk to us