Payment to eProcurement vendors can be made by PCard or by a SAP purchase order for non-PCard vendors.
Payments via PCard
Card security measures include:
eTravel: Card details are not retained in mymarket.com for travel bookings for security reasons. This means that card details must be captured for each transaction.
eShopping: Card details need to be captured for the first PCard transaction. The card details are then managed through the secure payment gateway into the bank. The user will be offered a masked number to confirm the card details for subsequent transactions. They can also enter a new card number at that point.
For additional security, card holders will receive an SMS from the bank after each transaction.
Managing your PCard credit limits
To prevent the loss of travel bookings and payment problems with eShopping PCard vendors, the PCard holder must remain aware of the available credit balance on their cards. Contact email@example.com to check your balance.
Clearing the transaction against the fund
PCard expenses do not reflect against the fund until the transaction has been posted by the card processor. Card holders must therefore pass their supporting documents and invoices to their card processor within 7 days of transaction date or 7 days after returning from a trip. The card processor will see the transaction in SAP within 48 hours of the transaction date. This ensures quick clearing of transactions and updating of the available SAP budget.
Payments via SAP purchase order
Once the purchase is approved, and if sufficient budget is available in the fund selected, the departmental purchaser will facilitate the creation of a SAP purchase order for payment. Budget is committed against a fund when the purchase order is created on SAP.