Compute
Purchase orders in Finance Sync
Review purchase-order policy, references, approvals, and cost allocation without guessing finance or tax requirements.
On this page
Confirm the policy
Finance Sync records whether your organization requires, allows, or forbids a purchase order. Lithi does not choose that policy for you.
Ask the authorized finance owner when the policy, supplier record, or destination is missing or conflicts with another source.
Capture the reference
When a purchase order is required, confirm its exact reference and approved period. Also confirm the approver, budget, cost centre, project, and entity.
Do not invent a reference or copy one from an unrelated invoice. Keep the source and freshness for each confirmed field.
Review allocation
Review how the approved finance system will receive the amount, currency, supplier, line items, and allocation fields. A mapping may be blocked when the system edition or accounting treatment is unclear.
The customer-payable flow records a bill owed to Lithi. It cannot accept provider earnings or become payout authority.
Apply with approval
Inspect the current record, plan a dry run, show the exact change, receive entitled approval, apply idempotently, and read the object back.
If your policy forbids purchase orders, leave the reference absent. Do not add a placeholder to satisfy a template.
Recover a conflict
MAPPING_CONFLICT means the proposed object does not match an approved fact. Resolve the source conflict before applying. A refusal keeps the evidence and next action.