The quick answer
Create a Sales Order workflow that initiates on create, or on create and update when edited orders are in scope. Add a Set Field Value action that runs After Field Edit on Customer, targets Payment Method, and sources Customer → Payment Method. Require the source to be nonblank and the target to be blank, then test a new order.
This setup makes the customer's normal payment method visible during order entry without replacing a method someone already chose on the transaction. It does not authorize or collect a payment. The screenshots use sample data and fictional person and operating-company names.
Before you start
Use a customer with a known, active Payment Method available in the account's transaction context. Your role needs access to the customer source field, the sales-order body field, and SuiteFlow. Build in Sandbox or test with an eligible, restricted role before release. Availability can depend on the subsidiary, currency, form, payment setup, and role. Labels and triggers can vary with account features and custom forms.
01. Confirm the customer source value
Open the test customer and check the Payment Method you expect to copy. In the example, Blue Peak Services uses Corporate Card. This gives the test a concrete expected result.
02. Configure the workflow action
Create a Transaction workflow with Sales Order selected as the subtype. Leave its release status at Testing while you configure it. Set the workflow initiation event to On Create, or add On View or Update when edited orders are in scope. This workflow-level event is separate from the action trigger.
Add a state and a Set Field Value action. Set Trigger On to After Field Edit and choose Customer as the triggering client field.
Open the action's Workflow Condition visual builder. Add Customer : Payment Method with not empty comparison. Add the current-record Payment Method with empty comparison, then save the condition. In the table, a blank Record cell identifies the current sales order. The second criterion protects an intentional transaction-level choice.
Set the sales-order body Payment Method as the target. Select From Field, then choose Customer and Payment Method as the source record and field. The action form summarizes both saved guards; it may label the current-record field simply “Payment Method.”
03. Test the sales order result
Start a new sales order and confirm Payment Method is blank. Select Blue Peak Services. The field changes to Corporate Card, which ties the visible result to the customer selection.
In the eligible test role, also try a customer with no source value and an order whose Payment Method is already filled. The first should stay blank; the second should keep its chosen value. Change the customer again to confirm that the guard behaves as intended. If edited orders are in scope, include On View or Update and test that path separately. Release the workflow to its intended audience only after these cases pass.
This client-side action is for interactive Sales Order entry. CSV, web services, SuiteScript, and transaction transformations may not run After Field Edit. If those channels need a default, add and test a save-time solution such as Before Record Submit or a script with the same blank-source and blank-target rules.
If the method does not appear, check Testing eligibility, whether the workflow and action were saved in the intended state, the Customer triggering client field, both condition fields, source-field access, form visibility, and other sourcing or scripts that may replace the value.
Test downstream billing, Terms, and payment-processing behavior in the account. The Payment Method value can affect transaction handling even though setting it does not authorize or collect money.
Common questions
Why does the workflow work in the UI but not during CSV import?
After Field Edit is a client-side event tied to interactive form entry. Add a separately tested save-time action or script for CSV, integrations, and other non-UI paths, and apply the same blank-source and blank-target rules.
Will setting Payment Method charge the customer?
No. It sets transaction data. Authorization, token handling, payment capture, settlement, and approval follow the account's payment-processing configuration.
How do I avoid overwriting a user's choice?
Add a condition that the sales order's Payment Method is empty. Test both a blank order and an order where a user already selected a different method.
Why do I also check the customer's Payment Method?
A blank customer source should leave the sales order blank. Check Customer : Payment Method separately from the current sales order's Payment Method so the default runs only when there is a value to copy.
When does the payment method populate?
The workflow initiates on create, or create and update, while the action runs after the Customer field is edited in the UI. In this example, selecting Blue Peak Services sources Corporate Card immediately.