Compute
SAP S/4HANA Finance Sync mapping
Choose the SAP S/4HANA edition, map a customer payable record to Supplier Invoice, and verify the returned object.
On this page
Resolve the edition first
SAP S/4HANA mappings require an explicit edition, deployment model, and API version. An unclear choice returns FINANCE_SYSTEM_EDITION_REQUIRED.
Do not infer the edition from a company name or an old integration note.
Supplier Invoice recipe
For a customer-payable flow, Finance Sync maps the bill owed to Lithi to the SAP Supplier Invoice object. This is a direction-specific recipe, not a Lithi-owned connector.
Confirm the organization, supplier record, duplicate check, currency, purchase-order policy, destination, and accounting treatment. Keep source, freshness, and conflict state.
Review the exact change
Inspect the source, plan a dry run, show the Supplier Invoice change, receive entitled approval, apply idempotently, and read the object back.
Never guess tax treatment, legal entity, ledger account, cost centre, project, or approver. Resolve every missing decision first.
Keep payment truth separate
SAP Paid is an external annotation only. It cannot settle a Lithi invoice. Authoritative Lithi invoice read-back remains customer payment truth.
Keep a changed read-back visible and reconcile it before another apply.