Consent from both sides
Nothing flows until both companies agree, and either can stop it instantly.
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.
Nothing flows until both companies agree, and either can stop it instantly.
A database-level guard keeps vendor figures with the owner and finance.
The dealer pays its people from its own rules, using vendor credits as input.
Vendor totals and ingested totals are compared and exceptions raised.
Cross-region movement is blocked unless explicitly allowed and recorded.
Search or filter. Planned items are labelled; everything else is available now.
A share starts with an offer and only flows when the dealer owner accepts.
7 featuresNo shared database and no shared identity: two companies stay two companies.
6 featuresVendor data arrives as facts; landing never pays anyone.
7 featuresThe dealer's employees are paid on the dealer's plans.
3 featuresEmployees see only their own pay.
4 featuresRespect regions and keep conversations where they belong.
4 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Company-to-Company Network.
Shares above the standard level need four-eyes approval, large revisions are held for acceptance, and late revisions produce adjustment proposals a person confirms.
Reconciliation by delivery and period, with restricted rows excluded from reports unless the viewer holds the role.
Datasets
Dashboards
Federation uses the public API surface, signed events and data integration landing.
Share and delivery endpoints on the /v1 surface
Events
Connectors
Not applicable.
Dealer portal screens are mobile-first responsive; the native app is planned.
icm: statements, credits, plans and payouts
crm: dealer onboarding and partner records
ap: self-billing invoice and pay-file hand-off
ar: dealer's sales invoice and receivable
integration: landing, mapping and events
workflow: four-eyes and holds
No. Each stays its own tenant; data crosses only through a consented, signed link.
No. The dealer recalculates on its own plans and the vendor sees acknowledgements only.
No. Vendor-sourced rows are restricted to the owner, finance and roles the owner names.
A new revision lands, the old one is superseded, and any adjustment for employees is proposed for a person to confirm.
Yes, either side, at once. Data already received stays with the dealer under its retention policy.
For this share, yes. A dealer whose vendor does not use AI can import a file or API in the same way.
Not yet. Today the exchange covers commission data and its invoicing.