How provider finance stays separate

Customer charges and Mac-provider earnings use separate records, permissions, and approvals. This page shows which authority answers each money question, where finance sync stops, and which record proves a specific Connector payout.

The direct answer

Lithi keeps customer costs and Mac-provider earnings in separate subledgers. One person or organization may buy Compute and share business Macs under one identity, but those grants stay independent. Revoking one grant preserves the other.

Lithi never nets, offsets, or silently credits customer costs against provider earnings. Expected earnings never authorize customer spending. The Lithi Compute Protocol sets the rules for accepted work and eligible revenue sharing; it does not turn one side's balance into the other side's payment.

Three separate directions

Finance Sync uses three fixed directions. Each direction answers a different question:

• Customer payable (customer_payable): What does the customer owe Lithi, and which invoice proves it?
• Provider receivable (provider_receivable): What approved earnings does a Mac provider have for accepted work?
• Provider payout reconciliation (provider_payout_reconciliation): Does a provider payout match the approved earnings record?

The first direction concerns a customer bill; see quotes, limits and billing. The second and third concern provider earnings and payouts. A finance sync or finance API must keep these directions visible and cannot combine them to force a match.

Which record proves each amount

Provider earnings truth comes from a signed allocation and immutable earnings statement for the named period. These records describe approved provider earnings for accepted work; they do not change a customer invoice or authorize a customer charge.

Provider payout truth comes from Mercury terminal read-back. It answers whether the payout reached its terminal state. It does not rewrite the earnings statement or settle a customer bill. An external finance system's Paid value is an annotation only; it cannot mark a Lithi invoice or payout as settled.

Your current Connector account and applicable agreement are the authorities for a payout that applies to you. Use them, not an old screenshot or a copied message, to confirm the organization, work, amount, status, timing, and destination. A public Trust page cannot calculate a payout, change its destination, or prove that money has moved. If anything looks unfamiliar, pause and ask support to review the visible reference before you share any further information.

Supported finance systems

An authorized customer environment may use QuickBooks Online, Xero, Sage Intacct, Oracle NetSuite, Microsoft Dynamics 365, SAP S/4HANA, or Other finance systems. The exact edition matters for each connection. If the edition or accounting treatment is unclear, Finance Sync stops instead of guessing.

Finance Sync is a controlled read and projection between Lithi and a customer-owned system. It can show approved records and return read-back evidence. It does not make an external payment true, and it does not choose tax treatment, legal responsibility, or a missing supplier fact.

Approval and read-back sequence

The safe sequence keeps each change visible:

1. Inspect the account, record direction, edition, and permitted scope.
2. Plan or dry-run the proposed mapping, export, or reconciliation.
3. Show the exact change before anything is applied.
4. Receive entitled approval from the role allowed to approve that change.
5. Apply or export idempotently so a repeated request does not create a second effect.
6. Perform authoritative read-back and compare the result with the approved plan.

A human payer approves each ACH bank debit in Mercury's hosted flow. Bank payment approval covers the stated payment method and scope; it does not give Lithi permission to choose a new amount or payment destination. Only the provider Owner changes a payout beneficiary, through secure Mercury onboarding.

Roles, privacy, and limits

Billing or Finance may review permitted mappings and earnings. IT may deploy selected Macs when granted, but IT cannot see earnings amounts or manage Finance Sync. Lithi holds no finance OAuth token, API key, bank detail, verification code, or mandate secret. The customer's authorized environment owns external finance access; provider payout onboarding remains separate from customer billing access.

When you ask support about a payout, share only the payout reference, the date, and the problem you can see. Do not send bank details, tax identifiers, identity documents, invoices, customer data, credentials, or access codes.

Primary action

Ask Connector support about a payout, or review quotes, limits and billing for the separate customer billing authority.