Once transactions post to PaymentNet, users can begin the review and approval process. Users assigned the Card Holder role complete reviews, and users assigned the Transaction Approver role submit approvals.
Cardholders can review transactions within their hierarchy ID and scope of view. For example, they might reconcile each transaction amount with a receipt or statement and then mark the transactions as Reviewed.
Once a transaction is reviewed, it can be routed to a transaction approver if additional approval is required. The approver ensures that the transaction meets organizational policies, verifies other details, and then marks the transaction as Approved.
If, however, the transaction does not satisfy organizational requirements, the approver can reject it. For example, the cardholder may have failed to attach receipts, allocated accounting codes incorrectly, or provided insufficient details about the transaction. When a transaction is rejected, it is sent back to the cardholder with a status of New. The cardholder must address the issues and then mark the transaction as Reviewed, which resubmits it for approval.
Program administrators can configure an approval workflow and manage the workflow rules for users who are assigned the Transaction Approver role. For more information, see Transaction Workflow Rules.