Compute
Use another finance system
Use a registered finance adapter or export-only path when your system is not one of the named Compute mappings.
On this page
Choose the safe fallback
When your system is not named, use a registered_finance_adapter only when that adapter is registered and approved. Otherwise choose none_export_only.
The export-only path supports the Finance API, signed webhooks, JSON, and CSV. It does not claim a Lithi-owned connector or a write-capable integration.
Confirm your finance facts
Inspect the authorized organization, legal entity, supplier, currency, purchase-order policy, destination, and accounting treatment.
Keep provenance, freshness, and conflict state. Never guess tax treatment, account, cost centre, project, entity, or approver.
Plan the result
Finance Sync inspects the source, plans a dry run, shows the exact export or adapter change, receives entitled approval, applies idempotently when supported, and reads the result back.
If no safe write path exists, export the approved projection. Keep the safe external reference and mapping digest with the export.
Keep status boundaries
An external Paid label is an annotation only. It cannot settle a Lithi invoice. Authoritative Lithi invoice read-back remains customer payment truth.
If the system needs an edition or treatment decision, stop with the typed next action. Do not invent support for an unknown system.