The quick answer
In an account with an installed customer accounting-review customization, save the customer, find it in the pending accounting-review saved search, review its custom fields and choose Acc Approve. Verify Accounting Status, Accounting Approver and Accounting Approval Date on that same record. These fields are separate from native customer lifecycle status.
Person, operating-company and customer names are fictional example data.
Before you start
This walkthrough assumes that equivalent custom Customer entity fields, the workflow button and the pending saved search are already installed and available to your role. Their names and behavior vary by account. You need permission to create and view customers, access to the subsidiary and values for any other required fields in your account.
Jamie Reed uses the Administrator role to both create and approve this example. It demonstrates that path; it does not test denied roles or two-person approval. A disabled custom field describes this form's display behavior, not protection against changes through every other route.
01. Inspect the custom review fields
Open a new Customer using the configured accounting-review form. Confirm that Accounting Status starts at Pending accounting review. Accounting Approver and Accounting Approval Date are blank and disabled in this form.
02. Enter and save the customer
Enter Company Name Meadowline Services and Email billing@meadowline.example. Select Primary Subsidiary Example Supply US, confirm native Status CUSTOMER-Closed Won and complete any other required fields for your account.
Click Save. Verify Customer ID 5102 and the same company name. The custom Accounting Status remains Pending accounting review. Saving this customer has not completed the custom review.
03. Find the pending customer
Open the installed Customers pending accounting approvals search through the navigation available in your account. Find Meadowline Services. The columns shown in this installed search include Internal ID, Company Name, Date Created and Address, with Edit and View links. Search columns and access depend on the saved search and role.
The example's Internal ID is 9502; its displayed Customer ID is 5102. Check the company name as well as the relevant identifier before opening a record.
04. Review the same customer
Choose View for the matching row. Confirm Customer ID 5102 and Meadowline Services. Read Accounting Status Pending accounting review and the blank Accounting Approver and Accounting Approval Date fields. Collapse Email | Phone | Address if you need more room to inspect the review fields.
The current identity is still Jamie Reed in the Administrator role. Locate Acc Approve, the installed workflow button. It is not a native customer approval action.
05. Approve and verify the result
Click Acc Approve. On the same customer, confirm Accounting Status Accounting Approved, Accounting Approver Jamie Reed and Accounting Approval Date 10/15/2026.
Confirm that Acc Approve is gone from the resulting view and that native Status still reads CUSTOMER-Closed Won. The three custom values are the observed result. They do not establish credit approval, transaction eligibility, an immutable audit event or two-person enforcement.
Common questions
Why is a saved customer still Pending accounting review?
Saving the customer and completing this custom review are separate actions. Follow the installed review process and verify its result. A native customer lifecycle status does not substitute for the account's custom review fields.
Is Accounting Approved a native customer status?
In this example it is a value in an account-specific custom field. The separate native Status remains CUSTOMER-Closed Won after the custom review is approved.
Why is Acc Approve missing?
Button visibility depends on the installed workflow or customization, record and form context, status conditions and configured role access. This walkthrough demonstrates only the Administrator path. The button is gone after Accounting Approved; rejected-state behavior was not demonstrated. Ask the administrator to inspect the configuration rather than assume a permission denial.
Do disabled approval fields prevent changes through every route?
No. They describe this form's display behavior. Other forms, imports, integrations, scripts and permissions need independent verification.
Does this example prove two-person approval?
No. The same Administrator creates and approves the customer. The walkthrough does not test whether self-approval is blocked.
Is the approval date a full audit trail?
No. The custom date and user values are not a precise event timestamp or an immutable history. Inspect applicable System Notes and any separately configured workflow or audit history when audit evidence is required.