Compute
Oracle NetSuite Finance Sync mapping
Map a Compute customer payable record to an Oracle NetSuite vendorBill, review the dry run, and reconcile safely.
On this page
The NetSuite object
For a customer-payable flow, Finance Sync maps the bill owed to Lithi to Oracle NetSuite vendorBill. This recipe is not a Lithi-owned NetSuite connector.
The mapping names the system edition, object kind, accounting treatment, recipe digest, and safe external reference.
Confirm the source
Inspect the authorized organization, supplier record, duplicate check, currency, invoice period, purchase-order policy, and destination.
Keep provenance, freshness, and conflict state for every fact. Never guess tax treatment, legal entity, account, cost centre, project, or approver.
Approve one exact change
Inspect, plan or dry-run, show the exact vendorBill, receive entitled approval, apply idempotently, and read the object back.
Review the supplier, dates, currency, lines, allocation, and safe reference. Stop when the edition or accounting treatment needs a decision.
Separate external status
NetSuite Paid is an 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. Never replace the Lithi invoice state with an external label.