Automate client financial reviews
Keep client assessments up to date, react to financial changes and send exception requests to an eligible reviewer.
Use Assignar Pay steps to keep a client's financial assessment up to date from an accounting system or a manual review. Your organization chooses its own status names and policies; the workflow selects those statuses from your catalogue. Renaming a status keeps existing selections working.
Financial controls start switched off. Creating statuses, updating assessments and publishing a workflow leave that setting alone. Steps use the permissions of the person shown under Runs as in your workspace.
Choose the step you need
Add an action and search for Assignar Pay:
| Action | Use it to |
|---|---|
| Get Client Financial Controls | Read your settings and status catalogue. |
| Get Client Financial Assessment | Read one client's assessment, within your financial access. |
| Update Client Financial Assessment | Record a manual review or an integration observation. |
| Evaluate Client Financial Action | Check the current policy for a client and commercial action. |
| Update Client Financial Status | Create or edit a status and its policies. |
| Update Client Financial Settings | Maintain the policies for unassessed or stale assessments, and control enforcement. |
| Request Client Financial Exception | Ask for an exception when the current policy permits a request. |
| Get Client Financial Exception | Read a request's status, expiry and whether it has been used. |
The commercial action and policy choices come from Assignar Pay. To change one policy, select its action and policy together; leaving both empty preserves the current policies.
Bring in an accounting observation
For example, an accounting workflow can assess a client after it receives a fresh balance from your accounting system.
- Start with the accounting system's trigger or a scheduled lookup. Match the customer to the correct Client in Assignar Pay.
- Add Update Client Financial Assessment, select the Financial status your review calls for, and enter a Reason.
- Set Assessment source to Integration. Fill in Integration name and map the source's timestamp into Source observation time. You can also keep the source record's reference in Source reference.
- Map optional Financial figures using decimal text, for example
{"exposure":"1200.50","currency":"AUD"}. Leave a figure out to keep it unchanged; usenullto clear it. - Test the step and check the client's assessment before publishing the workflow.
Use the time the source actually observed the balance. Substituting the workflow's current time for an old observation can make stale information look fresh. Assignar Pay refuses older observations and integration changes to a manually locked assessment.
The acting user needs permission to update assessments. Reading or writing money also requires See sell figures; withheld amounts remain empty, with an indication that they were hidden, rather than becoming zero.
Keep a manual decision in control
For a review made by your team, use Update Client Financial Assessment with Assessment source set to Manual. Lock manual assessment starts selected, so an accounting import cannot replace the decision. Clear it on a later manual update when you want integration updates to resume.
Use Update Client Financial Status to maintain your catalogue and Update Client Financial Settings to maintain organization policies. Financial controls starts at Keep current setting; choose Enable only when you are ready to apply the policies. See Set client financial policies for the policies and the actions they govern.
React to financial changes
Use Client Updated and choose Financial Assessment under Changed Fields. To react to manual reviews while excluding your integration's writes, select Manual under Financial Assessment Source and set the workflow's assessment updates to Integration. Leave Sources empty for financial events; that filter describes where the client was originally created.
The trigger keeps the ordinary client under record. Select Include Private Financial Assessment only when the workflow needs the additional financial information and the acting user can read it. This option starts off; financial figures keep the same visibility rules as other assessment reads.
Financial event metadata in the test sample is illustrative. The client record, and any private assessment you chose to include, are read from Assignar Pay.
Use Client Financial Configuration Changed for settings or status-policy changes. Before writing from that trigger, read the current controls and compare them with the desired values; skip the write when they already match. A configuration change can start the workflow again, including a change the workflow made itself.
Send an exception to a reviewer
Evaluate Client Financial Action checks a Client and Commercial action. It is a client-level policy check; it does not evaluate the details of a particular job. Its result tells you whether controls are inactive, the action is allowed or warned, or it requires approval or is blocked.
- Add Request Client Financial Exception for the client and action, and enter a Request reason. To limit the request to an existing job or order, map its Order ID; it must belong to that client.
- Set Expires at when you need a specific deadline. Otherwise the request expires after 24 hours.
- Continue to the approval step only when the request returns an exception. An inactive, allowed or warned action, or a policy that does not permit an exception, returns no exception.
- Add Request Approval in Assignar and map the request's
exception.idinto Financial Exception ID. Set Title and choose Approver Roles, Approver Users, or both. - Branch on the approval step's Approved and Outcome results. The workflow waits while an eligible person reviews the linked financial request.
The reviewer must be named by the request and hold the current permission to approve financial exceptions or override blocked actions. An approval request requires a different eligible person from the person who requested it. A general workflow approval without the financial link does not grant a financial exception.
Assignar Pay checks the exception again when the commercial action is attempted, including its scope, expiry, any amount cap and whether it has already been used. A later revocation or policy change can prevent the action from proceeding. Private review comments stay in Assignar Pay rather than returning in the workflow's Comment result.
Recover a failed step
A financial write times out. Retry the failed step. It keeps the original change and version, so the retry cannot silently replace a newer assessment or policy.
A write is refused because the assessment or policy changed. Read the current assessment or controls, review the difference and start a fresh run. Retrying the same failed step keeps the earlier version and will not resolve that conflict.
"The financial request or its approvers changed. Refresh the request and choose an eligible financial approver." Check the request and the nominated person's current financial permissions before raising a new request.
Assess a principal contractor privately
In Subcontractor Hub, select your principal contractor's client record in your own organization. For example, your accounts team can keep a manual assessment while an accounting workflow imports later observations after the manual lock is released. Your statuses, assessments and financial history stay within your organization.
These policies govern new commercial commitments. Workers can still check in and out, submit timesheets and record completed work, and office staff can keep reviewing those records.

