Finance Sync
How to move Lithi invoices and impact reports into your accounting workflow by review and export, without giving the mapping any power to pay.
Follow the record into your accounting process
Start with the invoice, statement, export or filed impact report you intend to map. Keep its account, period, currency and immutable identity with the mapping, then follow this sequence:
Lithi source record
|
Preview the mapping
|
Supported CSV or manual export
|
Customer imports the reviewed projection
|
Reconcile the available evidenceA finance mapping changes how that record appears in the customer-owned accounting process. It does not change the underlying Lithi charge or report.
Keep prepaid purchases separate from consumption. The paid purchase invoice records the prepayment; the monthly statement records accepted usage against that credit with zero amount due. Your finance team chooses the accounting treatment. Importing both documents must not create a duplicate expense or payable. Historical invoice collections and provider earnings keep their own commercial direction.
Choose the registered system family
Use the current Finance mappings reference for the supported system families and object types.
A vendor name alone is not enough. Check the registered system edition/object mapping that applies to the customer connection.
Preview before any external action
The mapping preview should show how source fields map to accounting fields, the external object kind and any required customer reference such as a PO or cost center.
Do not change invoice amount, beneficiary, payment state or customer ownership to make a mapping fit.
Keep the supported action explicit
A mapping acknowledgement is not hosted ERP posting authority. Finance Sync supports reviewed CSV and manual-document projections; it does not post to the customer-owned accounting system or move money. Complete any import in that system using the reviewed projection. The export does not prove payment.
Do not infer OAuth/apply support merely because a system appears in the reference.
File the impact report separately
The monthly impact report is its own document. It can be carried into a sustainability or ERP process using its filed report identity. Buying credit does not itself create measured impact. Do not turn environmental values into invoice lines or substitute an accounting-system timestamp for the report's own period and revision.
Use Impact Reports API for exact retrieval and Impact methodology for claim boundaries.
Read back and reconcile
After your accounting team imports the projection, compare its source identity, amount, currency, period and mapping version with the Lithi record.
An external Paid annotation is not a reconciled payment confirmation. Use Invoices and payment to reconcile payment separately.
If the mapping or sync is unavailable, preserve the source record and reviewed projection. Do not create a duplicate invoice or payment to make the sync appear complete.