ctcLink Reference CenterPurchasing P-CardsSplitting and Updating Transaction Lines

Splitting and Updating Transaction Lines

Purpose: Use this document as a reference for splitting and updating transaction lines when reconciling P-Card transactions in ctcLink.

Audience: Purchasing Staff

You can split incoming transaction lines to provide greater detail in your Reconciliation actions. 

Navigation: Main Menu > Purchasing > Procurement Cards > Reconcile > Reconcile Statement

Splitting and Updating Transaction Lines

  1. Use the Procurement Card Transaction page to review, manage, and approve procurement card transactions loaded by the Load Statement process. You can view all of the procurement card transactions that you have been granted authority to access on the Cardholder Profile - Card Data: Assign Proxies page
    1. Review the P-Card transactions.
    2. Use the Selection checkbox to the left of   the line you want to split to select one of the transaction lines.
    3. Click the Split Line link at the bottom of   the page.
  1. Use the ProCard Transaction Splits page to add the splitting account details:
    1. Click the Add a new row button.
    2. Enter an appropriate   description (for both items as necessary) to identify what the new splits   represent in the Description   field.
    3. Distribute the original   amount between the BillingAmount fields.                                                                               

Note: The Percentage fields will recalculate. Billing Amount fields must total 100%.

  1. Click the OK button.

Note: There are now two line items for the same (original) Merchant and Trans Date.

  1. Click the Comment button to add a comment to the split lines.
  1. Use the ProCard Comments page to add comments:
    1. Add your comment in the Comments field.
    2. When finished, click the OK button.
  1. To complete reconciliation processing of P-Card transactions, refer to QRG Reconciling P-Card Transactions/Statements Manually.


Add your comment

E-Mail me when someone replies to this comment